Hello IPFire community,
With the upcoming Core-Update 179 integrating PPP 2.5.0, it’s paramount that we test our array of dial-up connections, with a special emphasis on the PPPoE bridging functionality, given its prevalent use and the major changes in the PPP update.
Key Connection Types to Test:
- PPPoE (Priority): Ensure seamless connection establishment, stability, and termination. Due to the significant changes in PPP 2.5.0, our primary attention should be on the PPPoE connection.
- VDSL: Verify PPPoE via VLAN functionality.
- Modem: Test connections via different modems, including 3G and 4G (LTE) wireless modems.
- Serial: Validate direct serial links without modems.
- PPTP & PPxxx over ATM-BRIDGE: While perhaps less common, ensure that these connections are also operational.
Focused Testing Points for PPPoE:
- Dial-in Options: Review the ‘Idle timeout’ behavior and the Dial-on-Demand mode.
- Authentication: Test both PAP and CHAP authentication methods.
- Reconnection Behavior: Examine IPFire’s handling of disconnections.
- Additional Settings: Check non-default settings like MTU adjustments.
Feedback Format:
- Connection Type:
- Issue/Feedback:
- Steps to reproduce:
- Configuration (if applicable):
- Logs or Error Messages:
If you’re unfamiliar or need a refresher on IPFire’s dial-up configurations, the IPFire wiki is a comprehensive resource.
Your assistance in testing this vital update is invaluable. By ensuring stability and functionality across all connection types, especially PPPoE, we’re paving the way for a robust and reliable release for the entire community.
Thank you for your unwavering support and commitment to IPFire.
Admin: Please feel free to edit this post for relevancy.
Best, A G
1 Like
Following up on the initial call for testing, I wanted to share my own findings regarding the PPPoE connections post Core-Update 179.
System Update and Reboot:
Upon applying the update and rebooting my IPFire firewall, I noticed that the PPP version has indeed been updated to 2.5.0 as indicated in the logs.
Logs Overview:
13:25:05 pppd[5192]: Modem hangup
13:25:05 pppd[5192]: Connect time 2936.2 minutes.
13:25:05 pppd[5192]: Sent 2901882632 bytes, received 2170197149 bytes.
13:25:05 pppd[5192]: Connection terminated.
13:25:07 pppd[5192]: Exit.
13:25:52 pppd[2205]: Plugin pppoe.so loaded.
13:25:52 pppd[2205]: PPPoE plugin from pppd 2.5.0
13:25:52 pppd[2205]: pppd 2.5.0 started by root, uid 0
13:25:52 pppd[2205]: Failed to create pid file /usr/var/run/pppdppp-ipfire.pid: No such file or directory
13:25:57 pppd[2205]: PPP session is 11
13:25:57 pppd[2205]: Connected to AA:BB:CC:DD:EE:FF via interface red0
13:25:57 pppd[2205]: Using interface ppp0
13:25:57 pppd[2205]: Failed to create pid file /usr/var/run/pppdppp0.pid: No such file or directory
13:25:57 pppd[2205]: Failed to create pid file /usr/var/run/pppdppp-ipfire.pid: No such file or directory
13:25:57 pppd[2205]: Connect: ppp0 <--> red0
13:25:57 pppd[2205]: CHAP authentication succeeded
13:25:57 pppd[2205]: CHAP authentication succeeded
13:25:57 pppd[2205]: peer from calling number AA:BB:CC:DD:EE:FF authorized
13:25:57 pppd[2205]: local IP address 192.168.XX.XX
13:25:57 pppd[2205]: remote IP address 10.XX.XX.XX
13:25:57 pppd[2205]: primary DNS address XXX.XX.X.XXX
13:25:57 pppd[2205]: secondary DNS address XXX.XX.X.XXX
Observations:
- The connection gets established successfully after the update and the reboot.
- There are errors related to the creation of pid files:
/usr/var/run/pppdppp-ipfire.pid and /usr/var/run/pppdppp0.pid. This indicates that the respective directories might be missing or there could be permission issues. These errors should be looked into for rectification.
It’s essential for other community members to also share their findings, especially if they are facing similar issues or different challenges. This collective effort will ensure that any anomalies get addressed and result in a more refined final release.
Best regards,
A G
3 Likes
Core Update 179 Testing has not yet been issued for testing, although I think it is pretty close to it.
Can everyone testing out the PPP-2.5.0 in CU179 Testing add any comments into the bug report.
https://bugzilla.ipfire.org/show_bug.cgi?id=13164
Your IPFire People email address and password will act as your login credentials for the IPFire Bugzilla.
2 Likes
It looks like there needs to be an additional configure option to define the correct pid path. Currently it is using the PREFIX of /usr, which is incorrect.
I will do an update of that.
3 Likes
Hi @adamgibbo and all,
The patch for fixing the pid directory to /var/run has been submitted and merged and is now in the latest build of Core Update Testing.
To update to that version then edit /opt/pakfire/db/core/mine to change the entry from 179 to 178.
Then go to the pakfire menu page and refresh the lists and then you should see the Core Update 179 release again. This will then upgrade your system to the latest CU179 version.
3 Likes
Thanks @bonnietwin I appreciate your time and efforts in updating this package.
Following @bonnietwin’s update, I’ve updated and monitored the logs for the most recent build of Core Update 179. Here are my findings post-patch:
Log:
18:20:52 pppd[16899]: Modem hangup
18:20:52 pppd[16899]: Connect time 3968.4 minutes.
18:20:52 pppd[16899]: Sent 2767761688 bytes, received 1668173239 bytes.
18:20:52 pppd[16899]: Connection terminated.
18:20:54 pppd[16899]: Exit.
18:21:39 pppd[2206]: Plugin pppoe.so loaded.
18:21:39 pppd[2206]: PPPoE plugin from pppd 2.5.0
18:21:39 pppd[2206]: pppd 2.5.0 started by root, uid 0
18:21:44 pppd[2206]: PPP session is 1
18:21:44 pppd[2206]: Connected to AA:BB:CC:DD:EE:FF via interface red0
18:21:44 pppd[2206]: Using interface ppp0
18:21:44 pppd[2206]: Connect: ppp0 <--> red0
18:21:44 pppd[2206]: CHAP authentication succeeded
18:21:44 pppd[2206]: CHAP authentication succeeded
18:21:44 pppd[2206]: peer from calling number AA:BB:CC:DD:EE:FF authorized
18:21:45 pppd[2206]: local IP address 192.168.XX.XX
18:21:45 pppd[2206]: remote IP address 10.XX.XX.XX
18:21:45 pppd[2206]: primary DNS address XXX.XX.X.XXX
18:21:45 pppd[2206]: secondary DNS address XXX.XX.X.XXX
Observations:
- The connection was successfully terminated and re-established.
- The previous errors related to the creation of pid files seem to be resolved post-patch.
Regards.
A G
3 Likes
Running CU 179 Testing for a couple of days, OK so far.
My IPFire reconnects daily to get a new WAN IP and again, OK so far.
Fibre MODEM by the way.
3 Likes
Happy Friday!
I’m writing with an update on the PPP package anomaly reported by @pmueller for Core Update 179. Peter observed a system log message post-upgrade indicating potential concerns:
Aug 23 16:12:24 maverick kernel: pppd uses obsolete (PF_INET,SOCK_PACKET)
Following this discovery, @AdolfBelka identified a related issue on the PPP GitHub page. Before the official fix in version 2.5.1, a patch has been made available for IPFire. Detailed information and discussions can be found here and here.
This patch is now integrated into Core Update 179 Testing. I encourage those interested to update again and test this version. I’ll be conducting my tests later today and will share the outcomes here.
Your feedback is invaluable. Let us know your findings.
Regards,
A G
2 Likes
Hello everyone,
I hope you’re all doing well.
I’ve updated and restarted my IPFire firewall to the new testing release, and I can confirm that the bug observed by @pmueller and also present in my logs (though I initially did not see it) has been resolved.
Log Post-Update:
18:23:21 pppd[15842]: Modem hangup
18:23:21 pppd[15842]: Connect time 6894.4 minutes.
18:23:21 pppd[15842]: Sent 760791880 bytes, received 3009721987 bytes.
18:23:21 pppd[15842]: Connection terminated.
18:24:08 pppd[2467]: Plugin pppoe.so loaded.
18:24:08 pppd[2467]: PPPoE plugin from pppd 2.5.0
18:24:08 pppd[2467]: pppd 2.5.0 started by root, uid 0
18:24:13 pppd[2467]: PPP session is 24
18:24:13 pppd[2467]: Connected to AA:BB:CC:DD:EE:FF via interface red0
18:24:13 pppd[2467]: Using interface ppp0
18:24:13 pppd[2467]: Connect: ppp0 <--> red0
18:24:13 pppd[2467]: CHAP authentication succeeded
18:24:13 pppd[2467]: CHAP authentication succeeded
18:24:13 pppd[2467]: peer from calling number AA:BB:CC:DD:EE:FF authorized
18:24:13 pppd[2467]: local IP address 192.168.XX.XX
18:24:13 pppd[2467]: remote IP address 10.XX.XX.XX
18:24:13 pppd[2467]: primary DNS address XXX.XX.X.XXX
18:24:13 pppd[2467]: secondary DNS address XXX.XX.X.XXX
Observations:
- The previous issue with the message
'pppd uses obsolete (PF_INET,SOCK_PACKET) is now resolved.
- The connection was terminated and re-established successfully without any issues.
In summary, the updated release appears stable in my setup and addresses the previously noted issues.
Thanks to @AdolfBelka and everyone involved.
Best regards,
A G
3 Likes