probably use haproxy and it has some of the smarts to know which
"backend" is free.

IE: I dont think you can do it without something in the middle, but haproxy was designed for use in this scenario.

The only downside (which is why I dont use it), then backend gets
a connection from the proxy, not the source, so if you do any IP
address level decision making, you dont know the source IP address,
unless your backend application supports "proxy mode" (and I doubt

I briefly looked over haproxy.... there was something funny about it from memory, I'll have to revisit it. I s'pose first up, how does it check on the back end? At the moment I go looking for suseron.x where x is the node number in the common directory. I s'pose if it proxies everything it'll know what its doing anyway. I can't do any IP level decision this far along the chain the BBS is next and we know thats just serial. If I end up having to for some reason I'll re-route the traffic back through the linux box for I dunno, fail2ban or something.

Thanks for the reminder...


--- SuperBBS 1.17-3 (Eval)
* Origin: <Shoot'n the breeze on The Lower Planes> (21:3/105)

You shouldnt need to do that, it should be able to handle the SSH
session - if it was setup purely as a TCP proxy. ...ëîåã

I'm not sure thats going to fly.... if the incoming into the proxy is ssh, then
its ultimately going to have land at an sshd, which it won't it'll land at a telnet server. But I haven't mounted it up on 22 to try it that way.

Spec


--- SuperBBS 1.17-3 (Eval)
* Origin: <Shoot'n the breeze on The Lower Planes> (21:3/105)