Shorten nmcli connection timeout from 120s to 10s, try a lower priority interface quicker











up vote
0
down vote

favorite












On Ubuntu 16.04 lts I am using nmcli to manage the network interfaces. I have connections like so.



NAME          UUID                                  TYPE             DEVICE

link-local-0  da55e0dd-c5a2-414c-9ec5-f17b781df1a4  802-3-ethernet   eth0

ethernet-0    395f7a42-fe6c-4863-8527-1d94d9946da9  802-3-ethernet   --


When the device boots up and it is directly connect to another computer via Ethernet it takes around 120 seconds before ethernet-0 will timeout and move on to the link-local-0 connection. My goal is to have the device be reachable immediately via the peer to peer connection if it is not plugged in to the network. I tried changing the ipv4.dhcp-timeout value between 15 and 2 but it did not seem to make any difference, I have not been able to find where the timeout is configured to make the first connection fail faster.



nmcli tool, version 1.2.6 . The device is headless. Ubuntu 16.06. The avahi zero conf daemon is also running.




  1. How can I have the device configure its self with a 169.254.0.0/16 address when dhcp is not available within 0-5 seconds of initial boot up while still using network-manager.

  2. Network manager supports dispatcher scripts, would making a dispatcher script be the correct way to solve this?

  3. Am I just going about this the wrong way?


Here is the configurations of each interface



nmcli> print

===============================================================================

                    Connection profile details (ethernet-0)

===============================================================================

connection.id:                          ethernet-0

connection.uuid:                        395f7a42-fe6c-4863-8527-1d94d9946da9

connection.interface-name:              eth0

connection.type:                        802-3-ethernet

connection.autoconnect:                 yes

connection.autoconnect-priority:        2

connection.timestamp:                   1543331562

connection.read-only:                   no

connection.permissions:

connection.zone:                        --

connection.master:                      --

connection.slave-type:                  --

connection.autoconnect-slaves:          -1 (default)

connection.secondaries:

connection.gateway-ping-timeout:        0

connection.metered:                     unknown

connection.lldp:                        -1 (default)

-------------------------------------------------------------------------------

802-3-ethernet.port:                    --

802-3-ethernet.speed:                   0

802-3-ethernet.duplex:                  --

802-3-ethernet.auto-negotiate:          yes

802-3-ethernet.mac-address:             --

802-3-ethernet.cloned-mac-address:      --

802-3-ethernet.mac-address-blacklist:

802-3-ethernet.mtu:                     auto

802-3-ethernet.s390-subchannels:

802-3-ethernet.s390-nettype:            --

802-3-ethernet.s390-options:

802-3-ethernet.wake-on-lan:             1 (default)

802-3-ethernet.wake-on-lan-password:    --

-------------------------------------------------------------------------------

ipv4.method:                            auto

ipv4.dns:

ipv4.dns-search:

ipv4.dns-options:                       (default)

ipv4.dns-priority:                      0

ipv4.addresses:

ipv4.gateway:                           --

ipv4.routes:

ipv4.route-metric:                      -1

ipv4.ignore-auto-routes:                no

ipv4.ignore-auto-dns:                   no

ipv4.dhcp-client-id:                    --

ipv4.dhcp-timeout:                      2

ipv4.dhcp-send-hostname:                yes

ipv4.dhcp-hostname:                     --

ipv4.dhcp-fqdn:                         --

ipv4.never-default:                     no

ipv4.may-fail:                          yes

ipv4.dad-timeout:                       -1 (default)

-------------------------------------------------------------------------------

ipv6.method:                            auto

ipv6.dns:

ipv6.dns-search:

ipv6.dns-options:                       (default)

ipv6.dns-priority:                      0

ipv6.addresses:

ipv6.gateway:                           --

ipv6.routes:

ipv6.route-metric:                      -1

ipv6.ignore-auto-routes:                no

ipv6.ignore-auto-dns:                   no

ipv6.never-default:                     no

ipv6.may-fail:                          yes

ipv6.ip6-privacy:                       -1 (unknown)

ipv6.addr-gen-mode:                     stable-privacy

ipv6.dhcp-send-hostname:                yes

ipv6.dhcp-hostname:                     --

-------------------------------------------------------------------------------


Link local



                   Connection profile details (link-local-0)

===============================================================================

connection.id:                          link-local-0

connection.uuid:                        da55e0dd-c5a2-414c-9ec5-f17b781df1a4

connection.interface-name:              eth0

connection.type:                        802-3-ethernet

connection.autoconnect:                 yes

connection.autoconnect-priority:        1

connection.timestamp:                   1543420131

connection.read-only:                   no

connection.permissions:

connection.zone:                        --

connection.master:                      --

connection.slave-type:                  --

connection.autoconnect-slaves:          -1 (default)

connection.secondaries:

connection.gateway-ping-timeout:        0

connection.metered:                     unknown

connection.lldp:                        -1 (default)

-------------------------------------------------------------------------------

802-3-ethernet.port:                    --

802-3-ethernet.speed:                   0

802-3-ethernet.duplex:                  --

802-3-ethernet.auto-negotiate:          yes

802-3-ethernet.mac-address:             --

802-3-ethernet.cloned-mac-address:      --

802-3-ethernet.mac-address-blacklist:

802-3-ethernet.mtu:                     auto

802-3-ethernet.s390-subchannels:

802-3-ethernet.s390-nettype:            --

802-3-ethernet.s390-options:

802-3-ethernet.wake-on-lan:             1 (default)

802-3-ethernet.wake-on-lan-password:    --

-------------------------------------------------------------------------------

ipv4.method:                            link-local

ipv4.dns:

ipv4.dns-search:

ipv4.dns-options:                       (default)

ipv4.dns-priority:                      0

ipv4.addresses:

ipv4.gateway:                           --

ipv4.routes:

ipv4.route-metric:                      -1

ipv4.ignore-auto-routes:                no

ipv4.ignore-auto-dns:                   no

ipv4.dhcp-client-id:                    --

ipv4.dhcp-timeout:                      0

ipv4.dhcp-send-hostname:                yes

ipv4.dhcp-hostname:                     --

ipv4.dhcp-fqdn:                         --

ipv4.never-default:                     no

ipv4.may-fail:                          yes

ipv4.dad-timeout:                       -1 (default)

-------------------------------------------------------------------------------

ipv6.method:                            auto

ipv6.dns:

ipv6.dns-search:

ipv6.dns-options:                       (default)

ipv6.dns-priority:                      0

ipv6.addresses:

ipv6.gateway:                           --

ipv6.routes:

ipv6.route-metric:                      -1

ipv6.ignore-auto-routes:                no

ipv6.ignore-auto-dns:                   no

ipv6.never-default:                     no

ipv6.may-fail:                          yes

ipv6.ip6-privacy:                       -1 (unknown)

ipv6.addr-gen-mode:                     stable-privacy

ipv6.dhcp-send-hostname:                yes

ipv6.dhcp-hostname:                     --

-------------------------------------------------------------------------------


The route table



Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

default         192.168.1.1     0.0.0.0         UG    600    0        0 wlan0

link-local      *               255.255.0.0     U     100    0        0 eth0

192.168.1.0     *               255.255.255.0   U     600    0        0 wlan0

224.0.0.0       *               240.0.0.0       U     100    0        0 eth0





16.04 network-manager dhcp headless avahi







share|improve this question


























    up vote
    0
    down vote

    favorite












    On Ubuntu 16.04 lts I am using nmcli to manage the network interfaces. I have connections like so.



    NAME          UUID                                  TYPE             DEVICE
    
link-local-0  da55e0dd-c5a2-414c-9ec5-f17b781df1a4  802-3-ethernet   eth0
    
ethernet-0    395f7a42-fe6c-4863-8527-1d94d9946da9  802-3-ethernet   --


    When the device boots up and it is directly connect to another computer via Ethernet it takes around 120 seconds before ethernet-0 will timeout and move on to the link-local-0 connection. My goal is to have the device be reachable immediately via the peer to peer connection if it is not plugged in to the network. I tried changing the ipv4.dhcp-timeout value between 15 and 2 but it did not seem to make any difference, I have not been able to find where the timeout is configured to make the first connection fail faster.



    nmcli tool, version 1.2.6 . The device is headless. Ubuntu 16.06. The avahi zero conf daemon is also running.




    1. How can I have the device configure its self with a 169.254.0.0/16 address when dhcp is not available within 0-5 seconds of initial boot up while still using network-manager.

    2. Network manager supports dispatcher scripts, would making a dispatcher script be the correct way to solve this?

    3. Am I just going about this the wrong way?


    Here is the configurations of each interface



    nmcli> print
    
===============================================================================
    
                    Connection profile details (ethernet-0)
    
===============================================================================
    
connection.id:                          ethernet-0
    
connection.uuid:                        395f7a42-fe6c-4863-8527-1d94d9946da9
    
connection.interface-name:              eth0
    
connection.type:                        802-3-ethernet
    
connection.autoconnect:                 yes
    
connection.autoconnect-priority:        2
    
connection.timestamp:                   1543331562
    
connection.read-only:                   no
    
connection.permissions:
    
connection.zone:                        --
    
connection.master:                      --
    
connection.slave-type:                  --
    
connection.autoconnect-slaves:          -1 (default)
    
connection.secondaries:
    
connection.gateway-ping-timeout:        0
    
connection.metered:                     unknown
    
connection.lldp:                        -1 (default)
    
-------------------------------------------------------------------------------
    
802-3-ethernet.port:                    --
    
802-3-ethernet.speed:                   0
    
802-3-ethernet.duplex:                  --
    
802-3-ethernet.auto-negotiate:          yes
    
802-3-ethernet.mac-address:             --
    
802-3-ethernet.cloned-mac-address:      --
    
802-3-ethernet.mac-address-blacklist:
    
802-3-ethernet.mtu:                     auto
    
802-3-ethernet.s390-subchannels:
    
802-3-ethernet.s390-nettype:            --
    
802-3-ethernet.s390-options:
    
802-3-ethernet.wake-on-lan:             1 (default)
    
802-3-ethernet.wake-on-lan-password:    --
    
-------------------------------------------------------------------------------
    
ipv4.method:                            auto
    
ipv4.dns:
    
ipv4.dns-search:
    
ipv4.dns-options:                       (default)
    
ipv4.dns-priority:                      0
    
ipv4.addresses:
    
ipv4.gateway:                           --
    
ipv4.routes:
    
ipv4.route-metric:                      -1
    
ipv4.ignore-auto-routes:                no
    
ipv4.ignore-auto-dns:                   no
    
ipv4.dhcp-client-id:                    --
    
ipv4.dhcp-timeout:                      2
    
ipv4.dhcp-send-hostname:                yes
    
ipv4.dhcp-hostname:                     --
    
ipv4.dhcp-fqdn:                         --
    
ipv4.never-default:                     no
    
ipv4.may-fail:                          yes
    
ipv4.dad-timeout:                       -1 (default)
    
-------------------------------------------------------------------------------
    
ipv6.method:                            auto
    
ipv6.dns:
    
ipv6.dns-search:
    
ipv6.dns-options:                       (default)
    
ipv6.dns-priority:                      0
    
ipv6.addresses:
    
ipv6.gateway:                           --
    
ipv6.routes:
    
ipv6.route-metric:                      -1
    
ipv6.ignore-auto-routes:                no
    
ipv6.ignore-auto-dns:                   no
    
ipv6.never-default:                     no
    
ipv6.may-fail:                          yes
    
ipv6.ip6-privacy:                       -1 (unknown)
    
ipv6.addr-gen-mode:                     stable-privacy
    
ipv6.dhcp-send-hostname:                yes
    
ipv6.dhcp-hostname:                     --
    
-------------------------------------------------------------------------------


    Link local



                       Connection profile details (link-local-0)
    
===============================================================================
    
connection.id:                          link-local-0
    
connection.uuid:                        da55e0dd-c5a2-414c-9ec5-f17b781df1a4
    
connection.interface-name:              eth0
    
connection.type:                        802-3-ethernet
    
connection.autoconnect:                 yes
    
connection.autoconnect-priority:        1
    
connection.timestamp:                   1543420131
    
connection.read-only:                   no
    
connection.permissions:
    
connection.zone:                        --
    
connection.master:                      --
    
connection.slave-type:                  --
    
connection.autoconnect-slaves:          -1 (default)
    
connection.secondaries:
    
connection.gateway-ping-timeout:        0
    
connection.metered:                     unknown
    
connection.lldp:                        -1 (default)
    
-------------------------------------------------------------------------------
    
802-3-ethernet.port:                    --
    
802-3-ethernet.speed:                   0
    
802-3-ethernet.duplex:                  --
    
802-3-ethernet.auto-negotiate:          yes
    
802-3-ethernet.mac-address:             --
    
802-3-ethernet.cloned-mac-address:      --
    
802-3-ethernet.mac-address-blacklist:
    
802-3-ethernet.mtu:                     auto
    
802-3-ethernet.s390-subchannels:
    
802-3-ethernet.s390-nettype:            --
    
802-3-ethernet.s390-options:
    
802-3-ethernet.wake-on-lan:             1 (default)
    
802-3-ethernet.wake-on-lan-password:    --
    
-------------------------------------------------------------------------------
    
ipv4.method:                            link-local
    
ipv4.dns:
    
ipv4.dns-search:
    
ipv4.dns-options:                       (default)
    
ipv4.dns-priority:                      0
    
ipv4.addresses:
    
ipv4.gateway:                           --
    
ipv4.routes:
    
ipv4.route-metric:                      -1
    
ipv4.ignore-auto-routes:                no
    
ipv4.ignore-auto-dns:                   no
    
ipv4.dhcp-client-id:                    --
    
ipv4.dhcp-timeout:                      0
    
ipv4.dhcp-send-hostname:                yes
    
ipv4.dhcp-hostname:                     --
    
ipv4.dhcp-fqdn:                         --
    
ipv4.never-default:                     no
    
ipv4.may-fail:                          yes
    
ipv4.dad-timeout:                       -1 (default)
    
-------------------------------------------------------------------------------
    
ipv6.method:                            auto
    
ipv6.dns:
    
ipv6.dns-search:
    
ipv6.dns-options:                       (default)
    
ipv6.dns-priority:                      0
    
ipv6.addresses:
    
ipv6.gateway:                           --
    
ipv6.routes:
    
ipv6.route-metric:                      -1
    
ipv6.ignore-auto-routes:                no
    
ipv6.ignore-auto-dns:                   no
    
ipv6.never-default:                     no
    
ipv6.may-fail:                          yes
    
ipv6.ip6-privacy:                       -1 (unknown)
    
ipv6.addr-gen-mode:                     stable-privacy
    
ipv6.dhcp-send-hostname:                yes
    
ipv6.dhcp-hostname:                     --
    
-------------------------------------------------------------------------------


    The route table



    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
    
default         192.168.1.1     0.0.0.0         UG    600    0        0 wlan0
    
link-local      *               255.255.0.0     U     100    0        0 eth0
    
192.168.1.0     *               255.255.255.0   U     600    0        0 wlan0
    
224.0.0.0       *               240.0.0.0       U     100    0        0 eth0





    16.04 network-manager dhcp headless avahi







    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      On Ubuntu 16.04 lts I am using nmcli to manage the network interfaces. I have connections like so.



      NAME          UUID                                  TYPE             DEVICE
      
link-local-0  da55e0dd-c5a2-414c-9ec5-f17b781df1a4  802-3-ethernet   eth0
      
ethernet-0    395f7a42-fe6c-4863-8527-1d94d9946da9  802-3-ethernet   --


      When the device boots up and it is directly connect to another computer via Ethernet it takes around 120 seconds before ethernet-0 will timeout and move on to the link-local-0 connection. My goal is to have the device be reachable immediately via the peer to peer connection if it is not plugged in to the network. I tried changing the ipv4.dhcp-timeout value between 15 and 2 but it did not seem to make any difference, I have not been able to find where the timeout is configured to make the first connection fail faster.



      nmcli tool, version 1.2.6 . The device is headless. Ubuntu 16.06. The avahi zero conf daemon is also running.




      1. How can I have the device configure its self with a 169.254.0.0/16 address when dhcp is not available within 0-5 seconds of initial boot up while still using network-manager.

      2. Network manager supports dispatcher scripts, would making a dispatcher script be the correct way to solve this?

      3. Am I just going about this the wrong way?


      Here is the configurations of each interface



      nmcli> print
      
===============================================================================
      
                    Connection profile details (ethernet-0)
      
===============================================================================
      
connection.id:                          ethernet-0
      
connection.uuid:                        395f7a42-fe6c-4863-8527-1d94d9946da9
      
connection.interface-name:              eth0
      
connection.type:                        802-3-ethernet
      
connection.autoconnect:                 yes
      
connection.autoconnect-priority:        2
      
connection.timestamp:                   1543331562
      
connection.read-only:                   no
      
connection.permissions:
      
connection.zone:                        --
      
connection.master:                      --
      
connection.slave-type:                  --
      
connection.autoconnect-slaves:          -1 (default)
      
connection.secondaries:
      
connection.gateway-ping-timeout:        0
      
connection.metered:                     unknown
      
connection.lldp:                        -1 (default)
      
-------------------------------------------------------------------------------
      
802-3-ethernet.port:                    --
      
802-3-ethernet.speed:                   0
      
802-3-ethernet.duplex:                  --
      
802-3-ethernet.auto-negotiate:          yes
      
802-3-ethernet.mac-address:             --
      
802-3-ethernet.cloned-mac-address:      --
      
802-3-ethernet.mac-address-blacklist:
      
802-3-ethernet.mtu:                     auto
      
802-3-ethernet.s390-subchannels:
      
802-3-ethernet.s390-nettype:            --
      
802-3-ethernet.s390-options:
      
802-3-ethernet.wake-on-lan:             1 (default)
      
802-3-ethernet.wake-on-lan-password:    --
      
-------------------------------------------------------------------------------
      
ipv4.method:                            auto
      
ipv4.dns:
      
ipv4.dns-search:
      
ipv4.dns-options:                       (default)
      
ipv4.dns-priority:                      0
      
ipv4.addresses:
      
ipv4.gateway:                           --
      
ipv4.routes:
      
ipv4.route-metric:                      -1
      
ipv4.ignore-auto-routes:                no
      
ipv4.ignore-auto-dns:                   no
      
ipv4.dhcp-client-id:                    --
      
ipv4.dhcp-timeout:                      2
      
ipv4.dhcp-send-hostname:                yes
      
ipv4.dhcp-hostname:                     --
      
ipv4.dhcp-fqdn:                         --
      
ipv4.never-default:                     no
      
ipv4.may-fail:                          yes
      
ipv4.dad-timeout:                       -1 (default)
      
-------------------------------------------------------------------------------
      
ipv6.method:                            auto
      
ipv6.dns:
      
ipv6.dns-search:
      
ipv6.dns-options:                       (default)
      
ipv6.dns-priority:                      0
      
ipv6.addresses:
      
ipv6.gateway:                           --
      
ipv6.routes:
      
ipv6.route-metric:                      -1
      
ipv6.ignore-auto-routes:                no
      
ipv6.ignore-auto-dns:                   no
      
ipv6.never-default:                     no
      
ipv6.may-fail:                          yes
      
ipv6.ip6-privacy:                       -1 (unknown)
      
ipv6.addr-gen-mode:                     stable-privacy
      
ipv6.dhcp-send-hostname:                yes
      
ipv6.dhcp-hostname:                     --
      
-------------------------------------------------------------------------------


      Link local



                         Connection profile details (link-local-0)
      
===============================================================================
      
connection.id:                          link-local-0
      
connection.uuid:                        da55e0dd-c5a2-414c-9ec5-f17b781df1a4
      
connection.interface-name:              eth0
      
connection.type:                        802-3-ethernet
      
connection.autoconnect:                 yes
      
connection.autoconnect-priority:        1
      
connection.timestamp:                   1543420131
      
connection.read-only:                   no
      
connection.permissions:
      
connection.zone:                        --
      
connection.master:                      --
      
connection.slave-type:                  --
      
connection.autoconnect-slaves:          -1 (default)
      
connection.secondaries:
      
connection.gateway-ping-timeout:        0
      
connection.metered:                     unknown
      
connection.lldp:                        -1 (default)
      
-------------------------------------------------------------------------------
      
802-3-ethernet.port:                    --
      
802-3-ethernet.speed:                   0
      
802-3-ethernet.duplex:                  --
      
802-3-ethernet.auto-negotiate:          yes
      
802-3-ethernet.mac-address:             --
      
802-3-ethernet.cloned-mac-address:      --
      
802-3-ethernet.mac-address-blacklist:
      
802-3-ethernet.mtu:                     auto
      
802-3-ethernet.s390-subchannels:
      
802-3-ethernet.s390-nettype:            --
      
802-3-ethernet.s390-options:
      
802-3-ethernet.wake-on-lan:             1 (default)
      
802-3-ethernet.wake-on-lan-password:    --
      
-------------------------------------------------------------------------------
      
ipv4.method:                            link-local
      
ipv4.dns:
      
ipv4.dns-search:
      
ipv4.dns-options:                       (default)
      
ipv4.dns-priority:                      0
      
ipv4.addresses:
      
ipv4.gateway:                           --
      
ipv4.routes:
      
ipv4.route-metric:                      -1
      
ipv4.ignore-auto-routes:                no
      
ipv4.ignore-auto-dns:                   no
      
ipv4.dhcp-client-id:                    --
      
ipv4.dhcp-timeout:                      0
      
ipv4.dhcp-send-hostname:                yes
      
ipv4.dhcp-hostname:                     --
      
ipv4.dhcp-fqdn:                         --
      
ipv4.never-default:                     no
      
ipv4.may-fail:                          yes
      
ipv4.dad-timeout:                       -1 (default)
      
-------------------------------------------------------------------------------
      
ipv6.method:                            auto
      
ipv6.dns:
      
ipv6.dns-search:
      
ipv6.dns-options:                       (default)
      
ipv6.dns-priority:                      0
      
ipv6.addresses:
      
ipv6.gateway:                           --
      
ipv6.routes:
      
ipv6.route-metric:                      -1
      
ipv6.ignore-auto-routes:                no
      
ipv6.ignore-auto-dns:                   no
      
ipv6.never-default:                     no
      
ipv6.may-fail:                          yes
      
ipv6.ip6-privacy:                       -1 (unknown)
      
ipv6.addr-gen-mode:                     stable-privacy
      
ipv6.dhcp-send-hostname:                yes
      
ipv6.dhcp-hostname:                     --
      
-------------------------------------------------------------------------------


      The route table



      Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
      
default         192.168.1.1     0.0.0.0         UG    600    0        0 wlan0
      
link-local      *               255.255.0.0     U     100    0        0 eth0
      
192.168.1.0     *               255.255.255.0   U     600    0        0 wlan0
      
224.0.0.0       *               240.0.0.0       U     100    0        0 eth0





      16.04 network-manager dhcp headless avahi







      share|improve this question













      On Ubuntu 16.04 lts I am using nmcli to manage the network interfaces. I have connections like so.



      NAME          UUID                                  TYPE             DEVICE
      
link-local-0  da55e0dd-c5a2-414c-9ec5-f17b781df1a4  802-3-ethernet   eth0
      
ethernet-0    395f7a42-fe6c-4863-8527-1d94d9946da9  802-3-ethernet   --


      When the device boots up and it is directly connect to another computer via Ethernet it takes around 120 seconds before ethernet-0 will timeout and move on to the link-local-0 connection. My goal is to have the device be reachable immediately via the peer to peer connection if it is not plugged in to the network. I tried changing the ipv4.dhcp-timeout value between 15 and 2 but it did not seem to make any difference, I have not been able to find where the timeout is configured to make the first connection fail faster.



      nmcli tool, version 1.2.6 . The device is headless. Ubuntu 16.06. The avahi zero conf daemon is also running.




      1. How can I have the device configure its self with a 169.254.0.0/16 address when dhcp is not available within 0-5 seconds of initial boot up while still using network-manager.

      2. Network manager supports dispatcher scripts, would making a dispatcher script be the correct way to solve this?

      3. Am I just going about this the wrong way?


      Here is the configurations of each interface



      nmcli> print
      
===============================================================================
      
                    Connection profile details (ethernet-0)
      
===============================================================================
      
connection.id:                          ethernet-0
      
connection.uuid:                        395f7a42-fe6c-4863-8527-1d94d9946da9
      
connection.interface-name:              eth0
      
connection.type:                        802-3-ethernet
      
connection.autoconnect:                 yes
      
connection.autoconnect-priority:        2
      
connection.timestamp:                   1543331562
      
connection.read-only:                   no
      
connection.permissions:
      
connection.zone:                        --
      
connection.master:                      --
      
connection.slave-type:                  --
      
connection.autoconnect-slaves:          -1 (default)
      
connection.secondaries:
      
connection.gateway-ping-timeout:        0
      
connection.metered:                     unknown
      
connection.lldp:                        -1 (default)
      
-------------------------------------------------------------------------------
      
802-3-ethernet.port:                    --
      
802-3-ethernet.speed:                   0
      
802-3-ethernet.duplex:                  --
      
802-3-ethernet.auto-negotiate:          yes
      
802-3-ethernet.mac-address:             --
      
802-3-ethernet.cloned-mac-address:      --
      
802-3-ethernet.mac-address-blacklist:
      
802-3-ethernet.mtu:                     auto
      
802-3-ethernet.s390-subchannels:
      
802-3-ethernet.s390-nettype:            --
      
802-3-ethernet.s390-options:
      
802-3-ethernet.wake-on-lan:             1 (default)
      
802-3-ethernet.wake-on-lan-password:    --
      
-------------------------------------------------------------------------------
      
ipv4.method:                            auto
      
ipv4.dns:
      
ipv4.dns-search:
      
ipv4.dns-options:                       (default)
      
ipv4.dns-priority:                      0
      
ipv4.addresses:
      
ipv4.gateway:                           --
      
ipv4.routes:
      
ipv4.route-metric:                      -1
      
ipv4.ignore-auto-routes:                no
      
ipv4.ignore-auto-dns:                   no
      
ipv4.dhcp-client-id:                    --
      
ipv4.dhcp-timeout:                      2
      
ipv4.dhcp-send-hostname:                yes
      
ipv4.dhcp-hostname:                     --
      
ipv4.dhcp-fqdn:                         --
      
ipv4.never-default:                     no
      
ipv4.may-fail:                          yes
      
ipv4.dad-timeout:                       -1 (default)
      
-------------------------------------------------------------------------------
      
ipv6.method:                            auto
      
ipv6.dns:
      
ipv6.dns-search:
      
ipv6.dns-options:                       (default)
      
ipv6.dns-priority:                      0
      
ipv6.addresses:
      
ipv6.gateway:                           --
      
ipv6.routes:
      
ipv6.route-metric:                      -1
      
ipv6.ignore-auto-routes:                no
      
ipv6.ignore-auto-dns:                   no
      
ipv6.never-default:                     no
      
ipv6.may-fail:                          yes
      
ipv6.ip6-privacy:                       -1 (unknown)
      
ipv6.addr-gen-mode:                     stable-privacy
      
ipv6.dhcp-send-hostname:                yes
      
ipv6.dhcp-hostname:                     --
      
-------------------------------------------------------------------------------


      Link local



                         Connection profile details (link-local-0)
      
===============================================================================
      
connection.id:                          link-local-0
      
connection.uuid:                        da55e0dd-c5a2-414c-9ec5-f17b781df1a4
      
connection.interface-name:              eth0
      
connection.type:                        802-3-ethernet
      
connection.autoconnect:                 yes
      
connection.autoconnect-priority:        1
      
connection.timestamp:                   1543420131
      
connection.read-only:                   no
      
connection.permissions:
      
connection.zone:                        --
      
connection.master:                      --
      
connection.slave-type:                  --
      
connection.autoconnect-slaves:          -1 (default)
      
connection.secondaries:
      
connection.gateway-ping-timeout:        0
      
connection.metered:                     unknown
      
connection.lldp:                        -1 (default)
      
-------------------------------------------------------------------------------
      
802-3-ethernet.port:                    --
      
802-3-ethernet.speed:                   0
      
802-3-ethernet.duplex:                  --
      
802-3-ethernet.auto-negotiate:          yes
      
802-3-ethernet.mac-address:             --
      
802-3-ethernet.cloned-mac-address:      --
      
802-3-ethernet.mac-address-blacklist:
      
802-3-ethernet.mtu:                     auto
      
802-3-ethernet.s390-subchannels:
      
802-3-ethernet.s390-nettype:            --
      
802-3-ethernet.s390-options:
      
802-3-ethernet.wake-on-lan:             1 (default)
      
802-3-ethernet.wake-on-lan-password:    --
      
-------------------------------------------------------------------------------
      
ipv4.method:                            link-local
      
ipv4.dns:
      
ipv4.dns-search:
      
ipv4.dns-options:                       (default)
      
ipv4.dns-priority:                      0
      
ipv4.addresses:
      
ipv4.gateway:                           --
      
ipv4.routes:
      
ipv4.route-metric:                      -1
      
ipv4.ignore-auto-routes:                no
      
ipv4.ignore-auto-dns:                   no
      
ipv4.dhcp-client-id:                    --
      
ipv4.dhcp-timeout:                      0
      
ipv4.dhcp-send-hostname:                yes
      
ipv4.dhcp-hostname:                     --
      
ipv4.dhcp-fqdn:                         --
      
ipv4.never-default:                     no
      
ipv4.may-fail:                          yes
      
ipv4.dad-timeout:                       -1 (default)
      
-------------------------------------------------------------------------------
      
ipv6.method:                            auto
      
ipv6.dns:
      
ipv6.dns-search:
      
ipv6.dns-options:                       (default)
      
ipv6.dns-priority:                      0
      
ipv6.addresses:
      
ipv6.gateway:                           --
      
ipv6.routes:
      
ipv6.route-metric:                      -1
      
ipv6.ignore-auto-routes:                no
      
ipv6.ignore-auto-dns:                   no
      
ipv6.never-default:                     no
      
ipv6.may-fail:                          yes
      
ipv6.ip6-privacy:                       -1 (unknown)
      
ipv6.addr-gen-mode:                     stable-privacy
      
ipv6.dhcp-send-hostname:                yes
      
ipv6.dhcp-hostname:                     --
      
-------------------------------------------------------------------------------


      The route table



      Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
      
default         192.168.1.1     0.0.0.0         UG    600    0        0 wlan0
      
link-local      *               255.255.0.0     U     100    0        0 eth0
      
192.168.1.0     *               255.255.255.0   U     600    0        0 wlan0
      
224.0.0.0       *               240.0.0.0       U     100    0        0 eth0





      16.04 network-manager dhcp headless avahi




      16.04 network-manager dhcp headless avahi






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 28 at 16:09









      grahas

      11




      11






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote



          accepted










          I found an answer on this page. https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/configuring_the_dhcp_client_behavior



          I needed to set ipv4.may-fail to no. Then it will just time out (ipv4.dhcp-timeout) after 2 seconds. Retrying the connection 4 times and then failing. This way I only wait for 8 seconds vs two mins or so.






          share|improve this answer





















            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "89"
            };
            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',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            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%2faskubuntu.com%2fquestions%2f1096858%2fshorten-nmcli-connection-timeout-from-120s-to-10s-try-a-lower-priority-interfac%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








            up vote
            0
            down vote



            accepted










            I found an answer on this page. https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/configuring_the_dhcp_client_behavior



            I needed to set ipv4.may-fail to no. Then it will just time out (ipv4.dhcp-timeout) after 2 seconds. Retrying the connection 4 times and then failing. This way I only wait for 8 seconds vs two mins or so.






            share|improve this answer

























              up vote
              0
              down vote



              accepted










              I found an answer on this page. https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/configuring_the_dhcp_client_behavior



              I needed to set ipv4.may-fail to no. Then it will just time out (ipv4.dhcp-timeout) after 2 seconds. Retrying the connection 4 times and then failing. This way I only wait for 8 seconds vs two mins or so.






              share|improve this answer























                up vote
                0
                down vote



                accepted







                up vote
                0
                down vote



                accepted






                I found an answer on this page. https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/configuring_the_dhcp_client_behavior



                I needed to set ipv4.may-fail to no. Then it will just time out (ipv4.dhcp-timeout) after 2 seconds. Retrying the connection 4 times and then failing. This way I only wait for 8 seconds vs two mins or so.






                share|improve this answer












                I found an answer on this page. https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/configuring_the_dhcp_client_behavior



                I needed to set ipv4.may-fail to no. Then it will just time out (ipv4.dhcp-timeout) after 2 seconds. Retrying the connection 4 times and then failing. This way I only wait for 8 seconds vs two mins or so.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 30 at 18:51









                grahas

                11




                11






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Ask Ubuntu!


                    • 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.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • 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%2faskubuntu.com%2fquestions%2f1096858%2fshorten-nmcli-connection-timeout-from-120s-to-10s-try-a-lower-priority-interfac%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

                    Mouse cursor on multiple screens with different PPI

                    Image
                    24 6 I'm using a 4K display along with a Full HD display with both almost the same physical size and it brings some mouse cursor problems to me working with it on the default Windows settings. As the mouse movement speed depends on the pixels, it's very slow on the 4K display and very fast on the Full HD display. Is there a windows setting or application to move the mouse depending on the visible distance and not the pixels? Another problem is the virtual wall between the screens I can't move the cursor from the upper half of the 4K screen to the Full HD screen: How is it possible to virtually stretch the cursor transition area of the Full HD screen to the one of the 4K monitor? The smallest problem, nevertheless painful, is the cursor size which varies between the screens. Is there a way ...
                    Read more

                    Agildo Ribeiro

                    Image
                    Agildo Ribeiro Agildo em 2015 Nome completo Agildo da Gama Barata Ribeiro Filho Nascimento 26 de abril de 1932 Rio de Janeiro, DF Morte 28 de abril de 2018 (86 anos) Rio de Janeiro, RJ Ocupação Ator e humorista ...
                    Read more

                    Sometime when accessing a menu: “Ubuntu 16.04 has experienced an internal error”

                    Image
                    0 Sometime, when I try to access some menu (may be inside an application or desktop, doesn't matter), I got the following error. The menu and submenu disappear for a while. After that, I can continue using the system. And the lspci gave me the following output: $ lspci -k | grep -EA3 'VGA|3D|Display' 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) DeviceName: Onboard IGD Subsystem: Dell Haswell-ULT Integrated Graphics Controller Kernel driver in use: i915 unity compiz error-handling share | improve this question edited Mar 5 at 16:09 ...
                    Read more