| |
ZL2BSJ > WLAN 19.09.03 13:05l 25 Lines 847 Bytes #999 (0) @ WW
BID : 000016ZL2BSJ
Read: DB0FHN OE5RCO HA1SE DK5RAS DO6NP GUEST
Subj: Re^2: Wireless Lans
Path: DB0FHN<DB0RGB<DB0SL<DB0FSG<DB0MAK<DB0MRW<OK0PKL<OK0PPL<DB0RES<ON0AR<
7M3TJZ<SP7MGD<ZL2TZE<ZL2TZE<ZL2WA
Sent: 030919/1000Z @:ZL2WA.#60.NZL.OC #:24907 [NZ] FBB7.00g25 $:000016ZL2BSJ
From: ZL2BSJ@ZL2WA.#60.NZL.OC
To : WLAN@WW
>>> LinPac 0.17pre3 : Message sent by ZL2BSJ : Date 09/19/03 Time 21:55 <<<
> 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.
Why not just put out a UDP packet every 10 minutes with your callsign?
You don't *have* to ID with every frame.
The UDP broadcast identifies the hardware address as belonging to that
callsign.
With regards to restricting access to licenced amateurs only: get prospective
users to register their MAC address with the node sysop. All traffic from
non-authorised users is ignored.
Wilbert, ZL2BSJ
Read previous mail | Read next mail
| |
