| |
VK3JMA > WLAN 14.04.04 04:03l 84 Lines 3346 Bytes #999 (0) @ WW
BID : 10739_VK3DSE
Read: DB0FHN GUEST IW3BRC OE7FTJ DK5RAS DO6NP
Subj: Success with Winpack over tcp!
Path: DB0FHN<DB0RGB<OK0PPL<DB0RES<ON0AR<VK6HGR<VK3AYM<VK3DSE
Sent: 040413/0723Z @:VK3DSE.#MEL.VIC.AUS.OC #:10739 [Narre Warren] FBB7.00g25
From: VK3JMA@VK3DSE.#MEL.VIC.AUS.OC
To : WLAN@WW
Hello,
As many of you may know I have been pushing the 2.4 GHz wireless lan for
some time now. And to attempt to keep as much as possible in the RF side
of things while also keeping fimilar software I have been attempting to
get winpack to operate over my local wireless lan into my linux box, into
the kiss tnc and out into the 1200 baud world. Why? Why not!
Anyway, I was having a heap of trouble using Winpack with Telnet as I
could not get the winpack system to successfully connect to the linux
packet box, even though windows telnet would work like a charm???
Nothing I tried would work, then a email from Rodolfo Brasnarol (no
callsign in email) suggesting a method arrived.....quite simple to
implement, a few issues, but it still worked!
The method, Ok, setting up a script to initiate a telnet connection,
logging on and then issuing a "call [port] [call] [digi]" just did not
work!
So Rodolfo's method was to set up a 'port' to flow tcp data through the
linux kernel, run the 'ax25_call' command and out into the 2m 1200 baud
world. This is accomplished by editing the /etc/initd.conf file as
such...
<ip_port> stream tcp nowait root /usr/sbin/tcpd /usr/sbin/ax25_call
<ax_port> <local_call> <remote_call> <digi's>
Now I substituted for local details and arrived at the folowing......
port# stream tcp nowait root /usr/sbin/tcp /usr/sbin/ax25_call 1 vk3jma
vk3dse
From there set up a script that initated a telnet connection to your
desired system (ip address) to port number 'port#' then a waitprompt
command in the script, have winpack in "human mode" and all should work as
it should. And it does.
The limitations and problems I see are as follows....
A seperate inetd.conf file and associated port# would need to be set up in
order to connect to multiple packet bbs's, nodes and individual systems.
Not a big deal just time consuming for an admin person.
Security becomes an issue as any person that has access to your system can
link out into the packet world using your callsign. Ok in a small local
wireless network with proper security arrangments, wep and Mac filtering,
but in an open system then one has to consider a bit of firewalling etc.
Further developments...
I wonder if one could do the reverse and stream the RXed packet data from
say 2m into the kernel and then oout on the wireless lan???? I know I
used to "RXECHO" received data from the linux's RF packet port to a
seperate KISS link serial cable port to a windows box making it appear
that the windows PC was physically attached to the TNC.
There is not actually a "port" that one could 'rxecho' down...mmmmhhh,
food for thought....anyone have any ideas on this?
Summary.
I now have moved my packet activities onto 2.4 GHz, novel, yes, however,
there are far better ways to utilise the power of 2.4 GHz wireless lann in
the ham data enviroment and that would be to place FBB on a linux system
and then all users could telnet into fbb at ***FAST*** speeds, or, set up
a nntp server to accept common packet mail from the usual sources and make
available to users on the WLAN using normal internet style programs such
as freeagent/outlook express/korn/etc.
The WLAN is our oyster, lets utilise it.
BTW. This message has come to you via 2.4 GHz and winpack.
Best of luck
Mark
Read previous mail | Read next mail
| |
