TID: Mystic BBS 1.12 A48
MSGID: 1:129/215 d86dbfa0
REPLY: 2:201/137 57d30aec
TZUTC: -0500
 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
 BW> see 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)
SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 120/340 616 123/10
SEEN-BY: 123/131 124/5016 129/215 305 153/757 7715 154/10 30 40 50
SEEN-BY: 154/700 203/0 218/700 220/90 221/0 1 6 226/18 30 70 227/114
SEEN-BY: 227/201 229/110 111 112 113 114 206 275 307 310 317 400 424
SEEN-BY: 229/426 428 452 470 550 664 700 240/1120 5832 261/38 266/512
SEEN-BY: 280/464 5003 282/1038 292/854 8125 301/1 317/3 320/219 322/757
SEEN-BY: 335/364 341/66 234 342/200 396/45 460/58 633/280 712/848
SEEN-BY: 770/1 2320/105 3634/12 5020/1042
PATH: 129/215 154/10 280/464 292/854 229/426