Portál AbcLinuxu, 11. května 2025 10:39
cat /etc/network/interfaces # The loopback network interface auto lo iface lo inet loopback auto eth0 iface eth0 inet manual bond-master bond0 auto eth1 iface eth1 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.0.2.100 gateway 10.0.2.2 netmask 255.255.255.0 bondmode active-backup bond-miimon 100 bond-downdelay 200 bond-updelay 200 dns-nameservers 8.8.8.8 dns-search home.lan
Raději než jakýsi distro-specific konfigurační soubor ukažte, co je v /proc/net/bonding a jak vypadá výstup "ip addr show". Taky by bylo dobré popsat, kam jsou ty kabely zapojené a který jste vytáhl.
P.S.: nešlo by místo toho syntax-highlighteru, který hází alerty, použít obyčejný element pre?
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: load balancing (round-robin) MII Status: up MII Polling Interval (ms): 0 Up Delay (ms): 0 Down Delay (ms): 0 Slave Interface: eth0 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 08:00:27:17:24:03 Slave queue ID: 0 Slave Interface: eth1 MII Status: up Speed: 1000 Mbps Duplex: fullip addr show
1: lo: <.LOOPBACK,UP,LOWER_UP.> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <.BROADCAST,.MULTICAST,.SLAVE,.UP,LOWER_UP.> mtu 1500 qdisc pfifo_fast master bond0 state UP qlen 1000
link/ether 08:00:27:17:24:03 brd ff:ff:ff:ff:ff:ff
3: eth1: <.BROADCAST,.MULTICAST,.SLAVE,.UP,LOWER_UP.> mtu 1500 qdisc pfifo_fast master bond0 state UP qlen 1000
link/ether 08:00:27:17:24:03 brd ff:ff:ff:ff:ff:ff
4: bond0: <.BROADCAST,.MULTICAST,.MASTER,UP,LOWER_UP.> mtu 1500 qdisc noqueue state UP
link/ether 08:00:27:17:24:03 brd ff:ff:ff:ff:ff:ff
inet 10.0.2.100/24 brd 10.0.2.255 scope global bond0
inet6 fe80::a00:27ff:fe17:2403/64 scope link
valid_lft forever preferred_lft forever
mam jeden switch do ktoreho su zapojene oba kable z oboch sietoviek. Ked su zapojene oba kable prechadza kazdy druhy ping
PING 10.0.2.2 (10.0.2.2) 56(84) bytes of data. 64 bytes from 10.0.2.2: icmp_req=2 ttl=63 time=0.176 ms 64 bytes from 10.0.2.2: icmp_req=4 ttl=63 time=0.309 ms 64 bytes from 10.0.2.2: icmp_req=6 ttl=63 time=0.525 ms 64 bytes from 10.0.2.2: icmp_req=8 ttl=63 time=0.188 ms 64 bytes from 10.0.2.2: icmp_req=10 ttl=63 time=0.173 msKed je zapojena len eth0. kazdy ping prejde
64 bytes from 10.0.2.2: icmp_req=73 ttl=63 time=0.191 ms 64 bytes from 10.0.2.2: icmp_req=74 ttl=63 time=0.116 ms 64 bytes from 10.0.2.2: icmp_req=75 ttl=63 time=0.276 ms 64 bytes from 10.0.2.2: icmp_req=76 ttl=63 time=0.218 ms 64 bytes from 10.0.2.2: icmp_req=77 ttl=63 time=0.227 ms 64 bytes from 10.0.2.2: icmp_req=78 ttl=63 time=0.209 ms 64 bytes from 10.0.2.2: icmp_req=79 ttl=63 time=0.174 ms 64 bytes from 10.0.2.2: icmp_req=80 ttl=63 time=0.175 ms 64 bytes from 10.0.2.2: icmp_req=81 ttl=63 time=0.217 ms 64 bytes from 10.0.2.2: icmp_req=82 ttl=63 time=0.227 msKed je zapojena len eth1. neprejde ziadny ping Pardon za syntax-highlighteru, som tu na fore novacik tak som tam dal class="brush: Plain", podla napovedy uvedenej nizsie.
Bonding Mode: load balancing (round-robin)
Tohle bude problém. Buď máte chybu v tom konfiguračním souboru, nebo je nějaká ve skriptu, který ho zpracovává.
som tu na fore novacik tak som tam dal class="brush: Plain"
Pokud nechcete žádný syntax highlighting, je nejjednodušší dát jen <pre>...</pre> nebo <pre class="kod"e;>...</pre> Ale tohle bude nejspíš buď chyba té nápovědy nebo toho javascriptu.
skus pignut gw alebo nieco z toho stroja, niekedy su switche neochotne robit discovery a treba im oznamit zmenu tabulky napr pingom
D.
Tiskni
Sdílej:
ISSN 1214-1267, (c) 1999-2007 Stickfish s.r.o.