I learned today that if someone is connected to the BBS from ftelnet, and ftelnet is configured with SendLocation=true, the IP message variable accurately displays the user's IP address, but the client.ip_address property does not. This seems to be the case whether running the WS/WSS services built into SBBS or running Rick Parrish's standalone ftelnetproxy service.
For that reason, I'm using bbs.atcode("IP") in place of client.ip_address wherever I depend on the user's IP address (e.g.: location-based weather data).
Curious whether client.ip_address is meant to be equal to the IP message variable though...
client. client.ip_addres has the real IP address of the client (or proxy) that the Synchronet server is communicating with.
I learned today that if someone is connected to the BBS from ftelnet, and ftelnet is configured with SendLocation=true, the IP message variable accurately displays the user's IP address, but the client.ip_address property does not. This seems to be the case whether running the WS/WSS services built into SBBS or running Rick Parrish's standalone ftelnetproxy service.
For that reason, I'm using bbs.atcode("IP") in place of client.ip_address
Re: client.ip_address != bbs.atcode("IP") while using ftelnet
By: Digital Man to Codefenix on Thu Mar 09 2023 06:15 pm
client. client.ip_addres has the real IP address of the client (or proxy) that the Synchronet server is communicating with.
I'm finding that client.ip_address has the BBS PC's local IP (127.0.0.1) if the user is connecting via the ftelnetproxy.
Sysop: | Zazz |
---|---|
Location: | Mesquite, Tx |
Users: | 7 |
Nodes: | 4 (0 / 4) |
Uptime: | 77:20:07 |
Calls: | 157 |
Files: | 2,110 |
Messages: | 145,577 |