alan@cunixc.columbia.edu (Alan Crosswell) (10/12/87)
Has anyone succeeded in getting 5798-FAL TCP/IP for the PC to talk
to ACIS 4.3/RT? It looks like they are using incompatible ARP
implementations. When I run the "ping server" on the PC with the
debugging options turned on and try to ping it from the RT, the
PC complains about bad protocol type 6 instead of recognizing the
arp packet. The dump of the 63 bytes of the frame from the RT which
the PC prints are something like this (with my annotations):
10 40 ff ff ff ff ff ff 7f ff 81 00 08 e5 00 00
AC FC ---destination--- ------source----- 802.2 dsap/ssap?
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
99 99 03 00 06 08 00 06 04 00 01 7f ff 81 00 08
----source---->
e5 80 3b 25 01 00 00 00 00 00 00 80 3b 25 02
-- -RT's addr- -PC's addr-
128.59.37.1 128.59.37.2
/ajac@umd5.umd.edu (Joseph A. Cimmino Jr.) (10/13/87)
In article <186@cunixc.columbia.edu> alan@cunixc.columbia.edu (Alan Crosswell) writes: >Has anyone succeeded in getting 5798-FAL TCP/IP for the PC to talk >to ACIS 4.3/RT? It looks like they are using incompatible ARP >implementations. No, the arps aren't incompatible. As the frame below shows, the RT is still using the old style SAP 6/99 for IP/ARP. The PC code uses the new (rfc 990/1010) SNAP encapsulation. To enable this on the RT, use "ifconfig lan0 snap bridge". > >10 40 ff ff ff ff ff ff 7f ff 81 00 08 e5 00 00 >AC FC ---destination--- ------source----- ----- > >00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >--- space reserved for routing information ---- > >99 99 03 00 06 08 00 06 04 00 01 7f ff 81 00 08 >-SAP- Cl ----- ARP Header ------ ----Source----> > >e5 80 3b 25 01 00 00 00 00 00 00 80 3b 25 02 >-- -RT's addr- -PC's addr- > 128.59.37.1 128.59.37.2 > ------------------------------ Joseph A. Cimmino, Jr. University of Maryland, Systems jac@umd5.umd.edu 1+ 301 454 2946 PC/IP Group cimminoj@umdd.bitnet Bertolt Brecht: You made your bed, so you lie in it.