Problem iproute2 od wersji 5.1

Maciej Kędzierski pld-devel-pl-list at vip.server.pl
Wed Feb 5 17:05:12 CET 2020


W załącznikach są wyniki.

*test.ip.przed.txt* - przed restartem sieci
*test.ip.po50.txt* - po restarcie sieci (iproute2-5.0)
*test.ip.po54.txt* - po restarcie sieci (iproute2-5.4)

Są 2 różnice.

Między test.ip.przed.txt i test.ip.po50.txt - KOSMETYCZNA
Każda linijka po 'ip rule list' ma dodatkową spację.

0:    from all lookup local
32766:    from all lookup main
32767:    from all lookup default

Między test.ip.przed.txt i test.ip.po54.txt - ZASADNICZA
Wynik 'ip rule list' JEST PUSTY i to zapewne jest powodem takiego 
zachowania.


Próbuję więc dodać:
ip rule add from all table local
ip rule del from all table default
ip rule del from all table main

w wyniku czego dostaję:
0:    from all lookup local
0:    from all lookup main
0:    from all lookup default

ping localhost - działa
reszta nie, zapewne przez te 0: wszędzie

Jak z ręki ustawić tą liczbę przed ":" ???

Nie zmienia to faktu, że restart nie tworzy reguł routingu.


PS. Jestem już chyba z czasów linuksa/uniksa łupanego ;) Lubię ifconfig 
:) choć nie wszystko pokaże.



W dniu 05.02.2020 o 14:50, Adam Przybyla pisze:
> Pusc na niedzialajacej maszynie:
> ip a ; ip l ; ip ru ;ip r
> i to samo na dzialajacej.
> Podeslij oba wyniki.
> ifconfig to wiesz, byla za czasow uniksa lupanego ...;-)
> Z powazaniem
>                        Adam Przybyla
>
> On Wed, Feb 5, 2020 at 2:23 PM Maciej Kędzierski <
> pld-devel-pl-list at vip.server.pl> wrote:
>
>> Witam.
>>
>> Opisywałem już parę miesięcy temu problem bezpośrednio osobom, które
>> zajmowały się pakietem iproute2, ale że nie został o rozwiązany, piszę
>> więc na grupie.
>>
>>
>> Po aktualizacji iproute2, od wersji 5.1 wzwyż, pojawił się problem z
>> działaniem sieci po restarcie usługi "network". Zwyczajnie sieć nie
>> działa, chociaż wszystko restartuje się poprawnie, nie ma błędów.
>>
>> Pomaga tylko restart całej maszyny.
>>
>> Z tego co sprawdziłem to wersje 4.x i 5.0 działają normalnie, ale 5.1 i
>> 5.2, aż po obecne 5.4, już nie. Identyczne zachowanie jest na wszystkich
>> maszynach, gdzie mam PLD.
>>
>> Z tego co namierzyłem "winny" jest program 'ip', z tego pakietu, ale nie
>> potrafię znaleźć przyczyny takiego zachowania.
>>
>>
>> Opis problemu
>> ============
>>
>> IPROUTE2-5.0
>> ===========
>>
>> # rpm -qv iproute2
>> iproute2-5.0.0-1.x86_64
>>
>> # ping localhost
>> PING localhost (127.0.0.1) 56(84) bytes of data.
>> 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.032 ms
>> 64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.019 ms
>> 64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.013 ms
>>
>> # ping 192.168.2.100
>> PING 192.168.2.100 (192.168.2.100) 56(84) bytes of data.
>> 64 bytes from 192.168.2.100: icmp_seq=1 ttl=64 time=0.039 ms
>> 64 bytes from 192.168.2.100: icmp_seq=2 ttl=64 time=0.016 ms
>>
>> # /etc/init.d/network restart
>> Wyłączanie interfejsu
>> eth0.......................................................................................
>> [116G [0;10m [36m[ [0;10m [35m
>> BUSY  [0;10m [36m] [0;10m [315m [116G [0;10m [36m[ [0;10m [32m DONE
>>   [0;10m [36m] [0;10m [315m
>> Wyłączanie interfejsu
>> eth1.......................................................................................
>> [116G [0;10m [36m[ [0;10m [35m
>> BUSY  [0;10m [36m] [0;10m [315m [116G [0;10m [36m[ [0;10m [32m DONE
>>   [0;10m [36m] [0;10m [315m
>> Wyłączanie interfejsu
>> eth2.......................................................................................
>> [116G [0;10m [36m[ [0;10m [35m
>> BUSY  [0;10m [36m] [0;10m [315m [116G [0;10m [36m[ [0;10m [32m DONE
>>   [0;10m [36m] [0;10m [315m
>> Podnoszenie interfejsu
>> eth0........................................................................................
>> [116G [0;10m [36m[ [0;10m [35m
>> BUSY  [0;10m [36m] [0;10m [315m [116G [0;10m [36m[ [0;10m [32m DONE
>>   [0;10m [36m] [0;10m [315m
>> Podnoszenie interfejsu
>> eth1........................................................................................
>> [116G [0;10m [36m[ [0;10m [35m
>> BUSY  [0;10m [36m] [0;10m [315m [116G [0;10m [36m[ [0;10m [32m DONE
>>   [0;10m [36m] [0;10m [315m
>> Podnoszenie interfejsu
>> eth2........................................................................................
>> [116G [0;10m [36m[ [0;10m [35m
>> BUSY  [0;10m [36m] [0;10m [315m [116G [0;10m [36m[ [0;10m [32m DONE
>>   [0;10m [36m] [0;10m [315m
>>
>> # ping localhost
>> PING localhost (127.0.0.1) 56(84) bytes of data.
>> 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.039 ms
>> 64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.020 ms
>>
>> # ping 192.168.2.100
>> PING 192.168.2.100 (192.168.2.100) 56(84) bytes of data.
>> 64 bytes from 192.168.2.100: icmp_seq=1 ttl=64 time=0.041 ms
>> 64 bytes from 192.168.2.100: icmp_seq=2 ttl=64 time=0.035 ms
>>
>>
>> Po restarcie sieci, wszystko działa jak należy.
>>
>>
>> IPROUTE2-5.1 (lub nowszy)
>> =======================
>> Teraz upgrade iproute2 do wersji 5.1
>>
>>
>> # rpm -Uvh iproute2-5.1.0-1.x86_64.rpm
>> Przygotowywanie... ##################################################
>> Ponowne pakowanie...
>> iproute2 ##################################################
>> Uaktualnianie...
>> iproute2 ##################################################
>>
>> # ping 192.168.2.100
>> PING 192.168.2.100 (192.168.2.100) 56(84) bytes of data.
>> 64 bytes from 192.168.2.100: icmp_seq=1 ttl=64 time=0.037 ms
>> 64 bytes from 192.168.2.100: icmp_seq=2 ttl=64 time=0.015 ms
>>
>> # /etc/init.d/network restart
>> Wyłączanie interfejsu
>> eth0.......................................................................................
>> [116G [0;10m [36m[ [0;10m [35m
>> BUSY  [0;10m [36m] [0;10m [315m [116G [0;10m [36m[ [0;10m [32m DONE
>>   [0;10m [36m] [0;10m [315m
>> Wyłączanie interfejsu
>> eth1.......................................................................................
>> [116G [0;10m [36m[ [0;10m [35m
>> BUSY  [0;10m [36m] [0;10m [315m [116G [0;10m [36m[ [0;10m [32m DONE
>>   [0;10m [36m] [0;10m [315m
>> Wyłączanie interfejsu
>> eth2.......................................................................................
>> [116G [0;10m [36m[ [0;10m [35m
>> BUSY  [0;10m [36m] [0;10m [315m [116G [0;10m [36m[ [0;10m [32m DONE
>>   [0;10m [36m] [0;10m [315m
>> Podnoszenie interfejsu
>> eth0........................................................................................
>> [116G [0;10m [36m[ [0;10m [35m
>> BUSY  [0;10m [36m] [0;10m [315m [116G [0;10m [36m[ [0;10m [32m DONE
>>   [0;10m [36m] [0;10m [315m
>> Podnoszenie interfejsu
>> eth1........................................................................................
>> [116G [0;10m [36m[ [0;10m [35m
>> BUSY  [0;10m [36m] [0;10m [315m [116G [0;10m [36m[ [0;10m [32m DONE
>>   [0;10m [36m] [0;10m [315m
>> Podnoszenie interfejsu
>> eth2........................................................................................
>> [116G [0;10m [36m[ [0;10m [35m
>> BUSY  [0;10m [36m] [0;10m [315m [116G [0;10m [36m[ [0;10m [32m DONE
>>   [0;10m [36m] [0;10m [315m
>>
>> Po restarcie sieci, mimo faktu, że wszystko uruchamia się normalnie, nie
>> ma błędów, interfejsy teoretycznie się podnoszą, usługi dają
>> zrestartować (np. SSH) - to SIEC NIE DZIAŁA
>>
>>
>> # ping localhost
>> connect: Sieć jest niedostępna
>>
>> # ping 192.168.2.100
>> connect: Sieć jest niedostępna
>>
>> # ifconfig lo
>> lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
>>           inet 127.0.0.1  netmask 255.0.0.0
>>           inet6 ::1  prefixlen 128  scopeid 0x10<host>
>>           loop  txqueuelen 1000  (Local Loopback)
>>           RX packets 132  bytes 9766 (9.5 KiB)
>>           RX errors 0  dropped 0  overruns 0  frame 0
>>           TX packets 132  bytes 9766 (9.5 KiB)
>>           TX errors 0  dropped 0 overruns 0  carrier 0 collisions 0
>>
>> # ifconfig eth2
>> eth2: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
>>           inet 192.168.2.100  netmask 255.255.255.0 broadcast 192.168.2.255
>>           ether 00:1b:11:59:9e:21  txqueuelen 1000 (Ethernet)
>>           RX packets 0  bytes 0 (0.0 B)
>>           RX errors 0  dropped 0  overruns 0  frame 0
>>           TX packets 0  bytes 0 (0.0 B)
>>           TX errors 0  dropped 0 overruns 0  carrier 0 collisions 0
>>
>> # ip link show lo
>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode
>> DEFAULT group default qlen 1000
>>       link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>>
>> # ip link show eth2
>> 5: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc htb state UP
>> mode DEFAULT group default qlen 1000
>>       link/ether 00:1b:11:59:9e:21 brd ff:ff:ff:ff:ff:ff
>>
>>
>> # /etc/init.d/sshd
>> Zatrzymywanie usługi
>> OpenSSH......................................................................................
>> [116G [0;10m [36m[ [0;10m [32m
>> DONE  [0;10m [36m] [0;10m [315m
>> Uruchamianie usługi
>> OpenSSH.......................................................................................
>> [116G [0;10m [36m[ [0;10m [35m
>> BUSY  [0;10m [36m] [0;10m [315m [116G [0;10m [36m[ [0;10m [32m DONE
>>   [0;10m [36m] [0;10m [315m
>>
>> # ssh localhost
>> ssh: connect to host localhost port 22: Network is unreachable
>>
>> # uname -a
>> Linux xxxxxxxxx 4.14.133-1 #1 SMP Thu Jul 11 16:34:42 CEST 2019 x86_64
>> AMD_Athlon(tm)_64_X2_Dual_Core_Processor_4200+ PLD Linux
>>
>>
>> Jak widać, przy wszystkich operacjach pojawia się komunikat: Network is
>> unreachable.
>> Sieć nie działa.
>> Pomaga tylko restart serwera. Przy starcie systemu normalnie uruchamia
>> się sieć.
>> Wystarczy jednak zrobić jej restart i sieć znowu znika.
>>
>>
>> Może ktoś z Was ma pomysł dlaczego tak się dzieje, może ktoś z Was się
>> spotkał z tym problemem?
>> W tej chwili muszę się trzymać wersji 5.0, albo pilnować się, żeby nie
>> zapomnieć, że nie mogę restartować sieci.
>>
>> Pozdrawiam
>> MK
>>
>>
>> _______________________________________________
>> pld-devel-pl mailing list
>> pld-devel-pl at lists.pld-linux.org
>> http://lists.pld-linux.org/mailman/listinfo/pld-devel-pl
>>
> _______________________________________________
> pld-devel-pl mailing list
> pld-devel-pl at lists.pld-linux.org
> http://lists.pld-linux.org/mailman/listinfo/pld-devel-pl
>

-------------- next part --------------

Przed restartem sieci

ip a ; ip l ; ip ru ;ip r
==

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 54:a0:50:86:c5:cf brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.9/23 brd 192.168.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::56a0:50ff:fe86:c5cf/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 54:a0:50:86:c5:d0 brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.9/24 brd 10.10.10.255 scope global eth1
       valid_lft forever preferred_lft forever
    inet6 fe80::56a0:50ff:fe86:c5d0/64 scope link 
       valid_lft forever preferred_lft forever

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether 54:a0:50:86:c5:cf brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether 54:a0:50:86:c5:d0 brd ff:ff:ff:ff:ff:ff

0:	from all lookup local
32766:	from all lookup main
32767:	from all lookup default

default via 192.168.0.1 dev eth0 onlink 
10.10.10.0/24 dev eth1 proto kernel scope link src 10.10.10.9 
192.168.0.0/23 dev eth0 proto kernel scope link src 192.168.0.9 
-------------- next part --------------

iproute2-5.0
==

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 54:a0:50:86:c5:cf brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.9/23 brd 192.168.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::56a0:50ff:fe86:c5cf/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 54:a0:50:86:c5:d0 brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.9/24 brd 10.10.10.255 scope global eth1
       valid_lft forever preferred_lft forever
    inet6 fe80::56a0:50ff:fe86:c5d0/64 scope link 
       valid_lft forever preferred_lft forever

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether 54:a0:50:86:c5:cf brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether 54:a0:50:86:c5:d0 brd ff:ff:ff:ff:ff:ff

0:	from all lookup local 
32766:	from all lookup main 
32767:	from all lookup default 

default via 192.168.0.1 dev eth0 onlink 
10.10.10.0/24 dev eth1 proto kernel scope link src 10.10.10.9 
192.168.0.0/23 dev eth0 proto kernel scope link src 192.168.0.9 
-------------- next part --------------

iproute2-5.4
==

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 54:a0:50:86:c5:cf brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.9/23 brd 192.168.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::56a0:50ff:fe86:c5cf/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 54:a0:50:86:c5:d0 brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.9/24 brd 10.10.10.255 scope global eth1
       valid_lft forever preferred_lft forever
    inet6 fe80::56a0:50ff:fe86:c5d0/64 scope link 
       valid_lft forever preferred_lft forever

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether 54:a0:50:86:c5:cf brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether 54:a0:50:86:c5:d0 brd ff:ff:ff:ff:ff:ff


default via 192.168.0.1 dev eth0 onlink 
10.10.10.0/24 dev eth1 proto kernel scope link src 10.10.10.9 
192.168.0.0/23 dev eth0 proto kernel scope link src 192.168.0.9 


More information about the pld-devel-pl mailing list