| View previous topic :: View next topic |
| Author |
Message |
Q
Tux's lil' helper
Joined: 17 Apr 2002
Posts: 149
Location: Oxford, UK
|
 Posted: Thu May 09, 2002 6:29 pm Post subject: Problems using wget and ssh with Netgear NIC |
 |
|
Hi all,
I am setting up a gentoo machine for a friend but have hit the following problem.
The machine has a netgear NIC and I am installing from stage 1. The machine is sitting behind my gateway server which is using IPTABLES.
The NIc was not detected but I did "modprobe tulip" and that seemed to work. (tried natsemi but that didn't work).
After completing the ifconfig and route command and setting up the resolve.conf I can now ping and traceroute to internal and external sites by IP and name.
However if I try to use wget or ssh to internal or external addresses or names the machines just seems to hold until I ctrl-c out of it. I am at a loss to understand this.
Here is the output from ifconfig and route.
eth0
Link encap: Ethernet HWaddr FF:FF:3B:CC:FF:FF
inet addr: 192.168.1.5 Bcast: 192.168.1.255 Mask 255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU: 1500 Metric: 1
RX packets: 148 errors: 1 dropped: 0 overruns: 0 frame: 0
TX packets: 118 errors: 0 dropped: 0 overruns: 0 carrier: 0 collisions: txqueuelen: 100
RX bytes 14312(13.9 kb) TX bytes: 7719(7.5 kb)
Interrupt: 11 Base address: 0xc800
route
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
default 192.168.1.1 0.0.0.0 UG 1 0 0 eth0
The first of these lines gets added when I complete the ifconfig command. An explanation of this would be useful.
Any assistance would be greatly appreciated.
Q |
|
| Back to top |
|
 |
funsize
n00b
Joined: 08 May 2002
Posts: 67
Location: The Lone Star State
|
| Posted: Thu May 09, 2002 7:46 pm Post subject: what NIC? |
|
|
what NIC is it?
a FA310TX?
_________________
...SO SAYS FUNSIZE |
|
| Back to top |
|
|
Nitro
Bodhisattva
Joined: 08 Apr 2002
Posts: 661
Location: San Francisco
|
| Posted: Thu May 09, 2002 8:51 pm Post subject: |
|
|
As funsize asked, what NIC are you running, if you don't know off the top of your head, you can see what your kernel sees it as by searching through the result of:
I'm not sure if this is on the install CD, but could you run and give us any relevant information? Maybe it will mention something about why the insmod/modprobe failed on natsemi.
I have a Netgear FA311 running in a P180 which is also running Gentoo, the natsemi driver worked fine for me, but you mentioned you tried that.
_________________
- Kyle Manna
Please, please SEARCH before posting.
There are three kinds of people in the world: those who can count, and those who can't. |
|
| Back to top |
|
|
funsize
n00b
Joined: 08 May 2002
Posts: 67
Location: The Lone Star State
|
|
| Back to top |
|
|
Q
Tux's lil' helper
Joined: 17 Apr 2002
Posts: 149
Location: Oxford, UK
|
| Posted: Thu May 09, 2002 11:10 pm Post subject: |
|
|
| Nitro wrote: | As funsize asked, what NIC are you running, if you don't know off the top of your head, you can see what your kernel sees it as by searching through the result of:
I'm not sure if this is on the install CD, but could you run and give us any relevant information? Maybe it will mention something about why the insmod/modprobe failed on natsemi.
I have a Netgear FA311 running in a P180 which is also running Gentoo, the natsemi driver worked fine for me, but you mentioned you tried that. |
Here is the output from /proc/pci
Ethernet controller: Lite-On Communications Inc LNE100TX (rev33) IRQ11
MAster compatible latency=32
I/O at 0xc800
Non prefetchable 32 bit memory at 0xfe000000 [0xfe0000ff] |
|
| Back to top |
|
|
zom
Guest
|
| Posted: Mon May 13, 2002 12:17 pm Post subject: |
|
|
I have the same NIC and it uses the tulip drivers so thats set up right, plus the fact u can ping proves its working.
Just out of curiosity, when you said you had edited /etc/resolve.conf, was that a typo? cuz it should be resolv.conf (dont wanna sound patronising). |
|
| Back to top |
|
|
|
Networking & Security
