search

bitraf / infrastructure

Infrastructure stuff for Bitraf's sysadmins
1 stars 3 forks source link

bite - the lan0 interface configuration messes up for bite.lan.bitraf.no IPv4 address #160

Open tingox opened 3 years ago

tingox commented 3 years ago

when the lan0 interface is up, bite can't talk (or be talked to) on the local interface (bite.lan.bitraf.no)

tingo@bite:~$ ip addr show dev lan0
8: lan0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 06:f0:3b:2f:0f:32 brd ff:ff:ff:ff:ff:ff
    inet 10.13.37.211/24 brd 10.13.37.255 scope global lan0
       valid_lft forever preferred_lft forever
    inet6 fe80::4f0:3bff:fe2f:f32/64 scope link 
       valid_lft forever preferred_lft forever
tingo@bite:~$ ping 10.13.37.1
PING 10.13.37.1 (10.13.37.1) 56(84) bytes of data.
^C
--- 10.13.37.1 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 30ms

tingo@bite:~$ ping 10.13.37.4
PING 10.13.37.4 (10.13.37.4) 56(84) bytes of data.
^C
--- 10.13.37.4 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 12ms

as soon as the lan0 interface goes down, the local interface on bite works again:

tingo@bite:~$ sudo ip link set down lan0
tingo@bite:~$ ip addr show dev lan0
8: lan0: <BROADCAST,NOARP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 06:f0:3b:2f:0f:32 brd ff:ff:ff:ff:ff:ff
tingo@bite:~$ ping 10.13.37.1
PING 10.13.37.1 (10.13.37.1) 56(84) bytes of data.
64 bytes from 10.13.37.1: icmp_seq=1 ttl=255 time=0.803 ms
64 bytes from 10.13.37.1: icmp_seq=2 ttl=255 time=0.486 ms
^C
--- 10.13.37.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 2ms
rtt min/avg/max/mdev = 0.486/0.644/0.803/0.160 ms
tingo@bite:~$ ping 10.13.37.4
PING 10.13.37.4 (10.13.37.4) 56(84) bytes of data.
64 bytes from 10.13.37.4: icmp_seq=1 ttl=64 time=0.307 ms
^C
--- 10.13.37.4 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms

needs to be fixed permanently, but I'm too tired now.

tingox commented 3 years ago

had to power off / power on the server again today (funny story, ask me sometime), and as usual, the lan0 interface needed to be down before the server responds on it's bite.lan.bitraf.no address. $ sudo ip link set down lan0 that's all.

tingox commented 3 years ago

After todays power outage (electrical work on premisies) everything came up again as it was supposed to do, but p2k16 gave a "refused to connect" error message when you tried to reach it in a web browser. As soon as I did $ sudo ip link set down lan0 on bite, the problem vanished.

tingox commented 3 years ago

After todays power outage (electrical work on premisies) everything came up again as it was supposed to do, but p2k16 gave a "refused to connect" error message when you tried to reach it in a web browser. As soon as I did $ sudo ip link set down lan0 on bite, the problem vanished.

scratch that - I've set the interface up now, and p2k16 still works.

tingox commented 2 years ago

checked the lan0 interface today after the server came up

tingo@bite:~$ sudo ip link show dev lan0
8: lan0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether 06:f0:3b:2f:0f:32 brd ff:ff:ff:ff:ff:ff

no ip address there. Trying to set it down and up

tingo@bite:~$ sudo ip link set up lan0
tingo@bite:~$ sudo ip link show dev lan0
8: lan0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether 06:f0:3b:2f:0f:32 brd ff:ff:ff:ff:ff:ff