On Mon, 25 Mar 2024 14:48:23 -0700 Samuel Sieb samuel@sieb.net wrote:
On 3/25/24 11:52, Franta Hanzlík via users wrote:
After upgrading my gateway x86_64 Linux box to F39, my VDSL connection to internet does not work, although I have all the necessary packages (network-scripts, ppp, rp-pppoe) installed. And it all worked correctly on the previous F37 system. After some investigation the cause was clear - network-scripts ifup-ppp runs adsl-start - and this script not exist in rp-pppoe-4.0-2.fc39.x86_64 package, but was in older rp-pppoe-3.15-4.fc37.x86_64.rpm (as symlink to pppoe-start - which now also is not in the rp-pppoe-4.0 package.
It seem as in F39 also is not pppoe.service systemd unit - which would also be a possible solution for an xDSL connection.
About NetworkManager - I read that it can not do system-wide VPN - which I also need (net-to-net OpenVPN connection).
What do you mean by "system-wide"? I use it for site to site VPN.
System-wide should be connections, which are not user-dependent (i.e. connections, which starts immediately after system boot up. - as typical for servers). Unlike user connections, which are activated only after the user logs in. And what I saw somewhere was that VPN connections can only be of the second kind - user initiated. But maybe it was some old information and now system-wide VPN connection is now also possible? I confess that I hardly know the NetworkManager, or only its graphical interface...
Is there any reasonable xDSL connection solution in this F39 distro?
(For now I downgrade rp-pppoe-4.0-2.fc39 to rp-pppoe-3.15-4.fc38, but it is probably not very promising (the network-scripts package seems be deprecated))
Right, don't use network-scripts. Use "nm-connection-editor" for creating the PPPoE connection. I think upgrading to F39 would have converted all your ifcfg files to NetworkManager connection files anyway.
I have always preferred network-scripts over NetworkManager on the server, for its reliability and stability. And why should a useless program run on the server when I only need to activate the interface at startup and then nothing else? (a few (10?) years back I had an unpleasant experience with the NetworkManager when, after restarting a remote multihome server, it set the routing so badly that the machine became unreachable. Is it time to trust him again?).