Re: [Server-devel] XS 0.5 Second Attempt at eth1
2008/12/5 Reuben K. Caron [EMAIL PROTECTED]: After doing a clean install 4 times and dhcpd not starting Thanks for the dedication and the report - I managed to repro the issue as you describe below. ... When I cd /etc/sysconfig/olpc-scripts ./domain_config xs5.org It creates the xs_domain_name file in /etc/sysconfig/olpc-scripts/ that's the wrong landing place, as you recognised. The current working directory should not affect us. The patch is here: http://dev.laptop.org/git?p=projects/xs-config;a=commitdiff;h=ae030b75d85fa46962134424667dfa6fb7eba5cf and there's an xs-config 0.5.8-biglonghash.rpm on its way to the xs-dev server. Not quite in the same league as the bonding issue, but a good thing to spot and fix. cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS 0.5 Second Attempt at eth1
On Fri, Dec 5, 2008 at 12:06 AM, Jerry Vonau [EMAIL PROTECTED] wrote: Anna wrote: So, what are the repercussions of this? Not sure... Martin? Good sleuthing! Bonding-related errors was the last thing I'd imagined, and with the e1000 driver too -- it's widely used and generally well maintained. Anna, what's your NIC? Ideally, we want to know the marketing make/name/model and what lspci reports for it. Perhaps I can get my hands on the same hw you have. Googling a bit for e1000 and bonding to see if there are any known issues I see quite a bit of traffic back in 2006/2007 with e1000 devices coming up / powering up late and confusing the bond drivers and sometimes bad performance. But nothing current, it looks like it got sorted out. What's your other NIC? If you run xs-swapnics (and swap the cables too), do things work better with the bonding configuration we're shipping? Also - I'm trying to think this through - I am fairly certain that one of the test machines in Wellington has an e1000 and it worked correctly for me (with a crossover cable to the AP). cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS 0.5 Second Attempt at eth1
On Fri, Dec 5, 2008 at 5:04 AM, Martin Langhoff [EMAIL PROTECTED]wrote: Anna, what's your NIC? Ideally, we want to know the marketing make/name/model and what lspci reports for it. Perhaps I can get my hands on the same hw you have. I'm currently testing on two machines. They're both circa 2003 Dells - GX270 P4's. Server A 02:09.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10) 02:0c.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02) Server B 01:07.0 Ethernet controller: Macronix, Inc. [MXIC] MX987x5 (rev 25) 01:0c.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02) Of course the Intel NICs are the onboard ones. I found the other two in my junkyard, so more than likely they're circa 2000. What's your other NIC? If you run xs-swapnics (and swap the cables too), do things work better with the bonding configuration we're shipping? I tried xs-swapnics on both boxes during my first installation attempts, so I know all four have had the different roles at some point. I've moved the D-Link to different slots in Server A when it was assigned the eth1 role. I've tried using different cables; tried with a hub and without; and tried getting an IP with an AP, a Fedora Desktop, and an Ubuntu desktop. I think I've been rather thorough. So based on all that trial and error and messing around, I think I can definitively report that I can not get bonding to work with any of my hardware. I sure hope it's not an issue with the Dell GX270, because our deployment got hold of a couple dozen of them to use as XS's. Anna Schoolfield Birmingham ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS 0.5 Second Attempt at eth1
I was hit by the same problem last week.. ARP works but no ping nor IP messages seem to get through. I am far away from the server now but I think the NIC was a CNet. On Vie, 5 de Diciembre de 2008, 12:34 pm, Reuben K. Caron wrote: Now that I have DHCPD running on a clean install. I can report that it still does not hand out IPs. When I assign my laptop ethernet adapter as 172.18.96.1 and 172.18.0.1 I do get an ARP error from the server; however, when I bump it up one address 172.18.0.2 it still does not ping. Martin Langhoff wrote: On Fri, Dec 5, 2008 at 12:06 AM, Jerry Vonau [EMAIL PROTECTED] wrote: Anna wrote: So, what are the repercussions of this? Not sure... Martin? Good sleuthing! Bonding-related errors was the last thing I'd imagined, and with the e1000 driver too -- it's widely used and generally well maintained. Anna, what's your NIC? Ideally, we want to know the marketing make/name/model and what lspci reports for it. Perhaps I can get my hands on the same hw you have. Googling a bit for e1000 and bonding to see if there are any known issues I see quite a bit of traffic back in 2006/2007 with e1000 devices coming up / powering up late and confusing the bond drivers and sometimes bad performance. But nothing current, it looks like it got sorted out. What's your other NIC? If you run xs-swapnics (and swap the cables too), do things work better with the bonding configuration we're shipping? Also - I'm trying to think this through - I am fairly certain that one of the test machines in Wellington has an e1000 and it worked correctly for me (with a crossover cable to the AP). cheers, m -- Reuben K. Caron Country Support Engineer One Laptop per Child Mobile: +1-617-230-3893 [EMAIL PROTECTED] Deployments Support http://wiki.laptop.org/go/Deployments_Support ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel --- Raúl Gutiérrez Segalés +595 981 231 839 ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS 0.5 Second Attempt at eth1
2008/12/3 Anna [EMAIL PROTECTED]: Has anyone gotten eth1 on XS 0.5 working? I have, at least on 4 different bits of hw, but I worked on it too much to be a good tester of it. Others have installed successfully. One thing that 0.5 has is that it almost always picks the ordering of the NICs _in reverse_ of what 0.4 did. So perhaps your NIC identities are reversed? You can test changing the ethernet cables around or use xs-swapnics (and then reboot). Other than that, I'm a bit lost. Can you get any output from calling ethtool eth1 ? What's the physical hw? It's also possible (though unlikely) that F9 has bad drivers for your specific hw... cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS 0.5 Second Attempt at eth1
I too am having problems with DHCP (and ejabberd) on XS 0.5. Let me detail my steps Appended upgradeany- ran default install Restarted NICs were swapped. Ran xs-swapnics Check var/log/messages found (snipet): Dec 4 09:36:58 schoolserver1 dhcpd: Listening on LPF/lanbond0/00:00:00:00:00:00/172.18.96.0/19 Dec 4 09:36:58 schoolserver1 dhcpd: Sending on LPF/lanbond0/00:00:00:00:00:00/172.18.96.0/19 Dec 4 09:06:24 schoolserver1 dhcpd: No subnet declaration for lanbond0 (172.18.96.1). Dec 4 09:06:24 schoolserver1 dhcpd: ** Ignoring requests on lanbond0. If this is not what Dec 4 09:06:24 schoolserver1 dhcpd:you want, please write a subnet declaration Dec 4 09:06:24 schoolserver1 dhcpd:in your dhcpd.conf file for the network segment Dec 4 09:06:24 schoolserver1 dhcpd:to which interface lanbond0 is attached. ** Reviewed dhcpd-xs.conf file: It did not have a declaration for 172.18.96.* I reviewed /etc/sysconfig/olpc-scripts/dhcpd.conf.1 - It did not match dhcpd-xs.conf I ran ./network-config 1 I ran ./domain-config xs4.org (i know it isn't xs4 but I'm maintaining domain for posterity) Rebooted. dhcpd-xs.conf now has the declaration for 172.18.96 DHCP is started but still does not hand out an IP. Below are ethtool outputs: [EMAIL PROTECTED] log]# ethtool eth1 Settings for eth1: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on Supports Wake-on: g Wake-on: d Current message level: 0x00ff (255) Link detected: yes [EMAIL PROTECTED] log]# ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 1 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: d Current message level: 0x0001 (1) Link detected: yes Martin Langhoff wrote: 2008/12/3 Anna [EMAIL PROTECTED]: Has anyone gotten eth1 on XS 0.5 working? I have, at least on 4 different bits of hw, but I worked on it too much to be a good tester of it. Others have installed successfully. One thing that 0.5 has is that it almost always picks the ordering of the NICs _in reverse_ of what 0.4 did. So perhaps your NIC identities are reversed? You can test changing the ethernet cables around or use xs-swapnics (and then reboot). Other than that, I'm a bit lost. Can you get any output from calling ethtool eth1 ? What's the physical hw? It's also possible (though unlikely) that F9 has bad drivers for your specific hw... cheers, m ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS 0.5 Second Attempt at eth1
Anna wrote: I tried the XS 0.5 install on another box to see if the LAN issues on my previous attempt were a hardware problem or something. It's a different model Dell with 2 nics. Here are my notes: Basic install from the CD, text mode, default everything. Boot up, then: /etc/sysconfig/olpc-scripts/domain_config anna.org Reboot /etc/sysconfig/olpc-scripts/network_config 1 Reboot Of course, the hostname was still localhost.localdomain so I edited /etc/sysconfig/network for HOSTNAME=schoolserver1 Reboot. Hostname was now updated to schoolserver1. Eth0 pulled an IP from my main LAN, so I knew which card was which. I connected my AP (set to 172.18.96.5 and netmask 255.255.224.0) but couldn't ping it. I tried connecting to the AP with an XO, but of course it didn't do anything. I even connected my Ubuntu machine to the XS, but it couldn't get an IP and I couldn't ping anything either way. Pulled this from your posted log file: Dec 2 21:00:41 alabamaxo kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1 Dec 2 21:00:41 alabamaxo kernel: Ethernet Channel Bonding Driver: v3.3.0 (June 10, 2008) Dec 2 21:00:41 alabamaxo kernel: bonding: MII link monitoring set to 100 ms Dec 2 21:00:41 alabamaxo kernel: bonding: lanbond0 is being created... Dec 2 21:00:41 alabamaxo kernel: ADDRCONF(NETDEV_UP): lanbond0: link is not ready Dec 2 21:00:41 alabamaxo kernel: e1000: eth1: e1000_watchdog: NIC Link is Up 10 Mbps Half Duplex, Flow Control: None Can you post the output of ip addr and ethtool please. What is eth1 plugged into? hub? switch? AP? Half Duplex doesn't quite look right, unless it really is a 10mbps hub. Think we need pass arp_interval= and arp_ip_target= in place of miimon= in xs_bonding, as there is no Port: MII on the gigbit card, sorry I missed that before. If your make the edit and /sbin/ifdown eth1, unload, reload the e1000 module, that should pickup the change when you /sbin/ifup eth1. Tail the log file to see if landbond0 becomes active. Jerry ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS 0.5 Second Attempt at eth1
Reuben K. Caron wrote: I too am having problems with DHCP (and ejabberd) on XS 0.5. Let me detail my steps Appended upgradeany- ran default install Restarted NICs were swapped. Ran xs-swapnics Check var/log/messages found (snipet): Dec 4 09:36:58 schoolserver1 dhcpd: Listening on LPF/lanbond0/00:00:00:00:00:00/172.18.96.0/19 Dec 4 09:36:58 schoolserver1 dhcpd: Sending on LPF/lanbond0/00:00:00:00:00:00/172.18.96.0/19 Dec 4 09:06:24 schoolserver1 dhcpd: No subnet declaration for lanbond0 (172.18.96.1). Dec 4 09:06:24 schoolserver1 dhcpd: ** Ignoring requests on lanbond0. If this is not what Dec 4 09:06:24 schoolserver1 dhcpd:you want, please write a subnet declaration Dec 4 09:06:24 schoolserver1 dhcpd:in your dhcpd.conf file for the network segment Dec 4 09:06:24 schoolserver1 dhcpd:to which interface lanbond0 is attached. ** Reviewed dhcpd-xs.conf file: It did not have a declaration for 172.18.96.* I reviewed /etc/sysconfig/olpc-scripts/dhcpd.conf.1 - It did not match dhcpd-xs.conf I ran ./network-config 1 I ran ./domain-config xs4.org (i know it isn't xs4 but I'm maintaining domain for posterity) Rebooted. dhcpd-xs.conf now has the declaration for 172.18.96 DHCP is started but still does not hand out an IP. Below are ethtool outputs: [EMAIL PROTECTED] log]# ethtool eth1 Settings for eth1: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on Supports Wake-on: g Wake-on: d Current message level: 0x00ff (255) Link detected: yes OK, is starting to look like the 1000baseT nics are having issues with bonding, can you try the fix I proposed to Anna. Jerry ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS 0.5 Second Attempt at eth1
Jerry Vonau wrote: Reuben K. Caron wrote: I too am having problems with DHCP (and ejabberd) on XS 0.5. Let me detail my steps Appended upgradeany- ran default install Restarted NICs were swapped. Ran xs-swapnics Check var/log/messages found (snipet): Dec 4 09:36:58 schoolserver1 dhcpd: Listening on LPF/lanbond0/00:00:00:00:00:00/172.18.96.0/19 Dec 4 09:36:58 schoolserver1 dhcpd: Sending on LPF/lanbond0/00:00:00:00:00:00/172.18.96.0/19 Dec 4 09:06:24 schoolserver1 dhcpd: No subnet declaration for lanbond0 (172.18.96.1). Dec 4 09:06:24 schoolserver1 dhcpd: ** Ignoring requests on lanbond0. If this is not what Dec 4 09:06:24 schoolserver1 dhcpd:you want, please write a subnet declaration Dec 4 09:06:24 schoolserver1 dhcpd:in your dhcpd.conf file for the network segment Dec 4 09:06:24 schoolserver1 dhcpd:to which interface lanbond0 is attached. ** Reviewed dhcpd-xs.conf file: It did not have a declaration for 172.18.96.* I reviewed /etc/sysconfig/olpc-scripts/dhcpd.conf.1 - It did not match dhcpd-xs.conf I ran ./network-config 1 I ran ./domain-config xs4.org (i know it isn't xs4 but I'm maintaining domain for posterity) Rebooted. dhcpd-xs.conf now has the declaration for 172.18.96 DHCP is started but still does not hand out an IP. Below are ethtool outputs: [EMAIL PROTECTED] log]# ethtool eth1 Settings for eth1: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on Supports Wake-on: g Wake-on: d Current message level: 0x00ff (255) Link detected: yes OK, is starting to look like the 1000baseT nics are having issues with bonding, can you try the fix I proposed to Anna. OK, I'm tired, all on one line at the bottom /etc/modprobe.d/xs_bonding: options lanbond0 mode=active-backup arp_interval=1000 arp_ip_target=ip-of-AP Jerry ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS 0.5 Second Attempt at eth1
Thanks for clarification. Still no go: Dec 4 12:12:24 schoolserver1 kernel: eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1 Dec 4 12:12:24 schoolserver1 kernel: eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1 Dec 4 12:12:24 schoolserver1 kernel: Ethernet Channel Bonding Driver: v3.3.0 (June 10, 2008) Dec 4 12:12:24 schoolserver1 kernel: bonding: ARP monitoring set to 1000 ms, validate none, with 1 target(s): 172.18.0.1 Dec 4 12:12:24 schoolserver1 kernel: bonding: lanbond0 is being created... Dec 4 12:12:24 schoolserver1 kernel: ADDRCONF(NETDEV_UP): lanbond0: link is not ready Dec 4 12:12:24 schoolserver1 kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready Dec 4 12:12:24 schoolserver1 kernel: tg3: eth1: Link is up at 100 Mbps, full duplex. Dec 4 12:12:24 schoolserver1 kernel: tg3: eth1: Flow control is on for TX and on for RX. Dec 4 12:12:24 schoolserver1 kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready Dec 4 12:12:24 schoolserver1 kernel: bonding: mshbond0 is being created... Dec 4 12:12:24 schoolserver1 kernel: ADDRCONF(NETDEV_UP): mshbond0: link is not ready Dec 4 12:12:24 schoolserver1 kernel: bonding: mshbond1 is being created... Dec 4 12:12:24 schoolserver1 kernel: ADDRCONF(NETDEV_UP): mshbond1: link is not ready Dec 4 12:12:24 schoolserver1 kernel: bonding: mshbond2 is being created... Dec 4 12:12:24 schoolserver1 kernel: ADDRCONF(NETDEV_UP): mshbond2: link is not ready ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS 0.5 Second Attempt at eth1
Not having done this before, and after getting syntax errors and command not found for speed, I googled and edited /etc/sysconfig/network-scripts/ifcfg-eth1 like so. I figured 100 might be a good place to start. I haven't tried half duplex yet, but I can if you think that would do anything. ETHTOOL_OPTS=speed 100 duplex full autoneg off Restarting the network didn't give any errors. After that, ethtool eth1 gives this: [EMAIL PROTECTED] ~]# 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: Not reported Advertised auto-negotiation: No Speed: Unknown! (65535) Duplex: Unknown! (255) Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: off Supports Wake-on: umbg Wake-on: g Current message level: 0x0007 (7) Link detected: no Of course, still no pinging anything. In fact, I don't have blinky lights on the NIC anymore or a link light on the AP, which I had before. Anna ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS 0.5 Second Attempt at eth1
Anna wrote: Not having done this before, and after getting syntax errors and command not found for speed, I googled and edited /etc/sysconfig/network-scripts/ifcfg-eth1 like so. I figured 100 might be a good place to start. I haven't tried half duplex yet, but I can if you think that would do anything. ETHTOOL_OPTS=speed 100 duplex full autoneg off Restarting the network didn't give any errors. After that, ethtool eth1 gives this: [EMAIL PROTECTED] ~]# 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: Not reported Advertised auto-negotiation: No Speed: Unknown! (65535) Duplex: Unknown! (255) Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: off Supports Wake-on: umbg Wake-on: g Current message level: 0x0007 (7) Link detected: no Of course, still no pinging anything. In fact, I don't have blinky lights on the NIC anymore or a link light on the AP, which I had before. Anna OK, I'm out of ideas, lets see if we can configure eth1 without bonding, not sure if this is nic driver issue with bonding, or what... backup the ifcfg-eth1 file, copy ifcfg-landbond0, ifcfg-lanbond0:1 ifcfg-lanbond0:2 and to ifcfg-eth1, ifcfg-eth1:1 ifcfg-eth1:2 respectively. edit the ifcfg-eth1* files changing the device line to match the new name, eth1 eth1:1 eth1:2. Please stop the network before editing the files. Jerry ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS 0.5 Second Attempt at eth1
On Thu, Dec 4, 2008 at 6:29 PM, Jerry Vonau [EMAIL PROTECTED] wrote: OK, I'm out of ideas, lets see if we can configure eth1 without bonding, not sure if this is nic driver issue with bonding, or what... backup the ifcfg-eth1 file, copy ifcfg-landbond0, ifcfg-lanbond0:1 ifcfg-lanbond0:2 and to ifcfg-eth1, ifcfg-eth1:1 ifcfg-eth1:2 respectively. edit the ifcfg-eth1* files changing the device line to match the new name, eth1 eth1:1 eth1:2. Please stop the network before editing the files. Jerry W00t! That did it. I'm emailing from my Ubuntu machine on: eth0 Link encap:Ethernet HWaddr 00:0f:1f:80:0d:ea inet addr:172.18.96.2 Bcast:172.18.127.255 Mask:255.255.224.0 inet6 addr: fe80::20f:1fff:fe80:dea/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:49210 errors:0 dropped:0 overruns:0 frame:0 TX packets:47393 errors:0 dropped:0 overruns:0 carrier:0 collisions:2059 txqueuelen:10 RX bytes:27778611 (26.4 MB) TX bytes:8279042 (7.8 MB) Base address:0xdf40 Memory:feae-feb0 My wifi AP is up and running and an XO pulled 172.18.96.3. Obviously there's a hub in the middle. Oh, here's the latest output of ethtool eth1: [EMAIL PROTECTED] ~]# 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: 10Mb/s Duplex: Half Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: umbg Wake-on: g Current message level: 0x0007 (7) Link detected: yes So, what are the repercussions of this? Anna ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
