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

    How to get pfSense WAN to accept VLAN 0

    Scheduled Pinned Locked Moved
    General pfSense Questions
    25
    414
    169.2k
    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.
    • C
      cucu007 @jalano
      last edited by

      @jalano said in How to get pfSense WAN to accept VLAN 0:

      I've been researching lots of possible solutions to this.

      Here's what I'm at now, in case anyone stumbles across this thread in July of 2022!

      • FreeBSD 13.1 now has a dhclient that is aware of the DHCPOFFER datagrams inside 802.1q-encapsulated frames with VLAN 0.
      • OPNSense 22.7-RC1 is on FreeBSD 13.1.

      In theory, when pfSense moves to FreeBSD 13.1 this problem should be fixed. According to this, it's been fixed this way on OPNSense:

      https://github.com/opnsense/src/issues/114

      Well this is certainly an update and it seems someone is looking into this issue from the BSD end. Jalono have you been able to validate this working on OPNsense yet? Please advise.

      J 1 Reply Last reply Reply Quote 0
      • J
        jalano @cucu007
        last edited by

        @cucu007 said in How to get pfSense WAN to accept VLAN 0:

        @jalano said in How to get pfSense WAN to accept VLAN 0:

        I've been researching lots of possible solutions to this.

        Here's what I'm at now, in case anyone stumbles across this thread in July of 2022!

        • FreeBSD 13.1 now has a dhclient that is aware of the DHCPOFFER datagrams inside 802.1q-encapsulated frames with VLAN 0.
        • OPNSense 22.7-RC1 is on FreeBSD 13.1.

        In theory, when pfSense moves to FreeBSD 13.1 this problem should be fixed. According to this, it's been fixed this way on OPNSense:

        https://github.com/opnsense/src/issues/114

        Well this is certainly an update and it seems someone is looking into this issue from the BSD end. Jalono have you been able to validate this working on OPNsense yet? Please advise.

        I have not been able to test this - I need to get another bit of gear to install OPNsense on. I'm currently running an SG-1100 with 2.4.5p1.

        Looking at OPNsense 22.7 it appears I will have a lot of work to do to convert the config file or will have to spend some time hand-entering the configuration, which I'm not looking forward to; it's quite different from pfSense now. I was hoping to have found a good solution that would allow me to keep using my pfSense hardware.

        C 1 Reply Last reply Reply Quote 0
        • C
          cucu007 @jalano
          last edited by

          @jalano said in How to get pfSense WAN to accept VLAN 0:

          @cucu007 said in How to get pfSense WAN to accept VLAN 0:

          @jalano said in How to get pfSense WAN to accept VLAN 0:

          I've been researching lots of possible solutions to this.

          Here's what I'm at now, in case anyone stumbles across this thread in July of 2022!

          • FreeBSD 13.1 now has a dhclient that is aware of the DHCPOFFER datagrams inside 802.1q-encapsulated frames with VLAN 0.
          • OPNSense 22.7-RC1 is on FreeBSD 13.1.

          In theory, when pfSense moves to FreeBSD 13.1 this problem should be fixed. According to this, it's been fixed this way on OPNSense:

          https://github.com/opnsense/src/issues/114

          Well this is certainly an update and it seems someone is looking into this issue from the BSD end. Jalono have you been able to validate this working on OPNsense yet? Please advise.

          I have not been able to test this - I need to get another bit of gear to install OPNsense on. I'm currently running an SG-1100 with 2.4.5p1.

          Looking at OPNsense 22.7 it appears I will have a lot of work to do to convert the config file or will have to spend some time hand-entering the configuration, which I'm not looking forward to; it's quite different from pfSense now. I was hoping to have found a good solution that would allow me to keep using my pfSense hardware.

          According tot he pfsense release notes, it seems the 2.7 upcoming version will be base on 12.3 and not 13.x, this might mean we will be stuck even with this issue after code 2.7 gets to GA. Unless someone backports some kind of workaround for the 2.7 code to work with the VLA 0 issue at hand. Looking forward to get this issue resolve once and for all.

          Reference: https://docs.netgate.com/pfsense/en/latest/releases/versions.html

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            It's based on 12.3 now but that doesn't mean it will be.

            The dhclient accepting vlan0 tagged packets doesn't address the fact that igb/em doesn't pass the packets to it. Otherwise the netgraph workaround would still work in 2.6.

            AT&T is whole different problem. That's very unlikely to ever be supported natively.

            Steve

            C 1 Reply Last reply Reply Quote 0
            • C
              cucu007 @stephenw10
              last edited by

              @stephenw10

              Steve,
              I would be happy if we can at least get this working for frontier.

              M 1 Reply Last reply Reply Quote 0
              • M
                michaellacroix @cucu007
                last edited by

                @cucu007

                I just loaded some old hardware with current version of opnsense and it works like a charm. No netgraph script necessary. The interface drivers were re0 and em0. DO YOU HEAR THAT NETGATE!
                I have frontier fiber.

                C bmeeksB stephenw10S 3 Replies Last reply Reply Quote 0
                • C
                  cucu007 @michaellacroix
                  last edited by

                  @michaellacroix said in How to get pfSense WAN to accept VLAN 0:

                  @cucu007

                  I just loaded some old hardware with current version of opnsense and it works like a charm. No netgraph script necessary. The interface drivers were re0 and em0. DO YOU HEAR THAT NETGATE!
                  I have frontier fiber.

                  Michael,
                  I think the big challenge for PFS is actually the intel NICs (igb/em) as previously mentioned by steve

                  Steve,
                  Please correct me if I am wrong...

                  M 1 Reply Last reply Reply Quote 0
                  • bmeeksB
                    bmeeks @michaellacroix
                    last edited by bmeeks

                    @michaellacroix said in How to get pfSense WAN to accept VLAN 0:

                    @cucu007

                    I just loaded some old hardware with current version of opnsense and it works like a charm. No netgraph script necessary. The interface drivers were re0 and em0. DO YOU HEAR THAT NETGATE!
                    I have frontier fiber.

                    Just for clarification if others read this thread:

                    OPNsense is currently based on FreeBSD 13 while pfSense is using 12.3-STABLE. The OPNsense team had a number of growing pains with that move to FreeBSD 13. They continue to still have a few. There seems to be quite a few changes around VLANs in particular with FreeBSD 13.

                    So a willy-nilly jump to FreeBSD 13 may result in more bugs than fixes. The pfSense team will get there for sure, but they tend to be a bit more deliberate when making FreeBSD major version moves. If I recall the timeline correctly, the OPNsense team abandoned Hardened FreeBSD (11, I think) and jumped over to FreeBSD 13.

                    There are differences in the NIC drivers as you change among the FreeBSD versions.

                    C 1 Reply Last reply Reply Quote 0
                    • C
                      cucu007 @bmeeks
                      last edited by

                      @bmeeks

                      In that note, my guess we just have to wait patiently...when the cake is fully bake we will eat it. :-)

                      luckman212L 1 Reply Last reply Reply Quote 0
                      • luckman212L
                        luckman212 LAYER 8 @cucu007
                        last edited by

                        ...when the cake is fully bake we will eat it

                        yum. save me a piece! 🍰

                        1 Reply Last reply Reply Quote 0
                        • M
                          michaellacroix @cucu007
                          last edited by

                          @cucu007
                          Not really, please keep in mind this discussion was started for the issue of PFS not being able to grab an IP from DHCP on the WAN interface because of the vlan tag.
                          I poked the bear because netgate hid behind freebsd about this issue when they could have easily built something into the application to handle the traffic. Now we know when pfs goes to freebsd 13 issue resolved and that will be a sweet peice of cake...

                          1 Reply Last reply Reply Quote 0
                          • stephenw10S
                            stephenw10 Netgate Administrator @michaellacroix
                            last edited by

                            @michaellacroix said in How to get pfSense WAN to accept VLAN 0:

                            @cucu007

                            I just loaded some old hardware with current version of opnsense and it works like a charm. No netgraph script necessary. The interface drivers were re0 and em0. DO YOU HEAR THAT NETGATE!
                            I have frontier fiber.

                            To be clear that was using em0 as the WAN interface?
                            That implies the driver issue there is fixed in FreeBSD 13 and will be inherited when we move to it.

                            Steve

                            M 1 Reply Last reply Reply Quote 0
                            • M
                              michaellacroix @stephenw10
                              last edited by

                              @stephenw10

                              Let me double check Steve, I believe I was using emo as the wan interface but I will verify.
                              thanks

                              S 1 Reply Last reply Reply Quote 1
                              • S
                                Schwiing @michaellacroix
                                last edited by

                                @michaellacroix is this an issue with ix? I'm getting frontier in a couple weeks (2gig) and I assume it'll have the same problem. I have an Intel x520-da2.

                                If it is a problem with pfsense, could I put a mikrotik switch in front of it to strip the tag?

                                Thanks!

                                M 1 Reply Last reply Reply Quote 0
                                • M
                                  michaellacroix @Schwiing
                                  last edited by

                                  @schwiing Doesn't matter what equipment you have because frontier tags their internet connection you will either need to put a switch between your pfs router and ONT or use the netgraph script. Somewhere in this forum are directions to use netgraph. That's what I use.

                                  S 1 Reply Last reply Reply Quote 1
                                  • S
                                    Schwiing @michaellacroix
                                    last edited by

                                    @michaellacroix I'm open to either method. Does netgraph work with 22.05 or did/do you have to downgrade to 2.6 or below?

                                    M 1 Reply Last reply Reply Quote 0
                                    • M
                                      michaellacroix @Schwiing
                                      last edited by

                                      @schwiing I'm using 22.05 and it works great. If you look back in this forum I did run into a problem upgrading from 2.6 to 22.05 and needed to remove a couple of lines from the script. But other than that it works great.

                                      S 1 Reply Last reply Reply Quote 1
                                      • S
                                        Schwiing @michaellacroix
                                        last edited by

                                        @michaellacroix said in How to get pfSense WAN to accept VLAN 0:

                                        @schwiing I'm using 22.05 and it works great. If you look back in this forum I did run into a problem upgrading from 2.6 to 22.05 and needed to remove a couple of lines from the script. But other than that it works great.

                                        Thanks. That gives me some hope.

                                        This is what my script looks like (Let me know if I did it right [the MAC is for my WAN port in PFsense):

                                        https://pastebin.com/LMJhVphx

                                        Do I still need to change my WAN from "ix0" to "ngeth0"? If so, how do I do that?

                                        M 1 Reply Last reply Reply Quote 0
                                        • M
                                          michaellacroix @Schwiing
                                          last edited by

                                          @schwiing Script looks good. Once you run the script you will have an option in the interface assignments section of pfs to change the adapter interface to netgraph

                                          M 1 Reply Last reply Reply Quote 1
                                          • M
                                            michaellacroix @michaellacroix
                                            last edited by

                                            @michaellacroix Here is the original github for the netgraph instructions. We only need to worry about the vlan tagging.

                                            https://github.com/MonkWho/pfatt

                                            S 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post