Every client showing my own IP on local server

It crashed, it is bugged, ...

Every client showing my own IP on local server

Postby khalonen » Sun Nov 13, 2016 10:42 am

Recently after many years of hosting my own server, I had to ban user.. So this created a ban for my own public IP and no user could connect to the server? I managed to remove the ban but started to dig why it is that way.

My Murmur is version 1.2.16 and behind NAT, static LAN IP, bound to that address 192.168.1.5:13862 in murmur.ini. Port 13862 is forwarded from my router and users can connect and talk no problem, however when looking information from users they all show my own public IP as their IP address. And when I ban one, it will ban all clients as for server it looks they all come from the same IP.
When I do "netstat -a" on the server machine, murmur connections look like this:
Code: Select all
          Local                    Foreing
TCP    192.168.1.5:13862      line-10888:25563       ESTABLISHED
TCP    192.168.1.5:13862      line-10888:47773       ESTABLISHED
TCP    192.168.1.5:13862      line-10888:56299       ESTABLISHED


My networking skills arent enough, is this some sort of routing thing in my router or what does that "line-10888" mean? I do run web and game servers behind the same NAT without problems.
khalonen
 
Posts: 2
Joined: Sun Nov 13, 2016 10:26 am

Re: Every client showing my own IP on local server

Postby kissaki » Fri Nov 18, 2016 5:21 pm

Huh, I would expect NAT to work just fine.

The router maps specific ports to specific hosts. The connections are still end-to-end. So I don’t know what is going on there.

You can pass the -n option to netstat to display numerical addresses. Maybe that helps identifying the IP device of the connection.
MumPI: Your Mumble Web Interface in PHP
User avatar
kissaki
Team member
Team member
 
Posts: 1289
Joined: Sat Jan 09, 2010 12:15 pm

Re: Every client showing my own IP on local server

Postby khalonen » Sat Nov 19, 2016 9:06 am

Thank you,

nestat -n told me that "line-10888" just resolves to my public IP..
Further investigation show that this is not Mumble issue. This same behaviour happens on all my servers behind my NAT. (2 games, ftp and web). Their log files are just full of my own public IP address. I did reset my router (Inteno FG500) back to factory settings and only did the port forwarding again. Still the same and for clients everything works perfectly.
I've googled and read that this might because of "NAT Looback" is enabled for my router. This will allow me to connect to my public IP from inside the NAT, but will make connections coming from Internet through the NAT look like what I'am seeing. However I could not find how to disable it. Will contact ISP if they can help configure the router as its their device rented. From murmur.log I can see that this started happening at end of July, about the time I got new router after lightning strike broke my old one..
khalonen
 
Posts: 2
Joined: Sun Nov 13, 2016 10:26 am


Return to Technical

Who is online

Users browsing this forum: No registered users and 4 guests