On Mon, 31 Mar 2008, Chris Buechler spaketh thusly: -}Randy Schultz wrote: -}> Hey there, -}> -}> This is just a report of a minor problem I've noticed. It's easy to work -}> around so this is more of a FWIW. -}> -}> I am currently toying with 1.2-RELEASE built on Sun Feb 24 17:04:58 EST -}> 2008. -}> We have a bit of a non-standard setup here where the default route on the -}> particular net our lab is on is .4. On install I noticed there was no -}> default -}> route set. I have to drop to command line and set a default route whenever -}> I -}> install. W/o this I of course cannot access the web page. I also have to -}> set -}> the default route on any reboot. If I hard-code the default route for the -}> interface in the config.xml, the default route will survive a reboot. -} -}The system's default route is the gateway of the WAN interface. You have to -}configure the WAN as the interface facing the default gateway. Numerous things -}done in the GUI cause routing to be re-configured in the back end, but under -}no circumstances should that ever drop your WAN's gateway, nor have I heard of -}that happening. It sounds like you're trying to use a default gateway on an -}interface other than WAN?
Ah. Now I remember why I used the LAN i'face instead of the WAN i'face - because the WAN is DHCP only whereas with the LAN I can set the static address. None of the nets involved have a DHCP server running on them. Also, (a lesser reason is) the LAN has the auto anti-lockout rule for the webUI. I tried re-installing from scratch. Since there is no way AFAIK to set a static on the WAN that early, I editted the /cf/conf/config.xml and set up a static that way, followed by a reboot. The proper address was set but the default route was not(I couldn't remember the syntax needed in the xml file). I dropped to the command line and added the default route which allowed things out but of course I cannot get to the webUI yet because the WAN has the default block. Which brings us full-circle. It seems to me that the webUI really needs to be contacted on the LAN i'face at least for initial configuration, however the route for it goes away whenever something is done on the interfaces tab. I could be doing something improper but do not know what it is or where to examine what I'm doing. Thoughts? -- Randy ([EMAIL PROTECTED]) 765.983.1283 <*> Love with your heart, think with your head; not the other way around. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
