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

    VLANS

    Scheduled Pinned Locked Moved Routing and Multi WAN
    26 Posts 7 Posters 12.1k 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.
    • M
      maynarja
      last edited by

      It may of been the switch although configured correctly it did die on me today…

      I will let you all know once I get it replaced.

      Thanks all for the info

      1 Reply Last reply Reply Quote 0
      • F
        fwuser07
        last edited by

        I had the same issue. After assigning the lan net to vlan0 no communication over this interface was possible although the switch port was configured correctly.

        While searching a solution I did a reboot of the pfsense box and after that all vlans are working fine.

        First I won't believe that so I reseted the pfsense to factory defaults and I could reproduce this behavior. In the testing machine a realtek nic is used so I don't know if this behavior has to do with the rl driver or if you have to do a reboot with all nics.

        I hope I will get my new intel hardware soon so I can test if there is also reboot required using an intel nic.

        1 Reply Last reply Reply Quote 0
        • C
          cmb
          last edited by

          fwuser07: That reminds me!  ;D  I had the exact same problem with my VLAN router, though it's running an OLD release (1.0-RC3…heh). I meant to attempt to duplicate the issue I saw, where my VLAN's wouldn't work until a reboot, but forgot about it until I saw your post.

          My VLAN trunk interface is a Realtek 8169 on a FX5620 donated to the project courtesy of LinITX.com.
          http://linitx.com/product_info.php?cPath=4&products_id=909

          So maybe it is a Realtek driver issue? The interfaces are created properly, IIRC, they just didn't work until after a reboot. What pfsense version are you using?

          Please let us know if you can duplicate the issue with Intel or any other NIC's. We may need to build in some logic to require a reboot after VLAN configurations.

          1 Reply Last reply Reply Quote 0
          • F
            fwuser07
            last edited by

            I was testing with the stable version 1.0.1 and 1.2-BETA-1.

            Before rebooting the following message appeared in the system log:
            kernel: arp: x.x.x.x is on vlan0 but got reply from 00:0e:6d:45:80:ae on vlan1
            (x.x.x.x is an internal ip address)

            1 Reply Last reply Reply Quote 0
            • T
              tedced
              last edited by

              realtek…  :(

              toss an intel in there :P  $30CAD

              1 Reply Last reply Reply Quote 0
              • F
                fwuser07
                last edited by

                I finally got the Tyan S3095 with two Intel PCIe nics onboard and the following things happened:

                I also had to restart pfsense after aktivating vlans. After assigning a new vlan pfsense needs 2-3 minutes to transmit the request and it happened once that pfsense suddenly restarts after clicking the save button for a new vlan.

                But the most important thing is that after assigning all vlans pfsense seems to work great :)

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