BW> Yes, it seems so. I have enabled the fTelnet SendLocation support (I'm
BW> using the https://embed-v2.ftelnet.ca/ fTelnet Embed Wizard), but still see
BW> the proxy IP instead of the client IP in the .dlreq data file.
I added some logging into the MIS window for the telnet location and its in the
latest Linux/Pi builds that I just put up. It does look like I wasn't passing
the location IP into Mystic, but there is code there to get the value.
Lets first make sure that the location part works and then I can move on to
getting dlreq sorted out.
... Enter any 12-digit prime number to continue.
--- Mystic BBS v1.12 A48 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)
|
