/etc/network/interfaces and ifup/ifdown still present. Why?
Clash Royale CLAN TAG#URR8PPP up vote
5
down vote
favorite
netplan is now the default network configurator on 18.04
- But on a freshly installed 18.04 system, I am still finding
/etc/networkstuff withinterfacesfile and other directories. - the ifup/ifdown utilities are still installed
Why ?
It seems the ifupdown package is a dependance of pppoeconf (?).
There is even a systemd service called networking that calls ifquery/ifup/ifdown ???
networking netplan
asked May 8 at 21:17
solsTiCe
4,90221642
add a comment |Â
up vote
5
down vote
favorite
netplan is now the default network configurator on 18.04
- But on a freshly installed 18.04 system, I am still finding
/etc/networkstuff withinterfacesfile and other directories. - the ifup/ifdown utilities are still installed
Why ?
It seems the ifupdown package is a dependance of pppoeconf (?).
There is even a systemd service called networking that calls ifquery/ifup/ifdown ???
networking netplan
asked May 8 at 21:17
solsTiCe
4,90221642
2
One reason I can think of is for backwards compatibility. Like why iscpiostill there? Or why isifconfigoregrep?
– Terrance
May 8 at 22:24
The reason, I'm guessing, is that netplan hands off control to systemd , and that inturn uses the ifup/ifdown stuff. At least that's my impression from reading git.launchpad.net/netplan/tree/doc/… Also perhaps some scripts use it git.launchpad.net/netplan/tree/doc/…
– Sergiy Kolodyazhnyy
May 8 at 22:28
2
netplan is used to configure systemd-networkd (which has already its configuration file but never mind) or hand it to network-manager. I don't think networkd use ifupdown. I just runsudo apt remove ifupdownwithout problem. Just waiting to see if something will break at next boot ;-)
– solsTiCe
May 8 at 22:52
1
@solsTiCe I see you like to live dangerously :)
– Sergiy Kolodyazhnyy
May 8 at 23:41
"Look ma, no hands !". ;-) .Well calculated risk. Nothing bad happeneded. It's just fear that let ubuntu dev accumulate dust. I can tell you I have removed also rsyslog. Using systemd-journald in persistent mode.
– solsTiCe
May 9 at 10:49
add a comment |Â
up vote
5
down vote
favorite
up vote
5
down vote
favorite
netplan is now the default network configurator on 18.04
- But on a freshly installed 18.04 system, I am still finding
/etc/networkstuff withinterfacesfile and other directories. - the ifup/ifdown utilities are still installed
Why ?
It seems the ifupdown package is a dependance of pppoeconf (?).
There is even a systemd service called networking that calls ifquery/ifup/ifdown ???
networking netplan
asked May 8 at 21:17
solsTiCe
4,90221642
netplan is now the default network configurator on 18.04
- But on a freshly installed 18.04 system, I am still finding
/etc/networkstuff withinterfacesfile and other directories. - the ifup/ifdown utilities are still installed
Why ?
It seems the ifupdown package is a dependance of pppoeconf (?).
There is even a systemd service called networking that calls ifquery/ifup/ifdown ???
networking netplan
asked May 8 at 21:17
solsTiCe
4,90221642
edited May 8 at 22:46
asked May 8 at 21:17
solsTiCe
4,90221642
asked May 8 at 21:17
solsTiCe
4,90221642
asked May 8 at 21:17
solsTiCe
4,90221642
4,90221642
2
One reason I can think of is for backwards compatibility. Like why iscpiostill there? Or why isifconfigoregrep?
– Terrance
May 8 at 22:24
The reason, I'm guessing, is that netplan hands off control to systemd , and that inturn uses the ifup/ifdown stuff. At least that's my impression from reading git.launchpad.net/netplan/tree/doc/… Also perhaps some scripts use it git.launchpad.net/netplan/tree/doc/…
– Sergiy Kolodyazhnyy
May 8 at 22:28
2
netplan is used to configure systemd-networkd (which has already its configuration file but never mind) or hand it to network-manager. I don't think networkd use ifupdown. I just runsudo apt remove ifupdownwithout problem. Just waiting to see if something will break at next boot ;-)
– solsTiCe
May 8 at 22:52
1
@solsTiCe I see you like to live dangerously :)
– Sergiy Kolodyazhnyy
May 8 at 23:41
"Look ma, no hands !". ;-) .Well calculated risk. Nothing bad happeneded. It's just fear that let ubuntu dev accumulate dust. I can tell you I have removed also rsyslog. Using systemd-journald in persistent mode.
– solsTiCe
May 9 at 10:49
add a comment |Â
2
One reason I can think of is for backwards compatibility. Like why iscpiostill there? Or why isifconfigoregrep?
– Terrance
May 8 at 22:24
The reason, I'm guessing, is that netplan hands off control to systemd , and that inturn uses the ifup/ifdown stuff. At least that's my impression from reading git.launchpad.net/netplan/tree/doc/… Also perhaps some scripts use it git.launchpad.net/netplan/tree/doc/…
– Sergiy Kolodyazhnyy
May 8 at 22:28
2
netplan is used to configure systemd-networkd (which has already its configuration file but never mind) or hand it to network-manager. I don't think networkd use ifupdown. I just runsudo apt remove ifupdownwithout problem. Just waiting to see if something will break at next boot ;-)
– solsTiCe
May 8 at 22:52
1
@solsTiCe I see you like to live dangerously :)
– Sergiy Kolodyazhnyy
May 8 at 23:41
"Look ma, no hands !". ;-) .Well calculated risk. Nothing bad happeneded. It's just fear that let ubuntu dev accumulate dust. I can tell you I have removed also rsyslog. Using systemd-journald in persistent mode.
– solsTiCe
May 9 at 10:49
2
2
One reason I can think of is for backwards compatibility. Like why is
cpio still there? Or why is ifconfig or egrep?– Terrance
May 8 at 22:24
One reason I can think of is for backwards compatibility. Like why is
cpio still there? Or why is ifconfig or egrep?– Terrance
May 8 at 22:24
The reason, I'm guessing, is that netplan hands off control to systemd , and that inturn uses the ifup/ifdown stuff. At least that's my impression from reading git.launchpad.net/netplan/tree/doc/… Also perhaps some scripts use it git.launchpad.net/netplan/tree/doc/…
– Sergiy Kolodyazhnyy
May 8 at 22:28
The reason, I'm guessing, is that netplan hands off control to systemd , and that inturn uses the ifup/ifdown stuff. At least that's my impression from reading git.launchpad.net/netplan/tree/doc/… Also perhaps some scripts use it git.launchpad.net/netplan/tree/doc/…
– Sergiy Kolodyazhnyy
May 8 at 22:28
2
2
netplan is used to configure systemd-networkd (which has already its configuration file but never mind) or hand it to network-manager. I don't think networkd use ifupdown. I just run
sudo apt remove ifupdown without problem. Just waiting to see if something will break at next boot ;-)– solsTiCe
May 8 at 22:52
netplan is used to configure systemd-networkd (which has already its configuration file but never mind) or hand it to network-manager. I don't think networkd use ifupdown. I just run
sudo apt remove ifupdown without problem. Just waiting to see if something will break at next boot ;-)– solsTiCe
May 8 at 22:52
1
1
@solsTiCe I see you like to live dangerously :)
– Sergiy Kolodyazhnyy
May 8 at 23:41
@solsTiCe I see you like to live dangerously :)
– Sergiy Kolodyazhnyy
May 8 at 23:41
"Look ma, no hands !". ;-) .Well calculated risk. Nothing bad happeneded. It's just fear that let ubuntu dev accumulate dust. I can tell you I have removed also rsyslog. Using systemd-journald in persistent mode.
– solsTiCe
May 9 at 10:49
"Look ma, no hands !". ;-) .Well calculated risk. Nothing bad happeneded. It's just fear that let ubuntu dev accumulate dust. I can tell you I have removed also rsyslog. Using systemd-journald in persistent mode.
– solsTiCe
May 9 at 10:49
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
ifupdown is still being pulled in by pppoeconf; which may get installed on desktops (on servers, there should be no trace of ifupdown).
There is no use for ifupdown if you don't use pppoeconf, both can be safely removed. They were still installed automatically because some users may need pppoeconf to successfully get online and get additional packages.
If you upgrade from 16.04 or from 17.10, you will also have ifupdown remain on the system, since we can't safely migrate all configurations. It's better to leave ~400k around on the system (ifupdown + pppoeconf + any config they have) than to remove them and risk breaking things on upgrade.
/etc/network/interfaces is also left behind so we can point users to netplan, given the large number of docs that will be left around mentioning ifupdown here and there on the Internet.
answered May 10 at 20:15
Mathieu Trudel-Lapierre
1,9921130
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
ifupdown is still being pulled in by pppoeconf; which may get installed on desktops (on servers, there should be no trace of ifupdown).
There is no use for ifupdown if you don't use pppoeconf, both can be safely removed. They were still installed automatically because some users may need pppoeconf to successfully get online and get additional packages.
If you upgrade from 16.04 or from 17.10, you will also have ifupdown remain on the system, since we can't safely migrate all configurations. It's better to leave ~400k around on the system (ifupdown + pppoeconf + any config they have) than to remove them and risk breaking things on upgrade.
/etc/network/interfaces is also left behind so we can point users to netplan, given the large number of docs that will be left around mentioning ifupdown here and there on the Internet.
answered May 10 at 20:15
Mathieu Trudel-Lapierre
1,9921130
add a comment |Â
up vote
0
down vote
ifupdown is still being pulled in by pppoeconf; which may get installed on desktops (on servers, there should be no trace of ifupdown).
There is no use for ifupdown if you don't use pppoeconf, both can be safely removed. They were still installed automatically because some users may need pppoeconf to successfully get online and get additional packages.
If you upgrade from 16.04 or from 17.10, you will also have ifupdown remain on the system, since we can't safely migrate all configurations. It's better to leave ~400k around on the system (ifupdown + pppoeconf + any config they have) than to remove them and risk breaking things on upgrade.
/etc/network/interfaces is also left behind so we can point users to netplan, given the large number of docs that will be left around mentioning ifupdown here and there on the Internet.
answered May 10 at 20:15
Mathieu Trudel-Lapierre
1,9921130
add a comment |Â
up vote
0
down vote
up vote
0
down vote
ifupdown is still being pulled in by pppoeconf; which may get installed on desktops (on servers, there should be no trace of ifupdown).
There is no use for ifupdown if you don't use pppoeconf, both can be safely removed. They were still installed automatically because some users may need pppoeconf to successfully get online and get additional packages.
If you upgrade from 16.04 or from 17.10, you will also have ifupdown remain on the system, since we can't safely migrate all configurations. It's better to leave ~400k around on the system (ifupdown + pppoeconf + any config they have) than to remove them and risk breaking things on upgrade.
/etc/network/interfaces is also left behind so we can point users to netplan, given the large number of docs that will be left around mentioning ifupdown here and there on the Internet.
answered May 10 at 20:15
Mathieu Trudel-Lapierre
1,9921130
ifupdown is still being pulled in by pppoeconf; which may get installed on desktops (on servers, there should be no trace of ifupdown).
There is no use for ifupdown if you don't use pppoeconf, both can be safely removed. They were still installed automatically because some users may need pppoeconf to successfully get online and get additional packages.
If you upgrade from 16.04 or from 17.10, you will also have ifupdown remain on the system, since we can't safely migrate all configurations. It's better to leave ~400k around on the system (ifupdown + pppoeconf + any config they have) than to remove them and risk breaking things on upgrade.
/etc/network/interfaces is also left behind so we can point users to netplan, given the large number of docs that will be left around mentioning ifupdown here and there on the Internet.
answered May 10 at 20:15
Mathieu Trudel-Lapierre
1,9921130
answered May 10 at 20:15
Mathieu Trudel-Lapierre
1,9921130
answered May 10 at 20:15
Mathieu Trudel-Lapierre
1,9921130
answered May 10 at 20:15
Mathieu Trudel-Lapierre
1,9921130
1,9921130
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1033771%2fetc-network-interfaces-and-ifup-ifdown-still-present-why%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
2
One reason I can think of is for backwards compatibility. Like why is
cpiostill there? Or why isifconfigoregrep?– Terrance
May 8 at 22:24
The reason, I'm guessing, is that netplan hands off control to systemd , and that inturn uses the ifup/ifdown stuff. At least that's my impression from reading git.launchpad.net/netplan/tree/doc/… Also perhaps some scripts use it git.launchpad.net/netplan/tree/doc/…
– Sergiy Kolodyazhnyy
May 8 at 22:28
2
netplan is used to configure systemd-networkd (which has already its configuration file but never mind) or hand it to network-manager. I don't think networkd use ifupdown. I just run
sudo apt remove ifupdownwithout problem. Just waiting to see if something will break at next boot ;-)– solsTiCe
May 8 at 22:52
1
@solsTiCe I see you like to live dangerously :)
– Sergiy Kolodyazhnyy
May 8 at 23:41
"Look ma, no hands !". ;-) .Well calculated risk. Nothing bad happeneded. It's just fear that let ubuntu dev accumulate dust. I can tell you I have removed also rsyslog. Using systemd-journald in persistent mode.
– solsTiCe
May 9 at 10:49