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

    Vlan communication on em interfaces

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    4 Posts 2 Posters 2.0k 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.
    • O Offline
      oggsct
      last edited by

      I tried updating to the last snapshot last night and lost connectivity across my vlans again. I have to fallback to an April 17 2012 snapshot in order to get my vlans working again. I have tried to update to the latest snapshot a number of times since April, but the results are always the same.

      Should I try a clean install of the latest snapshot or is there still a known issue with em interfaces and vlan communication? I have 2 em NICs that are on direct connected vlans with no tagging and they can't communicate with each other either.

      LAN (em0) can't talk to Opt1 or any other network connected to the pfsense
      Opt1 (em1) can't talk to LAN or any other network connected to the pfsense

      Communication works correctly on the April 17 2012 snapshot

      1 Reply Last reply Reply Quote 0
      • marcellocM Offline
        marcelloc
        last edited by

        You. Have two interfaces without vlan configured?

        Vlan Id x untagged on switch means no config on server's interface.

        Treinamentos de Elite: http://sys-squad.com

        Help a community developer! ;D

        1 Reply Last reply Reply Quote 0
        • O Offline
          oggsct
          last edited by

          I did a clean install and these issues are resolved. My only guess is the constant snapshot upgrade path broke something along the way.

          1 Reply Last reply Reply Quote 0
          • O Offline
            oggsct
            last edited by

            After manually entering all of my settings from a backup configuration, I believe I found a more concrete answer than 'something in the upgrade path'. I have a multi-wan setup and do load balancing and prioritization across each link. Everything on the clean installed worked fine until I had loaded all of the rules in (which is where outbound gateways are defined). It seems that between the April 17 2012 snapshot that I was running and last weeks, something changed with how internal IPs and directly connected networks are routed when the default rule for an interface does load balancing. I believe the change occurred in a more narrow timeframe as I have had this issue on other snapshots I tried as well, prior to list week, including a Sept 2012 snapshot.

            I am not sure how many others have come across this issue, or if you always needed a rule per interface to handle internal/direct connected networks and the snapshot I was using had a bug that ignored that, but it would be good to know what changed in regards to that and why.

            Thanks all for reading about my troublesome weekend messing with pfSense snapshots.

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