Re: Strange problems with USB ethernet card
From: Gregory Richards
Date: Fri Jan 09 2004 - 16:24:57 EST
Trying to break my bad habit of top-posting >_< Post at bottom.
From: Laurent Fazio <Laurent.Fazio@xxxxxxxxxx>
To: Gregory Richards <akaquinn@xxxxxxxxxxx>
Subject: Re: Strange problems with USB ethernet card
Date: Fri, 09 Jan 2004 21:55:01 +0100
Gregory Richards wrote:
Hmmm
Well that me realize that if I ifconfig while pinging shows the interface
as up, I have an IP . . . if I do it while the interface is down, I have
no IP. Maybe it's the DHCP server? I'm going to try using static IP and
see if that works . . . .
IMHO, it is due to the fact that the iface is getting an IP address
according to the zero conf standard by the OS... I do not remember exactly
in which range... But I think it is the expected behavior.
Laurent Fazio
- Gregory Richards
From: fazio.laurent@xxxxxxxxxx
To: akaquinn@xxxxxxxxxxx
Subject: Re: Strange problems with USB ethernet card
Date: Fri, 9 Jan 2004 11:26:14 +0100
comments inline...
akaquinn@xxxxxxxxxxx wrote (on 9 Jan 2004 at 01:53):
> I'm running Mandake GNU/Linux 9.2, and have a D-Link USB-H3ETX USB
network
> card. It uses the pegasus module. For some reason, my network
connection
> goes up and down. It never did under Windows.
>
> As you can see, it goes up and down erradically. Here's my ifconfig:
> eth0 Link encap:Ethernet HWaddr 00:50:BA:8A:94:54
Here, if you compare with the loopback interface,
you can see that the *inet* and *Mask* field are
missing...
I think you've forgotten to give a IP address to the
network interface:
$ ifconfig eth0 <ip_address_of_the_interface>
It should solve your problem.
Hope it helps.
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:24779 errors:0 dropped:0 overruns:0 frame:0
> TX packets:20370 errors:14390 dropped:0 overruns:0
carrier:14390
> collisions:0 txqueuelen:100
> RX bytes:5505240 (5.2 Mb) TX bytes:2342698 (2.2 Mb)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:24987 errors:0 dropped:0 overruns:0 frame:0
> TX packets:24987 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:1766076 (1.6 Mb) TX bytes:1766076 (1.6 Mb)
>
>
> I've been googling for info, but I'm not really sure what keywords to
look
> for, and haven't found anything. Does anybody have any words of
wisdom to
> keep my network up?
>
> If you need more info, what should I include?
>
> BTW, this is with no network activity whatsoever. I don't think that
it
> goes up or down any more irregularly, however, whether there is net
activity
> or not.
>
> - Gregory Richards
Well, I tried setting it to static, and that didn't work. It got the IP,
worked for a while . . . and then stopped. Still. Grrrrr.
As a temporary solution, I made a script:
while [ true ]
do
if [ ! "`ifconfig eth0 | grep 'inet addr'`" ]
then
ifconfig eth0 192.168.1.115
fi
done
And that sort of keeps it up, but it's about the stupidest solution
possible. Not even a solution, really.
I would suspect that it has something to do with the card itself, but it
works under Windows 98, and I find it difficult to believe that it would
work better under Windows 98 than GNU/Linux ;)
If anybody has other suggestions / magical solutions / whatnot, that'd be
grand :)
- Gregory Richards
Please ignore the following idiotic message from Micro$oft:
_________________________________________________________________
Tired of slow downloads? Compare online deals from your local high-speed
providers now. https://broadband.msn.com
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html