UDP 67 ISP DHCP ack/request, losing connectivity.



  • I had to exchange my modem about week and half ago since the old one bit the dust.

    This new one is giving me problems.

    Symptoms:
    Connection dropping every 6 hours or close to it. If you power cycle the modem, it will drop the connection again in 15 minutes, after that it's ok for 6 hours. it doesn't lose signal, or cable synchronization . I'm convince that pfsense is blocking somethingcritcal for dhcp renewal.

    In system logs:

    1:30ish am connection went down.
    bound to xx.xxx.xxx.xxx is my ip.

    
    Aug 22 01:36:57 	dhclient[19928]: bound to xx.xxx.xxx.xxx -- renewal in 10662 seconds.
    Aug 22 01:36:57 	dhclient[19928]: DHCPACK from 10.50.80.1
    Aug 22 01:36:57 	dhclient[19928]: DHCPREQUEST on xl0 to 255.255.255.255 port 67
    Aug 22 01:36:57 	kernel: xl0: link state changed to UP
    Aug 22 01:36:45 	dhclient[55419]: exiting.
    Aug 22 01:36:45 	dhclient[55419]: exiting.
    Aug 22 01:36:45 	dhclient[55419]: connection closed
    Aug 22 01:36:45 	dhclient[55419]: connection closed
    Aug 22 01:36:45 	kernel: xl0: link state changed to DOWN
    Aug 22 01:36:42 	php: : HOTPLUG: Configuring wan interface xl0
    Aug 22 01:36:42 	php: : DEVD Ethernet attached event for xl0
    Aug 22 01:36:42 	php: : Processing xl0 - start
    Aug 22 01:36:41 	check_reload_status: rc.linkup starting
    Aug 22 01:36:41 	kernel: xl0: link state changed to UP
    Aug 22 01:35:25 	kernel: xl0: link state changed to DOWN
    
    

    9ish conneciton went down.
    did the same thing above except around 8 it spam
    DHCPREQUEST on xl0 to 10.50.80.1
    repeats for 2 minutes before down link.

    
    Aug 21 21:18:54 	dnsmasq[61603]: exiting on receipt of SIGTERM
    Aug 21 21:18:52 	dhclient[54716]: bound to 192.168.100.10 -- renewal in 30 seconds.
    Aug 21 21:18:52 	dhclient[54716]: DHCPACK from 192.168.100.1
    Aug 21 21:18:52 	dhclient[54716]: DHCPREQUEST on xl0 to 255.255.255.255 port 67
    Aug 21 21:18:51 	dhclient[54716]: DHCPREQUEST on xl0 to 255.255.255.255 port 67
    Aug 21 21:18:49 	dhclient[54716]: DHCPOFFER from 192.168.100.1
    Aug 21 21:18:49 	dhclient[54716]: DHCPDISCOVER on xl0 to 255.255.255.255 port 67 interval 1
    Aug 21 21:18:49 	dhclient[54716]: DHCPNAK from 192.168.100.1
    Aug 21 21:18:49 	last message repeated 2 times
    Aug 21 21:18:47 	dhclient[54716]: DHCPREQUEST on xl0 to 255.255.255.255 port 67
    Aug 21 21:18:46 	dhclient[61485]: exiting.
    Aug 21 21:18:46 	dhclient[61485]: exiting.
    Aug 21 21:18:46 	dhclient[61485]: connection closed
    Aug 21 21:18:46 	dhclient[61485]: connection closed
    Aug 21 21:18:43 	php: : HOTPLUG: Configuring wan interface xl0
    Aug 21 21:18:43 	php: : DEVD Ethernet attached event for xl0
    Aug 21 21:18:43 	php: : Processing xl0 - start
    Aug 21 21:18:42 	check_reload_status: rc.linkup starting
    Aug 21 21:18:41 	kernel: xl0: link state changed to UP
    Aug 21 21:18:35 	kernel: xl0: link state changed to DOWN
    Aug 21 20:56:47 	dhclient[61562]: SENDING DIRECT
    Aug 21 20:56:47 	dhclient[61562]: DHCPREQUEST on xl0 to 10.50.80.1 port 67
    Aug 21 20:43:29 	dhclient[61562]: SENDING DIRECT
    Aug 21 20:43:29 	dhclient[61562]: DHCPREQUEST on xl0 to 10.50.80.1 port 67
    Aug 21 20:35:09 	dhclient[61562]: SENDING DIRECT
    Aug 21 20:35:09 	dhclient[61562]: DHCPREQUEST on xl0 to 10.50.80.1 port 67
    Aug 21 20:31:09 	dhclient[61562]: SENDING DIRECT
    Aug 21 20:31:09 	dhclient[61562]: DHCPREQUEST on xl0 to 10.50.80.1 port 67
    Aug 21 20:28:17 	dhclient[61562]: SENDING DIRECT
    Aug 21 20:28:17 	dhclient[61562]: DHCPREQUEST on xl0 to 10.50.80.1 port 67
    Aug 21 20:26:31 	dhclient[61562]: SENDING DIRECT
    Aug 21 20:26:31 	dhclient[61562]: DHCPREQUEST on xl0 to 10.50.80.1 port 67
    Aug 21 20:25:25 	dhclient[61562]: SENDING DIRECT
    Aug 21 20:25:25 	dhclient[61562]: DHCPREQUEST on xl0 to 10.50.80.1 port 67
    
    

    In firewall:

    
    Aug 22 03:44:52  WAN  10.50.80.1:67  255.255.255.255:68  UDP
    Aug 22 03:44:33 WAN 10.50.80.1:67 255.255.255.255:68 UDP
    Aug 22 03:44:33 WAN 10.50.80.1:67 255.255.255.255:68 UDP
    Aug 22 03:44:07 WAN 10.50.80.1:67 255.255.255.255:68 UDP
    Aug 22 03:42:07 WAN 10.50.80.1:67 255.255.255.255:68 UDP
    Aug 22 03:41:47 WAN 10.50.80.1:67 255.255.255.255:68 UDP
    Aug 22 03:41:43 WAN 10.50.80.1:67 255.255.255.255:68 UDP
    Aug 22 03:41:43 WAN 10.50.80.1:67 255.255.255.255:68 UDP
    Aug 22 03:41:42 WAN 10.50.80.1:67 255.255.255.255:68 UDP
    Aug 22 03:41:42 WAN 10.50.80.1:67 255.255.255.255:68 UDP
    Aug 22 03:40:59 WAN 10.50.80.1:67 255.255.255.255:68 UDP
    Aug 22 03:40:36 WAN 10.50.80.1:67 255.255.255.255:68 UDP
    Aug 22 03:39:47 WAN 10.50.80.1:67 255.255.255.255:68 UDP
    Aug 22 03:36:13 LAN 192.168.1.1:1024 239.255.255.250:1900 UDP
    Aug 22 03:36:13 BRIDGE0 192.168.1.1:1024 239.255.255.250:1900 UDP
    Aug 22 03:36:13 LAN 192.168.1.1:1024 239.255.255.250:1900 UDP
    Aug 22 03:36:13 LAN 192.168.1.1:1024 239.255.255.250:1900 UDP
    Aug 22 03:36:13 BRIDGE0 192.168.1.1:1024 239.255.255.250:1900 UDP
    Aug 22 03:36:13 LAN 192.168.1.1:1024 239.255.255.250:1900 UDP
    Aug 22 03:36:13 LAN 192.168.1.1:1024 239.255.255.250:1900 UDP
    Aug 22 03:36:13 BRIDGE0 192.168.1.1:1024 239.255.255.250:1900 UDP
    Aug 22 03:36:13 LAN 192.168.1.1:1024 239.255.255.250:1900 UDP
    Aug 22 03:36:13 LAN 192.168.1.1:1024 239.255.255.250:1900 UDP
    Aug 22 03:36:13 BRIDGE0 192.168.1.1:1024 239.255.255.250:1900 UDP
    Aug 22 03:36:13 LAN 192.168.1.1:1024 239.255.255.250:1900 UDP
    Aug 22 03:36:13 LAN 192.168.1.1:1024 239.255.255.250:1900 UDP
    Aug 22 03:36:13 BRIDGE0 192.168.1.1:1024 239.255.255.250:1900 UDP
    Aug 22 03:36:13 LAN 192.168.1.1:1024 239.255.255.250:1900 UDP
    Aug 22 03:36:13 LAN 192.168.1.1:1024 239.255.255.250:1900 UDP
    Aug 22 03:36:13 BRIDGE0 192.168.1.1:1024 239.255.255.250:1900 UDP
    Aug 22 03:36:13 LAN 192.168.1.1:1024 239.255.255.250:1900 UDP
    Aug 22 03:36:13 LAN 192.168.1.1:1024 239.255.255.250:1900 UDP
    Aug 22 03:36:13 BRIDGE0 192.168.1.1:1024 239.255.255.250:1900 UDP
    Aug 22 03:36:13 LAN 192.168.1.1:1024 239.255.2
    
    

    I have no idea what lan/bridge0 is. if anybody can tell me.
    But if you look at the top you see 10.50.80.1 trying to reach it destination 255.255.255.255
    It just floods my logs.

    I don't have second router, pfsense connects directly to modem.
    It's Scientific-Atlantic WebSTAR DPC2100R2 but in interfaces of pfsense I get a real ip, not a private space address.

    Looks like pfsense is trying to renew the ip when the lease time is up. I always have the same ip after power-cycling the modem.

    10.50.80.1 which is the first hop after pfsense in tracert to google. I assume that 10.50.80.1 is the wan node gateway?

    Question is how can I resolve it or can I just set wan to static instead of dhcp?

    Any help is appreciated, and don't give me the run around, please.



  • Looks like a problem with your ISP or modem, particularly as you say the only thing you changed was the modem.  What you describe perfectly matches what I'd expect with a broken DHCP server.



  • Forgot to mention in the firewall part they are all being block. In wan setup I have "Block private networks" checked.

    Are you sure? I can go tomorrow and swap modems again, perhaps I'll ask for another toshiba which is what I had before and never had a problem with pfsense.

    I guess my modem could be bad, the send light on it doesn't work, only receive.



  • Is the pfSense WAN IP 10.50.80.1?  If not what are the first 2 numbers (eg 10.50.x.x)?



  • 70.119.XXX.XXX

    small cut from tracert to google.com.

    
    1    <1 ms    <1 ms    <1 ms  router.local [192.168.0.1]
    2    23 ms    26 ms    22 ms  10.50.80.1
    3    54 ms    49 ms    58 ms  ten0-3-orld06-ser1.noc.bhn.net [72.31.XXX.XX]
    
    


  • Try disabling the option to block "bogon" networks, see if that helps.



  • All right I'll give it shot see what happens.

    Thank you Cry.



  • So after playing with it a little more, I did a modem swap and last few days it's been working smoothly, got Motorola Surfboard 5101 instead of another webstar.

    Thanks Cry.


Log in to reply