LinkSys Etherfast 10/100 (I know...)

LinkSys Etherfast 10/100 (I know...)

Post by Brian Whitma » Sat, 14 Aug 1999 04:00:00



I've seen all the other posts concerning this card, but my problem is
*special* :)

I have a Linksys Etherfast 10/100 NIC (PCI). I have compiled and
insmodded the tulip.o that comes with the card, and it recognizes it
wonderfully upon boot as eth0. Now, my problem is, I can't do anything
with it.

What I know:

* I can ping "myself": 192.168.0.1
* From the other system on my network (via crossover cable, a Win98), I
can ping it fine.
* I should be connecting to the inernet via Win98's DHCP / "Internet
Connection Sharing."
* In linuxconf I have IP address set to 192.168.0.1, driver set to
tulip, interface set to eth0, and netmask to 255.255.255.0... (I have
also tried selectively eliminating various parameters to no avail)
* I cannot ping to anywhere from linux but myself.
* ifconfig sees the card fine with the IP address set up.

So, what am I doing wrong? All I'd like to do is to be able to use the
other computer's net connection via DHCP...

Thanks!

--
Brian Whitman

http://www.netspace.org/users/bwhitman
[ Sound information: http://www.crudites.org ]

 
 
 

LinkSys Etherfast 10/100 (I know...)

Post by David Crook » Sat, 14 Aug 1999 04:00:00



> I've seen all the other posts concerning this card, but my problem is
> *special* :)

> I have a Linksys Etherfast 10/100 NIC (PCI). I have compiled and
> insmodded the tulip.o that comes with the card, and it recognizes it
> wonderfully upon boot as eth0. Now, my problem is, I can't do anything
> with it.

> What I know:

> * I can ping "myself": 192.168.0.1
> * From the other system on my network (via crossover cable, a Win98), I
> can ping it fine.
> * I should be connecting to the inernet via Win98's DHCP / "Internet
> Connection Sharing."
> * In linuxconf I have IP address set to 192.168.0.1, driver set to
> tulip, interface set to eth0, and netmask to 255.255.255.0... (I have
> also tried selectively eliminating various parameters to no avail)
> * I cannot ping to anywhere from linux but myself.
> * ifconfig sees the card fine with the IP address set up.

> So, what am I doing wrong? All I'd like to do is to be able to use the
> other computer's net connection via DHCP...

Okay, I think there are a few things jumbled here:

1. If ping works then the card is working fine - this is a sofware
configuration (not driver or hardware) issue

2. DHCP is a protocol used for one server to automatically assign
addresses to all the other machines on a subnet. If you want to use
Win98 as a DHCP server and have your Linux machine get an address via
DHCP, you need to run a DHCP client (like dhcpcd) on the Linux box. I'd
suggest however that you *don't* do that, and just stick to using
192.168.0.1 as a fixed address.

3. By "Internet Connection Sharing" I think you mean having the Win98 PC
act as a masquerading firewall. I don't know if the software you have
will do this (AFAIK it isn't a standard feature of Win98, and WinGate is
the most popular add-on that does it). For this to work, you need two
things:

- have the Win98 machine set up for IP masquerading

- tell the Linux machine to use the Win98 machine as its default router
(gateway), like this:

  /sbin/route add default gw 192.168.0.2 eth0

Long term: I would give due consideration to swapping them round,
putting the internet connection on the Linux box and using it as a
masquerading router. Linux supports this very well, with built in
masquerading and firewall capabilties.

Dave
--
David Crooke, Austin TX, USA. +1 (512) 656 6102
"Open source software - with no walls and fences, who needs Windows
and Gates?"

 
 
 

LinkSys Etherfast 10/100 (I know...)

Post by Brian Whitma » Sat, 14 Aug 1999 04:00:00


Quote:> 3. By "Internet Connection Sharing" I think you mean having the Win98 PC
> act as a masquerading firewall. I don't know if the software you have
> will do this (AFAIK it isn't a standard feature of Win98, and WinGate is
> the most popular add-on that does it). For this to work, you need two
> things:

It is a standard feature of Win98 SE - the 'new one' that came out last
month or so. From what I understand, it sets up a DHCP server to set up
the networking stuff on any other machine on the network. This Linux
machine is a dual boot, and the Connection Sharing stuff works with two
'98 machines.

Quote:> Long term: I would give due consideration to swapping them round,
> putting the internet connection on the Linux box and using it as a
> masquerading router. Linux supports this very well, with built in
> masquerading and firewall capabilties.

Well, that's an option for sure, but there's a lot of other stuff
happening with the machines that for now swapping the connections isn't
viable. For now...

thanks!

-brian

 
 
 

LinkSys Etherfast 10/100 (I know...)

Post by Stuart R. Full » Sat, 14 Aug 1999 04:00:00


:
: 1. If ping works then the card is working fine - this is a sofware
: configuration (not driver or hardware) issue

Actually, 'ping'ing one's own address does not indicate that the card is
working fine, since if you ping your own address, then the packet never went
out to the card.  Here's a demonstration:

bash$ /sbin/ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:E0:29:1F:5D:E7
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:28460 errors:0 dropped:0 overruns:0
          TX packets:26787 errors:0 dropped:0 overruns:0
          Interrupt:11 Base address:0xf400

bash$ ping -c 10 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=0.4 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.3 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.3 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.3 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.3 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.3 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=0.3 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=0.2 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=0.3 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=0.3 ms

--- 192.168.1.1 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 0.2/0.3/0.4 ms
bash$ /sbin/ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:E0:29:1F:5D:E7
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:28462 errors:0 dropped:0 overruns:0
          TX packets:26788 errors:0 dropped:0 overruns:0
          Interrupt:11 Base address:0xf400

As you can see, while there were 10 pings, the transmit and receive counters
did not go up by 10.  

        Stu

 
 
 

1. Linksys Etherfast 10/100 CardBus

We are having some trouble getting the Linksys EtherFast 10/100 CardBus
(PMC200) to work on RH linux 2.2.14 and pcmcia 3.1.14.  The first
problem we had was getting the TI1220 to power up the ethernet card.
Now that linux recognize the ethernet card(PMC200), I can't get the
linux machine to communicate with other machines.  The machine can only
ping itself.  I have checked the files /etc/pcmcia/network.opts and
/etc/sysconfig/network-scripts/ifcfg-eth0 many times.  It seems to have
all the right information.

Does anyone have any an idea what maybe wrong?  Any help would be
appreciated.  Thanks.

2. Linux path

3. linkSys EtherFast 10/100 PCI Card with Solaris 2.7 x86

4. DIP and PPP

5. LinkSys Etherfast 10/100 on RH6.2

6. LSB

7. Problem with LinkSys 10/100 Etherfast Lan Card

8. 2.4 bootdisk kernel panic

9. Linksys EtherFast 10/100 Card

10. Anyone running Linksys Etherfast 10/100 cards?

11. Linksys Etherfast 10/100

12. Linksys EtherFast 10/100 LAN Card Trouble

13. Linksys PCMCIA EtherFast 10/100 PC Card Problems...