You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since upgrading this specific virtual OPNsense appliance from version 22.7.9 to 24.1.6 (through multiple stages), there has been a nightly PPPoE reconnect at approximately 03:01 every day. This issue was not present before, and there were no nightly reconnects prior to the upgrade.
The ISP in use is 'Deutsche Telekom,' which does not officially mandate nightly reconnects (at most every 180 days). Similar setups at other locations using the same ISP do not experience nightly reconnects either.
There appears to be only one cronjob running at 03:01 (on the first of each month), updating bogons lists. However, this job would only be relevant today (01.05.2024), but the issue has persisted since the update on 27.04.2024.
No relevant config changes have been made since the upgrade.
Question: Has something changed regarding PPPoE, or is there a setting or cronjob for a different user that I may be overlooking, which is running at 03:01 every night?
To Reproduce
Hardly reproducible due to the specificity of external technical requirements (ISP, environment, etc.).
Expected behavior
No nightly reconnects as observed previously.
Describe alternatives you considered
Checking Telekom Forum, OPNsense Forum, Reddit, and my other similar setups for the same issue; ruling out automated backups, cronjobs, and other possible changes to the system.
Relevant log files
Here are logs from two the past two days showing the 'issue' and the reconnect.
22.x to 24.x are thousands of commits. It’s impossible to trace this. Also I think for Telekom the nightly reconnect can still be the norm, maybe you simply didn’t notice before?
22.x to 24.x are thousands of commits. It’s impossible to trace this. Also I think for Telekom the nightly reconnect can still be the norm, maybe you simply didn’t notice before?
Thank you for the swift response. I can delve into logs dating back at least one year, and this behavior distinctly emerged following the upgrades. Initially, I entertained the possibility of overlooking it previously, but the timing aligns precisely with the update. While it's plausible that some alteration occurred on the ISP's end coincidentally, it would seem rather arbitrary.
As for the nightly reconnect, it appears to deviate from the norm, at least in comparison to my other Telekom setups. Until now, this particular setup has mirrored others in its stability.
Could there be a new cronjob scheduled to run at that time?
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Describe the bug
Since upgrading this specific virtual OPNsense appliance from version 22.7.9 to 24.1.6 (through multiple stages), there has been a nightly PPPoE reconnect at approximately 03:01 every day. This issue was not present before, and there were no nightly reconnects prior to the upgrade.
The ISP in use is 'Deutsche Telekom,' which does not officially mandate nightly reconnects (at most every 180 days). Similar setups at other locations using the same ISP do not experience nightly reconnects either.
There appears to be only one cronjob running at 03:01 (on the first of each month), updating bogons lists. However, this job would only be relevant today (01.05.2024), but the issue has persisted since the update on 27.04.2024.
There are no further cronjobs in the GUI.
No relevant config changes have been made since the upgrade.
Question: Has something changed regarding PPPoE, or is there a setting or cronjob for a different user that I may be overlooking, which is running at 03:01 every night?
To Reproduce
Hardly reproducible due to the specificity of external technical requirements (ISP, environment, etc.).
Expected behavior
No nightly reconnects as observed previously.
Describe alternatives you considered
Checking Telekom Forum, OPNsense Forum, Reddit, and my other similar setups for the same issue; ruling out automated backups, cronjobs, and other possible changes to the system.
Relevant log files
Here are logs from two the past two days showing the 'issue' and the reconnect.
Environment
The text was updated successfully, but these errors were encountered: