[FADCA] Use of ESATCOM for TCP/IP

[Doug Christ]

Well Bud, so far, only you and I have the only comments about this. Maybe
everyone is on vacation.

>From what I was reading, John wants a plan submitted for utilizing ESATCOM
for TCP/IP traffic (forwarding). As far as I see it, we need to determine
the different locations where a BBS and the ESATCOM digital interface unit
(DIU) units are co-located. Once we know how many there are, we can produce
a simple drawing indicating the different locations and LANs that can be
serviced from each ESATCOM to BBS gateway. Mine is simple as both computers
(ESATCOM and BBS) are part of the same physical LAN. My gateway can service
the Southwest coastline from Sarasota down to Naples if need be. I know that
the Charlotte County's BBS and ESATCOM systems are co-located in the same
building. Lee County's system's are co-located and I believe that Collier
County's use to be but I'm not sure.

My problem, as of right now, is that I'm running MSYS (dos based) on a Win
98 machine. I got to see if I can pull in the NIC as a port in MSYS. If I
was running a fully DOS machine, it would be no problem. MSYS has been able
to forward via TCP/IP for as long as I been using it. Even across RF.
Interesting to watch but way too slow, even at 9600 baud.

Looks like I might better look at another BBS program again that runs under
windows instead of in a DOS box in windows.

Anyone else have any thoughts?


Doug/KN4YT