<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I too am having problems with DHCP (and ejabberd) on XS 0.5.<br>
<br>
Let me detail my steps<br>
<br>
Appended upgradeany- ran default install<br>
Restarted<br>
NICs were swapped. <br>
Ran xs-swapnics<br>
<br>
Check var/log/messages found (snipet):<br>
<br>
Dec 4 09:36:58 schoolserver1 dhcpd: Listening on
LPF/lanbond0/00:00:00:00:00:00/172.18.96.0/19<br>
Dec 4 09:36:58 schoolserver1 dhcpd: Sending on
LPF/lanbond0/00:00:00:00:00:00/172.18.96.0/19<br>
----<br>
<br>
Dec 4 09:06:24 schoolserver1 dhcpd: No subnet declaration for lanbond0
(172.18.96.1).<br>
Dec 4 09:06:24 schoolserver1 dhcpd: ** Ignoring requests on lanbond0.
If this is not what<br>
Dec 4 09:06:24 schoolserver1 dhcpd: you want, please write a subnet
declaration<br>
Dec 4 09:06:24 schoolserver1 dhcpd: in your dhcpd.conf file for the
network segment<br>
Dec 4 09:06:24 schoolserver1 dhcpd: to which interface lanbond0 is
attached. **<br>
<br>
Reviewed dhcpd-xs.conf file: It did not have a declaration for
172.18.96.*<br>
<br>
I reviewed /etc/sysconfig/olpc-scripts/dhcpd.conf.1 - It did not match
dhcpd-xs.conf<br>
<br>
I ran ./network-config 1<br>
I ran ./domain-config xs4.org (i know it isn't xs4 but I'm maintaining
domain for posterity)<br>
<br>
Rebooted.<br>
<br>
dhcpd-xs.conf now has the declaration for 172.18.96<br>
<br>
DHCP is started but still does not hand out an IP.<br>
<br>
Below are ethtool outputs:<br>
<br>
[root@schoolserver1 log]# ethtool eth1<br>
Settings for eth1:<br>
Supported ports: [ TP ]<br>
Supported link modes: 10baseT/Half 10baseT/Full <br>
100baseT/Half 100baseT/Full <br>
1000baseT/Half 1000baseT/Full <br>
Supports auto-negotiation: Yes<br>
Advertised link modes: 10baseT/Half 10baseT/Full <br>
100baseT/Half 100baseT/Full <br>
1000baseT/Half 1000baseT/Full <br>
Advertised auto-negotiation: Yes<br>
Speed: 100Mb/s<br>
Duplex: Full<br>
Port: Twisted Pair<br>
PHYAD: 1<br>
Transceiver: internal<br>
Auto-negotiation: on<br>
Supports Wake-on: g<br>
Wake-on: d<br>
Current message level: 0x000000ff (255)<br>
Link detected: yes<br>
[root@schoolserver1 log]# ethtool eth0<br>
Settings for eth0:<br>
Supported ports: [ TP MII ]<br>
Supported link modes: 10baseT/Half 10baseT/Full <br>
100baseT/Half 100baseT/Full <br>
Supports auto-negotiation: Yes<br>
Advertised link modes: 10baseT/Half 10baseT/Full <br>
100baseT/Half 100baseT/Full <br>
Advertised auto-negotiation: Yes<br>
Speed: 100Mb/s<br>
Duplex: Full<br>
Port: MII<br>
PHYAD: 1<br>
Transceiver: internal<br>
Auto-negotiation: on<br>
Supports Wake-on: pumbg<br>
Wake-on: d<br>
Current message level: 0x00000001 (1)<br>
Link detected: yes<br>
<br>
<br>
<br>
<br>
Martin Langhoff wrote:
<blockquote
cite="mid:46a038f90812040524l3af39bd6lbc146288aa32fef1@mail.gmail.com"
type="cite">
<pre wrap="">2008/12/3 Anna <a class="moz-txt-link-rfc2396E" href="mailto:aschoolf@gmail.com"><aschoolf@gmail.com></a>:
</pre>
<blockquote type="cite">
<pre wrap="">Has anyone gotten eth1 on XS 0.5 working?
</pre>
</blockquote>
<pre wrap=""><!---->
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
</pre>
</blockquote>
</body>
</html>