How to get pfSense WAN to accept VLAN 0
-
Hmm, I expect earlyshellcmd to work since that's what pfatt uses.
The only other alternatives are to add ngeth to the list on interfaces excluded from the check or to change the interface name the script uses to something that's already excluded.:
https://github.com/pfsense/pfsense/blob/master/src/etc/inc/util.inc#L2401Steve
-
@stephenw10 I think your right, in the boot process I see this:
sh: Syntax error: end of file unexpected (expecting word)
Updating configuration...done.
Warning: Configuration references interfaces that do not exist: ngeth0 -
@stephenw10 I think i have the syntax wrong for the earlyshellcmd. The vlanzero file is on root:
<earlyshellcmd>/vlanzero2</earlyshellcmd> -
Ah, OK. Yeah that's not right, it's not running. You need to specify the complete path to the file.
I would put it in the 'root' folder not the root of the filesystem, so:<earlyshellcmd>/root/vlanzero2.sh</earlyshellcmd>That's what I expect there.
-
Thanks so much for your help!
I had that from the start and it did not work. I checked the config.xml file and the shellcmd package was putting extra stuff in there. So I removed the package and edited the config file manually and viola! it worked. Only thing left id to test the internet connection when I get home.
-
Interesting. The shellcmd package works fine AFAIK. I have it running scripts here on several boxes.
-
@stephenw10
It worked fine on my other pfsense box as well. Strange huh?
Anyway I wanted to let you know i got it working minus a couple of issue:- Unable to get DHCP6 addrss.
- Looks like a took a little bit of a speed hit as well.
I'd love to hear any suggestions you have, you totally helped me out.
Thanks -
There's some discussion of v6 on the pfatt pages. May or may not be related. If it's just dhcpv6 I would expect it to be pulled over vlan0 like v4. So there's probably something else going on there.
Everything has to go through netgraph so I would expect a lot more CPU cycles to be required. There may be some tuning options it's not something I've ever looked into.
Try runningtop -aSHand see how the loading is spread across the CPU cores. Something might be single threaded now.Steve
-
@natbart just want to say thanks for figuring this out, it’s working great for me so far. just recently upgraded Fibe and my HH3000 would literally just freeze when maxing the connection out. Ecstatic that I can finally drop kick that POS and just have my pfsense box. Glad you didn’t give up and managed to figure it out. Great work.
-
@natbart Here is another thank you for the hard work you did. I am posting this via my Frontier Fiber modem through a SG-3100 running your netgraph script. Appreciate all the help. Also a shoutout to @stephenw10 for lots of posts and replies before we figured out where my problem lay.
-
J jaredo referenced this topic on
-
J jaredo referenced this topic on
-
@jaredo - Your welcome. It was definitely a learning experience! Glad I could help others out, the same way the community helped me find this out.
Have you tried it with 2.5.x? I am still on 2.4.5-RELEASE-p1 (amd64) and worried to upgrade. Please let me know.
-
@natbart said in How to get pfSense WAN to accept VLAN 0:
Have you tried it with 2.5.x? I am still on 2.4.5-RELEASE-p1 (amd64) and worried to upgrade. Please let me know.
I am using a SG-3100 at our office (the fiber location) so I am running 21.05.2-RELEASE (arm) which is 2.5.x on the community edition. Been running for the last week without any issues. I would say it is safe for you to update.
-
@natbart also no issues here running the latest version here, using the community version 2.5.2.
-
Don't upgrade to 2.6.0 or CE 22.01 it breaks the vlan0 script. The script runs without errors, and you can assign the correct interface to WAN, but it won't get an ip address from your ISP. Tried this on 2 routers and got the same result. Rolled back to 2.5.2 and everything works again. This is just a heads up to people wanting to use this script.
-
@c45p32 What NICs are you using?
This is almost certainly the same issue pfatt users are seeing.Steve
-
Both routers use intel nics.
-
Assuming they are em or igb loading Intels driver will probably fix it as shown here:
https://github.com/MonkWho/pfatt/issues/67#issuecomment-1043358822Not a permanent solution but would confirm the problem.
Steve
-
Oh... Thank You! One is em and the other is igb, so I will give this a try later night.
-
Tested the driver and was still not able to get an IP address.
-
Would probably only work if it's igb carrying vlan 0 there. If it's em you'd need that instead.
Steve
