How to get pfSense WAN to accept VLAN 0
-
I can confirm as of this morning, College Station, TX still wants vlan0.
11:34:03.435271 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype 802.1Q (0x8100), length 60: vlan 0, p 0, ethertype IPv4, (tos 0x0, ttl 246, id 54321, offset 0, flags [none], proto TCP (6), length 40)
xxx.xxx.xxx.72.50650 > xx.xxx.xxx.xxx.3050: Flags [S], cksum 0x8ea1 (correct), seq 1903919664, win 65535, length 0 -
@cucu007 said in How to get pfSense WAN to accept VLAN 0:
I am one of those stuck under 22.5 and working
You are seeing it pull a lease in 22.05?
If not it won't work there with VLAN0 without the netgraph script. You'll need to go to 2.7 or wait for 22.11 snaps (which should be any time now).
Steve
-
@stephenw10
I can confirm in my area frontier is still using vlan 0. Thanks -
The updates look like their coming pretty fast. I'm surprised 22.11 dev isn't available yet
-
@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!
