How to get pfSense WAN to accept VLAN 0
-
@michaellacroix When will 22.11 SS come out?
-
@stephenw10 said in How to get pfSense WAN to accept VLAN 0:
should be any time now
-
-
That is expected until Plus dev snaps are made public. That should be any time now but there will be an announcement when it happens.
-
-
Thanks Stephen, do you know if you clone the boot environment before upgrading to 22.11 DEV you can safely return to 22.05 by going back to that boot copy? I'm unsure if it captures the whole OS or just pfsense in that point in time. Thanks
-
I was just testing that and, yes, that is now possible. I'm not sure if the new bootloader that allows it has made it into snapshots yet but it will be when they go public.
-
Hi Stephen, have you done any testing with QOS on the WAN interface while using the netgraph script? I was going to configure traffic shaping for VOIP but am unable to choose the WAN interface as a selection. Thanks
-
I have not done that. I don't have a WAN that requires. It doesn't surprise me that it wouldn't work though ng is shown as altq capable:
https://github.com/pfsense/pfsense/blob/RELENG_2_6_0/src/etc/inc/interfaces.inc#L6946What error are you seeing?
-
Thanks so much Stephen, I cant wait to be able to use pfsense plus natively without the netgraph script.
-
Hi Team, any new updates on this...do we have a working for for the latest SS ? I am still stuck in the dark with 2.5.2
-
-
That's only required to send vlan0 tagged traffic. Most connections that fail to get a DHCP lease from the ISP do so because the ISP is sending vlan0 tagged traffic. That will work in current 2.7 snapshots. See: https://redmine.pfsense.org/issues/12070
Steve
-
@stephenw10 said in How to get pfSense WAN to accept VLAN 0:
That's only required to send vlan0 tagged traffic. Most connections that fail to get a DHCP lease from the ISP do so because the ISP is sending vlan0 tagged traffic. That will work in current 2.7 snapshots. See: https://redmine.pfsense.org/issues/12070
Steve
Hi Steve,
When would this be ready for us to comsume? -
I have several CE test boxes running current snapshots and they have been pretty stable for some time now. Still hard to recommend using it in 'production' though.
If you can test it that helps any issues of course.Steve
-
Hey guys- I'm using Ziply fiber- which used to be frontier. It is doing exactly this. No ip address on WAN. I've updated my netgate 4100 to the latest dev build and ran the command "ifconfig ix2 pcp 4" and it shows the flag being set correctly. Still no IP address.
I don't understand why this is even a problem. (I get it is because of vlan0-still) How can a major firewall manufacturer...which I actually paid for by the way...not allow all ISPs to work on their device? How can you then- choose to NOT support me. My last request for zero setup was completely ignored- now I know why. I've been in IT for a very long time and this is the first time I've ever run into something like this. First thing I'm doing for my new job is ripping out all the netgate devices that I'm responsible for- why trust a product that just doesn't even work on some internet connections in 2022?????! Absurd!
-
@jhiggy If you run pfsense in a virtual machine (ESXi is free for this), then you avoid this issue, and get a lot of advantages like snapshots that are very useful features that are not built into PFSense.
To be honest, this stupidity that AT&T started (and now other Arris based ISPs use) with using VLAN0 and such is highly unusual. They make it very hard for you to use your own equipment. I would not be so harsh on the Netgate people as much as your ISP who inflicts this stupidity on the world.
I think folks who have to suffer with these ISPs do have a great option by running in a ESXi VM. So it's not the end of the world even if this bug isn't fixed for a long time.
-
@jhiggy You might be hitting something else there because current 23.01 snaps can accept priority tagged traffic and can accept dhcp offers tagged that way.
You don't usually need to add priority tags to the replies so setting a pcp value shouldn't be required.
Perhaps that ISP has some other requirement like a vlan tag?The only thing outstanding there is the driver bug in e1000 that requires vlan hardware tagging be disabled. You wouldn't hit that on an ix NIC though.
Steve
-
Sorry- I'm obviously really upset- I've flashed this brand new device 4 different times now with different versions with no luck. (I refuse to use that script- maybe it would work?) I purchased this so that I could learn the new Pfsense OS for my job and time is out. =/ All I know is that I've had an Edgerouter and Unfi gateway working out of the box-along with pfsense installed on a server. I also just tested with a cheap asus router working. Ziply has a hard time replacing an ONT that works with 99.9% of routers out there so I'm stuck.
What else can I try?
I tried the dumb switch between the ont with no luck either. I tried an untagged port in my unifi switch- same. It always detected it but always shows 0.0.0.0 as the ip. (I've reset the ONT and had ziply repush the config as well)
-
First thing to do it grab a packet capture of the DHCP traffic on the WAN and see what's actually arriving. What made you think your ISP is using traffic in the first place? Perhaps you already saw it in a pcap?
https://docs.netgate.com/pfsense/en/latest/diagnostics/packetcapture/webgui.html
Steve
