"Different" IP in Mumble and TF2C

TF2C Profile: Obli
Region: Other

Browser: Mozilla Firefox
Critical plugins: --
OS: Windows
Connection type: --

Bug type: Mumble
Lobby ID: --
Date & Time: --

Greetings.

I have tried to verify my mumble in order to play on Mumble req servers. Even though I am connected to the mumble under the name "Obli" with the IP 93.12*.***.*** AND with the same IP to TF2C (checked using whois), it still won't verify me.

An admin told me in the chat that the IPs were not identical although I checked on whois and they are. Maybe it's a bug? Anyone care to help out? Eager to play on mumble-req lobbies!

The IP you are posting from is 212.101.224.2, and that is the exact same one that you logged in with on your TF2C Profile.

 

In mumble, you had the 93.12------ IP. Hence the conflict.

 

You sure you're not using a VPN / Proxy in your browser?

The IP you are posting from is ***, and that is the exact same one that you logged in with on your TF2C Profile.

 

In mumble, you had the 93.12------ IP. Hence the conflict.

 

You sure you're not using a VPN / Proxy in your browser?

Absolutely certain. I've seen in the mumble I had the 93.12--- IP, and even when I look up what's my IP, it shows me something like this:

 

http://puu.sh/dv0eG/04a3ecf781.png

 

Yet when I actually go on http://www.whatismyip.com/ it shows me the exact same IP you posted.

 

http://puu.sh/dv0iL/fbfa46a21b.png

 

I don't really understand the issue here although my guess is that the issue lies within Mumble itself. Apparently I have 2 IP addresses... pretty strange. I mean, it's pretty dumb since when I'm in the mumble it doesn't verify I'm in it.

 

I made sure I was NOT using any VPN or proxy.

http://puu.sh/dv0qA/cff6c7aa6c.png

 

I have no VPN in my networks, no program for such a thing either.

This is getting strange.

 

I'll throw the pending dev response tag on, see if they know anything about this.

Many thanks. I mean, it's not really possible to have 2 IPs at the same time. I will also look for solutions since you're also bothering helping out.

 

Much appreciated, have a nice day/evening

Would like to add something.

 

WHOIS of the IP 93.12---

 

http://puu.sh/dv2oq/9e463e14f3.jpg

 

WHOIS of the 212 IP

 

http://puu.sh/dv2rb/58b1679818.jpg

 

Both indicate to the same country, same ISP (obviously me), although I really don't get how Mumble functions.

Many thanks. I mean, it's not really possible to have 2 IPs at the same time. 

 

Why is that? Depends on how many networking interfaces you have. Companies usually have multiple outbound IPs, so you can't really be sure from a client perspective.

 

From your profile I was able to obtain the following IPs:

212.101.224.7
212.101.224.5
212.101.224.6
212.101.224.9
212.101.224.10

None of these have ever been used on our Mumble server, so it seems correct that you can't be verified. You need to figure out which IP is used when using Mumble; that could be a different one, since it is outbound UDP etc...

 

Since that is very hard to find out, here's what you should do: play a non-mumble required Lobby (that's the only type of Lobby you can play anyways...) join Mumble, and post here the Lobby no, date, time and your Mumble name, so I can dig into our audit logs.

^

Hey. Thanks for bothering to answer my thread, means a lot.

 

First, I only have on networking interface at home.

 

Well, here is the IP Mumble is recognizing:

 

http://puu.sh/dyPiI/cce8a59d3c.png

 

As you can see, the IP is 93.126.192.240. A simple whois of this IP will lead back to my ISP, along with all the other IPs you have posted.

 

Now, when I search "what's my IP on google" I get this:

 

http://puu.sh/dyPnY/266398a68d.png

 

Notice something? First, it's the same IP as the one mumble recognizes, second, it says that this is my PUBLIC IP address. That might be the issue.

 

None to say the least, I've seen some other users suffer from such a problem.

 

(Sorry for not doing what you asked of me, bit busy with real life, I'll join a lobby and its mumble on Friday and will post back, just wanted to keep you updated.)

 

My appreciations.

Could be his non-google browsing is being proxied. His IP on the last post is 212 as well. 

I see you connecting on that IP on our Mumble server; I also saw other IPs on that subnet. Long story short: you need to figure out how to use a single outbound IP. This seems no problem for the rest of the world, so I'm sure you can fix this as well.

 

Best of luck ;-)

 

MN

Using a VPN would solve the issue for you most likely. You can get them relative cheap for 5€ a month and aside from a higher privacy, you can play proper lobbies with a decent ping.