Re: WAP54G firmware upgrade goes awry

John Navas <spamfilter0@xxxxxxxxxxxxxx> hath wroth:

Access points (unlike routers) don't query DHCP servers because they
don't care about IP addresses. They are simply bridges that just pass
data link layer traffic back and forth, including DHCP traffic from
clients talking to DHCP servers on the other side of the bridge. The
management interface address of the access point is set manually, not by
DHCP.

I beg to differ. Although the default setting is usually a static IP
address, most access points allow the IP address to be set via DHCP.

For example:

DLink DWL-2100AP:
http://support.dlink.com/emulators/dwl2100ap/html/CfgIpSetup.html

DLink DWL-7100AP:
http://support.dlink.com/emulators/dwl7100ap/html/CfgIpSetup.html

Dlink DWL-900AP+:
http://support.dlink.com/emulators/dwl900ap+_revC/h_lan.html

Sorry, no Linksys examples until www.linksysdata.com/ui/ comes back.
My foggy memory seems to vaguely recall that these also support IP
address setting via DHCP.

The problem is what to do about the gateway IP address. Note that the
default value for the gateway on the above examples is blank or
0.0.0.0 which means no default gateway. That makes sense as you would
not want your return packets going off to the internet when they
should be going to whatever IP is originating the packets. The only
time one needs a real gateway IP is when the access point needs to get
or send something to or from the internet. That can be time sync,
update checks, logging output, and possibly DNS lookups. Otherwise,
no gateway is required or desired.

Another uncommon problem is what to do if the gateway IP address
happens to be outside of the netmask IP address range. This can
happen if the LAN is divided into subnets. All current desktop OS's
support this, but it seems to be lacking in commodity routers and
access points. It's not a big problem but should be consdered for
complex network topologies. (The easy solution is to alias the
internet gateway router with a LAN gateway IP in each sub-net).

--
Jeff Liebermann jeffl@xxxxxxxxxxxxxxxxxxxxxx
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558
.

Relevant Pages

  • Re: Home Network Configuarion
    ... ISA should do the proxy stuff so all users will be able to go to the ... internet. ... > So how about default gateway for internal NIC, ... >> set the router to pass dhcp addresses from the ISA dhcp server, ...
    (microsoft.public.win2000.networking)
  • Re: Home Network Configuarion
    ... ISA should do the proxy stuff so all users will be able to go to the ... internet. ... > So how about default gateway for internal NIC, ... >> set the router to pass dhcp addresses from the ISA dhcp server, ...
    (microsoft.public.windows.server.networking)
  • Re: Home Network Configuarion
    ... ISA should do the proxy stuff so all users will be able to go to the ... internet. ... > So how about default gateway for internal NIC, ... >> set the router to pass dhcp addresses from the ISA dhcp server, ...
    (microsoft.public.isa.vpn)
  • Re: Unable to Ping Network from Outside
    ... Those clients should not have the router gateway in their gateway settings; ... Check DHCP, Scope options and make sure that 003, 006 and 044 are pointing ... >>Post the ipconfig/all from the server. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD-DNS-DHCP
    ... If I do NOT remove the gateway configurationfrom my DHCP ... scope but add the following to my logon script, ... Internet Connection #1 ...
    (microsoft.public.windows.server.active_directory)