RedHat 9 Network Problem
Here are the requested files: Ifcfg-eth0: # Lite-On|LNE100TX DEVICE=eth0 ONBOOT=yes BOOTPROTO=dhcp HWADDR=FF:FF:FF:FF:FF:FF USERCTL=no PEERDNS=yes TYPE=Ethernet NETMASK=255.255.255.0 IPADDR=192.168.0.2 GATEWAY=192.168.0.1 Modules.conf: alias usb-controller usb-uhci alias sound-slot-0 emu10k1 post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L
/dev/null 2>&1 || : pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S /dev/null 2>&1 || : alias eth0 tulip
network: NETWORKING=yes HOSTNAME= Output of /sbin/lspci -vv - Non network devices removed to pass 40k post filter 00:0d.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20) Subsystem: Lite-On Communications Inc LNE100TX Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR+ Latency: 32 Interrupt: pin A routed to IRQ 9 Region 0: I/O ports at 8800 [disabled] [size=256] Region 1: Memory at d5800000 (32-bit, non-prefetchable) [disabled] [size=256] Expansion ROM at <unassigned> [disabled] [size=256K] ...... -----Original Message----- From: wlug-bounces@mail.wlug.org [mailto:wlug-bounces@mail.wlug.org] On Behalf Of Charles R. Anderson Sent: Tuesday, March 30, 2004 10:21 AM To: Worcester Linux Users Group Subject: Re: [Wlug] RedHat 9 Network Problem On Tue, Mar 30, 2004 at 10:13:15AM -0500, Dwight A. Ernest wrote:
Include your /etc/sysconfig/network-scripts/ifcfg-eth0 and your /etc/sysconfig/network files in an email so we can see what they look like.
Also include /etc/modules.conf and the Ethernet card entry from the "/sbin/lspci -vv" output. _______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
On Wed, Mar 31, 2004 at 10:25:53PM -0500, Joel J. Young wrote:
# Lite-On|LNE100TX DEVICE=eth0 ONBOOT=yes BOOTPROTO=dhcp HWADDR=FF:FF:FF:FF:FF:FF
The HWADDR here looks wrong. Can you post the output of: /sbin/ifconfig eth0 The HWaddr listed there should be what you set HWADDR= to in ifcfg-eth0.
Here it is: eth0 Link encap:Ethernet HWaddr FF:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:2490342 overruns:0 frame:0 TX packets:0 errors:3 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:9 I'm suspicious about the HWaddr too, but I don't know why it wouldn't be picking up the MAC address.
-----Original Message----- From: wlug-bounces@mail.wlug.org [mailto:wlug-bounces@mail.wlug.org] On Behalf Of Charles R. Anderson Sent: Wednesday, March 31, 2004 10:41 PM To: Wlug@mail.wlug.org Subject: Re: [Wlug] RedHat 9 Network Problem
On Wed, Mar 31, 2004 at 10:25:53PM -0500, Joel J. Young wrote:
# Lite-On|LNE100TX DEVICE=eth0 ONBOOT=yes BOOTPROTO=dhcp HWADDR=FF:FF:FF:FF:FF:FF
The HWADDR here looks wrong. Can you post the output of:
/sbin/ifconfig eth0
The HWaddr listed there should be what you set HWADDR= to in ifcfg-eth0.
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
That's the key problem, I think. Until you debug that, you're not going to get anywhere. You might try specifying a non-all-ones (the address shown is all ones in binary) MAC address in an ifconfig conmmand and see what happens. Joel J. Young wrote:
Here it is: eth0 Link encap:Ethernet HWaddr FF:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:2490342 overruns:0 frame:0 TX packets:0 errors:3 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:9
I'm suspicious about the HWaddr too, but I don't know why it wouldn't be picking up the MAC address.
-- Dwight A. Ernest, dwight at significant dot com GPG key A6999567 Cell: +1-508-523-1416 FAX: +1-978-405-2504 YIM: dwight_ernest RHCE #803004293310030 http://significant.com/~dwight/ KA2CNN Papa, partner, pilot, net geek, sysadmin, consultant, cohouser.
On Thu, Apr 01, 2004 at 12:07:28AM -0500, Joel J. Young wrote:
Here it is: eth0 Link encap:Ethernet HWaddr FF:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:2490342 overruns:0 frame:0 TX packets:0 errors:3 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:9
Adding my voice to the chorus.... :) Is it a PCI or ISA network device? Usually when I see FF:FF... it's when my ISA NIC is using the wrong IRQ, or the interrupt is conflicting with another device. So when the OS asks the NIC what the HWaddr is, it can't respond. -Chuck
participants (4)
-
Charles R. Anderson -
Chuck Homic -
Dwight A. Ernest -
Joel J. Young