Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    WAN won't reconnect

    Scheduled Pinned Locked Moved NAT
    4 Posts 2 Posters 1.2k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      A.Bursell
      last edited by

      Hello,

      Still very-very new to this but ran into a strange situation for me. Setup is a Cell modem (MOFI) connected to my Netgate pfSense router. I have configured the MOFI in IP Passthrough mode, there is no bridge mode available. I am unclear of the differences and not sure if this creates any issues. I am able to see the Public IP in pfSense, it is being correctly passed and everything is working correctly. pfSense is set to DHCP as I do not have a static public IP address, so it should pull a new address if this changes. (I think)

      Situation:
      The cell modem went down and did not recover on it's own, it needed to be restarted. Restarted cell modem and came back up. pfSense would not pass traffic and simply shows n/a for a WAN address. I released and renewed the IP and then all was well.

      Why did pfSense not automatically pick up the WAN connection and start working again?

      Logs that I think are pertinent and may be helpful:

      Feb 6 13:25:24 dhclient 5797 connection closed
      Feb 6 13:25:24 dhclient 5797 exiting.
      Feb 6 13:25:32 dhclient PREINIT
      Feb 6 13:25:32 dhclient 45640 DHCPREQUEST on vr1 to 255.255.255.255 port 67
      Feb 6 13:25:33 dhclient 45640 DHCPREQUEST on vr1 to 255.255.255.255 port 67
      Feb 6 13:25:34 dhclient 45640 DHCPREQUEST on vr1 to 255.255.255.255 port 67
      Feb 6 13:25:35 dhclient 45640 DHCPREQUEST on vr1 to 255.255.255.255 port 67
      Feb 6 13:25:36 dhclient 45640 DHCPREQUEST on vr1 to 255.255.255.255 port 67
      Feb 6 13:25:37 dhclient 45640 DHCPREQUEST on vr1 to 255.255.255.255 port 67
      Feb 6 13:25:39 dhclient 45640 DHCPREQUEST on vr1 to 255.255.255.255 port 67
      Feb 6 13:25:44 dhclient 45640 DHCPDISCOVER on vr1 to 255.255.255.255 port 67 interval 1
      Feb 6 13:25:45 dhclient 45640 DHCPDISCOVER on vr1 to 255.255.255.255 port 67 interval 2
      Feb 6 13:25:47 dhclient 45640 DHCPDISCOVER on vr1 to 255.255.255.255 port 67 interval 4
      Feb 6 13:25:51 dhclient 45640 DHCPDISCOVER on vr1 to 255.255.255.255 port 67 interval 5
      Feb 6 13:25:56 dhclient 45640 DHCPDISCOVER on vr1 to 255.255.255.255 port 67 interval 9
      Feb 6 13:26:05 dhclient 45640 DHCPDISCOVER on vr1 to 255.255.255.255 port 67 interval 10
      Feb 6 13:26:15 dhclient 45640 DHCPDISCOVER on vr1 to 255.255.255.255 port 67 interval 15
      Feb 6 13:26:30 dhclient 45640 DHCPDISCOVER on vr1 to 255.255.255.255 port 67 interval 10
      Feb 6 13:26:40 dhclient 45640 DHCPDISCOVER on vr1 to 255.255.255.255 port 67 interval 5
      Feb 6 13:26:45 dhclient 45640 No DHCPOFFERS received.
      Feb 6 13:26:45 dhclient 45640 Trying recorded lease 100.94.102.155
      Feb 6 13:26:45 dhclient TIMEOUT
      Feb 6 13:26:45 dhclient Starting add_new_address()
      Feb 6 13:26:45 dhclient ifconfig vr1 inet 100.94.102.155 netmask 255.255.255.248 broadcast 100.94.102.159
      Feb 6 13:26:45 dhclient New IP Address (vr1): 100.94.102.155
      Feb 6 13:26:45 dhclient New Subnet Mask (vr1): 255.255.255.248
      Feb 6 13:26:45 dhclient New Broadcast Address (vr1): 100.94.102.159
      Feb 6 13:26:45 dhclient New Routers (vr1): 100.94.102.156
      Feb 6 13:26:46 dhclient New Routers (vr1): 100.94.102.156
      Feb 6 13:26:47 dhclient Deleting old routes
      Feb 6 13:26:47 dhclient 45640 bound: renewal in 1232 seconds.
      Feb 6 13:26:50 dhcpd Internet Systems Consortium DHCP Server 4.3.4
      Feb 6 13:26:50 dhcpd Copyright 2004-2016 Internet Systems Consortium.
      Feb 6 13:26:50 dhcpd All rights reserved.
      Feb 6 13:26:50 dhcpd For info, please visit https://www.isc.org/software/dhcp/
      Feb 6 13:26:50 dhcpd Config file: /etc/dhcpd.conf
      Feb 6 13:26:50 dhcpd Database file: /var/db/dhcpd.leases
      Feb 6 13:26:50 dhcpd PID file: /var/run/dhcpd.pid
      Feb 6 13:26:50 dhcpd Internet Systems Consortium DHCP Server 4.3.4
      Feb 6 13:26:50 dhcpd Copyright 2004-2016 Internet Systems Consortium.
      Feb 6 13:26:50 dhcpd All rights reserved.
      Feb 6 13:26:50 dhcpd For info, please visit https://www.isc.org/software/dhcp/
      Feb 6 13:26:50 dhcpd Wrote 13 leases to leases file.
      Feb 6 13:26:50 dhcpd Listening on BPF/vr0/00:0d:b9:23:f3:34/192.168.1.0/24
      Feb 6 13:26:50 dhcpd Sending on BPF/vr0/00:0d:b9:23:f3:34/192.168.1.0/24
      Feb 6 13:26:50 dhcpd Sending on Socket/fallback/fallback-net
      Feb 6 13:26:50 dhcpd Server starting service.

      A whole series of LAN DHCP traffic

      Feb 6 13:47:17 dhclient 84527 DHCPREQUEST on vr1 to 192.168.10.1 port 67
      Feb 6 13:47:17 dhclient 46489 send_packet: No route to host
      This is repeated multiple times

      Then this is I believe when I released and renewed the address

      Feb 6 13:58:16 dhclient 46489 connection closed
      Feb 6 13:58:16 dhclient 46489 exiting.
      Feb 6 13:58:25 dhclient PREINIT
      Feb 6 13:58:25 dhclient 86798 DHCPREQUEST on vr1 to 255.255.255.255 port 67
      Feb 6 13:58:25 dhclient 86798 DHCPNAK from 192.168.10.1
      Feb 6 13:58:25 dhclient 86798 DHCPDISCOVER on vr1 to 255.255.255.255 port 67 interval 1
      Feb 6 13:58:25 dhclient 86798 DHCPOFFER from 192.168.10.1
      Feb 6 13:58:25 dhclient ARPSEND
      Feb 6 13:58:27 dhclient ARPCHECK
      Feb 6 13:58:27 dhclient 86798 DHCPREQUEST on vr1 to 255.255.255.255 port 67
      Feb 6 13:58:27 dhclient 86798 DHCPACK from 192.168.10.1
      Feb 6 13:58:27 dhclient BOUND
      Feb 6 13:58:27 dhclient Starting add_new_address()
      Feb 6 13:58:27 dhclient ifconfig vr1 inet 100.70.142.134 netmask 255.255.255.252 broadcast 100.70.142.135
      Feb 6 13:58:27 dhclient New IP Address (vr1): 100.70.142.134
      Feb 6 13:58:27 dhclient New Subnet Mask (vr1): 255.255.255.252
      Feb 6 13:58:27 dhclient New Broadcast Address (vr1): 100.70.142.135
      Feb 6 13:58:27 dhclient New Routers (vr1): 100.70.142.133
      Feb 6 13:58:27 dhclient Adding new routes to interface: vr1
      Feb 6 13:58:27 dhclient /sbin/route add default 100.70.142.133
      Feb 6 13:58:27 dhclient Creating resolv.conf
      Feb 6 13:58:27 dhclient 86798 bound to 100.70.142.134 – renewal in 1800 seconds.
      Feb 6 13:58:36 dhcpd Internet Systems Consortium DHCP Server 4.3.4
      Feb 6 13:58:36 dhcpd Copyright 2004-2016 Internet Systems Consortium.
      Feb 6 13:58:36 dhcpd All rights reserved.
      Feb 6 13:58:36 dhcpd For info, please visit https://www.isc.org/software/dhcp/
      Feb 6 13:58:36 dhcpd Config file: /etc/dhcpd.conf
      Feb 6 13:58:36 dhcpd Database file: /var/db/dhcpd.leases
      Feb 6 13:58:36 dhcpd PID file: /var/run/dhcpd.pid
      Feb 6 13:58:36 dhcpd Internet Systems Consortium DHCP Server 4.3.4
      Feb 6 13:58:36 dhcpd Copyright 2004-2016 Internet Systems Consortium.
      Feb 6 13:58:36 dhcpd All rights reserved.
      Feb 6 13:58:36 dhcpd For info, please visit https://www.isc.org/software/dhcp/
      Feb 6 13:58:36 dhcpd Wrote 13 leases to leases file.
      Feb 6 13:58:36 dhcpd Listening on BPF/vr0/00:0d:b9:23:f3:34/192.168.1.0/24
      Feb 6 13:58:36 dhcpd Sending on BPF/vr0/00:0d:b9:23:f3:34/192.168.1.0/24
      Feb 6 13:58:36 dhcpd Sending on Socket/fallback/fallback-net
      Feb 6 13:58:36 dhcpd Server starting service.

      Any help would be greatly appreciated! My goal of course is to have maximum uptime and not need to do any manual resets.

      Thanks,

      Adam

      1 Reply Last reply Reply Quote 0
      • A
        A.Bursell
        last edited by

        Adding a little more info- I just restarted the cell modem again even though it was working to see what happened. Same thing. Came back up but could not access the internet until I did a release and renew in pfSense.

        Essentially the issue is that pfSense is not automatically trying to release/renew from the WAN.

        Help?

        Adam

        1 Reply Last reply Reply Quote 0
        • A
          A.Bursell
          last edited by

          I updated the title, hopefully a little more attention.

          Summary is that after my WAN connection drops and comes back up, pfSense won't reconnect. It shows n/a in the WAN field. But if I release/renew it will come back.

          Why does it do this and what can I do to get it to happen automatically? I would think it would by default?

          Adam

          1 Reply Last reply Reply Quote 0
          • Z
            znart
            last edited by

            I've had that happen numerous times and finally found this post. Identical log messages (apart from other IPs).  Can't figure out why DHCPDISCOVER is not sent to 255.255.255.255 anymore but to a fix IP that is not routable.

            Yes, my ISP goes down more than what I like but not being able to recover leaves me standing without connectivity until I save my WAN IF settings and reload.

            Anyone?

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.