Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
ifupdown legacy(?)
ifupdown legacy(?)
Greetings!
The author of Debian Reference marked ifupdown as "legacy".
I can't figure out, what is the nowadays relevant alternative for interfaces configuration.(I mean it.)
https://www.debian.org/doc/manuals/debi ... own_legacy
The author of Debian Reference marked ifupdown as "legacy".
I can't figure out, what is the nowadays relevant alternative for interfaces configuration.(I mean it.)
https://www.debian.org/doc/manuals/debi ... own_legacy
- GarryRicketson
- Posts: 5644
- Joined: 2015-01-20 22:16
- Location: Durango, Mexico
Re: ifupdown legacy(?)
https://en.wikipedia.org/wiki/Legacy_system
There is more results, you just need to do some research, and read dome documentatation.
"What we expect you have already Done"
==========
Old Website
======================
For the Birds
==================
What Does a Parrot Know About PTSD?
==========
Old Website
======================
For the Birds
==================
What Does a Parrot Know About PTSD?
Re: ifupdown legacy(?)
GarryRicketson, thank you for you answer,
the statement "The system works satisfactorily, and the owner sees no reason to change it." from the Wikipedia article would, in turn, satisfy me in this case. So far, I've encountered support for wpa_supplicant, hostapd and openvswitch* Debian packages in ifupdown. Despite the documentation being a bit of a mess for ifupdown, so far the ifupdown itself seems very convenient and flexible enough with it's mapping feature and pre/post-up/down scripts.
I still don't get it... I am very confused with ifupdown marked as "legacy" in the Reference, since the term "legacy" implies "outdated". So my question is: did the author of the Reference mean network-manager or did he mean something else, which I am totally missing.
the statement "The system works satisfactorily, and the owner sees no reason to change it." from the Wikipedia article would, in turn, satisfy me in this case. So far, I've encountered support for wpa_supplicant, hostapd and openvswitch* Debian packages in ifupdown. Despite the documentation being a bit of a mess for ifupdown, so far the ifupdown itself seems very convenient and flexible enough with it's mapping feature and pre/post-up/down scripts.
I still don't get it... I am very confused with ifupdown marked as "legacy" in the Reference, since the term "legacy" implies "outdated". So my question is: did the author of the Reference mean network-manager or did he mean something else, which I am totally missing.
- GarryRicketson
- Posts: 5644
- Joined: 2015-01-20 22:16
- Location: Durango, Mexico
Re: ifupdown legacy(?)
Your welcome.
else probably will not work, or is entirely experimental.
I am very confused with ifupdown marked as "legacy" in the Reference, since the term "legacy" implies "outdated".
I don't know really, but it might be a matter of perspective,...I have never thought of "legacy" meaning outdated, at all, in fact , when I see that it is "legacy", I know it probably will work for me, anything----did he mean something else, which I am totally missing.
else probably will not work, or is entirely experimental.
"What we expect you have already Done"
==========
Old Website
======================
For the Birds
==================
What Does a Parrot Know About PTSD?
==========
Old Website
======================
For the Birds
==================
What Does a Parrot Know About PTSD?
Re: ifupdown legacy(?)
Thank you, Garry.
I think, I get your point.
I think, that the Reference means some management system, which name Debian users don't say outloud, and to get the final answer, one should go and dig into this system's current state and it's possible perspectives.
Thanks again!
I think, I get your point.
I think, that the Reference means some management system, which name Debian users don't say outloud, and to get the final answer, one should go and dig into this system's current state and it's possible perspectives.
Thanks again!
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 133 times
Re: ifupdown legacy(?)
https://www.debian.org/doc/manuals/debi ... or_desktopptvschkn wrote:I can't figure out, what is the nowadays relevant alternative for interfaces configuration.
I prefer ifupdown though
deadbang
Re: ifupdown legacy(?)
I like ifupdown, but I've been using networkmanager because it's nice on the desktop environment. I still have a couple of window manager boxes, and I like ifupdown on them. Networkmangler is a little standoffish, it does it's thing when it wants to, I think it's designed that way, while ifupdown does what you say PDQ! (edit:IF you follow syntax exactly right)
i thought this was an interesting article http://pureperl.blogspot.com/2013/01/th ... e-and.html
i thought this was an interesting article http://pureperl.blogspot.com/2013/01/th ... e-and.html
resigned by AI ChatGPT
Re: ifupdown legacy(?)
http://www.2daygeek.com/ip-command-exam ... -on-linux/
I have to admit though,
feels a bit easier than
I have to admit though,
Code: Select all
# ifup eth1
Code: Select all
# ip link set dev eth1 up
Bullseye amd64, AMD Ryzen 5 3600
Buster amd64, Intel Xeon E3-1240 v3
Sid ppc, PowerPC 7447a
Sid ppc64, PowerPC 970FX
Buster amd64, Intel Xeon E3-1240 v3
Sid ppc, PowerPC 7447a
Sid ppc64, PowerPC 970FX
Re: ifupdown legacy(?)
I believe that network-manager relies on systemd - so it would tend to deprecate ifup.
My experience has been that using ifup directly - occasionally made hung the routing tables, particularly when there was a disconnected TUN.
Network-mamager always worked flawlessly.
However, I am currently back to the networking in init.d, which seems to work fine, though could not find the correct interface on its own. It uses ifup.
The script should hopefully be a little better than ifup alone in restoring routing tables, when the VPN is unable to.
My experience has been that using ifup directly - occasionally made hung the routing tables, particularly when there was a disconnected TUN.
Network-mamager always worked flawlessly.
However, I am currently back to the networking in init.d, which seems to work fine, though could not find the correct interface on its own. It uses ifup.
The script should hopefully be a little better than ifup alone in restoring routing tables, when the VPN is unable to.
- dust hill resident
- Posts: 240
- Joined: 2007-05-18 13:31
Re: ifupdown legacy(?)
ifupdown is the BEST! I appreciate it for its simplicity and ease of use. I use it on all my systems.
Re: ifupdown legacy(?)
I used ifupdown as the workhorse for my simple-netaid-* project. Maybe, it is time to use a custom program to do the dirty work but at Devuan, ifupdown should remain available and independent of SystemD.
Debian == { > 30, 000 packages }; Debian != systemd
The worst infection of all, is a false sense of security!
It is hard to get away from CLI tools.
The worst infection of all, is a false sense of security!
It is hard to get away from CLI tools.
Re: ifupdown legacy(?)
From what I gathered ip tool doesn't only replace ifup and ifdown, but also route, brctl, ifconfig, arp and few others..
This is the same as with iw tool, which replaces iwconfig, iwlist...
Basically, one only only need to use/learn 2 tools, and forget about other tools which are limited on specific tasks.
This is the same as with iw tool, which replaces iwconfig, iwlist...
Basically, one only only need to use/learn 2 tools, and forget about other tools which are limited on specific tasks.