[Sussex] Anyone into bondage?

[Jon Fautley]

Brendan Whelan wrote:
> Jon,
> 
> Thanks for the response..............
> The problem is that, when I try to use bonding, I can connect to the
> Ethernet socket on the motherboard but not to the one on a separate card.
> (When not bonded, if I configure the two Ethernet ports with different IP
> addresses then they both work.) Below are the various files and system
> information. I have executed:
> service network restart
> ifup eth0
> ifup eth1
> 
[SNIP]

I'm not quite sure what you mean by this? When using bonding, the 
seperate physical interfaces 'go away' and can't be used individually. 
All network configuration or usage needs to go through the bondX device 
(bond0 in your case).

Do you mean that when you remove one of the network cables, it's not 
working? I.e. you pull the cable from the onboard NIC and it doesn't 
continue to use the offboard NIC?

Try running 'ifconfig eth0 up; ifconfig eth1 up' and see if this makes a 
difference. I don't think it will do, but it's worth a try ;)

What mode are you running the bonding in? Are you using the default? (if 
so, what Distro).

it's worth checking that the system realises when you remove the cable 
too, run ethtool eth0 | grep "Link" and see what it reports, both before 
and after the cable pull. Try this for eth1 too.

> I don't know where the 169.254.0.0 is coming from as it isn't one of my
> addresses?

That's the standard 'autoconfigure' address block as defined by RFC1918. 
All systems that can't obtain a DHCP lease are entitled to grab a random 
address in that range (169.254/16). It's most commonly used by Microsoft 
Windows to enable NetBIOS over TCP/IP to function in a broken network 
environment.

Regards,

Jon
-- 
Jon Fautley <jfautley at redhat.com>     direct: +44 1483 739615
  Presales Technical Consultant        office: +44 1483 300169
  Red Hat UK                           mobile: +44 7841 558683
  10 Alan Turing Road, Surrey Research Park, Guildford GU2 7YF