Sunday ...

[ysengrin]

What we did today -- for the last seven hours or so -- was reconfiguring the house network from DHCP to static IP. Most of that time was spent getting just one server changed over; all the rest went very smoothly.

A bit more of a pain when guests want to use the network to connect to the internet, but it'll resolve some of the issues we were having.

Comments

[xsg.livejournal.com]

Did you consider using static IP addresses assigned via DHCP, determined on the MAC address? All the systems on my network get their own IP address but they're all set to get a DHCP address. Whenever they try to get a lease, the DHCP server checks their MAC and assigns them the right address...

[ysengrin.livejournal.com]

Before the switch our DHCP server was a lower-end consumer router. No way to access the configuration, much less add a MAC-anchored static address. Yeah, that would have been easiest :)

After some discussion we decided not to run a DHCP server on one of the Linux boxes in addition to it's other duties. Maybe later. We *were* looking for quick, which it would have been except for the legacy Linux server that was being persnickety.

[ysengrin.livejournal.com]

... part of those hours were spent upgrading the one box from Gutsy, too.

[thakur.livejournal.com]

I just use a freeBSD firewall/NAT box for the net gateway and manually assigned 192.168 style addresses on the internal network ,nice and simple and works fine. When a visitor wants to connect, he can just pick an unused address.

[ysengrin.livejournal.com]

We talked about putting a DHCP server on one of the Linux boxes, but decided it would be more work (possibly, nay probably wrong given following events).

The original DHCP server was built into a low-end consumer router with no way to access the configuration beyond turning it on or off.