🚀 go-pugleaf

In article <4833@burdvax.PRC.Unisys.COM> you write:
>
>Our PUP software between 1100s and VAX/VMS cuurently uses protocol 2. This
>was fine so far but with VMS 4.6, DEC have put restrictions on the XEDRIVER
>regarding the protocol number you may use, so that the driver can also
>process IEEE 802 packets. The restriction is that the protocol should look
>> 1501 (10) after its two bytes have been swapped (VMS 4.6 release notes).
>
>Before we select a random number for our PUP protocol and go into the 
>burden of upgrading all our systems, is there a recommended/standard 
>protocol number for PUP that is compatible with the above restriction?
>
>Thanks for any info on the subject.
>
>Claude Barbe - Schlumberger-Doll Research - Ridgefield, CT 

Xerox has chosen new 802.3 compatible numbers, which can be found deep in
the release notes for Xerox Lisp.  This number is also buried in the
802.3 alternative of the Xerox Lisp System Tool.
Service old value       new value
        Dec  Hex        Dec  Hex
PUP     512  0200      2560  0A00
PUP arp 513  0201      2561  0A01
These values are shown in "standard byte order".
For a VAX (or other byte swapped machine), use something like hton(2560).
Needless to say, all machines on an Ethernet need to change at the same time.

-- 
Darrel J. Van Buer, PhD; unisys; 2525 Colorado Ave; Santa Monica, CA 90406
(213)829-7511 x5449        KI6VY        darrel@CAM.UNISYS.COM   or
...{allegra,burdvax,cbosgd,hplabs,ihnp4,sdcsvax}!sdcrdcf!darrelj