Local IPs + internet IPs

[0xFEEDC0DE64]

Hi,

I am running a minecraft server at home in my server cluster with dedicated internet public IP, but when I am at home and playing on my own server, I am not going over the internet but over local ip adresses (in fact my public dns name resolves locally to a LAN IP instead of the internet ip get my 40GBit/s link working :) )

How can I configure FastLogin, that it allows me to use minecraft authentication over lan ips, but still allow cracked/offline players at home in my lan AND from the internet with manual login on my server.

When I connect to my public internet IP, I can join with premium minecraft account.

When I connect to my local lan IP, it says Invalid session in minecraft, and the log output of the server shows the following:

[12:25:34 INFO]: feedc0de left the game
[12:25:37 INFO]: [FastLogin] New packet START[class=PacketLoginInStart, id=0] from com.comphenix.protocol.injector.temporary.TemporaryPlayerInvocationHandler@59a4110b
[12:25:37 INFO]: [FastLogin] Handling player feedc0de
[12:25:37 INFO]: [FastLogin] Requesting premium login for registered player: feedc0de
[12:25:37 INFO]: [FastLogin] New packet ENCRYPTION_BEGIN[class=PacketLoginInEncryptionBegin, id=1] from com.comphenix.protocol.injector.temporary.TemporaryPlayerInvocationHandler@59a4110b
[12:25:37 INFO]: [FastLogin] Enabling onlinemode encryption for /192.168.0.2:56350
[12:25:37 ERROR]: [FastLogin] Session server rejected incoming connection for GameProfile feedc0de (/192.168.0.2). Possible reasons are1) Client IP address contacting Mojang and server during server join were different (Do you use a reverse proxy? -> Enable IP forwarding, or disable the feature in the config). 2) Player is offline, but tried to bypass the authentication3) Client uses an outdated username for connecting (Fix: Restart client)
[12:25:37 WARN]: [FastLogin] The incoming request for player feedc0de uses a local IP address
[12:25:37 WARN]: [FastLogin] This indicates the use of reverse-proxy like HAProxy, TCPShield, BungeeCord, Velocity, etc. By default (configurable in the config) this plugin requests Mojang to verify the connecting IP to this server with the one used to log into Minecraft to prevent MITM attacks. In order to work this security feature, the actual client IP needs to be forwarding (keyword IP forwarding). This process will also be useful for other server features like IP banning, so that it doesn't ban the proxy IP.
[12:25:38 INFO]: /192.168.0.2:56350 lost connection: Disconnected

I am not using a reverse proxy for minecraft at all and I dont want to have one

[TuxCoding]

The proxy agnostic configuration option disables the source origin check. However, this will also deactivate it for all requests.