Re: Problem with 2.1.2 install
What exactly do you mean by ALIAS? When I go through the initial install
(the bootable Linux portion) it only asks me for an IP and Mask... when I go
through the web interface part, the only thing it asks me for when
configuring the GREEN interface is an IP, Mask, Hostname, and Domain... If I
try to erase the Host or Domain, it makes me put them in... obviously, the
IP and Mask have to be put in... I tried changing to a different IP here,
but it makes no difference... it just stops responding.... Where is this
ALIAS thing? Got a screenshot?
> I had the same problem, made the backup in 2.1 and applied it in 2.1.2...
> and never could access the EFW from the computer on the green network
> So I decided to install 2.1.2 from scratch and typed in all the
> configuration....everything went fine up to the point were I configured
> the ALIAS for the green network. After this alias was configured, no more
> access to the firewall was possible... if I reboot the firewall from the
> console, it comes back up in the same state.
> So I guess you try again without the ALIAS for the green network, because
> like this it works for me. Alias for blue and orange can be defined
> without any problems.
> I never installed 2.1.1, or did the in-place upgrade procedure, because
> our EFW is in production and I can't do any more testing...at the moment I
> have to live without green ALIAS...
> Hope this helps!
> oldirtdog wrote:
>> Ok, guys... here's one for you...
>> I was having trouble with the 2.1.1 install that I had in place... I
>> noticed that the 2.1.2 iso was released on Endian's website, so I decided
>> to go ahead and do the upgrade.... There wasn't much that I was making
>> use of... Clam, Snort, etc... just some stuff to mess around with....
>> Now, when I went to do the install, everything went fine up to the point
>> that it made me reboot... I could login to the firewall from another PC
>> in the house and go through the initial setup like normal.... all was
>> well up to this point... once it applies the configuration, it never
>> reboots or comes back up like normal... if I reboot the firewall from the
>> console, it comes back up in the same state... it never lets me login to
>> it again (unless I restore factory defaults) nor ping it.... The only odd
>> thing that I noticed was the system somehow found the original IP address
>> I had assigned to the GREEN interface during the initial install
>> screens.... EVEN after I ran a full wipe of the hard drive, it STILL
>> found the original IP address... What the heck is going on here?
>> I am going to install 2.1.1 again tonight and see if it likes it
>> better... I never had a problem with the install of 2.1.1 but I thought
>> it would be nice to be current again.... I am going to try to do the
>> in-place upgrade procedure mentioned on this forum tonight, as well... I
>> will let you know what happens...
>> What could be going on during that period where I tell it to "Ok, apply
>> configuration!" ????
View this message in context: http://www.nabble.com/Problem-with-2.1.2-install-tf4178837.html#a11981949
Sent from the efw-user mailing list archive at Nabble.com.
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/