1. Forum
  2. DOVE-Net
  3. Programming

  • Re: Python help...

    From Tracker1@VERT/TRN to poindexter FORTRAN on Monday, September 21, 2020 15:43:11
    On 9/10/2020 10:09 AM, poindexter FORTRAN wrote:
    I do run both; American Pi is @ AmericanPiBBS.com and 20 For Beers is @ 20ForBeers.com:1337 ...

    I've been doing a lot of work with NGINX and reverse proxying
    HTTP/HTTPS. If there were a way to reverse proxy SSH, I'd love it -
    throw a ton of different BBSes behind a proxy and sort them out by
    hostname.

    Probably could with client keys and credential forwarding... you can
    also do a reverse proxy over a websocket, but that would something on
    the client to handle that aspect.

    Would love it if syncterm supported wss+PROT and/or ws+PROT so you could
    do rlogin/telnet/ssh over a websocket connection. Of course that messes
    with the IP detected on the backing server/service.

    --
    Michael J. Ryan
    tracker1 +o Roughneck BBS

    ---
    þ Synchronet þ Roughneck BBS - coming back 2/2/20
  • From Tracker1@VERT/TRN to DaiTengu on Monday, September 21, 2020 15:46:25
    On 9/12/2020 11:05 PM, DaiTengu wrote:

    I just set up a reverse NGINX proxy on a dual-64 core EPYC (7742) server this week. We had it handling about 70,000 SSL connections per second (real world traffic) while only running around 45% CPU usage, with SMT (AMD's version of hyperthreading) turned off.

    at that point we ran out of SSL traffic to throw at it.

    If all it does is reverse-proxy, may also want to take a look at Caddy
    v2, and see if you get more throughput.

    --
    Michael J. Ryan
    tracker1 +o Roughneck BBS

    ---
    þ Synchronet þ Roughneck BBS - coming back 2/2/20
  • From DaiTengu@VERT/ENSEMBLE to Tracker1 on Thursday, September 24, 2020 11:36:08
    Re: Re: Python help...
    By: Tracker1 to DaiTengu on Mon Sep 21 2020 03:46 pm

    I just set up a reverse NGINX proxy on a dual-64 core EPYC (7742)
    server this week. We had it handling about 70,000 SSL connections per
    second (real world traffic) while only running around 45% CPU usage,
    with SMT (AMD's version of hyperthreading) turned off.

    at that point we ran out of SSL traffic to throw at it.

    If all it does is reverse-proxy, may also want to take a look at Caddy v2, and see if you get more throughput.

    We use some nginx modules as well. I'd have to dig through Caddy and see if there's anything similar.

    I'm more worried about the Linux kernel limitations than anything else.

    I guess we'll see how it goes! :)

    DaiTengu

    ... Everything beautiful has its moment and then passes away.

    ---
    þ Synchronet þ War Ensemble BBS - The sport is war, total war - warensemble.com