There are two BBS's that have went online supporting the TI-99/4A and Geneve 9640 that are running the AFTERHOURS BBS software with the TIPI. They can be accessed through a Telnet client.

They are:

Mytbox99.ddns.net port 61643
TheKeep.net port 9918

There is also two other BBS's available Telnet including:

Fusionbbs.ddns.net port 9640
Heatwave.ddns.net port 9640

The 9640News BBS is not accessible thanks to AT&T blocking all customers from inbound connections on their WIFI cellular network.

Beery

--Beery Miller -- 9640 News BBS -- 9640news.ddns.net:9640 --

--- Mystic BBS v1.12 A47 2020/10/31 (Windows/64)
* Origin: 9640 News BBS (21:4/109)

The 9640News BBS is not accessible thanks to AT&T blocking all customers from inbound connections on their WIFI cellular network.

You know the cheapest cloud guest you can find would let you tunnel that
stuff into your local network, right?

De

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Also there is still The Hidden Reef BBS that runs on a TI-99/4A but is
only accessable via modem normally, but if you telnet to thekeep.net:23
and create an account you can use my dialout to dial it.. /go dialout
and then D1 to dial the reef..

The direct modem number for the reef is 718-448-9402

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

The 9640News BBS is not accessible thanks to AT&T blocking all customers from bound connections on their WIFI cellular network.

I will have to check some of those boards out when I get a chance. How
much longer are you stuck with AT&T?

Mike


* SLMR 2.1a * Governments absorb 100x their weight in excess liberties.
--- SBBSecho 3.12-Linux
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (21:1/175)

I am stuck with AT&T until late summer. My only other option is to go back to AT&T DSL.

Beery

--Beery Miller -- 9640 News BBS -- 9640news.ddns.net:9640 --

--- Mystic BBS v1.12 A47 2020/10/31 (Windows/64)
* Origin: 9640 News BBS (21:4/109)

I have heard there is a way to tunnel in, but I have not seen a description with enough detail I could follow to configure to permit it.

The 9640News BBS is not accessible thanks to AT&T blocking all customer from inbound connections on their WIFI cellular network.

You know the cheapest cloud guest you can find would let you tunnel that stuff into your local network, right?

--Beery Miller -- 9640 News BBS -- 9640news.ddns.net:9640 --

--- Mystic BBS v1.12 A47 2020/10/31 (Windows/64)
* Origin: 9640 News BBS (21:4/109)

I have heard there is a way to tunnel in, but I have not seen a description BE>with enough detail I could follow to configure to permit it.

The 9640News BBS is not accessible thanks to AT&T blocking all custo from inbound connections on their WIFI cellular network.

You know the cheapest cloud guest you can find would let you tunnel tha stuff into your local network, right?

google vpn tunnel vm

aquire a vm on the internet somewhere with a public ip
set up a vpn from that server to your home network machine with a
private lan
port forward on the vm to the private lan ip address
profit

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <1214545331@f109.n4.z21.fsxnet>,
Beery <Beery@f109.n4.z21.fsxnet> wrote:

I have heard there is a way to tunnel in, but I have not seen a description >with enough detail I could follow to configure to permit it.

Perhaps an SSH reverse tunnel would work. Let's say you have a host of some sort (perhaps a VPS, or maybe even a webhost) at invalid.tld. The host you want to make accessible opens an SSH connection to invalid.tld and keeps it open:

ssh -NR 12345:localhost:23 invalid.tld

This will tunnel port 12345 on invalid.tld to port 23 on your firewalled system. People then telnet to invalid.tld:12345 to connect.

Sometimes the connection might be dropped for inactivity. Restarting it
with an infinite loop in a shell script will minimize downtime.

_/_
/ v \ Scott Alfter (remove the obvious to send mail)
(IIGS( https://alfter.us/ Top-posting!
\_^_/ >What's the most annoying thing on Usenet?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Perhaps an SSH reverse tunnel would work.

There's a tool called autossh that might help automate establishing
and maintaining a tunnel setup using ssh.

De

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Perhaps an SSH reverse tunnel would work. Let's say you have a host of somesort (perhaps a VPS, or maybe even a webhost) at invalid.tld. The host youwant to make accessible opens an SSH connection to invalid.tld
and keeps itopen:

ssh -NR 12345:localhost:23 invalid.tld

What I have is a program called Mystic BBS running on Windows 10 I need to reach from the outside.

Beery

--Beery Miller -- 9640 News BBS -- 9640news.ddns.net:9640 --

--- Mystic BBS v1.12 A47 2020/10/31 (Windows/64)
* Origin: 9640 News BBS (21:4/109)

What I have is a program called Mystic BBS running on Windows 10 I need to reach from the outside.

So you still get a tiny vm on one of the hosting services - AWS, Digital
Ocean, etc. Make sure you can ssh into it from home. Arrange for a
hostname for this vm that you can publish for your BBS. Imagine this
is bbs.beery.net.

Then you do one of two things:

1. Use an SSH client on the Windows 10 machine to set up the connection described in previous messages, although you may do it with mouse clicky
gui behaviors instead of a command line. It sets up a tunnel from the
Windows machine to the vm, and arranges for connections to a port on the
vm to be tunneled through to a specified port on the windows machine.
Specifics vary depending on what SSH client you select.

2. Use a razzpi or similar inside your local network, and use a
modified ssh command there which establishes the tunnel, and connects to
the bbs telnet port on the Windows machine across the room (instead of
to a port on the same machine) when a connection comes in. If the IP
address of the Windows machine is 192.168.1.3 and the bbs listens on
port 23, then the command is going to look something like:

ssh -NR23:192.168.1.3:23 username@bbs.beery.net

You'll either need to create keys so the ssh can happen automatically (recommended), or type the password each time the tunnel needs to be
started up.

If you've done the keys, you can also use autossh to _keep_ the tunnel
up in the face of occasional network flakies.

client -> vm [tunnel -> win-or-razzpi] -> bbs port

Because you set this tunnel up _outbound_, it doesn't get blocked. And
the vm doesn't have [much] blocking at the cloud host datacenter.

De

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)