Re: dhclient losing it's ip after time...

2002-02-27 Thread Osamu Aoki
; To: > Sent: Wednesday, February 27, 2002 12:10 PM > Subject: Re: dhclient losing it's ip after time... > > > > On Wed, Feb 27, 2002 at 01:16:58AM -0500, D. Clarke wrote: > > | Hi, > > | > > | I have a problem with dhclient losing it's ip after a whil

Re: dhclient losing it's ip after time...

2002-02-27 Thread dman
On Wed, Feb 27, 2002 at 01:02:53PM -0500, D. Clarke wrote: | That's right, I don't get a DHCPACK when ipmasq is started. | | I just get | | DHCPREQUEST on eth1 to 24.226.1.41 port 67 | over and over again, until i drop the masq, then i get an ACK no problem. Either open up port 67 (UDP, I think,

Re: dhclient losing it's ip after time...

2002-02-27 Thread D. Clarke
sday, February 27, 2002 12:10 PM Subject: Re: dhclient losing it's ip after time... > On Wed, Feb 27, 2002 at 01:16:58AM -0500, D. Clarke wrote: > | Hi, > | > | I have a problem with dhclient losing it's ip after a while. > > Look in your syslog to see what dh-client

Re: dhclient losing it's ip after time...

2002-02-27 Thread dman
On Wed, Feb 27, 2002 at 01:16:58AM -0500, D. Clarke wrote: | Hi, | | I have a problem with dhclient losing it's ip after a while. Look in your syslog to see what dh-client is trying to do. You should see entries similar to : Feb 27 06:45:53 dman dhclient-2.2.x: DHCPREQUEST on eth1 to 64.213.112

Re: dhclient losing it's ip after time...

2002-02-27 Thread Osamu Aoki
On Wed, Feb 27, 2002 at 01:16:58AM -0500, D. Clarke wrote: Hi, > Hi, > > I have a problem with dhclient losing it's ip after a while. > > I have ipmasq setup and i think it's the culpret but I'm not sure of what > rule (and where) to add to allow dhcp to work properly on the external > (cable) in

dhclient losing it's ip after time...

2002-02-27 Thread D. Clarke
Hi, I have a problem with dhclient losing it's ip after a while. I have ipmasq setup and i think it's the culpret but I'm not sure of what rule (and where) to add to allow dhcp to work properly on the external (cable) interface. The only way I can get dhclient to fix itself is to stop ipmasq, if