DHCP initial request on WAN fine, subsequent renewals on WAN result in disconnec
-
We use pfSense in bridge mode with our VSDL modem.
Our ISP uses DHCP and when connected, we are assigned an IP address.
After 4 hours, we are disconnected because we apparently not renewing our request to keep the IP address.
I see a lot of these in the logs:
Sep 2 03:34:21dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:34:50dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:36:10dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:36:21dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:36:38dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:37:15dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:37:53dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:39:33dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:41:01dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:41:56dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:42:14dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:42:40dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:43:10dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:43:36dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:44:05dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:44:16dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:44:42dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:44:56dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:45:24dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:45:46dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:45:55dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:46:03dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:46:17dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:46:37dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:47:12dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:47:29dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:48:10dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:49:09dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:50:55dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:51:16dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:51:27dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:51:38dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:51:45dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:51:54dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:52:09dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:52:28dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:52:37dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:53:05dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:54:05dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:55:54dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:56:59dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:58:42dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:58:59dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:59:06dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:59:17dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67
Sep 2 03:59:25dhclient1874DHCPREQUEST on xn1 to 150.XXX.XX.XX port 67But the reconnect never happens, unless we a re-save the connection.
I've allowed * to * for UDP 67 and 68 on the WAN, but this hasn't made a difference.
-
Found the powerline was issuing its own MAC address on the WAN network and ISP was picking it up, so had to tell pfSense to emulate that. Seems to have stopped drop outs.