Yeah, I wonder if it would work just sending raw TCP/IP without any ax25 headers
at all. Aren't the crc's and packet lengths and all that stuff just transmitted twice?
Or, is there not enough information in raw tcp/ip to know where the blocks are, and
whether the packets are valid. Seems like the header bytes are slowing down ham
tcp/ip.
>On Mon, Nov 08, 1999 at 05:10:24PM +0000, Jose A. Amador wrote:
>> or host, or 6pack, or whatever protocol is devised for the purpose.
>> But the radio must transmit and receive AX.25, as it is legally
>> required for radio amateurs, set by the FCC in the USA and a defacto
>> standard created by the massive distribution of such devices all over
>> the world. It is even used commercially.
>
>I remember reading a discussion about this recently -- does your
>part 97 actually say you must use AX.25 for packet? That's a bit surprising.
>
>There's no reason packet has to refer to AX.25 (generally speaking) as far
>as I can see, and even then you could come up with a similar mode
>and call it something else. PACTOR/WinLink seems to offer some similar
>functionality, and it's not packet nor AX.25.
>
>Our regulations here in VK just list the emission modes we can use
>and general identification requirements. No mention of AX.25.
>
>Hamish
>--
>Hamish Moffatt Mobile: +61 412 011 176 [EMAIL PROTECTED]
>Rising Software Australia Pty. Ltd. http://www.risingsoftware.com/
>Phone: +61 3 9894 4788 Fax: +61 3 9894 3362 USA: 1 888 667 7839
