[Server-devel] eth1 problems

[Alex Kleider]

Jerry (and others,)

Forgive me for not being clear enough: (I mentioned eth1 picking up an IP
under another OS only to demonstrate that the hardware seems good.)

The XS configuration is pretty standard: I have the Internet connected via
eth0 as you mention. The second interface card (which I've been calling
eth1) is connected to a WAP (which on another computer running XS has been
demonstrated to do its job of establishing connectivity with XOs.) The
problem is that eth1 is not  used to connect to lanbond0.

Your suggestion that I run ip addr gives us an explanation:

eth1 is NOT LISTED. Instead that card is listed as eth2.
So I think the challenge now is to either have it seen as eth1
or to get the landbond0 connection to connect to eth2 instead of eth1.ip
addr reveals no entry for eth1, eth0 has an IP address on my network as
expected, the card that I've been referring to as eth1 is listed as eth2!
3: eth2 .....state DOWN qlen 1000
    link/ether 00:26:5a:05:ac:31


I'll spend a little quality time with
/usr/share/doc/xs-config-0.6.0.16.g3c1e949/*

thanks,
alex



On Sun, Oct 25, 2009 at 10:00 PM, Jerry Vonau <jvonau at shaw.ca> wrote:

> On Sun, 2009-10-25 at 20:11 -0700, Alex Kleider wrote:
> > I'd be grateful if someone on the list could help me set up an XS
> > using a
> > desktop.
> >
> > For reasons I can not understand, the eth1 is not recognized
> > although research suggests that the correct driver is there.
> > ie dmesg output includes
> > skge eth1: addr 00:26:5a:05:ac:31
> > ...
> > bonding: lanbond0 is being created..
> > ADDRCONF(NETDEV_UP): lanbond0: link is not ready
> >
> > during boot up the following flashes by:
> > Bringing up interface lanbond0: Device eth1 does not seem to be
> > present.
> >
> That would be normal if you have only one nic. How many nics are
> installed in this machine? Did you edit any config files?
>
> Two nics: eth0 connected to the internet and works fine; eth1 (hardware
demonstrated to be fine under another OS) gets its driver skge eth1
recognized at boot time but later in the process the XS seems to refer to
the same card as eth2.


No relevant config files changed. I only changed /etc/ssh/sshd.config to
allow root login.


>  > On the same computer, if I use an Ubuntu live CD
> > with eth1 connected to my home network, it picks up an IP address
> > without any difficulty. Its mac is 00:26:5a:ac:31.
>
> If your looking to just get internet access to XS have a look at
> README.networking in /usr/share/doc/xs-config-*/  The *bond interfaces
> that are shown with "ip addr" are just holders for the ip addresses that
> the default XS layout would use. This allows a cleaner DHCP server
> installation, where the internal interfaces that dhcp is bound to don't
> need to be present at boot. If eth1 is present it should be added to
> lanbond0.
>
>
 With your saying "it picks up an IP address", that suggests that your
> home network has a dhcp server on it already. If eth0 were to be plugged
> in to your home network, you should get a dhcp address on eth0. The XS
> layout assumes that eth0 will be the interface that would have the
> default gateway to the internet, and would be providing XS services,
> including dhcp, to whatever is connected to the *bond interfaces.
>
> In a terminal window what is the output of "ip addr"?
>
> Jerry
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.laptop.org/pipermail/server-devel/attachments/20091026/969ba666/attachment.htm