The question is not if the unit has failed, but if the unit is in range
of an "access point" (DStar repeater, Mesh node, or 4G wireless tower)
at any moment in time.

I've uploaded a diagram of the proposed system. This entire setup is
going to be installed on my pickup truck along with hard mounted
antennas, and a 30ft pneumatic mast for the rare occasions where I can't
establish a link with the antennas mounted to the overhead rack.

Hehehe (let the flame wars begin) The portal computer is going to be a
windows box running IIS with all the portal software written in C#..
I'll do my best to keep it clean enough to port over to a Linux/Mono
server if anyone is interested. The portal database will be MySQL so
that will not be an issue. I've been programming C# and ASP.NET for the
last 5 years and I am quite sick and tired of having to do all the low
level grunt work in PHP that gets done for me automatically when I'm
working in C#.... especially when it comes to accessing databases.
Hyperlinks are DEAD -- give me AJAX :) RAD to the HILT :)

When I talk about services on the portal, I mean things like a webmail
system tied into Winlink, a Weather Radar web app that downloads and
caches the imagery so that instead of 20 people downloading an image
every 5 minutes, the server downloads it once, and then serves it out as
needed to the 20 users (thus reducing the on air traffic to a minimum).
A full blown DotNetNuke content managment server with forums, news/RSS
feed capability. The "mini" server will be the one built into the public
access router in case the portal server fails, and it will not be
capable of granting access to the backhaul networks unless I decide to
add an SD card to store the login and service databases.

99% of the time, end users will have access to everything they need on
the portal. Only on rare occasions will an end user be allowed any sort
of direct access to the backhaul links. When backhaul access is granted,
it will be handled by opening holes in the firewall specifically for the
services that the specific end user is allowed to access, as defined in
the portal servers database.

erwestgard wrote:
>
>
>
>
> --- In D-STAR_23cm@...
>
> wrote:
> >
> > Has anyone put together a program that will periodically test data
> > connectivity to the current "access point" (dstar repeater), and if
> that
> > repeater is non-responsive, automatically switch through a list of
> > repeaters round robin until it finds an active connection ??
> >
> I'd need to see a diagram here. BTW we have never seen one of these
> units fail. How I might set this up is to have the mini web site on
> the Linux computer behind the repeater. The Linux box would have
> connectivity to various services and each would be a hyperlink. If
> your goal is to reach the Internet, you could try several ways= try
> each link in turn, which might each be a proxy server.
>
> Mini Portal Web Site
> - Internet via 3G
> - Internet via WiFi
> - Internet via DSL
>
> I have convinced our group to not put Internet on our primary access
> points. This way they cannot be hacked, and routine Internet access
> via this system is not part 97 friendly by my reading of it.
>
> If you *have* to have Internet, you can bounce via the repeater to an
> ID-1 someplace that is on someones cable modem, etc- and set up a
> remote gateway. Mixing Internet traffic into our limited half duplex
> links risks overloading them, but if you control it you can be OK.
>
> If you have Linux at both ends you could develop some scripts, etc
> that would test this.
>
>