[NCLUG] permanent IP addresses on a home LAN?

[Brian Fromme]

What I do to solve this is turn off DHCP on my cheap router and install and
configure it on a Linux "server".  Just make sure it is the only DHCP and
then configure all the MAC addresses to point to fixed addresses.  Setup the
other boxes to boot DHCP and you should have it.

I will say that you will need to study DHCP/DNS manuals to get the config
files setup right.  That took me quite a few hours.

 Brian

> -----Original Message-----
> From: nclug-bounces at nclug.org [mailto:nclug-bounces at nclug.org] On Behalf
> Of dlc at frii.com
> Sent: Wednesday, August 01, 2007 9:29 AM
> To: Northern Colorado Linux Users Group
> Subject: Re: [NCLUG] permanent IP addresses on a home LAN?
> 
>   Perhaps the quick and easy way to accomplish this is to just set your
> systems up with a fixed IP address and ignore the DHCP.  Since DHCP
> seems to assign starting with the low numbers first, what I did was put
> those machines that I wanted to keep at fixed addresses in the .200+
> range.  Things like file and print servers for instance.  Those then
> remain at those addresses (the DHCP server doesn't care) and everything
> else is assigned addresses down in the 100 range (on my DLink anyway).
> 
>   It is a hassle when you don't want to figure out how your computer sets
> this value, and would rather have something else sort it out, but if the
> alternative is to get a $1000 router or a potentially risky firmware
> replacement, then perhaps the brute-force method would be worth it.
> 
>   I'll apologize ahead if this has already been stated, I got into the
> discussion a bit late in the game...
> 
> DLC
> 
> > You could check out dd-wrt at http://dd-wrt.com  dd-wrt allows you to
> > turn a $50 SOHO wireless router into a router with a $200 router
> > featureset.  I've got a few routers that I've flashed with it, mostly
> > LinkSys routers, but I just flashed a Buffalo AirStation and am using
> > it.  It will allow you to do the exact thing you want (which I did for
> > my Wii to keep it out of DHCP namespace).  Check to see if your router
> > supports it, and if it does, I highly reccomend it.
> >
> > Paul
> >
> > S. Luke Jones wrote:
> >> I once had a 10/100Base-T switch + router that let me configure its
> >> DHCP server to assign IP addresses by MAC address. I replaced 10*BaseT
> >> with 802.3g or whatever you call WiFi and could never go back, but my
> >> wireless router doesn't let me configure the DHCP server that way.
> >>
> >> And I miss it. In particular, I miss it whenever we have a power
> >> outage and machines come back online in nondeterministic order, and
> >> get IP addresses at random, and all my .ssh/known_hosts lines become
> >> wrong, and I have to think a lot harder before I do things like rsync
> >> -av --delete . 192.168.2.101:work
> >>
> >> Could anyone recommend a way -- assuming there even is a one -- of
> >> overcoming the lack in my Wireless router and getting dynamically
> >> assigned IP addresses to be less dynamic and more static-ish?
> >>
> >> (No, it doesn't have anything to do with Linux, although one of the
> >> machines in question does run Linux.)
> >>
> >
> > _______________________________________________
> > NCLUG mailing list       NCLUG at nclug.org
> >
> > To unsubscribe, subscribe, or modify
> > your settings, go to:
> > http://www.nclug.org/mailman/listinfo/nclug
> >
> 
> 
> _______________________________________________
> NCLUG mailing list       NCLUG at nclug.org
> 
> To unsubscribe, subscribe, or modify
> your settings, go to:
> http://www.nclug.org/mailman/listinfo/nclug