I'm not aware of any formal spec, but Michael N6MEF's suggestion pretty much covers it. The only difference I've come across between implementations is that some require a specific source port as well as the defined destination port.
There seem to be two commonly used ports (93 and 10093).though others are also used. Using low numbered ports can be a problem with some operating systems (requiring root/admin rights) so I prefer 10093
73, John G8BPQ
-----Original Message----- From: 44Net [mailto:44net-bounces+john.wiseman=cantab.net@hamradio.ucsd.edu] On Behalf Of Brian Kantor Sent: 02 March 2017 16:18 To: AMPRNet working group Subject: Re: [44net] AXUDP spec
(Please trim inclusions from previous messages) _______________________________________________ Any description I gave would be necessarily incomplete, as I don't know frame sizes, port numbers, etc. Someone familiar with the implementation code could probably write the description fairly easily.
I was rather hoping that the people maintaining the AXUDP software would speak up. I think that JNOS or one of those programs implements it and hope that the author of the protocol was still with us. Some of the early packet pioneers have since died.
On Thu, Mar 02, 2017 at 08:01:57AM -0800, William Lewis wrote:
Since you state there is no official definition, but give a rather
eloquent
definition of it, is it possible to include your definition somewhere on
the
WIKI ?
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net