OPNsense Forum
Archive => 19.1 Legacy Series => Topic started by: schnipp on January 30, 2019, 06:07:55 pm
-
Opnsense 19.1 will be released the next time. Thank you to all who made this happen. I was really happy that the problem with PPPoE reconnect loops will get solved in this version. Unfortunately, a bugfix has been postponed again.
Without a bugfix opnsense stops working after every update and it is difficult to patch the system by hand because every reconnect attempt rises the state reset feature to clean up the NAT tables. This was introduced to keep SIP communication working after ISP initiated IP address change.
The previous part of the whole thread began with Opnsense 18.1: see here (https://forum.opnsense.org/index.php?topic=7270.90).
Is there a chance to get the problem solved before release 19.7?
-
Last ticket update on https://github.com/opnsense/core/issues/2267 on 26 Jun 2018. As stated elsewhere, please complain early *and* often.
My work queue that is based on 100% self-funding after my 40 hour day job entirely away from OPNsense is maxed out either way. I can only prioritise according to user feedback and progress.
Cheers,
Franco
I know how much time you and the other core members spent in programming within this project, many thanks for that. I help to improve things by testing, investigating bugs, giving hints and so forth. To investigate and isolate the PPPoE bug took me a long time. This bug affects a lot of people, especially those using 1&1 as ISP.
I reported and described the bug at github, so that everybody is able to comprehend what the real issue is. The bug is still open and will not solve itself. Currently, I use a workaround to make Opnsense work. But after a system update, the workaround gets overwritten and I have to reapply the temporary patch which is difficult because of regularly upcoming "state resets".
Ok, do you need any additional input, to proceed in solving this issue?
-
As I am experiencing the same issues with PPPoE reconnect loops I would be interested in a bugfix, too.
It's a pity that this issue hasn't been fixed yet.
Nevertheless, many thanks to all those who are contributing to the success of OPNsense.
-
I have applied the patches 5f4315c and 2806a0c in version 19.1.7 (see here (https://github.com/opnsense/core/issues/2267#issuecomment-494129737)).
Can I safely update to version 19.1.8 while the already applied patches won't get overwritten?
-
Patches will always be overwritten on updates for safety reasons.
Wait for tomorrow's 19.1.9 that has 5f4315c embedded so it only needs 2806a0c on top.
> It's a pity that this issue hasn't been fixed yet.
It was said a couple of times: there is no active dev for PPPoE so that is a self-made issue for better or worse. We advocate all possible solutions outside of OPNsense as long as they work.
Cheers,
Franco
-
After updating to v.19.1.9 and applying patch 2806a0c LCP echo requests are still immediately answered :)
-
Thanks, slowly warming up to the idea of bringing 2806a0c into 19.1.10 to conclude this adventure. Ayes to the left, noes to the right.... :D
Cheers,
Franco
-
After updating to v.19.1.9 and applying patch 2806a0c LCP echo requests are still immediately answered :)
Are you using OpenVPN? I've tried to use this patch to solve my PPPoE issue. It seems to help so far, but now I'm running in OpenVPN issues:
https://forum.opnsense.org/index.php?topic=11553.msg60518#msg60518