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

    Incoming traffic on vlan not recognized

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    28 Posts 6 Posters 12.6k 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.
    • dotOneD
      dotOne
      last edited by

      No, unfortunately still no new version.

      2.1-BETA0 (amd64)
      built on Mon Aug 27 14:57:37 EDT 2012
      FreeBSD 8.3-RELEASE-p4

      You are on the latest version.
      This was on Friday 08:00 CET

      Still waiting….:(

      1 Reply Last reply Reply Quote 0
      • P
        phil.davis
        last edited by

        The 32-bit nanobsd has had regular builds the last few days:

        Current version: 2.1-BETA0
  NanoBSD Size : 2g
       Built On: Thu Aug 30 02:36:04 EDT 2012
    New version: Thu Aug 30 06:26:55 EDT 2012

        So maybe something is going wrong building 64-bit?

        As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
        If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

        1 Reply Last reply Reply Quote 0
        • P
          podilarius
          last edited by

          Must be the embedded, full is there.

          2.1-BETA0 (amd64) 
built on Thu Aug 30 06:54:02 EDT 2012 
FreeBSD 8.3-RELEASE-p4
          1 Reply Last reply Reply Quote 0
          • dotOneD
            dotOne
            last edited by

            Then something must be wrong on my side.
            I still get that I'm on the latest version…. let's do the update by hand.

            Updated without problems.
            This afternoon I will test the PCP issue.

            1 Reply Last reply Reply Quote 0
            • dotOneD
              dotOne
              last edited by

              I can confirm that the issue has been fixed.
              I will do more elaborate testing this weekend with different PCP's and PCP combinations.
              For now it looks promising.

              @ndre

              1 Reply Last reply Reply Quote 0
              • E
                epek
                last edited by

                Confirmed. '2.1-BETA0 (amd64) built on Fri Aug 31 11:22:13 EDT 2012' seems to work.
                Thanks to everyone involved!
                What exactly went wrong?

                Update: the web interface for special rules for 802.1p still does not save different values. So shifting pcp on incoming/outgoing packets is still unsupported (through the gui).

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

                  Have you tried turning off VLAN_HWTAGGING ???

                  I have an Atom based machine with 2 Intel NICs and vlans don't work until I turn this feature off.

                  I had to put this in a cronjob:

                  ifconfig em0 | grep -q VLAN_HWTAG && ifconfig em0 -vlanhwtag  
ifconfig em1 | grep -q VLAN_HWTAG && ifconfig em1 -vlanhwtag 

                  Worth a try….

                  1 Reply Last reply Reply Quote 0
                  • D
                    dhatz
                    last edited by

                    @frater:

                    Have you tried turning off VLAN_HWTAGGING ???
                    I have an Atom based machine with 2 Intel NICs and vlans don't work until I turn this feature off.

                    I had to put this in a cronjob:

                    ifconfig em0 | grep -q VLAN_HWTAG && ifconfig em0 -vlanhwtag  
ifconfig em1 | grep -q VLAN_HWTAG && ifconfig em1 -vlanhwtag  

                    This is an issue that should be investigated …

                    What is the exact model of your Intel NIC (output of dmesg) and your mainboard ?

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

                      @dhatz:

                      This is an issue that should be investigated …

                      What is the exact model of your Intel NIC (output of dmesg) and your mainboard ?

                      I brought it up before ( http://forum.pfsense.org/index.php/topic,52224.0.html ) and made a bug report asking for an option to turn off hardware vlan tagging.

                      http://redmine.pfsense.org/issues/2577

                      I would welcome some follow-up, but don't want to hijack this thread.

                      1 Reply Last reply Reply Quote 0
                      • dotOneD
                        dotOne
                        last edited by

                        Well,  This is the output of dmesg regarding to my nics:

                        em0: <intel(r) 1000="" pro="" network="" connection="" 7.3.2="">port 0xcc00-0xcc1f mem 0xfe7e0000-0xfe7fffff,0xfe7dc000-0xfe7dffff irq 18 at device 0.0 on pci3
                        em0: Using MSIX interrupts with 3 vectors
                        em0: [ITHREAD]
                        em0: [ITHREAD]
                        em0: [ITHREAD]
                        pcib4: <acpi pci-pci="" bridge="">irq 19 at device 28.3 on pci0
                        pci4: <acpi pci="" bus="">on pcib4
                        em1: <intel(r) 1000="" pro="" network="" connection="" 7.3.2="">port 0xdc00-0xdc1f mem 0xfe8e0000-0xfe8fffff,0xfe8dc000-0xfe8dffff irq 19 at device 0.0 on pci4
                        em1: Using MSIX interrupts with 3 vectors
                        em1: [ITHREAD]
                        em1: [ITHREAD]
                        em1: [ITHREAD]
                        em2: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.4="">port 0xec00-0xec3f mem 0xfebe0000-0xfebfffff,0xfebc0000-0xfebdffff irq 18 at device 4.0 on pci6
                        em2: [FILTER]
                        em3: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.4="">port 0xe880-0xe8bf mem 0xfeb80000-0xfeb9ffff,0xfeb60000-0xfeb7ffff irq 19 at device 6.0 on pci6
                        em3: [FILTER]
                        em4: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.4="">port 0xe800-0xe83f mem 0xfeb20000-0xfeb3ffff,0xfeb00000-0xfeb1ffff irq 16 at device 7.0 on pci6

                        em0 and em1 are the on-board nics. em2..5 are the nics on the expansion board.

                        VLAN_HTWAG is off by default. I checked again to be sure.

                        @ndre</intel(r)></intel(r)></intel(r)></intel(r)></acpi></acpi></intel(r)>

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

                          @avink:

                          VLAN_HTWAG is off by default. I checked again to be sure.

                          @ndre

                          In this thread you gave the output of your ifconfig and it clearly shows you have VLAN_HWTAGGING enabled.
                          How did you disable it, then?
                          There's no option inside pfsense to do this.
                          That's why I made the feature request which was rejected.

                          
[2.1-BETA0][admin@firewall]/root(9): ifconfig -a
em0: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500
        options=5219b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,tso4,wol_magic,vlan_hwfilter,vlan_hwtso>ether 00:30:18:a2:bd:13
        inet6 fe80::230:18ff:fea2:bd13%em0 prefixlen 64 scopeid 0x6
        nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
em0_vlan4: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500
        options=103 <rxcsum,txcsum,tso4>ether 00:30:18:a2:bd:13
        inet6 fe80::76f0:6dff:fe80:9448%em0_vlan4 prefixlen 64 scopeid 0x13
        nd6 options=1 <performnud>media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
        vlan: 4 vlanpcp: 0 parent interface: em0</full-duplex></performnud></rxcsum,txcsum,tso4></up,broadcast,running,promisc,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,tso4,wol_magic,vlan_hwfilter,vlan_hwtso></up,broadcast,running,promisc,simplex,multicast>
                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.