Hi,
Today i received my 4 port network card (HP NC365T) an i installed it on my omv with all 4 interfaces at bound0 try 802.3ad (i have a managed switch (DGS-1216T) that configured port mirroring) every thing works fine wen i have my onboard ethernet plugged in for example on eth0 i have IP 192.168.1.128 and on bound 192.168.1.140. On my desktop when i access to 192.168.1.140 every thing works great but only if the eth0 is connected, if i disconnect the eth0 the ip of boud0 don't reply. Also try with balanced rr to increase NAS speed on network (on dashboard appears 4000Mbit/sec) but the same thing happens. After reading some documentation i will keep this config (balanced rr).
Anyone has some idea what causing this.
Strange thing happens with boud0 and eth0
-
- OMV 2.x
- jms
-
-
Post the output of:
ifconfig -a
-
there is the output
Code
Alles anzeigenroot@JMS-OMV:~# ifconfig -a bond0 Link encap:Ethernet HWaddr 00:1c:c4:47:31:f9 inet addr:192.168.1.140 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 RX packets:1952390 errors:0 dropped:0 overruns:0 frame:0 TX packets:12879 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:970672720 (925.7 MiB) TX bytes:3724516 (3.5 MiB) eth0 Link encap:Ethernet HWaddr 44:8a:5b:cb:86:69 inet addr:192.168.1.128 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2560719 errors:0 dropped:8 overruns:0 frame:0 TX packets:3348619 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1092655238 (1.0 GiB) TX bytes:2806698293 (2.6 GiB) eth2 Link encap:Ethernet HWaddr 00:1c:c4:47:31:f9 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:553860 errors:0 dropped:0 overruns:0 frame:0 TX packets:4385 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:299430884 (285.5 MiB) TX bytes:1003209 (979.6 KiB) Interrupt:19 Memory:f7960000-f7980000 eth3 Link encap:Ethernet HWaddr 00:1c:c4:47:31:f9 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:174775 errors:0 dropped:0 overruns:0 frame:0 TX packets:2832 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:63849337 (60.8 MiB) TX bytes:911196 (889.8 KiB) Interrupt:18 Memory:f7920000-f7940000 eth4 Link encap:Ethernet HWaddr 00:1c:c4:47:31:f9 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:224511 errors:0 dropped:0 overruns:0 frame:0 TX packets:2831 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:93267392 (88.9 MiB) TX bytes:907246 (885.9 KiB) Interrupt:17 Memory:f7860000-f7880000 eth5 Link encap:Ethernet HWaddr 00:1c:c4:47:31:f9 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:999246 errors:0 dropped:0 overruns:0 frame:0 TX packets:2831 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:514126269 (490.3 MiB) TX bytes:902865 (881.7 KiB) Interrupt:16 Memory:f7820000-f7840000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:415087 errors:0 dropped:0 overruns:0 frame:0 TX packets:415087 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:139139710 (132.6 MiB) TX bytes:139139710 (132.6 MiB)
-
-
Please take some time and read some articles about bonding ports.
port mirroring is not that function you are looking for (https://en.wikipedia.org/wiki/Port_mirroring).
There must create a LAG group on your switch to use 802.3ad as bonding type.
Some bonding types like balance-tlb oder balance-alb(nearly the same as 802.3ad) are working with out any switch configuration
-
Hello,
I have the same problem.
- Configured the Dynamic LAG on my Brocade Switch.
- Created the bond0 (802.3ad) with 2 Gigabit Interfaces (eth3, eth4) on my OMV
- Access the WebUI via Bond0 IP => OK
- Shutdown my interface eth0 and Bond0 become unresponsiveConclusion : Bond0 not working if eth0 is disconnected.
-
Anyone can help ?
-
-
It may take some time to Debian noting that it has to route over bond0, but why did you configure bond on the switch? No mode except LACP needs that.
Greetings
David -
Hello,
802.3ad requires LACP to be configure on the Switch. It works until I unplugged eth0 from my NAS.
Thanks
-
@bonkersGER and I used other modes - aside from LACP - just fine, so I suggest to try another mode instead.
Greetings
David -
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!