Re: Kingston KNE111TX NIC supported ???
From: Moe Trin (ibuprofin_at_painkiller.example.tld)
Date: 09/05/04
- Next message: Anton Ertl: "Re: continously running system or not?"
- Previous message: Moe Trin: "Re: continously running system or not?"
- Maybe in reply to: Tauno Voipio: "Re: Kingston KNE111TX NIC supported ???"
- Next in thread: Moe Trin: "Re: Kingston KNE111TX NIC supported ???"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 05 Sep 2004 11:19:38 -0500
In article <7687bfbd.0409041857.27a4d2f2@posting.google.com>,
Linux Lover wrote:
>mcintosh@nospam.com (Allen McIntosh) wrote in message
news:<ch7p6b$5av$1@mc-pc.research.telcordia.com>...
>> 3) Is there information for eth0 in the output of
>> ifconfig -a
>eth0 Link encap:Ethernet HWaddr 00:C0:F0:70:3B:A2
[compton ~]$ etherwhois 00:C0:F0
00-C0-F0 (hex) KINGSTON TECHNOLOGY CORP.
00C0F0 (base 16) KINGSTON TECHNOLOGY CORP.
17600 NEWHOPE STREET
FOUNTAIN VALLEY CA 92708
[compton ~]$
OK, you are definately finding the card.
> inet addr:192.168.0.130 Bcast:192.168.0.255
>Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:3 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2 errors:2 dropped:0 overruns:0 carrier:4
Not much use, but the 'carrier' count indicates a hardware problem
>The cable cannot be bad because when I reboot the machine to Windows
>XP (without touching anything in the hardware), it simply works.
Could that be a 10/100 MHz problem - I doubt it's ahalf/full duplex
problem, as that normally shows as collisions. You might look at the
boot messages (/var/log/messages) to see how the card is being
configured at boot time - grep for 'eth0' in that file.
>I know where the 192.168.X.X comes from, because that's how I
>configured my networking, but where does the 169.254.0.0 come from?
It's a windoze compatibility feature - allowing systems to work if
they are configured for DHCP, but can't find a DHCP server. It's meant
to allow sales weasels to trade pr0n and viruses when they meet in
airport waiting areas. All they need is a crossover cable.
I suspect that if you look inside /etc/sysconfig/network-scripts/ifup
you'll find something like:
# Add Zeroconf route.
if [ -z "${NOZEROCONF}" -a "${ISALIAS}" = "no" ]; then
ip route replace 169.254.0.0/16 dev ${REALDEVICE}
fi
So if you set NOZEROCONF=yes in the /etc/sysconfig/network configruation
file, this "feature" will be disabled.
Old guy
- Next message: Anton Ertl: "Re: continously running system or not?"
- Previous message: Moe Trin: "Re: continously running system or not?"
- Maybe in reply to: Tauno Voipio: "Re: Kingston KNE111TX NIC supported ???"
- Next in thread: Moe Trin: "Re: Kingston KNE111TX NIC supported ???"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|