<br><br><div class="gmail_quote">On Tue, Dec 9, 2008 at 11:49 AM, Jesper Krogh <span dir="ltr"><jesper@krogh.cc></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">
<br>
</div>I reverted the systems to the latest <a href="http://2.6.26.8" target="_blank">2.6.26.8</a> kernel and it havent been<br>
on my priority list since.. unfortunately.</blockquote><div><br>I reinstalled fresh and, after the usual setup stuff, compiled and installed <a href="http://2.6.26.8">2.6.26.8</a> according to these instructions:<br><br>
<a href="http://www.howtoforge.com/kernel_compilation_fedora_p2">http://www.howtoforge.com/kernel_compilation_fedora_p2</a><br><br>So now I've got this:<br><br>[root@schoolserver1 ~]# uname -a<br>Linux schoolserver1 <a href="http://2.6.26.8">2.6.26.8</a> #1 SMP Tue Dec 9 15:16:54 CST 2008 i686 i686 i386 GNU/Linux<br>
<br>In the messages, I saw it was complaining it didn't know how to bring up bonding. So, per Jerry's earlier suggestion, I edited /etc/modprobe.d/xs_bonding with this:<br><br>options lanbond0 mode=active-backup miimon=100<br>
options mshbond0 mode=active-backup miimon=100<br>options mshbond1 mode=active-backup miimon=100<br>options mshbond2 mode=active-backup miimon=100<br><br>But after a reboot, this is in /var/log/messages:<br><br>Dec 9 16:57:05 schoolserver1 kernel: bonding: MII link monitoring set to 100 ms<br>
Dec 9 16:57:05 schoolserver1 kernel: bonding: lanbond0 is being created...<br>Dec 9 16:57:05 schoolserver1 kernel: ADDRCONF(NETDEV_UP): lanbond0: link is not ready<br>Dec 9 16:57:05 schoolserver1 kernel: bonding: mshbond0 is being created...<br>
Dec 9 16:57:05 schoolserver1 kernel: ADDRCONF(NETDEV_UP): mshbond0: link is not ready<br>Dec 9 16:57:05 schoolserver1 kernel: bonding: mshbond1 is being created...<br>Dec 9 16:57:05 schoolserver1 kernel: ADDRCONF(NETDEV_UP): mshbond1: link is not ready<br>
Dec 9 16:57:05 schoolserver1 kernel: bonding: mshbond2 is being created...<br>Dec 9 16:57:05 schoolserver1 kernel: ADDRCONF(NETDEV_UP): mshbond2: link is not ready<br><br>I have an AP set to <a href="http://172.18.96.5">172.18.96.5</a> plugged into eth1, but can't ping it. The link is up, though:<br>
<br>[root@schoolserver1 ~]# ethtool eth1<br>Settings for eth1:<br> Supported ports: [ TP ]<br> Supported link modes: 10baseT/Half 10baseT/Full <br> 100baseT/Half 100baseT/Full <br> 1000baseT/Full <br>
Supports auto-negotiation: Yes<br> Advertised link modes: 10baseT/Half 10baseT/Full <br> 100baseT/Half 100baseT/Full <br> 1000baseT/Full <br> Advertised auto-negotiation: Yes<br>
Speed: 100Mb/s<br> Duplex: Full<br> Port: Twisted Pair<br> PHYAD: 0<br> Transceiver: internal<br> Auto-negotiation: on<br> Supports Wake-on: umbg<br> Wake-on: g<br> Current message level: 0x00000007 (7)<br>
Link detected: yes<br><br>So using the older kernel didn't automagically fix things, at least not for me.<br><br>Anna Schoolfield<br>Birmingham<br></div></div><br>