Upgrade to 2.4.1 cant connect to pppoe wan over vlan
-
i just updated to 2.4.1 on the apu2 and now cant connect to wan at all which is pppoe over vlan
-
this is a known issue, will be fixed in 2.4.2.
I dont know if its fixed in the current 2.4.2 dev branch.
-
for now i had to rename all igb.20 to igb1_20 to make it connect, why would they release it with such a bug
-
for now i had to rename all igb.20 to igb1_20 to make it connect, why would they release it with such a bug
I have two pppoe interface over VLAN
lagg0.1000
lagg0.835
and doesn't works…how can i rename for working?
-
Once again, reading the release notes is important: https://www.netgate.com/blog/pfsense-2-4-1-release-now-available.html
https://redmine.pfsense.org/issues/7981
-
for now i had to rename all igb.20 to igb1_20 to make it connect, why would they release it with such a bug
It was allegedly done because of some ARM nonsense where some genius decided to name the interface mvneta and they found that it was too long after beginning to sell hardware with those. (Those are the SG3100 units than can be recycled as paperweight once your one year support has ended and you need to reinstall, since there are no public ARM images available.)
Renaming interfaces is about the most critical thing you can mess with on a networking gear such as firewall. So, of course a minor bugfix release is an excellent opportunity to change those, completely untested and after 2.4 has been tested for ~1 year. Sigh.
Once again, reading the release notes is important: https://www.netgate.com/blog/pfsense-2-4-1-release-now-available.html
https://redmine.pfsense.org/issues/7981
Yeah, once again, noone sane makes and expects such changes at this time point.
-
(Those are the SG3100 units than can be recycled as paperweight once your one year support has ended and you need to reinstall, since there are no public ARM images available.)
I don't think so: https://forum.pfsense.org/index.php?topic=126627.msg757029#msg757029
The SG-3100 will have a recovery partition which will allow you to always reinstall your SG-3100 without downloading images. You will always be able to use the factory version, not Community Edition.
-
I don't think so: https://forum.pfsense.org/index.php?topic=126627.msg757029#msg757029
This doesn't work once the storage dies, plus it doesn't work when you screw up that partition either. Again, silly games that serve no useful purpose beyond being a royal PITA for users who decided to spend their money on buying Netgate hardware. (No, you cannot take those images and recycle them for other ARM boxes, ARM is not an Intel PC, so it just doesn't work like that.)
I don't care about ARM and wouldn't buy any of those boxes from Netgate either due to the above reasons… this weirdo platform is something I'd happily ignore altogether (there's not much to write home about when it comes to ARM on routers, things like Cavium Octeon are whole lot more interesting when it comes to packet processing/UTM/DPI etc.) – if only it didn't harm the vast majority of users. There's a bunch of fixes and improvements that didn't make it to 2.4, the reason often being that more testing is required. Then you go, and start messing with kernel behind the scenes, breaking the OS altogether in RC phase. After that gets fixed and the long overdue release finally goes out, you commit apparently untested super-intrusive stuff into the very first patch version, even knowing that it's broken before you actually release that. All of that due to some niche super-minority platform you started selling a couple of days earlier.
Sigh.
-
Since this also screwed up my PPPOE unexpectedly - where can I get 2.4.0 to roll back? I have the config.xml but only see 2.4.1 for download…
Thx!
-
for now i had to rename all igb.20 to igb1_20 to make it connect, why would they release it with such a bug
I have two pppoe interface over VLAN
lagg0.1000
lagg0.835
and doesn't works…how can i rename for working?
u need to rename under the pppoe as well as the vlan section in the config file, works well for me so far
-
vi /conf/config.xml
:%s/lagg0./lagg0_/g
:wq
reboot
should solve problem -
u need to rename under the pppoe as well as the vlan section in the config file, works well for me so far
Thx - that was much easier than rolling back. Wouldn't have thought this is in config.xml but good to see!
-
vi /conf/config.xml
:%s/lagg0./lagg0_/g
:wq
reboot
should solve problemTried it an it seems I have now broke it.
Fed up with it at the moment. Unbelievable that they have released this update with this broken bit..
Will try again tomorrow.. Or so
-
where can I get 2.4.0 to roll back?
Just for the record: https://atxfiles.pfsense.org/mirror/downloads/
-
@Satras:
vi /conf/config.xml
:%s/lagg0./lagg0_/g
:wq
reboot
should solve problemTried it an it seems I have now broke it.
Fed up with it at the moment. Unbelievable that they have released this update with this broken bit..
Will try again tomorrow.. Or so
you can try roll back config to previous state then just upgrade to 2.4.2 (dev branch) as there problem is fixed
then set in upgrade section htat you wish to use stable branch.
it will not downgrade, but will upgrade you to stable with 2.4.2 release ;) -
That's what I have planned for tomorrow.
What is the best way to roll back? Do a clean install and use the config backup of 2.4.0 version?
-
TBH, douche move to do this in a maintenance release. Broke PPP. Rolled back via VM Snapshot…
I didn't read the release notes fully, but it's a maint release shortly after a major release. The below came in the newsletter - so basically I expected a KRACK patch and stability fix. Not to have the PPP stack entirely borked, which was found in tested and pushed out anyway.
PPP might not be all that widely used, but I expected things to break in 2.4.0 and planned accordingly, as would the people who did the upgrade to 2.4.0 and found the VLAN problems. I didn't expect the same from 2.4.1
pfSense software version 2.4.1 release
We are excited to announce the release of pfSense software version 2.4.1, now available for new installations and upgrades!
pfSense software version 2.4.1 is a maintenance release bringing security patches and stability fixes for issues discovered in pfSense 2.4.0-RELEASE, including a patch for the recently announced WPA-2 KRACK vulnerability.
pfSense 2.4.1-RELEASE updates and installation images are available now!
-
It was allegedly done because of some ARM nonsense where some genius decided to name the interface mvneta and they found that it was too long after beginning to sell hardware with those.
I suggest you fix your attitude.
Those are the SG3100 units than can be recycled as paperweight once your one year support has ended and you need to reinstall, since there are no public ARM images available.
This is incorrect. You can always reinstall your SG-1000 using its image that's available on portal.pfsense.org. After 1 year, portal access, not support as no support is bundled with the device, is locked out BUT you can still use SG-1000, continue to update it or reinstall it using the image. Please refrain from making such wrong conclusions.
-
TBH, douche move to do this in a maintenance release. Broke PPP. Rolled back via VM Snapshot…
I didn't read the release notes fully, but it's a maint release shortly after a major release.
Then start reading the release notes or at least the announcement blog post. "douche move" remark is not nice.
-
for now i had to rename all igb.20 to igb1_20 to make it connect, why would they release it with such a bug
It was allegedly done because of some ARM nonsense where some genius decided to name the interface mvneta and they found that it was too long after beginning to sell hardware with those. (Those are the SG3100 units than can be recycled as paperweight once your one year support has ended and you need to reinstall, since there are no public ARM images available.)
Renaming interfaces is about the most critical thing you can mess with on a networking gear such as firewall. So, of course a minor bugfix release is an excellent opportunity to change those, completely untested and after 2.4 has been tested for ~1 year. Sigh.
Once again, reading the release notes is important: https://www.netgate.com/blog/pfsense-2-4-1-release-now-available.html
https://redmine.pfsense.org/issues/7981
Yeah, once again, noone sane makes and expects such changes at this time point.
Doktornotor,
Point in-fact the "too long" was due to some work done (by people who are now gone) to use "interfacename<unit>_vlan<number>" in pfSense.
What we did is to repair the pfSenes code to use the FreeBSD standard "interfacename<unit>. <number>where <number here="" is="" the="" vlan="" tag".<br="">As you should be well-aware, choices made over the last decade mean that pfSense can be quite difficult to maintain.
This did not occur "after beginning to sell hardware" as you assert. You are 100% wrong on this point, and you need to retract. 2.4.0-RELEASE occurred prior to SG-3100 entering a shipping state, and, in fact, the earliest release of pfSense for the SG-3100 is 2.4.1-RELEASE.
This "mvneta" name did not come from us, it came from Semihalf, via FreeBSD.
Many people are misinformed about being able to get reload images for Netgate platforms. You perpetuate the myth, and I think only to gain advantage.You've made several false statements in the above, and denigrated members of the team.
We've been here before. Back down the rhetoric, and retract the above, or go somewhere else.
You have zero more chances, and I am 100% serious on this point. Criticism is fine, but lying is not.</number></number></unit></number></unit>
