|
||||||||
Yes, according to the logs there is DHCP renew every 45-55 seconds: Jan 15 02:28:33 dhclient: bound to 86.140.103.121 -- renewal in 55 seconds. Jan 15 02:29:28 dhclient: DHCPREQUEST on sis1 to 192.168.254.254 port 67 Jan 15 02:29:28 dhclient: DHCPACK from 192.168.254.254 Jan 15 02:29:28 dhclient: New Network Number: 86.140.103.0 Jan 15 02:29:28 dhclient: New Broadcast Address: 255.255.255.255 Jan 15 02:29:29 dhclient: bound to 86.140.103.121 -- renewal in 46 seconds. Jan 15 02:30:15 dhclient: DHCPREQUEST on sis1 to 192.168.254.254 port 67 Jan 15 02:30:15 dhclient: DHCPACK from 192.168.254.254 Jan 15 02:30:15 dhclient: New Network Number: 86.140.103.0 Jan 15 02:30:15 dhclient: New Broadcast Address: 255.255.255.255 Jan 15 02:30:16 dhclient: bound to 86.140.103.121 -- renewal in 54 seconds. Jan 15 02:31:10 dhclient: DHCPREQUEST on sis1 to 192.168.254.254 port 67 Jan 15 02:31:10 dhclient: DHCPACK from 192.168.254.254 Jan 15 02:31:10 dhclient: New Network Number: 86.140.103.0 Jan 15 02:31:10 dhclient: New Broadcast Address: 255.255.255.255 Jan 15 02:31:11 dhclient: bound to 86.140.103.121 -- renewal in 48 seconds. Jan 15 02:31:59 dhclient: DHCPREQUEST on sis1 to 192.168.254.254 port 67 Jan 15 02:31:59 dhclient: DHCPACK from 192.168.254.254 Jan 15 02:31:59 dhclient: New Network Number: 86.140.103.0 Jan 15 02:31:59 dhclient: New Broadcast Address: 255.255.255.255 Jan 15 02:32:00 dhclient: bound to 86.140.103.121 -- renewal in 54 seconds. Jan 15 02:32:54 dhclient: DHCPREQUEST on sis1 to 192.168.254.254 port 67 Jan 15 02:32:54 dhclient: DHCPACK from 192.168.254.254 Jan 15 02:32:54 dhclient: New Network Number: 86.140.103.0 Jan 15 02:32:54 dhclient: New Broadcast Address: 255.255.255.255 Jan 15 02:32:55 dhclient: bound to 86.140.103.121 -- renewal in 55 seconds. Jan 15 02:33:50 dhclient: DHCPREQUEST on sis1 to 192.168.254.254 port 67 Jan 15 02:33:50 dhclient: DHCPACK from 192.168.254.254 Jan 15 02:33:50 dhclient: New Network Number: 86.140.103.0 Jan 15 02:33:50 dhclient: New Broadcast Address: 255.255.255.255 Jan 15 02:33:51 dhclient: bound to 86.140.103.121 -- renewal in 52 seconds. Gilad ----- Original Message ----- From: "Chris Bagnall" <m0n0wall at minotaur dot cc> To: "'Dan Bond'" <dan dot bond at gmail dot com>; <m0n0wall at lists dot m0n0 dot ch> Sent: Sunday, January 15, 2006 1:41 AM Subject: RE: [m0n0wall] Route Modified Image updated to 1.2.1 (for anyone using a Dlink 300T or X-modem) >> > seems like every 45-50 seconds there is jump - the cpu utilization >> > goes up to 95-80 percent, and immediately going back down to 8-5 >> > percent. > > As you probably know the X-Modem has a DHCP lease time of 60 seconds. > Don't > know if m0n0 constantly renewing the DHCP lease on the WAN interface might > account for this? > > I'll be updating a client's m0n0wall to the updated image some time over > the > coming week, so I'll keep an eye out for this behaviour. > > Regards, > > Chris > -- > C.M. Bagnall, Director, Minotaur I.T. Limited > This email is made from 100% recycled electrons > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch > For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch > |