Why is my connection getting a DHCP renew every 2-3 minutes??
[ipCop firewall log]
13:17:58 dhcpcd[1242] wan-1: offered 50.0.13.254 from 76.191.253.72
13:17:58 dhcpcd[1242] wan-1: acknowledged 50.0.13.254 from 76.191.253.72
13:17:58 dhcpcd[1242] wan-1: checking for 50.0.13.254
13:18:03 dhcpcd[1242] wan-1: leased 50.0.13.254 for 300 seconds
13:18:04 dhcpcd[] wan-1 has been configured with new IP=50.0.13.254
13:20:33 dhcpcd[1242] wan-1: renewing lease of 50.0.13.254
13:20:33 dhcpcd[1242] wan-1: acknowledged 50.0.13.254 from 76.191.253.72
13:20:33 dhcpcd[1242] wan-1: leased 50.0.13.254 for 300 seconds
13:20:34 dhcpcd[] wan-1 has been configured with same IP=50.0.13.254
13:23:03 dhcpcd[1242] wan-1: renewing lease of 50.0.13.254
13:23:03 dhcpcd[1242] wan-1: acknowledged 50.0.13.254 from 76.191.253.72
13:23:03 dhcpcd[1242] wan-1: leased 50.0.13.254 for 300 seconds
13:23:04 dhcpcd[] wan-1 has been configured with same IP=50.0.13.254
13:25:33 dhcpcd[1242] wan-1: renewing lease of 50.0.13.254
13:25:33 dhcpcd[1242] wan-1: acknowledged 50.0.13.254 from 76.191.253.72
13:25:33 dhcpcd[1242] wan-1: leased 50.0.13.254 for 300 seconds
13:25:35 dhcpcd[] wan-1 has been configured with same IP=50.0.13.254
13:28:03 dhcpcd[1242] wan-1: renewing lease of 50.0.13.254
13:28:03 dhcpcd[1242] wan-1: acknowledged 50.0.13.254 from 76.191.253.72
13:28:03 dhcpcd[1242] wan-1: leased 50.0.13.254 for 300 seconds
13:28:05 dhcpcd[] wan-1 has been configured with same IP=50.0.13.254
I'd rather not be renewing every 300 seconds. Is this possible to change? I have heard of other's connections dropping from this renew and thing I might have been seeing this same experience over a long time being connected this way. And, I've noticed that I get this IP 50.0.13.254, the last in my subnet, whenever I connect with my Cisco877w->ipCop firewall, and traffic varies. Last week I was getting terrible timeouts and 10-20% packet loss (ping -t to a few diff DNS servers that are very solid) with this setup. Right now I am getting 0% packet loss on 700+ icmps on the same setup so I guess there is no problem at the moment. Maybe it happened to be a flooded pedestal or something with all the rain we were having last week. But when I reconnected with my motorola 2210, immediately the latency was down at 12ms with absolutely 0% PL immediately after had 10-20% on my other setup. It was very solid when I set it up about 4 months ago.
I always get a lower IP of 50.0.12.34 when I connect with my motorola 2210, But I want to use my ipcop firewall and Cisco 877w if at all possible.
I'm using a pure bridged configuration on my Cisco 877w. Can post this upon request. My ipCop firewall is running on quad gigabits on a riverbed steelhead 550(?) box. I thought it might be a time/date issue on my systems at first due to the constant DHCP renews but its not that. I also thought maybe I was blocking the DHCP renew on the firewall as I read a couple posts about that. But since I see these lines in the log, that tells me the DHCP renews from WAN don't seem to be dropped... I sent an email to support@sonic.net a few days ago re: 'dhcp renews every 3-5 mins' but have not received a response yet.
Any info or ideas appreciated, although now it seems my latency / packet loss problem is intermittent or has gone away. Still interested in what might have been occurring though, or why DHCP renew is set for 300 seconds!! Seems like quite a bit of unnecessary traffic and should be something like 24h at least =]
Thanks,
Alex
[ipCop firewall log]
13:17:58 dhcpcd[1242] wan-1: offered 50.0.13.254 from 76.191.253.72
13:17:58 dhcpcd[1242] wan-1: acknowledged 50.0.13.254 from 76.191.253.72
13:17:58 dhcpcd[1242] wan-1: checking for 50.0.13.254
13:18:03 dhcpcd[1242] wan-1: leased 50.0.13.254 for 300 seconds
13:18:04 dhcpcd[] wan-1 has been configured with new IP=50.0.13.254
13:20:33 dhcpcd[1242] wan-1: renewing lease of 50.0.13.254
13:20:33 dhcpcd[1242] wan-1: acknowledged 50.0.13.254 from 76.191.253.72
13:20:33 dhcpcd[1242] wan-1: leased 50.0.13.254 for 300 seconds
13:20:34 dhcpcd[] wan-1 has been configured with same IP=50.0.13.254
13:23:03 dhcpcd[1242] wan-1: renewing lease of 50.0.13.254
13:23:03 dhcpcd[1242] wan-1: acknowledged 50.0.13.254 from 76.191.253.72
13:23:03 dhcpcd[1242] wan-1: leased 50.0.13.254 for 300 seconds
13:23:04 dhcpcd[] wan-1 has been configured with same IP=50.0.13.254
13:25:33 dhcpcd[1242] wan-1: renewing lease of 50.0.13.254
13:25:33 dhcpcd[1242] wan-1: acknowledged 50.0.13.254 from 76.191.253.72
13:25:33 dhcpcd[1242] wan-1: leased 50.0.13.254 for 300 seconds
13:25:35 dhcpcd[] wan-1 has been configured with same IP=50.0.13.254
13:28:03 dhcpcd[1242] wan-1: renewing lease of 50.0.13.254
13:28:03 dhcpcd[1242] wan-1: acknowledged 50.0.13.254 from 76.191.253.72
13:28:03 dhcpcd[1242] wan-1: leased 50.0.13.254 for 300 seconds
13:28:05 dhcpcd[] wan-1 has been configured with same IP=50.0.13.254
I'd rather not be renewing every 300 seconds. Is this possible to change? I have heard of other's connections dropping from this renew and thing I might have been seeing this same experience over a long time being connected this way. And, I've noticed that I get this IP 50.0.13.254, the last in my subnet, whenever I connect with my Cisco877w->ipCop firewall, and traffic varies. Last week I was getting terrible timeouts and 10-20% packet loss (ping -t to a few diff DNS servers that are very solid) with this setup. Right now I am getting 0% packet loss on 700+ icmps on the same setup so I guess there is no problem at the moment. Maybe it happened to be a flooded pedestal or something with all the rain we were having last week. But when I reconnected with my motorola 2210, immediately the latency was down at 12ms with absolutely 0% PL immediately after had 10-20% on my other setup. It was very solid when I set it up about 4 months ago.
I always get a lower IP of 50.0.12.34 when I connect with my motorola 2210, But I want to use my ipcop firewall and Cisco 877w if at all possible.
I'm using a pure bridged configuration on my Cisco 877w. Can post this upon request. My ipCop firewall is running on quad gigabits on a riverbed steelhead 550(?) box. I thought it might be a time/date issue on my systems at first due to the constant DHCP renews but its not that. I also thought maybe I was blocking the DHCP renew on the firewall as I read a couple posts about that. But since I see these lines in the log, that tells me the DHCP renews from WAN don't seem to be dropped... I sent an email to support@sonic.net a few days ago re: 'dhcp renews every 3-5 mins' but have not received a response yet.
Any info or ideas appreciated, although now it seems my latency / packet loss problem is intermittent or has gone away. Still interested in what might have been occurring though, or why DHCP renew is set for 300 seconds!! Seems like quite a bit of unnecessary traffic and should be something like 24h at least =]
Thanks,
Alex