| |
PA2AGA > HDDIG 20.09.00 23:16l 193 Lines 7140 Bytes #999 (0) @ EU
BID : HD_2000_255D
Read: GUEST
Subj: HamDigitalDigest 2000/255D
Path: DB0AAB<DB0ZKA<DB0GPP<DB0LX<DB0RBS<DB0PSC<DB0ACH<PI8JOP<PI8ZAA<PI8HGL
Sent: 000920/1859Z @:PI8HGL.#ZH1.NLD.EU #:16257 [Den Haag] FBB $:HD_2000_255D
From: PA2AGA@PI8HGL.#ZH1.NLD.EU
To : HDDIG@EU
Date: Tue, 19 Sep 00 00:12:32 MET
Message-Id: <hd_2000_255D>
From: pa2aga@pe1mvx.ampr.org
To: hd_broadcast@pa2aga.ampr.org
X-BBS-Msg-Type: B
Have you looked at SNOS to see what is needed?
> They are available for about two years now, but they came too late to
> leverage (popular buzzword) the initial developments in amateur TCP/IP into
> the average-ham shack.
>
> There was a painful gap between the introduction of Windows 95 and the
> usability of its TCP/IP networking on amateur packet radio. One would
> have expected the TNC manufacturers to step in with a TNC with modified
> firmware to provide a PPP interface on the ASYNC end while running IP over
> AX.25 on the radio. Then, it would have been possible to use the standard
> dialup networking of Windows 95 with amateur radio, with the addition of
> only a small control-panel program to perform some settings of the TNC.
There is a good deal more required. We are in complete agreement of
course on the direction taken by the TNC manufacturers. I've talked
to two of them, and their response was essentially that making changes
like this is very expensive (I agree) and that there is little market
pressure to make those changes (I also agree).
> But no, they all seemed to be glued to KISS and Hostmode.
We are stuck with what is available in the TNCs. This should not stop
us from doing interesting things, it just makes the problem "more
interesting."
> Rob
> --
> +----------------------------------+--------------------------------------+
> | Rob Janssen pe1chl@amsat.org | WWW: http://www.knoware.nl/users/rob |
> | AMPRnet: rob@pe1chl.ampr.org | AX.25 BBS: PE1CHL@PI8WNO.#UTR.NLD.EU |
> +----------------------------------+--------------------------------------+
--
... Hank
http://horedson.home.att.net
------------------------------
Date: Sun, 17 Sep 2000 12:49:22 -0500
From: "Steve Sampson \(K5OKC\)" <ssampson@nospam.radio-link.net>
Subject: TCP/IP Address
I've been running a Linksys router for about 2 months now. That's
really the way devices need to arrive these days. It plugs into the WAN
on one end, the LAN on the other, and is configured with a Web page.
Web interfaces have been done before (My Hawking iRouter did the
same thing for the same price, but only with modems). Cisco did it
a long time ago (but who the heck cares at their prices).
Cheap, and needs to do the job.
That's really how Ham gear must be designed today. If it has a Web
interface, it will sell like hot cakes (just ask Linksys, and Hawking) :-)
I haven't opened up my Linksys yet, but I'm dying to see if it is a
modern CPU.
"Hank Oredson" says:
>
> A different architecture is needed.
>
> To get hams to use tcp/ip there needs to be a better solution than either
> of these. It must be simple to install and simple to configure and simple
> to use.
------------------------------
Date: Sun, 17 Sep 2000 18:07:36 GMT
From: "Hank Oredson" <horedson@att.net>
Subject: TCP/IP Address
"Steve Sampson (K5OKC)" <ssampson@nospam.radio-link.net> wrote in message
news:ssa0ukqah3t146@corp.supernews.com...
> I've been running a Linksys router for about 2 months now. That's
> really the way devices need to arrive these days. It plugs into the WAN
> on one end, the LAN on the other, and is configured with a Web page.
>
> Web interfaces have been done before (My Hawking iRouter did the
> same thing for the same price, but only with modems). Cisco did it
> a long time ago (but who the heck cares at their prices).
>
> Cheap, and needs to do the job.
At least one manufacturer of controllers for digital ham radio
has this under consideration. I would sure like a PACTOR and
CLOVER (and etc.) HF modem with an ethernet port instead
of serial port.
> That's really how Ham gear must be designed today. If it has a Web
> interface, it will sell like hot cakes (just ask Linksys, and Hawking) :-)
Thus the experiments with web based remote admin in SNOS.
The idea works fine. Needs a lot of code to do everything needed.
> I haven't opened up my Linksys yet, but I'm dying to see if it is a
> modern CPU.
Probably not a Z-80 or 6502/7/9 :-)
> "Hank Oredson" says:
> >
> > A different architecture is needed.
> >
> > To get hams to use tcp/ip there needs to be a better solution than either
> > of these. It must be simple to install and simple to configure and simple
> > to use.
--
... Hank
http://horedson.home.att.net
------------------------------
Date: Sun, 17 Sep 2000 13:28:14 -0500
From: "Steve Sampson \(K5OKC\)" <ssampson@nospam.radio-link.net>
Subject: TCP/IP Address
I'm using the AGWPE on APRS and it is kind of neat to interface with. Right
now I have an application that connects to the AGW server on its port 8000
and feeds the data into a MySQL database (just now working on the mysql
database interface and table design). I think the limitation of AGW is
that if you want to use TCP/IP on the radio port, you must have some other
means to get to other networks such as ROSE, NETROM, etc. That is,
it only talks to things it can ARP with, if I'm not mistaken.
While the AGW interface is kind of neat, I will be switching to the aprsd
I/O code to feed my database in the interest of speed, and a one machine
solution.
Oh well...
"Rob Janssen" says:
> Yes, at least two of them. From SV1AGW and from the Flexnet group.
> These don't need the hackery you propose, they just implement a network
> interface that runs packet protocols (just like the Linux solution).
------------------------------
Date: Sun, 17 Sep 2000 18:18:13 -0000
From: "Gert Leunen" <Gert.Leunen@tijd.com>
Subject: TCP/IP Address
"Hank Oredson" <horedson@att.net> wrote in message
news:tD5x5.32542$M37.880409@bgtnsc07-news.ops.worldnet.att.net...
> Are there any other solutions available?
>
Have you ever heard of the MCB-152? Yes, some Europeans actually do some
development from time to time :-) The MCB-152 is a general-purpose
micro-controller board (based on a special Intel 80c152 microcontroller with
special communication gear on board). Our first firmware project was the
KISS-firmware (just to get the toy usable). Next, the SLIP firmware was
developed (now going into its third revision). What makes this SLIP firmware
so special is that it behaves as an ordinary telephone modem (AT command
set) towards the modem and applies classic Packet-Radio to its radio-port.
Result: you can
simply use the generic modem driver that comes with your OS (Win9x, NT,
W2K, Linux, MacOS, ...). You setup a dialup connection like you do to reach
your ISP and there you go! No proprietary drivers to install, no tedious
configuration (you already have done it once to get connected to the
Internet), what more could you ask for?
You could have a look at our generic project page at
http://www.qsl.net/on1blu. From there you will also find links to the
MCB-152 project page and the like.
Our opinion is: users should be able to recuperate their genuine Internet
software to travel the ampr.org network, for servers we prefer Linux (since
To be continued in digest: hd_2000_255E
Read previous mail | Read next mail
| |
