Chocolate Software Forums

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Connect from 192.168.1.x  (Read 6951 times)

johannesmueller

  • Full Member
  • ***
  • Offline Offline
  • Posts: 49
Connect from 192.168.1.x
« on: February 13, 2004, 06:21:12 PM »

Hi Guys!

I'm kinda stumped on this one, maybe you can give me a clue. My server seems to be running fine but I keep having some people who can't connect. My log file says he's trying to connect from 192.168.1.2, i.e. an internal, non-routable IP (not from my subnet).

In the FAQ I found a note saying that a different pilot in the session could cause something like this, is this the case here? How would I find the 'badly' configured router? Or is it more likely the new player with a Router and non-routing ports?

Funny thing is, it tries to keep the connection for a while (even though it couldn't possibly with that IP), but then looses it.

Here's an excerpt of the log file:
040213 21:52:48  *** DPlayMsg2004: DPN_MSGID_INDICATE_CONNECT, player=Marcel, type=pilot, fake=no
040213 21:52:48  *** DPlayMsg2004: DPN_MSGID_CREATE_PLAYER, player=Marcel, id=2650869438, IP=192.168.1.2, type=pilot, fake=no
040213 21:52:48  Updated FS2002 session description to 'flightforum.ch', 6/16 pilots, 0/2 observers, joins allowed, not unlimited, no password
040213 21:52:48  Updated FS2004 session description to 'flightforum.ch', 6/16 pilots, 0/2 observers, joins allowed, not unlimited, no password
040213 21:52:48  Added 'Marcel' to game as an FS2004 pilot (6 pilots, 0 observers)
040213 21:52:48  IP address for 'Marcel Staubli': 192.168.1.2
040213 21:52:48  *** DPlayMsg2002: CREATEPLAYERORGROUP, player=@Marcel, id=125764
040213 21:52:48  AddPlayer: Created fake FS2002 pilot player '@Marcel'
040213 21:52:48  *** DPlayMsg2002: ADD_PLAYER_REQUEST, player=@Marcel
040213 21:52:48  Sent FS2002 CHANGE_TO_PLAYER from host, id=0 to @Marcel, id=125764
040213 21:52:53  Sending all 2002 planes to new 2004 player Marcel, id=2650869438
....
040213 21:53:24  *** DPlayMsg2004: DPN_MSGID_DESTROY_PLAYER, player=Marcel, id=2650869438
040213 21:53:24  Removed pilot 'Marcel' (5 pilots, 0 observers)
040213 21:53:24  Updated FS2002 session description to 'flightforum.ch', 5/16 pilots, 0/2 observers, joins allowed, not unlimited, no password
040213 21:53:24  Updated FS2004 session description to 'flightforum.ch', 5/16 pilots, 0/2 observers, joins allowed, not unlimited, no password
040213 21:53:24  *** DPlayMsg2002: DESTROYPLAYERORGROUP, player=@Marcel, id=125764

On a related note, what else can I read from this log-segment? Is he really using FS2004 (i.e. the 'fake' player is in FS2002)? If the connect from 192.168.. is caused on his side, could FSHost recognise the 'mistake' and somehow send him a message - or say post a 'Marcel your IP is strange, check your router, see FAQs' onto the status page? That would be really helpful!

Thankful for any advice!
John
Logged

Russell Gilbert

  • Administrator
  • Guru
  • *****
  • Offline Offline
  • Posts: 1476
    • FSHost
Re: Connect from 192.168.1.x
« Reply #1 on: February 13, 2004, 07:09:36 PM »

Hi John,

Yes, he's using FS2004 in this case, and the fake player is being added to the 2002 session. We can tell because the initial connection comes from the 2004 side (DPlayMsg2004: DPN_MSGID_INDICATE_CONNECT).

And I believe the problem is on his side, like you suggested.  I've heard of this happening before, but I don't know for sure what causes it.  But I'd guess that 192.168.1.2 is his internal IP, and for some reason his machine is sending it to you in the TCP/IP packets (I believe that's actually called IP spoofing, if he was doing it deliberately, which I'm sure in this case he's not).

Your suggestion about sending him back a msg is interesting -- I think since it's FS2004, I actually can do that.  That's one of the nice changes about DirectX 9, that we now have the option of sending back error messages that FS will show to the user -- that wasn't possible in FS2002, which was written for DirectX 7.  I'll take a look at it and see how difficult it'd be.

Russell
Logged

jordan

  • Junior Member
  • **
  • Offline Offline
  • Posts: 15
  • Have you flown your Helicopter Today?
Re: Connect from 192.168.1.x
« Reply #2 on: February 17, 2004, 08:03:41 PM »

I have some information to add on this subject.

I have found that several of my users are able to connect, and stay connected, yet their "internal" IP address is displayed in the logs.  Normally a 192.168.x.x type address, but doesn't have to be -  of course.

My guess is that the IP address on the TCP/IP level is correct, and leads back to their gateway as it should.

It is probably something more to do with Directplay.  My guess is that IP address is part of the directplay session information and is just a "string" and might have no relevance as to what is going on underneath.  I have checked my router logs, and of course I don't see these internal address as being an origination point or destination.  Even though they show up in the FSHost log screen.

Am I anywhere close on this one Russell?

Logged
Jordan M.

Russell Gilbert

  • Administrator
  • Guru
  • *****
  • Offline Offline
  • Posts: 1476
    • FSHost
Re: Connect from 192.168.1.x
« Reply #3 on: February 17, 2004, 09:21:45 PM »

Interesting, Jordan.  This would suggest that we should be careful about blocking people that show up with internal-looking IPs.  I agree that if everything else seems to be ok, then the IP FSHost is getting from DirectPlay must be wrong somehow.  I wonder if it's not better to keep things as they are, and when we see people having trouble connecting with these IPs, try to contact them and make sure they have everything setup right.

Russell
Logged

johannesmueller

  • Full Member
  • ***
  • Offline Offline
  • Posts: 49
Re: Connect from 192.168.1.x
« Reply #4 on: March 01, 2004, 05:04:39 AM »

Just a feedback, I think we have it solved now ;):
- The User was running XP with the Firewall activated (ha ha, and claimed it wasn't  ;D)
- Connection is via ADSL, ethernet router (Zyxel 642 ME)
- When alone on the server it was never a problem to connect (even with the IP shown)
- It also worked when there were several others online, but it would never work when "certain" players were online
- It turns out that it would work as long as there was no-one else from the same internet-provider active! When he was on the server, as soon as one of these tried to connect, it killed his connection to the server & brought the error messages on the top of the thread.

Strange! I wonder why it ever worked? (oh well, computers :))

Solution: Turn off ICF in XP, of course. Has anyone had any luck just turning on several Ports for a client?

Thanks + maybe this can help some others when they see things like this in the logs!
John
Logged

Russell Gilbert

  • Administrator
  • Guru
  • *****
  • Offline Offline
  • Posts: 1476
    • FSHost
Re: Connect from 192.168.1.x
« Reply #5 on: March 01, 2004, 07:27:23 PM »

Thanks for the update John!  Very interesting.
Logged
Pages: [1]   Go Up
 

anything