Randy Schultz wrote:
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.
You can configure a static IP on the WAN. In fact you have to configure
the IP on the WAN in this case, because that's the interface where your
default gateway resides.
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.
Just add appropriate firewall rules to let you in on the WAN IP.
I tried re-installing from scratch. Since there is no way AFAIK to set a
static on the WAN that early,
Oh, I see what you're saying. You'll need to get the LAN interface up to
do the initial configuration of the WAN interface, static IP, gateway,
and rules.
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?
You have to do the initial configuration connected directly to the LAN
subnet, there is no supported way around that.
You just have to get into the web interface, assign the WAN IP and
gateway info, configure the firewall rules, and then you can finish the
configuration from where ever you want.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
