PPPoE - Chap and Pap
I'm seeing that the wiki states that (perhaps in a "home-network" situation?) it is safe to choose either one or the other of the above authentication protocol. Wouldn't it be better to explain that using pap in productivity networks may be harmful (due to the fact that password are sent in clear text)? Lo1 (talk) 20:34, 5 December 2017 (UTC)Lo1
Edit: done. Let me know if you're not comfortable with these changes. Lo1 (talk) 09:33, 7 December 2017 (UTC)Lo1
Starting pppd on boot
I've found that just enabling ppp@.service isn't sufficient for many cases to start on boot. If the interface needed is a virtual device (for some reason) then it will be configured by something else. In most cases using systemd-networkd one can just add a drop-in file for the device which adds Requires=systemd-networkd.service and After=systemd-networkd.service. I'm not sure if this is the optimal approach, but it works for me.
—This unsigned comment is by Aplund (talk) 09:50, 3 January 2018 (UTC). Please sign your posts with ~~~~!
At least for me the journalctl -b --grep=pppd command doesn't show the pppd output.
I need to use journalctl -t pppd (with -f optionally). Should we change this?
Gabriel B. Casella (talk) 21:47, 10 January 2022 (UTC)
PPPoE - name someloginname
In the name field of the PPPoE configuration file, an error occurred if "someloginname" had double quotation marks. It use to be OK, but I think the specification has changed recently. The version of pppd is 2.4.9.
The PPPoE configuration field on the ArchWiki page is name "someloginname" in the name someloginname I think it would be more accurate if it were name "someloginname".