How to get pfSense WAN to accept VLAN 0
-
@stephenw10 It shows the packet, it isn’t tagged by vlan0 though, I just installed 2.5.2, previous tcpdump was from 2.4.4, I’ll see what it’s doing later today. I don’t think it’s the NIC as I have tried a whole plethora of devices, none of which will pull an IP via DHCP. Before having bellmts come by to replace the Nokia ont with an SFP module, itd link up and assign my win10 desktop a dynamic 207.x.x.x IP. It links, doesn’t pull an IP, I am so stumped. Offering .2 ETH to anyone who can help me get this working.
-
How do you have the script configured?
What interface are you running that capture on? It has to be the parent interface.
Steve
-
@mikela - sorry I got my pfsense setup and it has been cruzing ever since.
I used the earlyshellcmd
-
@dayneparrott do you have a service higher than 1gb. I think the Bell MTS design is different for 1gb+
I have 1Gb and for this and lower speeds the ONT stays in place and the HH3000 is removed.
With >1GB i dont think they use the ONT and add a Fiber SFP module right into the HH3000. Are you putting the SFP in to your pfSense box?
-
I am currently still on 2.4.5-RELEASE-p1 (amd64), am I safe to do an in place upgrade to 2.5.2?
Can I upgrade with packages still installed and not break anything. Asking in this space just because i dont want it to break this functionality of course.
-
2.5.2 should be fine. The igb driver in 2.6 does not pass VLAN0 correctly. That should now be fixed in 2.7 snapshots though, we are waiting for feedback on that.
Steve
-
I had my pfsense running 2.6 working flawless for a bit then I switch from xfinity to frontier fiber then all hell broke loose. After much research and testing I had no choice bu to roll things back to 2.5.2 and apply the vlan script fix, which so far is working fine. Is there an ETA for getting this bug fix in an upcoming release for 2.6 or will this have to wait for 2.7?
Also, are there any plans to update the vlan script to make it comaptible with release 2.6? Please advise.
-
@stephenw10 I tried running the latest 04/03 snapshot for 2.7 and it doesnt seem to work either, had no choice but to rollback to 2.5.2 to get my internet up and running, it was a bad weekend to say the least getting this VLAN 0 issue sorted.
-
Hmm, the fix for the known issue in e1000 should now be in 2.7 snapshots:
https://github.com/pfsense/FreeBSD-src/commit/9c762cc125c0c2dae9fbf49cc526bb97c14b54a4If you're sure you were running a snap with that in that might not be the issue after all.
Try running a pcap to see the tagged traffic.
Steve
-
@stephenw10 I was running the latest development SS as of Saturday and it didnt work. So I opted to rollback to 2.5.2 and apply the VLAN script fix, so far is working. Do you happen to now if the script will soon be modify to accommodate release 2.6, I like to stay ahead rather than behind :-)
-
The script itself should be fine in 2.6 or 2.7. The issue is the e1000 driver which incorrectly handles VLAN0 from what I can see.
To be clear you applied the script in 2.7 and it failed? Did it show any errors?
Steve
-
@stephenw10 it just didnt work, I give up on it, didnt even check the logs.
I am on 2.5.2 and is working, but my downloads is now slow. I am using frontier fiber. Did you get the script working on 2.6?
-
I personally don't use it. My ISP doesn't require priority tagging.
The script works fine in 2.6 as long as you don't have an Intel e1000 NIC as I understand it.
Steve
-
I can confirm that with fix https://github.com/MonkWho/pfatt/issues/67#issuecomment-1043358822 on 2.6.0 works perfect. I haven't had any issues. My backup router has em drivers and I haven't had time to test that out yet on 2.7.0.
-
@c45p32 said in How to get pfSense WAN to accept VLAN 0:
I can confirm that with fix https://github.com/MonkWho/pfatt/issues/67#issuecomment-1043358822 on 2.6.0 works perfect. I haven't had any issues. My backup router has em drivers and I haven't had time to test that out yet on 2.7.0.
I am planning to do some testing this weekend with 2.6.0. My internet was down for two days, so I opted to bring back my old router running openWRT and so far is working flawless, but if at all possible I would like to go back to pfSence since is my favorite!
Any ideas of what the 2.7.0 roadmap looks like in terms of release? Any potential tentatrrive dates?
-
stephenw10 Netgate Administratorlast edited by stephenw10 Apr 8, 2022, 5:53 PM Apr 8, 2022, 5:52 PM
No, there's no schedule for a 2.7 release yet.
22.05 is targeted at May obviously. That also contains the same fix. Assuming that fixes it.
-
I tried again today, doesnt work....I tried uploading both em and igb even when I only needed igb. I follow the instructions by the book in the post you reference, it looks like this remains broken as of 2.6.0. Going back to OpenWRT until this is sorted out correctly, will miss my pfSense box. ;-(
Please consider integrating this fix into the high priority list as it impact all AT&T and Frontier fiber customers. Thank you all for the good intentions. Shame on the ISPs for doing this vlan 0 tagging.
-
Can you elaborate on how you getting this working, please provide the details as you follow.
I did follow the reference link you provided and follow the verbatin how-to but still not working on 2.6.0....I am using the igb driver, I even tried executing the pfat script from the shell and it keep giving me an error somehow on line 7. Anyways, any help would be apreciated as this is driving me nuts and had to put back in the closet my pfSense box.
-
I use Frontier, all you should have to do is put the driver fix in first.
Next, put the VLAN 0 script in and create the shellcmd job I run my preshellcmd, make sure you are updating the script to your mac address for the WAN, and using the correct interface IE igb0.
Next just update your WAN interface to ngeth0. Reboot and you should be good to go. But make sure you release your IP. -
@c45p32 if at all possible, can you spare 5 minutes and put a quick how-to for those of us struggling in the integration with 2.6.0. I am using frontier fiber as well. Thank you in advance.