[tulip] nothing except ping - linksys lne100tx+pcmpc100

Tue, 26 Dec 2000 17:13:39 -0600

Hi all, I just subscribed in the hope someone here is able to point me in the 
right direction. I already tried it at the debian-user-list but there nobody 
has any idea about this anymore.

I'm fighting to replace my working plip connection between two computers.
The desktop on one end has a linksys LNE100TX and is connected to a laptop 
with a PCMPC100 over a crossover cable. Both are running Debian Potato with 
upgraded kernel 2.2.18.

The relly strange thing is that with the plip down and the eth-connection up 
ping to each other works fine and nothing else works at all. (I tried telnet 
and nfs-mount)

I downloaded the latest kern_compat.h  pci-scan.c  pci-scan.h and tulip.c and 
replaced sources provided with the card with the new ones. No change.

I used tcpdump to get some hint and got:

With plip:

21:18:36.347694 192.168.0.1.1027 > 192.168.0.3.telnet: S 
3184875831:3184875831(0) win 32120 <mss 1460,sackOK,timestamp 740469[|tcp]> 
(DF) [tos 0x10] (ttl 64, id 43)
21:18:36.347828 192.168.0.3.telnet > 192.168.0.1.1027: S 
3210480529:3210480529(0) ack 3184875832 win 32120 <mss 1460,sackOK,timestamp 
416764[|tcp]> (DF) (ttl 64, id 47)
21:18:36.350921 192.168.0.1.1027 > 192.168.0.3.telnet: . ack 1 win 32120 
<nop,nop,timestamp 740470 416764> (DF) [tos 0x10] (ttl 64, id 44)
...
Everything works fine with plip.

With eth:
14:04:04.856737 arp who-has 192.168.0.3 tell matthschulzg
14:04:04.856782 arp reply 192.168.0.3 is-at xx:xx:xx:xx:xx:xx
14:04:04.857111 matthschulzg > 192.168.0.3: icmp: echo request (ttl 64, id 78)
14:04:04.857145 192.168.0.3 > matthschulzg: icmp: echo reply (ttl 255, id 24)
14:04:05.847840 matthschulzg > 192.168.0.3: icmp: echo request (ttl 64, id 79)
14:04:05.847873 192.168.0.3 > matthschulzg: icmp: echo reply (ttl 255, id 25)
14:04:06.847680 matthschulzg > 192.168.0.3: icmp: echo request (ttl 64, id 80)
14:04:06.847693 192.168.0.3 > matthschulzg: icmp: echo reply (ttl 255, id 26)
14:04:09.851552 arp who-has matthschulzg tell 192.168.0.3
14:04:09.851855 arp reply matthschulzg is-at xx:xx:xx:xx:xx:xx
14:04:11.136301 matthschulzg.1030 > 192.168.0.3.telnet: S 
2475006242:2475006242(0) win 32120 <mss 1460,sackOK,timestamp 6774544[|tcp]> 
(DF) [tos 0x10] (ttl 64, id 81)
14:04:14.126753 matthschulzg.1030 > 192.168.0.3.telnet: S 
2475006242:2475006242(0) win 32120 <mss 1460,sackOK,timestamp 6774844[|tcp]> 
(DF) [tos 0x10] (ttl 64, id 82)
14:04:16.126475 arp who-has 192.168.0.3 tell matthschulzg
14:04:16.126489 arp reply 192.168.0.3 is-at xx:xx:xx:xx:xx:xx

There is no reply at all at the remote machine (well still at the same desk 
right now) with telnet or mount -t nfs. As I already noted ping is fine.
I can't see any difference between the request for telnet in plip vs. eth.

ifcongig says:
> ifconfig
eth0      Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx
          inet addr:192.168.0.3  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:226 errors:0 dropped:0 overruns:0 frame:0
          TX packets:208 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          Interrupt:11 Base address:0x9000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:28 errors:0 dropped:0 overruns:0 frame:0
          TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0         

Because I had no more ideas i got tulip-diag and get following output:

> ./tulip-diag -aa -f | tee ../diag.log
tulip-diag.c:v2.04 9/26/2000 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a ADMtek AL985 Centaur-P adapter at 0xec00.
ADMtek AL985 Centaur-P chip registers at 0xec00:
  fff98000 ffffffff ffffffff 07b37800 07b37a00 fc664010 ff972117 ffffebff
  fffe0000 fff0dff8 00000000 fffe0000 00000000 00000000 00000000 c40ffec8
  00664010 40380004 00000100 07b37830 f0000000 ffff4839 00000000 00000000
  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
 Port selection is 100mbps-SYM/PCS 100baseTx scrambler, half-duplex.
 Transmit started, Receive started, half-duplex.
  The Rx process state is 'Waiting for packets'.
  The Tx process state is 'Idle'.
  The transmit threshold is 128.
 The Comet MAC registers are 48394839 ffff4839 filter 8000000000000000.
WARNING: The EEPROM is missing or erased!

I noticed the difference between th io-bases  reported by tulip-diag and 
ifconfig. What does that mean?

Any tip would be greatly appreciated!

Matth