Devuan… Reduce time to wait while internet interfaces being configured during boot

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












3















I am using devuan linux for my laptop after leaving debian back due to the first's better sequrity and its simplicity compared to debian.



I am really happy with it but I have the next problem:



When the OS starts, if my ethernet cable is not plunged in or even if there is a problem with my connection, it waits for about 20 seconds waiting while:




Configuring internet interfaces




... and after that it says:




ifup already configured. done




or something similar, even if it really configured the interfaces (that is really rare if the cable was not really attached from the beginning s supposed to be attached -I am possibly have a problem with the cable because it is too long or may be because the port has a problem-) even if the interface is not really configured and I will not be able to access internet.



What I want is:
1) A way to save the configuration and not need to wait for these 20 seconds for ifup to be reconfigured at every boot, but the ability to use



service networking restart


if my Internet is not really configure during the boot.



PS: 20 seconds are really many to wait at every boot and many times I just want to work offline without a cable plunged in.



/etc/network/interfaces:



# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
# This is an autoconfigured IPv6 interface
iface eth0 inet6 auto









share|improve this question
























  • Please show us the relevant bits of eth0 in /etc/network/interfaces. Btw, I prefer Antix to Devuan, which is another alternative of using Debian without systemd

    – Rui F Ribeiro
    Feb 27 at 9:51











  • Thanks for th comment and the suggestion @RuiFRibeiro.... I added the file's contents, but I am not sure if this is what you meant. (poor English)

    – koleygr
    Feb 27 at 9:55











  • etho seems ok, are you able to show wlan0? I suspect also 20s is ok for a waiting time...

    – Rui F Ribeiro
    Feb 27 at 9:59












  • @RuiFRibeiro: I don't use wlan0... No wi-fi at all... So, I don't know where to find it and also, I prefer to configure myself after boot because in most cases I don't need internet...

    – koleygr
    Feb 27 at 10:03












  • A 20s wait seems fine to me. You might want to see what services you are using, Apache is now to hang a bit while without DNS, and in the past X also hanged for a bit if you did not had a local DNS cache.

    – Rui F Ribeiro
    Feb 27 at 10:18
















3















I am using devuan linux for my laptop after leaving debian back due to the first's better sequrity and its simplicity compared to debian.



I am really happy with it but I have the next problem:



When the OS starts, if my ethernet cable is not plunged in or even if there is a problem with my connection, it waits for about 20 seconds waiting while:




Configuring internet interfaces




... and after that it says:




ifup already configured. done




or something similar, even if it really configured the interfaces (that is really rare if the cable was not really attached from the beginning s supposed to be attached -I am possibly have a problem with the cable because it is too long or may be because the port has a problem-) even if the interface is not really configured and I will not be able to access internet.



What I want is:
1) A way to save the configuration and not need to wait for these 20 seconds for ifup to be reconfigured at every boot, but the ability to use



service networking restart


if my Internet is not really configure during the boot.



PS: 20 seconds are really many to wait at every boot and many times I just want to work offline without a cable plunged in.



/etc/network/interfaces:



# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
# This is an autoconfigured IPv6 interface
iface eth0 inet6 auto









share|improve this question
























  • Please show us the relevant bits of eth0 in /etc/network/interfaces. Btw, I prefer Antix to Devuan, which is another alternative of using Debian without systemd

    – Rui F Ribeiro
    Feb 27 at 9:51











  • Thanks for th comment and the suggestion @RuiFRibeiro.... I added the file's contents, but I am not sure if this is what you meant. (poor English)

    – koleygr
    Feb 27 at 9:55











  • etho seems ok, are you able to show wlan0? I suspect also 20s is ok for a waiting time...

    – Rui F Ribeiro
    Feb 27 at 9:59












  • @RuiFRibeiro: I don't use wlan0... No wi-fi at all... So, I don't know where to find it and also, I prefer to configure myself after boot because in most cases I don't need internet...

    – koleygr
    Feb 27 at 10:03












  • A 20s wait seems fine to me. You might want to see what services you are using, Apache is now to hang a bit while without DNS, and in the past X also hanged for a bit if you did not had a local DNS cache.

    – Rui F Ribeiro
    Feb 27 at 10:18














3












3








3








I am using devuan linux for my laptop after leaving debian back due to the first's better sequrity and its simplicity compared to debian.



I am really happy with it but I have the next problem:



When the OS starts, if my ethernet cable is not plunged in or even if there is a problem with my connection, it waits for about 20 seconds waiting while:




Configuring internet interfaces




... and after that it says:




ifup already configured. done




or something similar, even if it really configured the interfaces (that is really rare if the cable was not really attached from the beginning s supposed to be attached -I am possibly have a problem with the cable because it is too long or may be because the port has a problem-) even if the interface is not really configured and I will not be able to access internet.



What I want is:
1) A way to save the configuration and not need to wait for these 20 seconds for ifup to be reconfigured at every boot, but the ability to use



service networking restart


if my Internet is not really configure during the boot.



PS: 20 seconds are really many to wait at every boot and many times I just want to work offline without a cable plunged in.



/etc/network/interfaces:



# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
# This is an autoconfigured IPv6 interface
iface eth0 inet6 auto









share|improve this question
















I am using devuan linux for my laptop after leaving debian back due to the first's better sequrity and its simplicity compared to debian.



I am really happy with it but I have the next problem:



When the OS starts, if my ethernet cable is not plunged in or even if there is a problem with my connection, it waits for about 20 seconds waiting while:




Configuring internet interfaces




... and after that it says:




ifup already configured. done




or something similar, even if it really configured the interfaces (that is really rare if the cable was not really attached from the beginning s supposed to be attached -I am possibly have a problem with the cable because it is too long or may be because the port has a problem-) even if the interface is not really configured and I will not be able to access internet.



What I want is:
1) A way to save the configuration and not need to wait for these 20 seconds for ifup to be reconfigured at every boot, but the ability to use



service networking restart


if my Internet is not really configure during the boot.



PS: 20 seconds are really many to wait at every boot and many times I just want to work offline without a cable plunged in.



/etc/network/interfaces:



# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
# This is an autoconfigured IPv6 interface
iface eth0 inet6 auto






network-interface internet devuan






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 9 at 14:50









GAD3R

27.4k1858114




27.4k1858114










asked Feb 27 at 9:24









koleygrkoleygr

14510




14510












  • Please show us the relevant bits of eth0 in /etc/network/interfaces. Btw, I prefer Antix to Devuan, which is another alternative of using Debian without systemd

    – Rui F Ribeiro
    Feb 27 at 9:51











  • Thanks for th comment and the suggestion @RuiFRibeiro.... I added the file's contents, but I am not sure if this is what you meant. (poor English)

    – koleygr
    Feb 27 at 9:55











  • etho seems ok, are you able to show wlan0? I suspect also 20s is ok for a waiting time...

    – Rui F Ribeiro
    Feb 27 at 9:59












  • @RuiFRibeiro: I don't use wlan0... No wi-fi at all... So, I don't know where to find it and also, I prefer to configure myself after boot because in most cases I don't need internet...

    – koleygr
    Feb 27 at 10:03












  • A 20s wait seems fine to me. You might want to see what services you are using, Apache is now to hang a bit while without DNS, and in the past X also hanged for a bit if you did not had a local DNS cache.

    – Rui F Ribeiro
    Feb 27 at 10:18


















  • Please show us the relevant bits of eth0 in /etc/network/interfaces. Btw, I prefer Antix to Devuan, which is another alternative of using Debian without systemd

    – Rui F Ribeiro
    Feb 27 at 9:51











  • Thanks for th comment and the suggestion @RuiFRibeiro.... I added the file's contents, but I am not sure if this is what you meant. (poor English)

    – koleygr
    Feb 27 at 9:55











  • etho seems ok, are you able to show wlan0? I suspect also 20s is ok for a waiting time...

    – Rui F Ribeiro
    Feb 27 at 9:59












  • @RuiFRibeiro: I don't use wlan0... No wi-fi at all... So, I don't know where to find it and also, I prefer to configure myself after boot because in most cases I don't need internet...

    – koleygr
    Feb 27 at 10:03












  • A 20s wait seems fine to me. You might want to see what services you are using, Apache is now to hang a bit while without DNS, and in the past X also hanged for a bit if you did not had a local DNS cache.

    – Rui F Ribeiro
    Feb 27 at 10:18

















Please show us the relevant bits of eth0 in /etc/network/interfaces. Btw, I prefer Antix to Devuan, which is another alternative of using Debian without systemd

– Rui F Ribeiro
Feb 27 at 9:51





Please show us the relevant bits of eth0 in /etc/network/interfaces. Btw, I prefer Antix to Devuan, which is another alternative of using Debian without systemd

– Rui F Ribeiro
Feb 27 at 9:51













Thanks for th comment and the suggestion @RuiFRibeiro.... I added the file's contents, but I am not sure if this is what you meant. (poor English)

– koleygr
Feb 27 at 9:55





Thanks for th comment and the suggestion @RuiFRibeiro.... I added the file's contents, but I am not sure if this is what you meant. (poor English)

– koleygr
Feb 27 at 9:55













etho seems ok, are you able to show wlan0? I suspect also 20s is ok for a waiting time...

– Rui F Ribeiro
Feb 27 at 9:59






etho seems ok, are you able to show wlan0? I suspect also 20s is ok for a waiting time...

– Rui F Ribeiro
Feb 27 at 9:59














@RuiFRibeiro: I don't use wlan0... No wi-fi at all... So, I don't know where to find it and also, I prefer to configure myself after boot because in most cases I don't need internet...

– koleygr
Feb 27 at 10:03






@RuiFRibeiro: I don't use wlan0... No wi-fi at all... So, I don't know where to find it and also, I prefer to configure myself after boot because in most cases I don't need internet...

– koleygr
Feb 27 at 10:03














A 20s wait seems fine to me. You might want to see what services you are using, Apache is now to hang a bit while without DNS, and in the past X also hanged for a bit if you did not had a local DNS cache.

– Rui F Ribeiro
Feb 27 at 10:18






A 20s wait seems fine to me. You might want to see what services you are using, Apache is now to hang a bit while without DNS, and in the past X also hanged for a bit if you did not had a local DNS cache.

– Rui F Ribeiro
Feb 27 at 10:18











1 Answer
1






active

oldest

votes


















4














Maybe the udev equivalent (eudev or mdev according to Devuan) isn't behaving 100% the same with regard to hotplug events. It's also possible if you're using a switch that the switch has a very long forwarding delay before actually letting traffic work both ways (in such case the 2nd solution below won't work).



Anyway, if you only want to have the interface unconfigured, this should be fairly easy. Here are two or three suggestions from easiest to more complex:




  1. exclude the interface from configuration



    1.1. just change default network settings in /etc/default/networking:



    either



    CONFIGURE_INTERFACES=no


    this is a bit extreme, as even lo won't be brought up, probably preventing even some non-networked applications to work properly (gdm...).



    1.2. or



    EXCLUDE_INTERFACES=eth0


    to exclude just the problematic interface.



    You can then later use ifup eth0 to bring it up.




  2. Or instead you can add a condition in the configuration to check if the link is available, and "fail" the interface if not. As I'm not sure if the dhcp hook is run before or after user-supplied up commands, I cheat and put it in pre-up which requires first bringing manually the interface up. You can check if using the up command is good enough without having to bring it up first.



    Edit the relevant /etc/network/interfaces part to look like this:



    allow-hotplug eth0
    iface eth0 inet dhcp
    pre-up ip link set eth0 up && sleep 1
    pre-up [ $(cat /sys/class/net/eth0/carrier) -eq 1 ]
    iface eth0 inet6 auto
    pre-up ip link set eth0 up && sleep 1
    pre-up [ $(cat /sys/class/net/eth0/carrier) -eq 1 ]


    (probably not needed for the ipv6 settings, this probably saves 1s. You could even remove the whole inet6 section if not interested)



    The return result of the test will make ifup consider the configuration failed and leave the logical (ifupdown's point of view) state of the card down.



You can then issue ifup eth0 or service networking restart later after having plugged the cable.






share|improve this answer

























  • Thanks... I already upvoted, but will test your solution before accepting too.

    – koleygr
    Feb 27 at 11:50











  • Perfect! Really appreciate your help! Tested the second solution and works fine! Thanks again!

    – koleygr
    Feb 27 at 12:01











  • That pre-up is brilliant, upvoted it. Have you any similar trick for wifi?

    – Rui F Ribeiro
    Feb 27 at 15:35












  • @koleygr Glad it worked as intended Anyway I just don't know why you had a problem, because Devuan's doc appears to tell the interface should come up only when there is a link (even if it describe what to do before migrating from debian to devuan...) : devuan.org/os/documentation/dev1fanboy/network-configuration

    – A.B
    Feb 27 at 20:15












  • @RuiFRibeiro for wifi, detection via only ifupdown would be more difficult. It's a bit asynchronous since the candidates have to be scanned (scan started with wpa_cli scan for example), the end of scan event retrieved, and depending upon results association started. wicd-cli is perhaps easier to use in scripts than plain wpa_cli.

    – A.B
    Feb 27 at 20:25











Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f503285%2fdevuan-reduce-time-to-wait-while-internet-interfaces-being-configured-during%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









4














Maybe the udev equivalent (eudev or mdev according to Devuan) isn't behaving 100% the same with regard to hotplug events. It's also possible if you're using a switch that the switch has a very long forwarding delay before actually letting traffic work both ways (in such case the 2nd solution below won't work).



Anyway, if you only want to have the interface unconfigured, this should be fairly easy. Here are two or three suggestions from easiest to more complex:




  1. exclude the interface from configuration



    1.1. just change default network settings in /etc/default/networking:



    either



    CONFIGURE_INTERFACES=no


    this is a bit extreme, as even lo won't be brought up, probably preventing even some non-networked applications to work properly (gdm...).



    1.2. or



    EXCLUDE_INTERFACES=eth0


    to exclude just the problematic interface.



    You can then later use ifup eth0 to bring it up.




  2. Or instead you can add a condition in the configuration to check if the link is available, and "fail" the interface if not. As I'm not sure if the dhcp hook is run before or after user-supplied up commands, I cheat and put it in pre-up which requires first bringing manually the interface up. You can check if using the up command is good enough without having to bring it up first.



    Edit the relevant /etc/network/interfaces part to look like this:



    allow-hotplug eth0
    iface eth0 inet dhcp
    pre-up ip link set eth0 up && sleep 1
    pre-up [ $(cat /sys/class/net/eth0/carrier) -eq 1 ]
    iface eth0 inet6 auto
    pre-up ip link set eth0 up && sleep 1
    pre-up [ $(cat /sys/class/net/eth0/carrier) -eq 1 ]


    (probably not needed for the ipv6 settings, this probably saves 1s. You could even remove the whole inet6 section if not interested)



    The return result of the test will make ifup consider the configuration failed and leave the logical (ifupdown's point of view) state of the card down.



You can then issue ifup eth0 or service networking restart later after having plugged the cable.






share|improve this answer

























  • Thanks... I already upvoted, but will test your solution before accepting too.

    – koleygr
    Feb 27 at 11:50











  • Perfect! Really appreciate your help! Tested the second solution and works fine! Thanks again!

    – koleygr
    Feb 27 at 12:01











  • That pre-up is brilliant, upvoted it. Have you any similar trick for wifi?

    – Rui F Ribeiro
    Feb 27 at 15:35












  • @koleygr Glad it worked as intended Anyway I just don't know why you had a problem, because Devuan's doc appears to tell the interface should come up only when there is a link (even if it describe what to do before migrating from debian to devuan...) : devuan.org/os/documentation/dev1fanboy/network-configuration

    – A.B
    Feb 27 at 20:15












  • @RuiFRibeiro for wifi, detection via only ifupdown would be more difficult. It's a bit asynchronous since the candidates have to be scanned (scan started with wpa_cli scan for example), the end of scan event retrieved, and depending upon results association started. wicd-cli is perhaps easier to use in scripts than plain wpa_cli.

    – A.B
    Feb 27 at 20:25
















4














Maybe the udev equivalent (eudev or mdev according to Devuan) isn't behaving 100% the same with regard to hotplug events. It's also possible if you're using a switch that the switch has a very long forwarding delay before actually letting traffic work both ways (in such case the 2nd solution below won't work).



Anyway, if you only want to have the interface unconfigured, this should be fairly easy. Here are two or three suggestions from easiest to more complex:




  1. exclude the interface from configuration



    1.1. just change default network settings in /etc/default/networking:



    either



    CONFIGURE_INTERFACES=no


    this is a bit extreme, as even lo won't be brought up, probably preventing even some non-networked applications to work properly (gdm...).



    1.2. or



    EXCLUDE_INTERFACES=eth0


    to exclude just the problematic interface.



    You can then later use ifup eth0 to bring it up.




  2. Or instead you can add a condition in the configuration to check if the link is available, and "fail" the interface if not. As I'm not sure if the dhcp hook is run before or after user-supplied up commands, I cheat and put it in pre-up which requires first bringing manually the interface up. You can check if using the up command is good enough without having to bring it up first.



    Edit the relevant /etc/network/interfaces part to look like this:



    allow-hotplug eth0
    iface eth0 inet dhcp
    pre-up ip link set eth0 up && sleep 1
    pre-up [ $(cat /sys/class/net/eth0/carrier) -eq 1 ]
    iface eth0 inet6 auto
    pre-up ip link set eth0 up && sleep 1
    pre-up [ $(cat /sys/class/net/eth0/carrier) -eq 1 ]


    (probably not needed for the ipv6 settings, this probably saves 1s. You could even remove the whole inet6 section if not interested)



    The return result of the test will make ifup consider the configuration failed and leave the logical (ifupdown's point of view) state of the card down.



You can then issue ifup eth0 or service networking restart later after having plugged the cable.






share|improve this answer

























  • Thanks... I already upvoted, but will test your solution before accepting too.

    – koleygr
    Feb 27 at 11:50











  • Perfect! Really appreciate your help! Tested the second solution and works fine! Thanks again!

    – koleygr
    Feb 27 at 12:01











  • That pre-up is brilliant, upvoted it. Have you any similar trick for wifi?

    – Rui F Ribeiro
    Feb 27 at 15:35












  • @koleygr Glad it worked as intended Anyway I just don't know why you had a problem, because Devuan's doc appears to tell the interface should come up only when there is a link (even if it describe what to do before migrating from debian to devuan...) : devuan.org/os/documentation/dev1fanboy/network-configuration

    – A.B
    Feb 27 at 20:15












  • @RuiFRibeiro for wifi, detection via only ifupdown would be more difficult. It's a bit asynchronous since the candidates have to be scanned (scan started with wpa_cli scan for example), the end of scan event retrieved, and depending upon results association started. wicd-cli is perhaps easier to use in scripts than plain wpa_cli.

    – A.B
    Feb 27 at 20:25














4












4








4







Maybe the udev equivalent (eudev or mdev according to Devuan) isn't behaving 100% the same with regard to hotplug events. It's also possible if you're using a switch that the switch has a very long forwarding delay before actually letting traffic work both ways (in such case the 2nd solution below won't work).



Anyway, if you only want to have the interface unconfigured, this should be fairly easy. Here are two or three suggestions from easiest to more complex:




  1. exclude the interface from configuration



    1.1. just change default network settings in /etc/default/networking:



    either



    CONFIGURE_INTERFACES=no


    this is a bit extreme, as even lo won't be brought up, probably preventing even some non-networked applications to work properly (gdm...).



    1.2. or



    EXCLUDE_INTERFACES=eth0


    to exclude just the problematic interface.



    You can then later use ifup eth0 to bring it up.




  2. Or instead you can add a condition in the configuration to check if the link is available, and "fail" the interface if not. As I'm not sure if the dhcp hook is run before or after user-supplied up commands, I cheat and put it in pre-up which requires first bringing manually the interface up. You can check if using the up command is good enough without having to bring it up first.



    Edit the relevant /etc/network/interfaces part to look like this:



    allow-hotplug eth0
    iface eth0 inet dhcp
    pre-up ip link set eth0 up && sleep 1
    pre-up [ $(cat /sys/class/net/eth0/carrier) -eq 1 ]
    iface eth0 inet6 auto
    pre-up ip link set eth0 up && sleep 1
    pre-up [ $(cat /sys/class/net/eth0/carrier) -eq 1 ]


    (probably not needed for the ipv6 settings, this probably saves 1s. You could even remove the whole inet6 section if not interested)



    The return result of the test will make ifup consider the configuration failed and leave the logical (ifupdown's point of view) state of the card down.



You can then issue ifup eth0 or service networking restart later after having plugged the cable.






share|improve this answer















Maybe the udev equivalent (eudev or mdev according to Devuan) isn't behaving 100% the same with regard to hotplug events. It's also possible if you're using a switch that the switch has a very long forwarding delay before actually letting traffic work both ways (in such case the 2nd solution below won't work).



Anyway, if you only want to have the interface unconfigured, this should be fairly easy. Here are two or three suggestions from easiest to more complex:




  1. exclude the interface from configuration



    1.1. just change default network settings in /etc/default/networking:



    either



    CONFIGURE_INTERFACES=no


    this is a bit extreme, as even lo won't be brought up, probably preventing even some non-networked applications to work properly (gdm...).



    1.2. or



    EXCLUDE_INTERFACES=eth0


    to exclude just the problematic interface.



    You can then later use ifup eth0 to bring it up.




  2. Or instead you can add a condition in the configuration to check if the link is available, and "fail" the interface if not. As I'm not sure if the dhcp hook is run before or after user-supplied up commands, I cheat and put it in pre-up which requires first bringing manually the interface up. You can check if using the up command is good enough without having to bring it up first.



    Edit the relevant /etc/network/interfaces part to look like this:



    allow-hotplug eth0
    iface eth0 inet dhcp
    pre-up ip link set eth0 up && sleep 1
    pre-up [ $(cat /sys/class/net/eth0/carrier) -eq 1 ]
    iface eth0 inet6 auto
    pre-up ip link set eth0 up && sleep 1
    pre-up [ $(cat /sys/class/net/eth0/carrier) -eq 1 ]


    (probably not needed for the ipv6 settings, this probably saves 1s. You could even remove the whole inet6 section if not interested)



    The return result of the test will make ifup consider the configuration failed and leave the logical (ifupdown's point of view) state of the card down.



You can then issue ifup eth0 or service networking restart later after having plugged the cable.







share|improve this answer














share|improve this answer



share|improve this answer








edited Feb 27 at 15:32









Rui F Ribeiro

41.7k1483142




41.7k1483142










answered Feb 27 at 11:08









A.BA.B

5,4871829




5,4871829












  • Thanks... I already upvoted, but will test your solution before accepting too.

    – koleygr
    Feb 27 at 11:50











  • Perfect! Really appreciate your help! Tested the second solution and works fine! Thanks again!

    – koleygr
    Feb 27 at 12:01











  • That pre-up is brilliant, upvoted it. Have you any similar trick for wifi?

    – Rui F Ribeiro
    Feb 27 at 15:35












  • @koleygr Glad it worked as intended Anyway I just don't know why you had a problem, because Devuan's doc appears to tell the interface should come up only when there is a link (even if it describe what to do before migrating from debian to devuan...) : devuan.org/os/documentation/dev1fanboy/network-configuration

    – A.B
    Feb 27 at 20:15












  • @RuiFRibeiro for wifi, detection via only ifupdown would be more difficult. It's a bit asynchronous since the candidates have to be scanned (scan started with wpa_cli scan for example), the end of scan event retrieved, and depending upon results association started. wicd-cli is perhaps easier to use in scripts than plain wpa_cli.

    – A.B
    Feb 27 at 20:25


















  • Thanks... I already upvoted, but will test your solution before accepting too.

    – koleygr
    Feb 27 at 11:50











  • Perfect! Really appreciate your help! Tested the second solution and works fine! Thanks again!

    – koleygr
    Feb 27 at 12:01











  • That pre-up is brilliant, upvoted it. Have you any similar trick for wifi?

    – Rui F Ribeiro
    Feb 27 at 15:35












  • @koleygr Glad it worked as intended Anyway I just don't know why you had a problem, because Devuan's doc appears to tell the interface should come up only when there is a link (even if it describe what to do before migrating from debian to devuan...) : devuan.org/os/documentation/dev1fanboy/network-configuration

    – A.B
    Feb 27 at 20:15












  • @RuiFRibeiro for wifi, detection via only ifupdown would be more difficult. It's a bit asynchronous since the candidates have to be scanned (scan started with wpa_cli scan for example), the end of scan event retrieved, and depending upon results association started. wicd-cli is perhaps easier to use in scripts than plain wpa_cli.

    – A.B
    Feb 27 at 20:25

















Thanks... I already upvoted, but will test your solution before accepting too.

– koleygr
Feb 27 at 11:50





Thanks... I already upvoted, but will test your solution before accepting too.

– koleygr
Feb 27 at 11:50













Perfect! Really appreciate your help! Tested the second solution and works fine! Thanks again!

– koleygr
Feb 27 at 12:01





Perfect! Really appreciate your help! Tested the second solution and works fine! Thanks again!

– koleygr
Feb 27 at 12:01













That pre-up is brilliant, upvoted it. Have you any similar trick for wifi?

– Rui F Ribeiro
Feb 27 at 15:35






That pre-up is brilliant, upvoted it. Have you any similar trick for wifi?

– Rui F Ribeiro
Feb 27 at 15:35














@koleygr Glad it worked as intended Anyway I just don't know why you had a problem, because Devuan's doc appears to tell the interface should come up only when there is a link (even if it describe what to do before migrating from debian to devuan...) : devuan.org/os/documentation/dev1fanboy/network-configuration

– A.B
Feb 27 at 20:15






@koleygr Glad it worked as intended Anyway I just don't know why you had a problem, because Devuan's doc appears to tell the interface should come up only when there is a link (even if it describe what to do before migrating from debian to devuan...) : devuan.org/os/documentation/dev1fanboy/network-configuration

– A.B
Feb 27 at 20:15














@RuiFRibeiro for wifi, detection via only ifupdown would be more difficult. It's a bit asynchronous since the candidates have to be scanned (scan started with wpa_cli scan for example), the end of scan event retrieved, and depending upon results association started. wicd-cli is perhaps easier to use in scripts than plain wpa_cli.

– A.B
Feb 27 at 20:25






@RuiFRibeiro for wifi, detection via only ifupdown would be more difficult. It's a bit asynchronous since the candidates have to be scanned (scan started with wpa_cli scan for example), the end of scan event retrieved, and depending upon results association started. wicd-cli is perhaps easier to use in scripts than plain wpa_cli.

– A.B
Feb 27 at 20:25


















draft saved

draft discarded
















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f503285%2fdevuan-reduce-time-to-wait-while-internet-interfaces-being-configured-during%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown






Popular posts from this blog

How to check contact read email or not when send email to Individual?

Displaying single band from multi-band raster using QGIS

How many registers does an x86_64 CPU actually have?