[ previous ] [ next ] [ threads ]
 
 From:  Bart Smit <bit at pipe dot nl>
 To:  Falcor <falcor at netassassin dot com>
 Cc:  m0n0wall dash dev at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall-dev] DHCP pitfall
 Date:  Thu, 21 Jun 2007 19:34:41 +0200
On 2007-06-21, at 17:20, Falcor wrote:
> Why would you change the interface IP and then leave the DHCP  
> issuing addresses for some other subnet?

Exactly! You don't want that. If you change the IP address of an  
interface, DHCP should become disabled for that particular interface  
only. DHCP on the other interfaces should continue to function normally.

In my case I used to have a small test network on one interface, but  
I later needed to use the interface for other purposes, so I had to  
change its IP address. However, I had forgotten about DHCP running on  
the interface. Immediately after changing the IP address, everything  
seemed fine, but after lunch, a trickle of complaints about network  
connectivity started to come in from people on *another* interface as  
leases began to expire.

> Perhaps if you updated that too, then say restarted the system?

Of course, once you know this can happen, you can avoid it. No need  
to restart the system.

B