 jimkPremium
join:2006-04-15
Raleigh, NC
 ·RoadRunner Cable
 ·voip.ms
| reply to cramer
Re: [TWC] Raleigh, NC TWC - which modem is best to purchase? I can confirm the DHCP behavior you have mentioned... here's what pfSense has to say for my public WAN IP, private data removed:
Jan 19 21:48:11 dhclient[6719]: DHCPREQUEST on em0 to 10.132.nnn.n port 67
Jan 19 21:51:35 dhclient[6719]: DHCPREQUEST on em0 to 10.132.nnn.n port 67
Jan 19 21:54:15 dhclient[6719]: DHCPREQUEST on em0 to 10.132.nnn.n port 67
Jan 19 21:54:32 dhclient[6719]: DHCPREQUEST on em0 to 10.132.nnn.n port 67
Jan 19 21:54:54 dhclient[6719]: DHCPREQUEST on em0 to 10.132.nnn.n port 67
Jan 19 21:55:41 dhclient[6719]: DHCPREQUEST on em0 to 10.132.nnn.n port 67
Jan 19 21:57:32 dhclient[6719]: DHCPREQUEST on em0 to 10.132.nnn.n port 67
Jan 19 21:58:24 dhclient[6719]: DHCPREQUEST on em0 to 10.132.nnn.n port 67
Jan 19 21:59:57 dhclient[6719]: DHCPREQUEST on em0 to 10.132.nnn.n port 67
Jan 19 22:01:08 dhclient[6719]: DHCPREQUEST on em0 to 10.132.nnn.n port 67
Jan 19 22:01:49 dhclient[6719]: DHCPREQUEST on em0 to 10.132.nnn.n port 67
Jan 19 22:02:23 dhclient[6719]: DHCPREQUEST on em0 to 10.132.nnn.n port 67
Jan 19 22:03:26 dhclient[6719]: DHCPREQUEST on em0 to 10.132.nnn.n port 67
Jan 19 22:04:22 dhclient[6719]: DHCPREQUEST on em0 to 10.132.nnn.n port 67
Jan 19 22:05:39 dhclient[6719]: DHCPREQUEST on em0 to 10.132.nnn.n port 67
Jan 19 22:07:19 dhclient[6719]: DHCPREQUEST on em0 to 10.132.nnn.n port 67
Jan 19 22:09:08 dhclient[6719]: DHCPREQUEST on em0 to 255.255.255.255 port 67
Jan 19 22:09:08 dhclient[6719]: DHCPACK from 10.132.nnn.n
Jan 19 22:09:08 dhclient: RENEW
Jan 19 22:09:08 dhclient: Creating resolv.conf
Jan 19 22:09:08 dhclient[6719]: bound to 24.nnn.nnn.nnn -- renewal in 20449 seconds.
The logs couldn't be clearer.
I will probably bring this up, since I'm sure the same thing is happening when the cable modem tries to renew its management IP. Maybe if more than one person complains they will listen. Then again, they can also just blame me for running an unsupported configuration.
Kind of embarrassed that I didn't catch this, but I was troubleshooting issues on the modem and not my firewall. |
