That took care of things. Thank you very much, Jerry.<br><br><div class="gmail_quote">On Mon, Oct 26, 2009 at 9:14 AM, Jerry Vonau <span dir="ltr"><<a href="mailto:jvonau@shaw.ca">jvonau@shaw.ca</a>></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="im">On Mon, 2009-10-26 at 08:48 -0700, Alex Kleider wrote:<br>
> Jerry (and others,)<br>
><br>
> Forgive me for not being clear enough: (I mentioned eth1 picking up an<br>
> IP under another OS only to demonstrate that the hardware seems<br>
> good.)<br>
><br>
> The XS configuration is pretty standard: I have the Internet connected<br>
> via eth0 as you mention. The second interface card (which I've been<br>
> calling eth1) is connected to a WAP (which on another computer running<br>
> XS has been demonstrated to do its job of establishing connectivity<br>
> with XOs.) The problem is that eth1 is not used to connect to<br>
> lanbond0.<br>
><br>
> Your suggestion that I run ip addr gives us an explanation:<br>
><br>
> eth1 is NOT LISTED. Instead that card is listed as eth2.<br>
> So I think the challenge now is to either have it seen as eth1<br>
> or to get the landbond0 connection to connect to eth2 instead of<br>
> eth1.ip addr reveals no entry for eth1, eth0 has an IP address on my<br>
> network as expected, the card that I've been referring to as eth1 is<br>
> listed as eth2!<br>
> 3: eth2 .....state DOWN qlen 1000<br>
> link/ether 00:26:5a:05:ac:31<br>
><br>
<br>
</div>Ok, that is a easy fix, as root<br>
service network stop<br>
then edit:<br>
/etc/udev/rules.d/70-persistent-net.rules<br>
<br>
if there is a line that has eth1 in it, delete that line, and change the<br>
line that has eth2 to be eth1.<br>
<br>
save and reboot to have the changes take effect.<br>
<br>
That should fix you up,<br>
<font color="#888888"><br>
Jerry<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</font></blockquote></div><br>