Re: Static IPs and WRT54gs?
- From: Robert Coe <bob@xxxxxxxx>
- Date: Sat, 01 Jul 2006 10:18:15 -0400
On 29 Jun 2006 21:21:14 -0700, "Justin" <Acurajustin1978@xxxxxxxxxxx> wrote:
:
: Bill Kearney wrote:
: > > Thats my question... is it possible to use static IPs on a WRT54gs?
: > > On both wired and wireless clients.
: >
: > Sure, it's possible. You'd just have to track the addresses manually.
: >
: > Using DHCP, however, is often quite worthwhile. Should there ever become a
: > need to renumber the subnet it's a pain in the ass to do manually. You have
: > to touch each and every workstation. Use DHCP and it's often no more
: > complicated than just rebooting them or using 'ipconfig /renew' on windows
: > boxes.
: >
: > Why do you ask? What're you trying to accomplish?
:
: I have printers and such on the network, I can't have their IP addies
: changine all the time.
If you're using Windows 2000 or XP Pro, you can define symbolic port names for
your network printers and use those names in the printers' definitions. Then
you don't care if their IP addresses change.
: I don't need DHCP simply because this is going to be a small network at
: my parent's house. A printer, two laptops and a desktop. I don't see
: the point of DHCP unless there's a shitload of machines and it would
: take an admin forever to goto each one - not to mention when the
: network configurtion changes.
What I normally do is pretend that everything on my network is going to use
DHCP. Then if I have a device that can't do it for some reason, I give it a
static address and insert a reservation for it on the DHCP server. (Very few
DHCP servers won't allow you to do that.) That helps me keep track of where
everything is.
You're right, of course, that you don't actually need DHCP on your home
network. But some of us who manage large networks in real life find the habit
hard to break. My home network has three computers, two printers, and a
wireless access point. But I do run a DHCP server - on my Windows Server 2003
domain controller. ;^)
Now the WRT54G is a bit of a special case. If you're using it as a router, it
can be a DHCP client on its WAN side and a DHCP server on its LAN side. (And
it's fairly straightforward to set the latter to accommodate both static and
dynamic clients.) But if you're using it in "access point" mode, in which case
it's connected to the network by one of its LAN-side ports, it can't use DHCP
and must be given a static address. I believe that some wireless routers can
be DHCP clients on their LAN side, but the WRT54G isn't one of them. (FWIW,
the comparably priced Belkin router wasn't either, the last time I looked.)
: I tried DHCP with the current router - a BEFSR41, and the printer
: jumped aroound. I don't know why. SO I went static.
: Also, sometimes I have to forware ports to get IRC file transfers
: working and junk like that.
.
- Follow-Ups:
- Re: Static IPs and WRT54gs?
- From: Justin
- Re: Static IPs and WRT54gs?
- From: John Navas
- Re: Static IPs and WRT54gs?
- From: Bill Kearney
- Re: Static IPs and WRT54gs?
- Prev by Date: Re: Questions re WEP encryption
- Next by Date: Re: Vendor Radio Specs Untrustworthy
- Previous by thread: Re: Intel Pro Wireless 3945 ABG no probs connecting, but dead line
- Next by thread: Re: Static IPs and WRT54gs?
- Index(es):
Relevant Pages
|
