Afternoon all.
After a factory reset of an ASG220 V7.1 i would like to aggregate my internal and external links using eth0 and eth2 for internal, with eth1 and eth3 handling external.
When I aggregate eth0 and eth2 to lag0 I lose all access to the ASG220 except via console cable.
dmesg info:
Ethernet Channel Bonding Driver: v3.0.1 (January 9, 2006)
bonding: Warning: miimon must be specified, otherwise bonding will not detect link failure, speed and dun
Forcing miimon to 100msec
bonding: MII link monitoring set to 100 ms
bonding: lag0: enslaving eth2 as a backup interface with a down link.
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
bonding: lag0: enslaving eth0 as a backup interface with an up link.
bonding: lag0: link status definitely down for interface eth0, disabling it
bonding: lag0: Warning: No 802.3ad response from the link partner for any adapters in the bond
bonding: lag0: Warning: No 802.3ad response from the link partner for any adapters in the bond
bonding: lag0: Warning: No 802.3ad response from the link partner for any adapters in the bond
e100: eth2: e100_watchdog: link up, 100Mbps, full-duplex
bonding: lag0: link status definitely up for interface eth2.
ifconfig info:
host:/root # ifconfig
eth2 Link encap:Ethernet HWaddr 00:10:F3:0A:1F:96
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:78 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6101 (5.9 Kb) TX bytes:3968 (3.8 Kb)
lag0 Link encap:Ethernet HWaddr 00:10:F3:0A:1F:96
inet addr:192.168.2.100 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST MASTER MULTICAST MTU:1500 Metric:1
RX packets:4274 errors:0 dropped:0 overruns:0 frame:0
TX packets:4288 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:502360 (490.5 Kb) TX bytes:2884325 (2.7 Mb)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:20942 errors:0 dropped:0 overruns:0 frame:0
TX packets:20942 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6562561 (6.2 Mb) TX bytes:6562561 (6.2 Mb)
tcpdump info from lag0 while pinging from 192.168.2.123:
host:/root # tcpdump -i lag0
15:19:06.609557 arp who-has 192.168.2.100 tell 192.168.2.123
15:19:15.547717 arp who-has 192.168.2.100 tell 192.168.2.123
host:/root # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 lag0
Any ideas? Or is this by design?
This thread was automatically locked due to age.
