How to get pfSense WAN to accept VLAN 0
-
Yes, the script still works.
-
@c45p32 thanks! I thought I had seen some messages fly that my script stopped worked in 2.5.x & 2.6.x?
-
@natbart Do not go to 2.6, it will break....I am still under 2.5.2 and it does work in that release....we are all waiting for a fix on 2.6.
I am thinking about jumping ship to OPNSENSE, but I love pfsense so much that I am debating at this point since I dont know for sure its fix under OPNsense....I dont have a spare box to test and can't afford to have the wife without internet.
-
@natbart I am using igb0-igb4 network cards.
-
I’m using igb0 on 22.05, and I used the same script on 2.6.0 without issue.
-
@cucu007 said in How to get pfSense WAN to accept VLAN 0:
@natbart Do not go to 2.6, it will break....I am still under 2.5.2 and it does work in that release....we are all waiting for a fix on 2.6.
I am thinking about jumping ship to OPNSENSE, but I love pfsense so much that I am debating at this point since I dont know for sure its fix under OPNsense....I dont have a spare box to test and can't afford to have the wife without internet.
It is fixed on opnsense.
-
What exactly is fixed there? The e1000 driver handling of VLAN0 tagged traffic?
Or it accepts priority tagged traffic without a netgraph script? Though I guess that would also require en e1000 driver fix.
Steve
-
@stephenw10 - can you comment on the ability to move past 2.4.5 and still have my script tag VLAN 0 traffic and work with my em0/em1?
Both ethernet ports are using Intel chipsets:
LAN1 = i217-LM
LAN2 = 82583V -
@jarhead Thank you jarhead for the confirmation.
Its taking Netgate way too long to fix this problem, I am not sure if we dont have adecuate people working on the development of this solution....but if it is indeed fixed under OPNsense why can pfsense that has been longer in the market than OPN able to fix this? I dont understand.
-
As I understand it opnsense inherited this fix with the move to FreeBSD 13. That will happen in pfSense when we move from 12-stable in the next release.
Developer time is limited and the resources required to backport it to 12 are not justified for the relatively small number of users who are hitting it. Especially when there are workarounds and it will be fixed anyway by the base update.Steve
-
@stephenw10 Steve, should we expect this ot be fix under 2.7?
is there a timely for the 2.7 release, at least is there a month where the Negate team is planning this released?
-
@cucu007 said in How to get pfSense WAN to accept VLAN 0:
should we expect this ot be fix under 2.7?
Since the dev snapshots you can get now currently list 12.3 stable, I would find it surprising that they would move to freebsd 13 in mid development. Anything is possible I guess - but if I was going to place a bet, my bet would be that wouldn't happen.
-
@johnpoz Steve, can you shine some light on this rationale?
-
2.7 is just a number after 2.6.
The actual version used is not determined until a release branch is created. I expect CE snapshots to be re-based before that happens given the current development work.
Steve
-
@stephenw10 said in How to get pfSense WAN to accept VLAN 0:
I expect CE snapshots to be re-based before that happens given the current development work
Steve,
What does this mean "I expect CE snapshots to be re-based before that happens given the current development work"
Are we expected to see this fix on the next release or not?
-
If the fix you mean is in the e1000 driver that is part of FreeBSD 13 then, yes, I expect that to be in CE snapshots before a 2.7 release is branched.
Steve
-
@stephenw10 Thank you Steve for the confirmation, as you know this is driving some of us insane. :-)
-
@stephenw10 said in How to get pfSense WAN to accept VLAN 0:
If the fix you mean is in the e1000 driver that is part of FreeBSD 13 then, yes, I expect that to be in CE snapshots before a 2.7 release is branched.
Steve
Just to clarify, you said the e1000 driver is already in the 2.7 snapshots, yet the vlan0 issue is not fixed by that. Just tried the latest to verify again. Vlan0 is still not working in it.
Are you saying the vlan0 fix is to be added to 2.7 at a later date?
-
He is hinting pfsense v2.7 will probably be based on BSD v13 by the time it is released.
But he isn’t going to guarantee it because he does not know what problems will be encountered until after it is done and can’t be certain it will fix your problem until your problem has been tested with the v2.7 release.
-
@patch said in How to get pfSense WAN to accept VLAN 0:
He is hinting pfsense v2.7 will probably be based on BSD v13 by the time it is released.
But he isn’t going to guarantee it because he does not know what problems will be encountered until after it is done and can’t be certain it will fix your problem until your problem has been tested with the v2.7 release.
Oh, I didn't get that at all. From what I understood from his "hint", they ported the e1000 driver thinking that would fix the vlan0 issue. But I don't think that's the fix we all want. Meaning it doesn't fix vlan0 compatibility.
Edit;
On another note, does anyone know if that script works on the chelsio (cxlx) driver?
