Malfunctioning Ethernet bridge after 2.0.1 to 2.3.4 upgrade

  • Hello,

    I imported config from a remote firewall running 2.0.1 and imported it to one on my desk with freshly installed 2.3.4.
    On the first web GUI login I was prompted to finalize setup so I accepted all the defaults which looked right.
    My config is a fairly simple setup, no packages installed and just several rules in place.

    The general idea is to hot swap the old version firewall with the new version.
    Both run on the same hardware which is a small 3 port ALIX.2.

    I'm limited in what I can test locally and also limited with comparing things between the two as the old one is in a distant remote location.

    On the local one 2.3.4 I have a problem with LAN bridge.
    My understanding is if I connect a laptop with the correct IP, mask and gateway to whichever of the 2 bridged ports I should be able to ping the gateway IP
    If I connect 2 devices they should both be able to ping the gateway and also each other so the two ports work as a mini switch.

    On the newer pfSense version connectivity only works on OPT1-LAN0-VR0 port but not OPT2-LAN1-VR1 (the other bridge member).

    I have spotted some differences between the (same) config running on 2.0.1 and 2.3.4:


    *** Welcome to pfSense 2.0.1-RELEASE-nanobsd (i386) on xxx ***

    WAN (wan)                -> vr2        ->
      LAN_BR (lan)              -> bridge0    ->
      LAN0 (opt1)              -> vr0        -> NONE
      LAN1 (opt2)              -> vr1        -> NONE


    vr0: NOIP
    vr1: NOIP

    *** Welcome to pfSense 2.3.4-RELEASE (i386 nanobsd) on xxx ***

    WAN (wan)      -> vr2        -> v4:
    LAN_BR (lan)    -> vr0        -> v4:
    LAN0 (opt1)    -> vr0        -> v4:
    LAN1 (opt2)    -> vr1        ->


    vr1: NOIP
    bridge0: NOIP

    Can somebody explain why outputs look different between versions and the reason why it's not working on one of the member interfaces?
    Because bridge0 has no IP assigned I have a suspicion it's not working at all.

    Please advise.


  • Problem solved.

    It looks like the bridge interface name was set incorrectly during the upgrade process:

    Config on 2.0.1



    Same config on 2.3.4



    After correcting the value and rebooting the bridge is working as expected.

    Can anybody explain it?
    Is it a known bug / glitch?

Log in to reply