Re: enable bonding
When I enable both eth0 and eth1 the network only works after boot when
I do /etc/init.d/networking restart
That's odd. Check the
dmesg
output to see what goes wrong suring boot.
dmesg looks ok:
<snip dmesg>
tg3.c:v2.9 (March 8, 2004)
eth0: Tigon3 [partno(BCM95704A6) rev 2002 PHY(5704)]
(PCIX:133MHz:64-bit) 10/100
/1000BaseT Ethernet 00:0f:20:7a:7a:53
eth1: Tigon3 [partno(BCM95704A6) rev 2002 PHY(5704)]
(PCIX:133MHz:64-bit) 10/100
/1000BaseT Ethernet 00:0f:20:7a:7a:52
</snip>
Also when I set up bonding I can not use the network. This is what I did:
modprobe bonding miimon=250 mode=1
ifconfig bond0 81.7.167.228 netmask 255.255.255.240
ifenslave bond0 eth0 eth1
Hmm, from the top of my head that seems ok. Did the modprobe module load
properly? (what's in dmesg). Can you see the bond0 interface in
ifconfig
?
Yes I can see bond0 in ifconfig, but not if I boot. If I boot it forgets
about bonding.
What's the output of ifconfig? What's your routing table like after the bonding?
route -n
I can't play with this now as I connect via SSH. Should I try that when
I'm with the maschine? What should I look for?
Can you ping the addresses of the 3 interfaces?
ping 81.7.167.226
ping 81.7.167.227
ping 81.7.167.228
Yes.
Can you ping another host on the same network.
ping 81.7.167.229
What does
arp -a
show you.
# arp -a
? (81.7.167.225) at 00:D0:00:E4:FC:0A [ether] on eth0
This is now, when bonding is not set up.
Thanks for your time :)
Jacob
Reply to: