1. Forum
  2. FidoNet
  3. SYNC SYSOPS

  • bbs access via webv4

    From xbit@1:103/705 to All on Sunday, February 23, 2025 04:31:11
    When a user access the bbs via webv4, sync will log the client compuer as my systems localhost name rather than the IP addy that they are connecting from. I don't thik we have a way to correlate the funtion of the terminal server and web server, correct?

    Currenty i'm just reviewing timeline logs from both if I
    really want to know. For example:

    terminal server:
    2/23 04:16:35a 3640 Telnet [127.0.0.1] Connection accepted on 127.0.0.1 port 2/23 04:16:35a 3640 Telnet [127.0.0.1] Hostname: XBITBBS
    2/23 04:16:36a 3640 Telnet [127.0.0.1] Attaching to Node 2

    web server:
    2/23 04:16:21a 1948 HTTPS [inet ip addy] Connection accepted on [192.*.*.*] 2/23 04:16:21a 1948 HTTPS [inet ip addy] Request: GET / HTTP/1.1
    2/23 04:16:21a 3092 HTTPS [inet ip addy] Connection accepted on 192.*.*.*] Not a big deal, its not like i'm offering Online Banking at xbit bbs <g>.

    ---
    � Synchronet � Do it @ the X: Sync: X-BIT.ORG <-> Spitfire: X-BIT.ORG:2323
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to xbit on Sunday, February 23, 2025 15:03:06
    Re: bbs access via webv4
    By: xbit to All on Sun Feb 23 2025 04:31 am

    When a user access the bbs via webv4, sync will log the client compuer as my systems localhost name rather than the IP addy that they are connecting from. I don't thik we have a way to correlate the funtion of the terminal server and web server, correct?

    Currenty i'm just reviewing timeline logs from both if I
    really want to know. For example:

    terminal server:
    2/23 04:16:35a 3640 Telnet [127.0.0.1] Connection accepted on 127.0.0.1 port 2/23 04:16:35a 3640 Telnet [127.0.0.1] Hostname: XBITBBS
    2/23 04:16:36a 3640 Telnet [127.0.0.1] Attaching to Node 2

    web server:
    2/23 04:16:21a 1948 HTTPS [inet ip addy] Connection accepted on [192.*.*.*] 2/23 04:16:21a 1948 HTTPS [inet ip addy] Request: GET / HTTP/1.1
    2/23 04:16:21a 3092 HTTPS [inet ip addy] Connection accepted on 192.*.*.*] Not a big deal, its not like i'm offering Online Banking at xbit bbs <g>.

    Yeah, that's really more function of fTelnet using the websocket service/proxy. If the Synchronet terminal server supported websocket connections directly, no proxy would be needed and we capture the client's IP address more accurately.
    --
    digital man (rob)

    Breaking Bad quote #2:
    We flipped a coin, OK? You and me. You and me! Coin flip is sacred! - Jesse Norco, CA WX: 81.2�F, 14.0% humidity, 2 mph WSW wind, 0.00 inches rain/24hrs --- SBBSecho 3.23-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)