Loose WAN when rebooting or power cycle.



  • I have tried to setup the PFSense appliance on the LAN side of my PepLink Router in Bridge Mode and alternatively tried running my PepLink Router as 192.168.5.1 with my PFSense appliance as 192.168.1.1

    In both cases when I reboot my PFSense appliance the WAN will not reestablish the lease. The correct LAN IP is available but it will not connect until I disconnect the WAN connection. Once logged in I can then plug in the WAN cable and I immeadiately have access to the internet.

    Running in Bridge Mode allows me to troubleshoot without take Ng down my main systems. So I tried setting under Advanced DHCP the option of Deny DHCP from 192.158.1.1 and my PFSense appliance did come back however it could not communicate to the internet because the WAN port was 0.0.0.0. I believe everything points to the issue of having 2 devices trying to control DHCP. I have tried many configurations but have been unable to turn off DHCP without loosing access to the appliance or the internet.

    Any help would be appreciated. In either Bridge Mode or as a Router, I need the WAN port to reestablish communications without manual intervention following a reboot or power cycle.



  • Can you share your DHCP logs from these events? That would be very helpful in understanding exactly what is happening here.

    Also, most ISPs only allow you to have one public IP address at a time; if your router is in bridge mode, meaning that it is effectively acting as a L2 switch, you usually can only have one DHCP enabled interface (such as the WAN interface of your pfSense appliance) connected to the router at a time.



  • I am currently running PFSense in Bridge Mode.
    I have assigned the Lan an IP 192.168.1.10
    Wan gets assigned 192.168.1.28
    DHCP Server is on.
    The Wan configuration is set to DHCP.

    PFSense is on one leg of my Lan system with my main router between it and the Internet. My main router still is running DHCP.

    If I reboot PFense I am unable to sign in on the LAN IP 192.168.1.10 until I remove the ethernet cable plugged from the Wan port. As soon as I pull the Wan port cable I can log back into 192.168.1.10 and I can then plug the Wan port cable back into the appliance and it gets 192.168.1.28 ... everything works again.

    I provide the DHCP Log below:

    May 9 08:11:47 dhcpd Server starting service.
    May 9 08:11:47 dhcpd Sending on Socket/fallback/fallback-net
    May 9 08:11:47 dhcpd Sending on BPF/bridge0/02:e6:9c:aa:ae:00/192.168.1.0/24
    May 9 08:11:47 dhcpd Listening on BPF/bridge0/02:e6:9c:aa:ae:00/192.168.1.0/24
    May 9 08:11:47 dhcpd Multiple interfaces match the same shared network: igb0 bridge0
    May 9 08:11:47 dhcpd Multiple interfaces match the same subnet: igb0 bridge0
    May 9 08:11:47 dhcpd Wrote 1 leases to leases file.
    May 9 08:11:47 dhcpd For info, please visit https://www.isc.org/software/dhcp/
    May 9 08:11:47 dhcpd All rights reserved.
    May 9 08:11:47 dhcpd Copyright 2004-2018 Internet Systems Consortium.
    May 9 08:11:47 dhcpd Internet Systems Consortium DHCP Server 4.3.6-P1
    May 9 08:11:47 dhcpd PID file: /var/run/dhcpd.pid
    May 9 08:11:47 dhcpd Database file: /var/db/dhcpd.leases
    May 9 08:11:47 dhcpd Config file: /etc/dhcpd.conf
    May 9 08:11:47 dhcpd For info, please visit https://www.isc.org/software/dhcp/
    May 9 08:11:47 dhcpd All rights reserved.
    May 9 08:11:47 dhcpd Copyright 2004-2018 Internet Systems Consortium.
    May 9 08:11:47 dhcpd Internet Systems Consortium DHCP Server 4.3.6-P1
    May 9 08:11:45 dhcpd Server starting service.
    May 9 08:11:45 dhcpd Sending on Socket/fallback/fallback-net
    May 9 08:11:45 dhcpd Sending on BPF/bridge0/02:e6:9c:aa:ae:00/192.168.1.0/24
    May 9 08:11:45 dhcpd Listening on BPF/bridge0/02:e6:9c:aa:ae:00/192.168.1.0/24
    May 9 08:11:45 dhcpd Multiple interfaces match the same shared network: igb0 bridge0
    May 9 08:11:45 dhcpd Multiple interfaces match the same subnet: igb0 bridge0
    May 9 08:11:45 dhcpd Wrote 1 leases to leases file.
    May 9 08:11:45 dhcpd For info, please visit https://www.isc.org/software/dhcp/
    May 9 08:11:45 dhcpd All rights reserved.
    May 9 08:11:45 dhcpd Copyright 2004-2018 Internet Systems Consortium.
    May 9 08:11:45 dhcpd Internet Systems Consortium DHCP Server 4.3.6-P1
    May 9 08:11:45 dhcpd PID file: /var/run/dhcpd.pid
    May 9 08:11:45 dhcpd Database file: /var/db/dhcpd.leases
    May 9 08:11:45 dhcpd Config file: /etc/dhcpd.conf
    May 9 08:11:45 dhcpd For info, please visit https://www.isc.org/software/dhcp/
    May 9 08:11:45 dhcpd All rights reserved.
    May 9 08:11:45 dhcpd Copyright 2004-2018 Internet Systems Consortium.
    May 9 08:11:45 dhcpd Internet Systems Consortium DHCP Server 4.3.6-P1
    May 9 08:11:41 dhclient 17181 bound to 192.168.1.28 -- renewal in 43200 seconds.
    May 9 08:11:40 dhclient Creating resolv.conf
    May 9 08:11:40 dhclient /sbin/route add default 192.168.1.1
    May 9 08:11:40 dhclient Adding new routes to interface: igb0
    May 9 08:11:40 dhclient New Routers (igb0): 192.168.1.1
    May 9 08:11:40 dhclient New Broadcast Address (igb0): 192.168.1.255
    May 9 08:11:40 dhclient New Subnet Mask (igb0): 255.255.255.0
    May 9 08:11:40 dhclient New IP Address (igb0): 192.168.1.28
    May 9 08:11:40 dhclient ifconfig igb0 inet 192.168.1.28 netmask 255.255.255.0 broadcast 192.168.1.255
    May 9 08:11:40 dhclient Starting add_new_address()
    May 9 08:11:40 dhclient REBOOT



  • @atomicboy said in Loose WAN when rebooting or power cycle.:

    May 9 08:11:47 dhcpd Multiple interfaces match the same shared network: igb0 bridge0

    Hard to follow your set up but it sounds like you have the same network on the LAN and WAN side of the pfSense device. That i imagine would really mess with the routing table on the pfSense.



  • Yes I agree. I am not able to configure PFSense to be transparent in the sense that it resides on the Lan side of my main router. I suspect my issue is having DHCP running on my router and PFSense. I did try turning off DHCP on PFSense but then I loose communication with the GUI.

    Most routers these days have a bridge mode option as do some firewalls.

    I did try running the PFSense appliance as a router but in that mode but it would not come back unattended if rebooted or power cycled.



  • @atomicboy said in Loose WAN when rebooting or power cycle.:

    I did try running the PFSense appliance as a router but in that mode but it would not come back unattended if rebooted or power cycled.

    I would look at that before trying to run the pfSense device in as a transparent device. But I still can't follow what you are trying to do, it reads like you have tried two different setups and i don't know which set up the DHCP logs refer to etc.

    For example set the Peplink to have an internal LAN of 192.168.5.1, set the WAN on the pfSense to have static 192.168.5.2 then set the LAN of the pfSense to have 192.168.1.1 with DHCP only running on the pfSense and don't use any bridges and make sure to delete the bridges from the config. Does it then recover from reboots?



  • I will give that a try over the next day and see how I make out.

    Thanks!


Log in to reply