I recently acquired cable internet service through
AT&T @Home. I currently lease their SURFBoard SB3100 cable modem. My
intended LEAF box is a Pentium 120MHz with 16MB RAM, 1.44 MB floppy, 1 DLink
DFE530TX+ NIC, and 1 NetGear FA311 NIC. The BIOS is AMIBIOS 1.00.02.CB0. My
internal, windows box has a NetGear FA311 NIC as well.
I started with Dachstein v1.0.2-1680. I uncommented
pci-scan and added via-rhine (for the DLink NIC) and natsemi (for the NetGear
NIC) in /etc/modules (I also tried the fa311 module without successful boot).
The natsemi.o and via-rhine.o modules were added and backed up.
I modified network.conf as follows (everything else
left at default setting):
MAX_LOOP=2
HOSTNAME=BIER
HOSTS0="eth1_IPADDR $HOSTNAME.attbi.com $HOSTNAME
fw"
I backed up etc.
When I reboot two of the last messages to appear on
the console are:
No subnet declaration for eth1
(0.0.0.0).
Please write a subnet declaration in your
dhcpd.conf file for the network segment to which eth1 is attached.
I've seen some discussion in the archives regarding
these messages, but there doesn't appear to be a consensus on the resolution.
The Dachstein documentation implies that configuration will be automatic when
connected to a DHCP server. Does that mean the subnet declaration in dhcpd.conf
is OK? Or do I need to modify this file?
Other discussions center on whether or not the
lease must be released prior to booting the LEAF box with the modem attached. I
tried releasing the lease via winipcfg, and then connecting the modem to the
LEAF box without any success. I also tried resetting the modem via power down (a
couple hours) to clear the MAC address, without success. I also tried an archive
suggestion to set the eth0 MAC address in network.conf to that of the NIC in the
windows box, which was used to install the internet service. This also seemed to
have little effect.
Several perhaps pertinent messages scroll by on the
console during boot up too fast to read (is there a way to scroll back?).
I managed to catch the following messages on
screen, but not in logs:
DHCPDISCOVER on eth0 to 255:255:255:255 port
67
DHCPOFFER 12.242.19:34
DHCPREQUEST on eth0 to 255:255:255:255 port
67
DHCPACK 12:242:19.34
Does this look like a good handshake? winipcfg on
the windows box shows that 12.242.19.34 is the ISPs DHCP server. Other pertinent
info from winipcfg:
MAC address: 00-02-E3-04-DA-61 (I tried to assign
this number to eth0)
IP address: 12.252.81.273
subnet mask: 255.255.248.0
Default Gateway: 12.252.80.1
Upon logging in to LEAF box I tried to ping
192.168.1.1. This resulted in 100% packet loss, but the NIC lights appeared to
cycle at 1 Hz as someone in the archives has suggested.
I executed net start with the following
result:
Starting Network:[IP Always Defrag:
ENABLED]
IP Filters: firewall [IP
forwarding: ENABLED]
Loopback interface:
lo
Starting interface: Cannot find
device eth1
SIOCGIFFLAGS: Operation not supported by device
eth1
Hostname: BIER
Static NS: 2 hosts
It seems that regardless which slot the NICs
are in or which order the module names are listed in /etc/modules, eth0 is
always associated with the NetGear NIC. How do I force the use of the DLink NIC
as eth0?
About the only things I have not tried
are:
1. Attempting to boot LEAF box with only one
NIC.
2. swapping the Windows NIC with one of the LEAF
NICs
Can anyone suggest what I might try next to get
this LEAF box operational? Any help will be appreciated.
Thanks,
Mike
|
- Re: [Leaf-user] Need help getting LEAF running hallm
- Re: [Leaf-user] Need help getting LEAF running guitarlynn
- Re: [Leaf-user] Need help getting LEAF running Matt Schalit
- Re: [Leaf-user] Need help getting LEAF running Patrick Benson
- Re: [Leaf-user] Need help getting LEAF running Jack Coates
- Re: [Leaf-user] Need help getting LEAF running guitarlynn
- Re: [Leaf-user] Need help getting LEAF running Victor McAllister
- Re: [Leaf-user] Need help getting LEAF running Robert Chambers
- RE: [Leaf-user] Need help getting LEAF running Hall, Michael A