Subj : Re: fTelnet sendlocation compatibility To : g00r00 From : ryan Date : Fri Apr 24 2020 11:54 pm g0> Sounds easy enough. It'll probably be harder for me to setup fTelnet g0> than it will be to make the IP work considering I've never looked at it g0> before. fTelnet has an automagic installer thingie: https://embed-v2.ftelnet.ca - this could help spin something up quick for testing. Just put it in a webroot and paste the crap in the wizard into your index.html or whatever. Optionally I could set it up in a vm and share access with you, let me know :) g0> One thing I worry about though is that terminals could use that to spoof g0> IP addresses in order to bypass an IP block. It'd be nice to determine g0> somehow if the connection was from fTelnet so that it could only g0> acknowledge an IP response from fTelnet. But then the terminal could g0> just spoof that its fTelnet. Yeah, the one tricky part is ws: or wss: in the configuration, but honestly that could help here with self-hosted setups. There are a couple ways to think about this, maybe: 1 - Local ws/wss, which means mystic actually notices the connection coming from 127.0.0.1 in the first place, and 2 - Connection from one of the proxy sites from the wizard (the link pasted above). My thought process is basically the actual tcp/ip connection will proxy through something in the whitelist, and then arbitrarily pass an IP. For what it's worth, I'm currently dealing with trying to host my BBS in the web and I'm losing any sort of IP block filtering from mystic for those connections anyway. g0> I suppose I could only do it if the address is a local IP 127.0.0.1 or :1 g0> or something? Yeah, that's what I was thinking. It'll come from one of those or maybe the online telnet guide, or one of the established ftelnet proxies...so sysops will just have to have those IPs in their whitelist as normal, I guess. g0> Since Mystic can spawn multiple copies of its terminal servers, I could g0> also make it a toggle in the TELNET server options and then someone g0> could spawn a second telnet server on an off-port just for their fTelnet g0> connections while leaving another TELNET server running on port 23 with g0> that feature disabled. Have you given any thought to ws or wss services? That could actually simplify much of this. I have wss connections on an arbitrary port, and they proxy the connection (and terminate TLS) directly to a telnet node. Thanks for thinking about this! --- Mystic BBS v1.12 A46 2020/04/13 (Linux/64) * Origin: monterey bbs (77:1/128) .