Jump to content

Network interface not come up automatically after disconnection / connection of the network cable


ebalcsk

Recommended Posts

Hello,

 

I am using a orangepi one plus, but that might be no connection with my issue.

 

I am having the following network configuration:

# Network is managed by Network manager
auto lo
iface lo inet loopback


allow-hotplug eth0 eth0.1 eth0.10

auto eth0
iface eth0 inet manual
  pre-up ifconfig $IFACE up
  post-down ifconfig $IFACE down

auto eth0.1
iface eth0.1 inet static
  address 192.168.1.250
  netmask 255.255.255.0
  gateway 192.168.1.1

auto eth0.10
iface eth0.10 inet static
  address 192.168.10.1
  netmask 255.255.255.0

if i disconnect the network cable and connect back the interface is not come up automatically

from the state it is loks like up (docker interfaces are omitted):

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 02:07:e8:23:49:f2  txqueuelen 1000  (Ethernet)
        RX packets 46188  bytes 4058716 (3.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5741  bytes 592928 (579.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 19

eth0.1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 02:07:e8:23:49:f2  txqueuelen 1000  (Ethernet)
        RX packets 54  bytes 3950 (3.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 80  bytes 7233 (7.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0.10: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 02:07:e8:23:49:f2  txqueuelen 1000  (Ethernet)
        RX packets 10603  bytes 611155 (596.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 184  bytes 14270 (13.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

but cannot ping

 

if i restart the interfaces connection is restored

ifdown eth0.10
ifdown eth0.1
ifdown eth0
ifup eth0
ifup eth0.1
ifup eth0.10

interface output looks the same:

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 02:07:e8:23:49:f2  txqueuelen 1000  (Ethernet)
        RX packets 49742  bytes 4332006 (4.1 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 6201  bytes 637517 (622.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 19

eth0.1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.250  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::7:e8ff:fe23:49f2  prefixlen 64  scopeid 0x20<link>
        ether 02:07:e8:23:49:f2  txqueuelen 1000  (Ethernet)
        RX packets 61  bytes 4730 (4.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 155  bytes 12779 (12.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0.10: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.1  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::7:e8ff:fe23:49f2  prefixlen 64  scopeid 0x20<link>
        ether 02:07:e8:23:49:f2  txqueuelen 1000  (Ethernet)
        RX packets 1844  bytes 135220 (132.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 235  bytes 18193 (17.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

I wonder what is the problem?

Thank you

 

Link to comment
Share on other sites

Armbian & Khadas are rewarding contributors

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines