Connectivity problems with bridge interface



  • I have setup a transparent bridge with two physical interfaces. Every time I plug in a device one the second one (em1/OPT1) it cannot get an IP from the DHCP server and cannot connect to the network even if I enter the IP manually.
    By the way in DHCP logs I can see DHCPOFFER/DHCPDISCOVER for this system and there is no problem the with connected device or the network cable itself. Sometimes the system gets an IP but that happens randomly, so if I disconnect it and connect it again I have the same problem. I have also put some firewall rules on both network interfaces to allow everything however this cannot be a problem since sometimes connectivity works fine. There are no errors in/out on both interfaces.

    Something interesting I see in the system logs are the following lines:

    Aug 21 16:55:53 	php: rc.newwanip: pfSense package system has detected an ip change 0.0.0.0 -> ... Restarting packages.
    Aug 21 16:55:50 	php: rc.newwanip: Creating rrd update script
    Aug 21 16:55:50 	php: rc.newwanip: Resyncing OpenVPN instances for interface OPT1.
    Aug 21 16:55:44 	php: rc.newwanip: rc.newwanip: on (IP address: ) (interface: OPT1[opt2]) (real interface: em1).
    Aug 21 16:55:44 	php: rc.newwanip: rc.newwanip: Informational is starting em1.
    Aug 21 16:55:36 	check_reload_status: rc.newwanip starting em1
    Aug 21 16:55:36 	php: rc.linkup: Hotplug event detected for OPT1(opt2) but ignoring since interface is configured with static IP()
    Aug 21 16:54:42 	check_reload_status: Reloading filter
    Aug 21 16:54:42 	check_reload_status: Starting packages
    Aug 21 16:54:42 	php: rc.newwanip: pfSense package system has detected an ip change 0.0.0.0 -> ... Restarting packages.
    

    I use 2.1.4-RELEASE (i386).
    Any ideas?


  • Netgate Administrator

    How are you using these inerfaces?
    You would normally have bridge member interfaces set as type 'none' with the IP and DHCP server running on the bridge interface itself. That avoids seeing the IP change and the package restart.

    Steve



  • @stephenw10:

    You would normally have bridge member interfaces set as type 'none' with the IP and DHCP server running on the bridge interface itself. That avoids seeing the IP change and the package restart.

    Yes, that's how I am using them, both bridge members have IPv4/6 -> none and I am running DHCP on the bridge interface itself. Both bridge members have exactly the same settings however one always works and the other has the issues I explained above.


  • Netgate Administrator

    Anything riding on those interfaces, VLANs, VPNs etc?
    Are they both em?

    Steve



  • @stephenw10:

    Anything riding on those interfaces, VLANs, VPNs etc?
    Are they both em?

    They are em0 and em1, no VLANs or VPNs on them. They belong to LAN bridge.


  • Netgate Administrator

    Hmm, I have a very similar setup on my test box with no issues. Why is it seeing a change of IP? Why is it calling newwanip? You don't have a gateway set on any of those interfaces?
    One thing I have experienced before similar to this was caused by an IP setting in the config that was hidden by the webgui. I only found it eventually by looking through the config file. For example perhaps you were using em1 as a WAN and had it set to dhcp. Then you set it as none, something is still seeing a dhcp or gateway setting but the webgui hides it because you've set type 'none'.

    Steve

    Edit: typos from touch-screen keyboard.  ::)



  • @stephenw10:

    Why is it seeing a change of IP? Why us it calling newwanip? You don't gave a gateway set on any of those interfaces?
    One thing I have experienced before similar to this was caused by an IP setting in the config that was hidden by the webgui. I only found it eventually by looking through the config file. For example perhaps you were using em1 as a WAN and had it set to dhcp.

    Thank you Steve! I was asking the same questions to myself. Why "newwanip"?
    Actually the same interfaces had different roles/assignments in the past and one of them was my WAN back then, so I am thinking you might be right and something might still exist in the config while isn't visible by the webgui. I tried to change the gui settings and press "save" hoping something could be fixed but that didn't help.
    So, should I check and possibly edit "config.xml" file, under "<interfaces>"?</interfaces>


  • Netgate Administrator

    Yes, backup the config file and read through it. Unless you've got a very complex setup it's all reasonably readable so you should spot something that shouldn't be there.
    In my case I had an old setting in the dhcp section that conflicted with another subnet. In the webgui it just reported an error whenever I tried to change any dhcp settings but the bad setting was hidden because only static interfaces are shown and i'd changed it's type.

    Steve



  • Delete your 2 interfaces in PF Sense so that you can't see them anymore in "interfaces", do a clean reboot, and assign your interfaces to your bridge again, and then set up your DHCP for that bridge.



  • I haven't found any obvious conflict in the config file so I might try the deletion of interfaces and let you know.