core
core copied to clipboard
PPPoE set idle timeout not working when INT value is 0.
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
- [x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
- [x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue
Describe the bug Unable to save PPPoE config after idle timeout is 0.
Tip: to validate your setup was working with the previous version, use opnsense-revert (https://docs.opnsense.org/manual/opnsense_tools.html#opnsense-revert)
To Reproduce
Steps to reproduce the behavior:
- Go to 'Interfaces'
- Click on 'WAN'
- Make sure WAN is PPPoE mode
- Scroll down to 'Idle timeout' and set a value that is 0
- Save
- Error "The field Idle timeout value is required." is seen
Expected behavior
Save and do other things :>
Environment
OPNsense 24.1.7 (amd64). Intel® Xeon™ E5-2673v3 @2.4GHz Network Intel® 82576 Quad Port Network Intel® X520-DA1
help text should probably be changed, if you choose Dial on demand a timeout is required, otherwise leaving it empty or 0 omits the value from the configuration.
https://github.com/opnsense/core/blob/af3d45c1e18434e712f8f3a1f07cc4ee1425bb06/src/www/interfaces.php#L686-L694
https://github.com/opnsense/core/blob/af3d45c1e18434e712f8f3a1f07cc4ee1425bb06/src/www/interfaces.php#L2423-L2432
So I suppose to set a timeout for Dial On Demand? @AdSchellevis
it looks like it, yes, but this has been in here for ages, I don't think a lot of people actually use dial on demand with PPPoE. looking briefly at the code, dropping the constraint doesn't hurt either likely (although it seems a but silly to need a connection which is not always open, but when it starts, should never close).
This issue has been automatically timed-out (after 180 days of inactivity).
For more information about the policies for this repository, please read https://github.com/opnsense/core/blob/master/CONTRIBUTING.md for further details.
If someone wants to step up and work on this issue, just let us know, so we can reopen the issue and assign an owner to it.