| |
W0RLI > WLAN 21.09.03 06:36l 59 Lines 1603 Bytes #999 (0) @ WW
BID : 16470W0RLI
Read: GUEST DB0FHN OE5RCO HA1SE DK5RAS DO6NP
Subj: Re: Wireless Lans
Path: DB0FHN<DB0RGB<DB0MRW<OK0PPL<DB0RES<ON0AR<7M3TJZ<IK1ZNW<HB9OK<WB0TAX<
N4ZKF<W4JAX<LU6DTS<N1UAN<WB1CHU<K1UGM<W1ON<W1ON-5<K1UOL<N7QDN<N7QDN<
KB7ZPJ<W0RLI
Sent: 030920/1435 25714@W0RLI.OR.USA.NOAM
<VK3JMA@VK3DSE.#MEL.VIC.AUS.OC> wrote in message news:0B0221VK3JMA...
>
>
>
> To : WLAN@WW
>
>
> Again Hi Jerry,
>
> K0CQ wrote:-
> > So how are you going to modify the protocol on those ethernet cards to
include
> > amateur call signs, to limit their frequency excursions to only the ham
band,
> > and to prevent the use of your amateur radio lan by all users of wireless
lan
> > cards? A critical difference between X.25 and AX.25 is that the address
field
> > in AX.25 is much longer and variable in length to allow for variable
length
> > call signs and the inclusion of digipeaters.
>
>
> Hank, w0rli, had a great idea, utilise BPQENET and a sort of IP>AX25>IP
> arrangement. The ethernet header carries the IP/TCP of the WLAN system
> which in turn has BPQENET running and attaches the AX25 information under
> the IP/TCP header. This can then allow the usual method of "packet"
> operation but at 11Meg/Sec.
Not exactly what I meant.
IP runs normally as it would over ethernet, so there are frames with
your IP address, in net 44, being transmitted. With BPQ over ethernet
there are also frames with your callsign being transmitted. You can include
the normal BEACON frames. There is no need to run AX.25 over IP!
> We could have IP>AX25>NET/ROM>IP you name it....The callsing is there!
You just have:
IP > TCP (or UDP or ICMP) as usual.
ARP as usual.
AX.25 > NET/ROM as usual.
No need for the extra complexity.
SNOS does it this way.
It works fine, exactly like an ethernet wired connection.
--
... Hank
Hank: http://horedson.home.att.net
W0RLI: http://w0rli.home.att.net
Read previous mail | Read next mail
| |
