Darren Reed wrote:
> Hmmm, ok.  On NetBSD, I do:
> 
> # ifconfig en0 192.168.10.1 netmask 255.255.255.0 up
> # route add -iface 192.168.10.2 -link en0:3.0.0.64
> # pvcsif en0
> # ifconfig pvc0 192.168.10.1 192.168.10.2 netmask 255.255.255.0
> # ifconfig pvc0
> # pvctxctl pvc0 100 -p 0

You should configure either en0 or pvc0, not both.

And you should configure Solaris not to use ATMARP. (I don't know how
to configure Solaris ATM, though.)
NetBSD doesn't support ATMARP so that NetBSD doesn't respond to an atm
arp request.

> it almost works - Solaris7 sees it and replies but the reply comes back
> like this:
> 
> # tcpdump -evni pvc0
> 23:39:56.499976 aa aa 03 00-00-00 0800: 192.168.10.1 > 192.168.10.2: icmp: echo request (ttl 255, id 7371)
>                          4500 0054 1ccb 0000 ff01 098a c0a8 0a01
>                          c0a8 0a02 0800 64e9 0536 0000 3a17 ca1c
>                          0007 9ea2 0809 0a0b 0c0d 0e0f 1011 1213
>                          1415 1617 1819 1a1b 1c1d 1e1f 2021 2223
>                          2425 2627 2829 2a2b 2c2d 2e2f 3031 3233
>                          3435 3637
> 23:39:56.500668 f03a0030a70696e 67205b2d4510002b 40 06 c4 9f-c0-a8 0c02: 

the above encap is strange. 
LLC/SNAP should be "aa aa 03 00-00-00 ethertype".

>                          89be 4000 ff01 5c96 c0a8 0a02 c0a8 0a01
>                          0000 6ce9 0536 0000 3a17 ca1c 0007 9ea2
>                          0809 0a0b 0c0d 0e0f 1011 1213 1415 1617
>                          1819 1a1b 1c1d 1e1f 2021 2223 2425 2627
>                          2829 2a2b 2c2d 2e2f 3031 3233 3435 3637
> 
> ...and ping doesn't work from Solaris7 either:
> 23:42:39.933222 f03a003080c20007 00000000 00 00 08 00-45-00 0054: 
                                                        ^^ ip header
seems to start here...
>                          89c7 4000 ff01 5c8d c0a8 0a02 c0a8 0a01
>                          0800 0862 029f 0001 3a17 ca6d 0001 fd74
>                          0809 0a0b 0c0d 0e0f 1011 1213 1415 1617
>                          1819 1a1b 1c1d 1e1f 2021 2223 2425 2627
>                          2829 2a2b 2c2d 2e2f 3031 3233 3435 3637


> and if I delete the arp entry from the Solaris box, it works again, once...
> manually adding an ARP entry with "0:0:0:0:0:0" as the MAC address causes
> Solaris to panic :-)  From Solaris, a tcpdump from "ci0":
> 
> # tcpdump -s 256 -xnvi ci0
> tcpdump: listening on ci0
> 00:09:10.995115 arp who-has 192.168.10.1 (ff:ff:ff:ff:ff:ff) tell 192.168.10.2 (0:20:48:6:9:8a) /+..............
>          0001 0800 0604 0001 0020 4806 098a c0a8        ......... H.....
>          0a02 ffff ffff ffff c0a8 0a01                  ............
> 00:09:10.995263 arp reply 192.168.10.1 (2:0:c0:a8:a:1) is-at 2:0:c0:a8:a:1 (6:0:c0:a8:a:2)      /...............
>          0001 0800 0604 0002 0200 c0a8 0a01 c0a8        ................
>          0a01 0600 c0a8 0a02 c0a8 0a02                  ............


> The ARP packets are never seen on NetBSD, be it on en0 or pvc0, with tcpdump.
> Is this a bug ?  How do we see them there ?

I believe that someone else replied to the arp request, and NetBSD never
saw the request.

-Kenjiro