|
VK3JMA > WLAN 19.04.04 01:47l 46 Lines 1720 Bytes #999 (0) @ WW
BID : 5E0009VK3JMA
Read: DB0FHN GUEST DK5RAS IW3BRC DO6NP
Subj: Re: VK3JMA > Winpack over tcp
Path: DB0FHN<DB0RGB<DB0MRW<OK0PKL<OK0PPL<DB0RES<ON0AR<VK6HGR<VK3AYM<VK3DSE
Sent: 040415/0958Z @:VK3DSE.#MEL.VIC.AUS.OC #:10800 [Narre Warren] FBB7.00g25
From: VK3JMA@VK3DSE.#MEL.VIC.AUS.OC
To : WLAN@WW
Hi Warren,
KB2VXA wrote:-
> Somehow I just don't get it. Since telnet is a rather ancient protocol
> and you surely don't need Winpack to use it I can't see why you bothered.
> Since Windows has a telnet terminal program built in, I would think you
> would have no trouble using something similar for Unix/Linux. Seems like
> you beat around the bush only to find the rabbit wasn't there.
Goes back to 'mountains and mohammed'!
I tried and tried to get winpack to connect via telnet, but as my bulletin
said, I could just not get it to work???? Which in itself is very strange
as I am now using winpack and telnet to connect as my previous bullet
explained, using another port number apart from the default 23. I dont
have an answer to why "common telnet" would not work yet "telnet
ip_address:port#" works if I dont use port 23????? Maybe some one else
out there can answer that.
Oh and warren, yes I did beat around the bush, but the rabbit was indeed
there and he tasted mighty good!!!
> Don't mind me, I'm a radio man and would have approached it from that
> angle bypassing the land line link altogether. Perhaps configuring a
> terminal directly using WLAN, the direct approach would be less
> frustrating.
This point confuses me???
What land line link are you thinking of warren? I am doing it entirely on
RF...2.4 GHz from Laptop to Access point over my local ethernet into the
linux packet box and out onto 144.975 MHz at 1200 baud...ok I use CAT5 for
the ethernet but even AFSK tones have to travel over wires!!!!
It is all still done within my own home, no link over wires to another
site, no internet, no dialup networking.
73
Mark
Read previous mail | Read next mail
| |