[Server-devel] XS 0.5 Second Attempt at eth1

[Anna]

Per Jerry's suggestion, I added this to /etc/modprobe.d/xs_bonding and
deleted stuff from the prior suggestion, though I can put that back in if
it's going to make a difference.

options lanbond0 mode=active-backup arp_interval=1000 arp_ip_target=
172.18.96.5

I went ahead and rebooted.  I connected my AP, which is set to that IP
address, directly to eth1.  Still couldn't ping it.

When I do ifdown eth1 then ifup eth1, here's the output from
/var/log/messages:

Dec  4 12:30:39 schoolserver1 avahi-daemon[3209]: Withdrawing address record
for fe80::20f:1fff:fedd:3b93 on eth1.
Dec  4 12:30:40 schoolserver1 ntpd[3109]: Deleting interface #14 eth1,
fe80::20f:1fff:fedd:3b93#123, interface stats: received=0, sent=0,
dropped=0, active_time=951 secs
Dec  4 12:30:44 schoolserver1 kernel: ADDRCONF(NETDEV_UP): eth1: link is not
ready

I even set my Ubuntu machine to 172.18.96.5 netmask 255.255.224.0 and
plugged it in directly to the XS.  Still nothing.

Here's the output of the other stuff you asked for.

[root at schoolserver1 ~]# ethtool eth1
Settings for eth1:
    Supported ports: [ TP ]
    Supported link modes:   10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Full
    Supports auto-negotiation: Yes
    Advertised link modes:  10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Full
    Advertised auto-negotiation: Yes
    Speed: Unknown! (65535)
    Duplex: Unknown! (255)
    Port: Twisted Pair
    PHYAD: 0
    Transceiver: internal
    Auto-negotiation: on
    Supports Wake-on: umbg
    Wake-on: g
    Current message level: 0x00000007 (7)
    Link detected: no

[root at schoolserver1 ~]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state
DOW
N qlen 100
    link/ether 00:0f:1f:dd:3b:93 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::20f:1fff:fedd:3b93/64 scope link
       valid_lft forever preferred_lft forever
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UNKNO
WN qlen 1000
    link/ether 00:80:c6:ea:10:2e brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.9/24 brd 192.168.1.255 scope global eth0
    inet6 fe80::280:c6ff:feea:102e/64 scope link
       valid_lft forever preferred_lft forever
4: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
5: lanbond0: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc
noqueue s
tate DOWN
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
    inet 172.18.96.1/19 brd 172.18.127.255 scope global lanbond0
    inet 172.18.1.1/24 brd 172.18.1.255 scope global lanbond0:1
    inet 172.18.0.1/24 brd 172.18.0.255 scope global lanbond0:2
6: mshbond0: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc
noqueue s
tate DOWN
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
    inet 172.18.10.1/23 brd 172.18.11.255 scope global mshbond0
    inet 172.18.16.1/24 brd 172.18.16.255 scope global mshbond0:1
7: mshbond1: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc
noqueue s
tate DOWN
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
    inet 172.18.12.1/23 brd 172.18.13.255 scope global mshbond1
8: mshbond2: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc
noqueue s
tate DOWN
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
    inet 172.18.14.1/23 brd 172.18.15.255 scope global mshbond2

And yes, I know which card is which.  If eth0 weren't connected properly to
my LAN, I couldn't have scp'd this output over to my "main" XS 0.5 test box,
which has active jabber users on it, so I'm trying to keep from messing with
it too much until I know exactly what's going on.

On both boxes, I have swapped cables, moved the NICs to different slots,
tried connecting with and without hubs, tried connecting to the AP and
Fedora and Ubuntu desktops, pretty much everything I can think of.  They're
both old Dells from circa 2003, though they're different models.  Both
worked fine with XS 0.4.

Anna Schoolfield
Birmingham
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.laptop.org/pipermail/server-devel/attachments/20081204/087daf87/attachment-0001.htm