--- Brian Phillips <[EMAIL PROTECTED]> wrote:
> Personally, I would assign it an address in the upper ranges
> of your private subnet, rather than 192.168.1.2 like that guy
> was suggested, but I think it's a matter of personal preference
> and has little effect on scalability. I can see one bad thing
> happening though... Your wireless router goes dead for some
> reason (wife/roommate unplugs it...what have you) then you
> log onto the network with a wired client and it grabs up the
> 192.168.1.2 address. You realize that your access point is
> down and turn it back on. You then have a conflict. I would
> go with 192.168.1.254 in this case ;)
That problem will only occur if two conditions exist:
1 - The address you assigned to the wireless router is in the
range that your DHCP server is serving, and
2 - All of the other addresses have been taken.
To avoid the problem, I use this setting on my DHCP server:
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.20 192.168.0.200;
}
and then assign the wireless access point (mine's not a router)
a fixed address at 192.168.0.254, outside the DHCP range. I
have a few other things that also get static IP addresses either
below 20 or above 200.
--------------------
BYU Unix Users Group
http://uug.byu.edu/
The opinions expressed in this message are the responsibility of their
author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG.
___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
