PDA

View Full Version : Internal IP in Info Incorrect


LordEntrails
December 10th, 2020, 01:09
The chat command "/info" shows "127.0.0.1" as the internal IP address, which does not match the Internal IP address shown on the campaign launch screen (which shows the router reserved IP address of 192.168.0.100).
Zarestia
December 10th, 2020, 21:57
This does not happen to me.
OS: Windows 10 Version 2004
Network: DHCP W-LAN, no LAN attached, Windows Firewall on, Windows Defender on


41888
LordEntrails
December 10th, 2020, 22:32
Thanks for checking.

I'm also on Win 10 and running a LAN game, but with a wifi connection. 5E ruleset. Nothing indicative in the network or console logs.

I did verify that I can duplicate/repeat it in different campaigns with no extensions.
Sulimo
December 10th, 2020, 22:43
I am seeing something similar LordEntrails.

However, I am not seeing 127.0.0.1 in /info.

On the launcher screen I see the IP address for my VM Network (this is a virtual switch for Hyper-V on the PC).
https://i.imgur.com/zYrL9kk.png

/info gives me the DHCP reservation I setup on the router (which is correct).
https://i.imgur.com/DbzRiOK.png
Weissrolf
December 10th, 2020, 23:17
For me the internal IP is shown correctly via /info (192.168.101.22), but "wrong" in the Launcher (192.168.255.1). The wrong one in the Launcher is a virtual adapter that VMware installed, FG is not running inside the VM, though.

My guess is that FGU just lists the first adapter out of a list and Launcher and /info don't agree about which one (maybe one lists the last and the other the first).
LordEntrails
December 10th, 2020, 23:30
Thanks all. Glad I'm not the only one seeing this strange behavior.
Weissrolf
December 10th, 2020, 23:38
To be fair, how would FG know which local IP we consider "correct"? If there are 3 local adapters present then all 3 IPs are valid, so it just picks one out of the list.
LordEntrails
December 11th, 2020, 01:51
Good point. Well, isn't 127.0.0.1 a loop b ack IP and only valid for the computer itself? If true, then at least that one wouldn't be useful to other computers trying to connect.
Sulimo
December 11th, 2020, 01:56
Yeah, 127.0.0.1 is the local loopback address.

It cannot be connected to remotely (it would just go to the local computer instead (localhost)).