Message system ... new paradigm?
dubose at texas.net
dubose at texas.net
Thu Jan 13 15:28:18 PST 2005
Whoa...you can't lump all EComms needs into just one basket.
Quoting Rick Williams <mrfarm at mwt.net>:
> Bill Vodall wrote:
> >>>>> There is nothing to implement. It's all done and working. JNOS
> does
> it in a crude
> way. Linux does it with standard tools and techniques. Maybe commercial
> sites use
> the same Linux software (Google, etc...) that we can and do use. The
> technology
> is there. The problem is in the implementation. And the RF...
>
> ====
For V/UHF, I REALLY don't see a need for anything more than JNOS or equal.
YOu can have mailboxes that are accessable via AX.25 or use JNOS as you pop
server and run from another JNOS box.
1200 BPS is slow but DOES work for low volum SMTP. 9600 BPS SMTP can handle
quite a bit of traffic. I used to run 19.2 KBPS TCP/IP on 70 cm and SMTP took
care of anything we could through at it.
HF is another problem...maybe we just need an HF mode interface.
While JNOS typically uses 44. domain IP addresses, there's not problem with
using them or even an unrouted domain IF they gateways are behind firewalls
using NAT.
>
> If there is "nothing to implement" and yet "the problem is in the
> implementation," that suggests something that is not ready for prime time.
> I do not see any products that are practical to use at this time.
>
Again, JNOS WILL work if it has an HF front end and routing can be based on
zip codes rather than FQDNs/IPs/MACs.
> The scenario that we are looking at here is a local type of incident that
> could be an attack by an outside group that affects a large number of
> people (several hundred); flooding that wipes out infrastructure (not as
> big a problem as 40 years ago since they hardened a lot of it); severe
> widespread storm damage, or a killer tornado taking out a small city.
>
> Much of what we then do is tactical communication. Things like locating
> the emergency response vehicles and ETA's. They do not have very long range
> interoperability from neighboring mutual assistance. After the initial
> situation is brought under control, we need to have a basic network to
> communicate between shelters and EOC/government/etc. And a way to move H&W
> traffic in and out if the telecommunications infrastructure is not
> working. I don't see good solutions other than WinLink. What am I missing?
>
True for you location but berhaps altogether different elsewhere...all the
"conditions" and requirment and scenerios need to be considered.
H&W should NOT be included in EComms...while very important, it has to take
a rear seat to priority EComms traffic.
I sometimes feel that we look at disaster relief with all to broad a brush.
Saving and sustaining lives is task one and H&W task two...we need to be
cautious about letting H&W communications get in the way of EComms.
73,
Walt/K5YFW
> 73,
>
> Rick, KV9U
>
>
>
>
>
>
> -----Original Message-----
> From: linlink-bounces at wetnet.net [mailto:linlink-bounces at wetnet.net]On
> Behalf Of Bill Vodall
> Sent: Thursday, January 13, 2005 11:27 AM
> To: linlink at wetnet.net
> Subject: Re: Message system ... new paradigm?
>
>
>
> >
> > I had asked about coming up with some kind of HF/VHF/UHF network that
> can
> > work at least within a region or a state. Why couldn't this be developed
> by
> > the LinLink team instead of reinventing the wheel? The main thing is
> that
> it
> > would allow robust connections between ham stations in some kind of
> network
> > topology but the connections would usually be amateur radio RF.
> >
> > What other system can do this? This does not seem to be one of the WL2K
> > strong points since WL2K is more focussed on e-mail for the served
> agencies.
> > Of course it would be OK if it went into the internet for the purpose of
> > sending and receiving e-mail, but I have no idea how you can implement
> this
> > without having a server like the WinLink 2000 system uses to act as the
> > internet access address point.
>
> There is nothing to implement. It's all done and working. JNOS does it
> in
> a crude
> way. Linux does it with standard tools and techniques. Maybe commercial
> sites use
> the same Linux software (Google, etc...) that we can and do use. The
> technology
> is there. The problem is in the implementation. And the RF...
>
> * It's a pain and a hassle to keep a Linux box running. It takes lots of
> time and effort.
> * There's no good interface for the most common client system (Windows.)
> SV2AGW-Packet
> Engine is the best there is and that's more complicated then needed.
> * Speed is way too slow. There is no off the shelf 9k6 equipment.
> (Kenwood
> missed it
> with the D700) DStar has so-so speeds but it's implementation is
> "lacking" (Icom missed it.)
> There are other hacks but nothing solid and readily available.
>
> Here's some things I think Linlink/Linux/xxx can do to contribute.
>
> * Is there a *nix interface for the SCS Pactor III modem?
>
> * Is there a good way to efficiently transfer, on RF, a file with *nix?
> Even the RDFT
> that's the basis for Rick's SCAMP.. If so, we can tie it in to UUCP
> and
> bring standard
> Email and File Transfers to HF.
>
> * We need an open SMTP/POP server written is some easily to modify script
> language like PERL.
> With that we can write interfaces to other systems such as old packet
> mailboxes or even Winlink
> gateways. (JNOS can do this but it's a lot of baggage for a single
> task.) This could be the
> interface between the real world Internet and any we hams can do on RF.
>
> * If there was some serious interest, we could rebuild the AMPR.ORG
> network
> and do it using
> modern tools and technologies.
>
> I'm sure there's more -- but I have to go to work.
>
> 73,
> Bill - WA7NWP
> http://www.jnos.org
>
>
>
>
>
> _______________________________________________
> Linlink mailing list
> Linlink at wetnet.net
> http://wetnet.net/mailman/listinfo/linlink
>
>
>
> _______________________________________________
> Linlink mailing list
> Linlink at wetnet.net
> http://wetnet.net/mailman/listinfo/linlink
>
>
More information about the Linlink
mailing list