[SOLVED] debian network down after reboot

lazydog · 07-20-2015, 12:33 PM

Quote:

Originally Posted by hiboy

Thank you for your reply
I can ping myself and `ethtool eth0` says "Link detected: yes".
How to reboot the router? I can't access to the hardware router. Do you mean the router table or something software?

No I was meaning the router itself.

Have you tried setting your network to DHCP?

hiboy · 07-20-2015, 09:12 PM

Quote:

Originally Posted by lazydog

No I was meaning the router itself.

Have you tried setting your network to DHCP?

All the computers under the LAN have a static IP, so I didn't and never setting to DHCP.
BTW, the computer also have a WIN8 system and its network is very fine!

Shadow_7 · 07-21-2015, 05:47 AM

I mean the linux routing table of sorts.

# route -n
or
$ netstat -r -n

Code:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 wlan0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 wlan0

It should list TWO items. One for sending packets, one for recieving packets. The recieving one is basically there when you assign an IP to the device. For static setups it goes something like.

# ifconfig eth0 192.168.1.42 netmask 255.255.255.0 broadcast 192.168.1.255 mtu 1492 up
# route add default gw 192.168.1.1

If you were to do it the hard way and not use network-manager or other things. Where # means as root / administrator. I only mention it because your previous output had the IP for the interface, but gave you host unreachable errors. So routing is in question, or your cable isn't plugged in. Or invalid wifi credentials.

hiboy · 07-21-2015, 07:15 AM

Quote:

Originally Posted by Shadow_7

I mean the linux routing table of sorts.

# route -n
or
$ netstat -r -n

Code:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 wlan0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 wlan0

It should list TWO items. One for sending packets, one for recieving packets. The recieving one is basically there when you assign an IP to the device. For static setups it goes something like.

# ifconfig eth0 192.168.1.42 netmask 255.255.255.0 broadcast 192.168.1.255 mtu 1492 up
# route add default gw 192.168.1.1

If you were to do it the hard way and not use network-manager or other things. Where # means as root / administrator. I only mention it because your previous output had the IP for the interface, but gave you host unreachable errors. So routing is in question, or your cable isn't plugged in. Or invalid wifi credentials.

The output of

Code:

$sudo route -n
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
    0.0.0.0         10.214.52.1     0.0.0.0         UG    0      0        0 eth0
    10.214.52.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0

seems OK.

Will it be the network-manager ? The network-manager(NM) is working and there may be some configure of NM mix up the network.

Shadow_7 · 07-21-2015, 08:04 AM

Do these work?

$ ping -c 2 10.214.52.112
(local machine)

$ ping -c 2 10.214.52.1
(gateway / router)

Assumes that the firewall doesn't block pings. How about:

$ ping -c 2 8.8.8.8
(one of googles DNS servers)

Meaning that the internet connection exists if you can get that one. So if there's an issue then it's DNS or stuff outside your control.

hiboy · 07-21-2015, 08:32 AM

Quote:

Originally Posted by Shadow_7

Do these work?

$ ping -c 2 10.214.52.112
(local machine)

$ ping -c 2 10.214.52.1
(gateway / router)

Assumes that the firewall doesn't block pings. How about:

$ ping -c 2 8.8.8.8
(one of googles DNS servers)

Meaning that the internet connection exists if you can get that one. So if there's an issue then it's DNS or stuff outside your control.

The output is here

Code:

jason@hiboy:glnxa64$ ping -c 10.214.52.112
Usage: ping [-LRUbdfnqrvVaAD] [-c count] [-i interval] [-w deadline]
            [-p pattern] [-s packetsize] [-t ttl] [-I interface]
            [-M pmtudisc-hint] [-m mark] [-S sndbuf]
            [-T tstamp-options] [-Q tos] [hop1 ...] destination
jason@hiboy:glnxa64$ ping -c 2 10.214.52.112
PING 10.214.52.112 (10.214.52.112) 56(84) bytes of data.
64 bytes from 10.214.52.112: icmp_req=1 ttl=64 time=0.016 ms
64 bytes from 10.214.52.112: icmp_req=2 ttl=64 time=0.012 ms

--- 10.214.52.112 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.012/0.014/0.016/0.002 ms
jason@hiboy:glnxa64$ ping -c 2 10.214.52.1
PING 10.214.52.1 (10.214.52.1) 56(84) bytes of data.
From 10.214.52.112 icmp_seq=1 Destination Host Unreachable
From 10.214.52.112 icmp_seq=2 Destination Host Unreachable

--- 10.214.52.1 ping statistics ---
2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 999ms
pipe 2
jason@hiboy:glnxa64$ ping -c 2 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

--- 8.8.8.8 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 999ms

Since it can't get through the gateway, ping outside IP is useless.

Shadow_7 · 07-21-2015, 11:39 AM

Quote:

Originally Posted by hiboy

Code:

jason@hiboy:glnxa64$ ping -c 2 10.214.52.1
PING 10.214.52.1 (10.214.52.1) 56(84) bytes of data.
From 10.214.52.112 icmp_seq=1 Destination Host Unreachable
From 10.214.52.112 icmp_seq=2 Destination Host Unreachable

Since it can't get through the gateway, ping outside IP is useless.

Still just guessing, but since you're making kernel updates, you may need to run $(depmod -a) and perhaps rebuild the initrd image if you use that kind of setup. Otherwise take note of the differences between lsmod output between a working and non working setup. Noticing the module names that might be missing from one or the other, and if the SIZE of the modules differ between the two (using different versions?).

$ lsmod

lazydog · 07-21-2015, 12:24 PM

Quote:

Originally Posted by hiboy

The output of

Code:

$sudo route -n
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
    0.0.0.0         10.214.52.1     0.0.0.0         UG    0      0        0 eth0
    10.214.52.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0

seems OK.

Will it be the network-manager ? The network-manager(NM) is working and there may be some configure of NM mix up the network.

How did you configure the network setting, through NM or another way?

hiboy · 08-12-2015, 10:22 PM

I just do

Code:

$sudo ifdown eth0
$sudo rmmod e1000e
$sudo reboot

Then the network come back.

After rebooting. e1000e is still there.

Code:

$ lsmod | grep e100
e1000e                133833  0