linux ethernet not working

even after months i m unable to get my ehternet working in linux. i
hav my comoputer in a switched-network, connected to internet through
a proxy. the problem is that i give same IP, Netmask, Gateway and
Proxy address in windows and everything works fine; while on linux it
not even pings to the local network. i hav tried this in many distros
Fedora Core1, PCQLinux, Fedora Core3, Knoppix, and Gentoo. All the
distros automaticall detect the Ethernet Card
RTL8139 Fast Ethernet

i did the following

first i configured the network graphically in Fedora using Newtwork
Device Control

it could not work; then i did the following

$ ifconfig eth0 ${IP} netmask ${NETMASK}
this works fine

$ route add degault gw ${GATEWAY}
this step gives an error like
SCIOADDR:address......

$ ping ${GATEWAY}
Network Unreachable

i also configured PROXY in Moxilla

i m in a great surprise that how the same addresses for IP, Gateway,
Netmask, Proxy work fine on Windows XP but not on Linux!!

can there be any problem with the wire (UTP) or i hav to do some more
configurations in Linux.

any help would be greatly appreciated

thanx [hey i m waiting ..:-)]

On 2005-02-07, parser <(E-Mail Removed)> wrote:
> $ ifconfig eth0 ${IP} netmask ${NETMASK}
> this works fine

After this issue an ifconfig and check if the nic is effectively
configured.

> $ route add degault gw ${GATEWAY}

it should be 'default'. The gateway need to be reachable on his own,
meaning: you need to have already a route that make the gateway known.

> this step gives an error like
> SCIOADDR:address......

Something wrong with your NIC driver.

> i also configured PROXY in Moxilla

if your basic network doesn't work is useless to try to configure something
else.

From what you told it looks like the network driver is broken or is
not the correct one. I'd suggest you to recompile the kernel and force
the correct driver to be used.

Davide

--
We are not gentle tolerant people. We like drastically effective solutions.
--Steve VanDevender

(E-Mail Removed) (parser) said:
>i did the following
>
>first i configured the network graphically in Fedora using Newtwork
>Device Control
>
>it could not work; then i did the following
>
>$ ifconfig eth0 ${IP} netmask ${NETMASK}
>this works fine
>
>$ route add degault gw ${GATEWAY}
>this step gives an error like
>SCIOADDR:address......

Could it be that one of your ip, netmask or gateway is wrong?
The gateway should be in the same network with your local IP,
that is, the network parts (as determined by the netmask) of
the IP address of your machine and the gateway should be equal.
--
Wolf a.k.a. Juha Laiho Espoo, Finland
(GC 3.0) GIT d- s+: a C++ ULSH++++$ P++@ L+++ E- W+$@ N++ !K w !O !M V
PS(+) PE Y+ PGP(+) t- 5 !X R !tv b+ !DI D G e+ h---- r+++ y++++
"...cancel my subscription to the resurrection!" (Jim Morrison)

On 7 Feb 2005, Davide Bianchi <(E-Mail Removed)> wrote:
> On 2005-02-07, parser <(E-Mail Removed)> wrote:
>> $ ifconfig eth0 ${IP} netmask ${NETMASK}
>> this works fine
>
> After this issue an ifconfig and check if the nic is effectively
> configured.
>
>> $ route add degault gw ${GATEWAY}
>
> it should be 'default'. The gateway need to be reachable on his own,
> meaning: you need to have already a route that make the gateway known.
>
>> this step gives an error like
>> SCIOADDR:address......
>
> Something wrong with your NIC driver.
>
>> i also configured PROXY in Moxilla
>
> if your basic network doesn't work is useless to try to configure something
> else.
>
> From what you told it looks like the network driver is broken or is
> not the correct one. I'd suggest you to recompile the kernel and force
> the correct driver to be used.

Actually if his system decided to use rtl8139 module, he might just need
to change it to use 8139too module instead. I had that problem with a nic
that hardware detection recognized as RTL8139, but rtl8139 module did NOT
work (8139too did work). Although, I occasionally still get some
flakyness when it runs full speed (flickering LED on switch and packet
loss), but it works fine 10baseT full-duplex if I do:
mii-tool -A 10baseT-FD,10baseT-HD eth0

On Mon, 07 Feb 2005 18:57:45 +0000, David Efflandt wrote:

> Actually if his system decided to use rtl8139 module, he might just need
> to change it to use 8139too module instead. I had that problem with a nic
> that hardware detection recognized as RTL8139, but rtl8139 module did NOT
> work (8139too did work). Although, I occasionally still get some
> flakyness when it runs full speed (flickering LED on switch and packet
> loss), but it works fine 10baseT full-duplex if I do: mii-tool -A
> 10baseT-FD,10baseT-HD eth0

IMHO NICs are now so cheap that there's no reason to use dubious ones like
RTL8139s at all. Intel EtherExpress 100 Pros work very well.

Regards, Ian