Problems reestablishing the connection
-
The log does not show that it connects. It doesn't automatically...
But I mean I can reboot pfSense in order to get the connection back or I can do a release and renew on the WAN interface (status --> interfaces -> WAN). -
So it spends 1m broadcasting for DHCP servers and gets no replies and then uses the old address and gateway?
Probably time for a packet capture to see what's actually being sent and recieved.
-
The strange thing is that the old ip and gateway are correct.
They are dynamic but do not change (or maybe once in 5 years).
So for some strange reason the connection stays down... -
I can confirm it's not a problem with DHCP.
I removed the DHCP (WAN) Gateway and created a static one.
When I pull the power cord on the modem and let it come back up after a few minutes the connection is not reestablished and I have to reboot pfSense in order to get connectivity. -
Mmm, packet capture time.
Does removing the WAN cable and reconnecting it also bring back the connection?
Steve
-
Will try the cable tomorrow.
Where to start with the capture?
Can you put me in the right direction? -
this is happening on every pfsense device I own since changing ISP this now makes sense
Following this thread for possible resolution
-
Capture on WAN when it's down. See if you see any packets coming in at all.
-
just went down again. packetcapture.cap [0_1582154630708_packet capture.docx](Uploading 100%)
i went to status > interface. release and renewed and was backonline instantly
Feb 19 18:21:53 dhcpd DHCPREQUEST for 192.168.1.240 from 18:e8:29:46:fb:3f via igb1
Feb 19 18:21:53 dhcpd DHCPACK on 192.168.1.240 to 18:e8:29:46:fb:3f via igb1
Feb 19 18:21:59 dhclient Internet Systems Consortium DHCP Client 4.3.6-P1
Feb 19 18:21:59 dhclient Copyright 2004-2018 Internet Systems Consortium.
Feb 19 18:21:59 dhclient All rights reserved.
Feb 19 18:21:59 dhclient For info, please visit https://www.isc.org/software/dhcp/
Feb 19 18:21:59 dhclient Listening on BPF/igb0/00:08:a2:09:e9:be
Feb 19 18:21:59 dhclient Sending on BPF/igb0/00:08:a2:09:e9:be
Feb 19 18:21:59 dhclient Can't attach interface {} to bpf device /dev/bpf0: Device not configured
Feb 19 18:21:59 dhclient If you think you have received this message due to a bug rather
Feb 19 18:21:59 dhclient than a configuration issue please read the section on submitting
Feb 19 18:21:59 dhclient bugs on either our web page at www.isc.org or in the README file
Feb 19 18:21:59 dhclient before submitting a bug. These pages explain the proper
Feb 19 18:21:59 dhclient process and the information we find helpful for debugging.
Feb 19 18:21:59 dhclient exiting.
Feb 19 18:21:59 dhclient 30894 connection closed -
There are only 100 packets there, it's all outbound from 100.92.220.245 and none of it is DHCP.
But you should start your own thread. Unless this turns out to be identical it's only going to confuse things here.
Steve
