Re: xDSL + network-scripts connection not working in Fedora 39

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 25 Mar 2024 18:47:37 -0700
Samuel Sieb <samuel@xxxxxxxx> wrote:

> On 3/25/24 17:31, Franta Hanzlík wrote:
> > On Mon, 25 Mar 2024 14:48:23 -0700
> > Samuel Sieb <samuel@xxxxxxxx> wrote:
> >   
> >> On 3/25/24 11:52, Franta Hanzlík via users wrote:  
>  [...]  
> >>
> >> 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...  
> 
> Even wifi connections are "system-wide" connections.
> And whatever information you had about VPNs is very old.  I've used NM 
> for that for a long time.

Really? Especially with WiFi connections, I thought they were in some user 
private profiles, for use only by a specific user... Hmm...
I seem to be behind the times. ;)

>  [...]  
> >>
> >> 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?).  
> 
> I've been using it for a long time on a remote many-homed server with no 
> issues and it doesn't use enough memory to bother me.

That sounds encouraging, I'll try to get through the NetworkManager - I 
guess I won't have any other choice...

Samuel, many thanks!
-- 
Franta Hanzlik
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux