Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 4 May 2000 16:07:54 -0400
From:      Brian Reichert <reichert@numachi.com>
To:        freebsd-mobile@freebsd.org, freebsd-isp@freebsd.org
Subject:   LinkSys NP100 vs the universe
Message-ID:  <20000504160754.A29902@numachi.com>

next in thread | raw e-mail | index | archive | help
This may not quite count as an update on my situation, but I have
a few more datapoints.

Quick recap:

  Problem machine is a Sony VAIO PCG-C1XS running FreeBSD-4.0-RELEASE.
  I have a LinkSys NP100 PCMCIA card (see
  <http://www.numachi.com/~reichert/laptop/PCMCIA/LinkSys%20NP100/>;
  for details.)

  The above does not reflect that Win98 see the MAC address as
  00:e0:98:77:1a:b2.

General symptom:

  The card _mostly_ works, in that only some kinds of hosts can it interact
  with in certain ways.

I've come up with a fairly simple test environment, that illuminates
things a little bit.

On a hub, I have:

  - my primary desktop machine, a Dell running 3.4-RELEASE.  It's interface:

    % ifconfig xl0
    xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	inet 10.1.135.160 netmask 0xffff0000 broadcast 10.1.255.255
	ether 00:50:04:7b:22:aa 
	media: 100baseTX <half-duplex>
	supported media: autoselect 100baseTX <full-duplex> 100baseTX
	<half-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP
	<half-duplex> 10baseT/UTP

 - and my problem laptop:

   % ifconfig ed0
   ed0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::3d4:ffff:fe03:20%ed0 prefixlen 64 scopeid 0xa 
        inet 10.1.135.250 netmask 0xffff0000 broadcast 10.1.255.255
        ether 01:d4:ff:03:00:20

The laptop's was successfully configured via DHCP from the desktop.

The laptop can ping the desktop.  Both machine's arp tables (modulo
'permanent'):

  % arp -na
  ? (10.1.1.1) at 8:0:20:80:df:6a [ethernet]
  ? (10.1.1.10) at 8:0:20:85:bd:d7 [ethernet]
  ? (10.1.135.160) at 0:50:4:7b:22:aa permanent [ethernet]
  ? (10.1.135.250) at 1:d4:ff:3:0:20 [ethernet]

The laptop can ping the desktop, and itself.

The laptop can ssh into the desktop, and itself.

(Both tests to itself were via 10.1.135.250, not 127.0.0.1, if that
makes any difference.)

On the laptop, using 'tcpdump -ni ed0 ether host 01:d4:ff:03:00:20':

Trying to ping the laptop yields:

  tcpdump: listening on ed0
  14:26:28.876328 10.1.135.160 > 10.1.135.250: icmp: echo request
  14:26:29.876817 10.1.135.160 > 10.1.135.250: icmp: echo request
  14:26:30.886790 10.1.135.160 > 10.1.135.250: icmp: echo request
  14:26:31.896756 10.1.135.160 > 10.1.135.250: icmp: echo request
  14:26:32.906724 10.1.135.160 > 10.1.135.250: icmp: echo request
  14:26:33.916693 10.1.135.160 > 10.1.135.250: icmp: echo request
  14:26:34.926665 10.1.135.160 > 10.1.135.250: icmp: echo request

Trying to ssh into the laptop yields:

  tcpdump: listening on ed0
  14:28:18.876206 10.1.135.160.1021 > 10.1.135.250.22: S
  2531066914:2531066914(0) win 16384 <mss 1460,nop,wscale 0,nop,nop,timestamp
  116811 0> (DF)
  14:28:21.703686 10.1.135.160.1021 > 10.1.135.250.22: S
  2531066914:2531066914(0) win 16384 <mss 1460,nop,wscale 0,nop,nop,timestamp
  116816 0> (DF)
  14:28:27.703524 10.1.135.160.1021 > 10.1.135.250.22: S
  2531066914:2531066914(0) win 16384 <mss 1460,nop,wscale 0,nop,nop,timestamp
  116828 0> (DF)
  14:28:39.703184 10.1.135.160.1021 > 10.1.135.250.22: S
  2531066914:2531066914(0) win 16384 <mss 1460,nop,wscale 0,nop,nop,timestamp
  116852 0> (DF)
  
After these experiments, netstat yields:

  % netstat -in -I ed0
  Name  Mtu   Network       Address            Ipkts Ierrs    Opkts Oerrs Coll
  ed0   1500  <Link#10>   01:d4:ff:03:00:20   185090    66     2001     0 0
  ed0   1500  fe80:a::3d4 fe80:a::3d4:ffff:   185090    66     2001     0 0
  ed0   1500  10.1/16       10.1.135.250      185090    66     2001     0 0

I have experimented with:

- setting the 'debug' flag of the ed driver
- removing IPv6 from the kernel

If I set 

  # sysctl -w net.inet.icmp.bmcastecho=1

I can respond to pings, but nothing else.

Cameron Slye <cslye@calweb.com>, noting the FBSD MAC address, said
'I think that's a multicast address :)  No, it won't work..'.  This
utility was suggested:

  http://people.FreeBSD.org/~wpaul/mac.tar.gz

but I don't know how to apply that to FBSD-4.0-R.

I _can_ ssh to various hosts with this card, and hence can get some
work done, but I've having a real rough time understanding these
symptoms.

Any advice is appreciated.  I can dredge up more details as needed.

-- 
Brian 'you Bastard' Reichert		reichert@numachi.com
37 Crystal Ave. #303			Daytime number: (603) 434-6842
Derry NH 03038-1713 USA			Intel architecture: the left-hand path


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000504160754.A29902>