ExampleMenu couldn't find my local machine's ip?

[blueskined]

the example menu working well for 1.3
when I update to 1.5, this example doen't work anymore. when I click start a local server, I can see actually the serverlist's ip is my external ip instead of a Internal IP.
when I click the list button to try to connect, it failed, the message: invald arguments.
what can possibly wrong?

[blueskined]

I created brand new scene and imported TNet.

[blueskined]

I tried on both my Mac and PC, same result.

[blueskined]

the standlone TNServer.exe working without any problem though.

[ArenMook]

Everything is fine here. Did you try importing TNet into a brand new project to make sure something didn't go wrong with the upgrade process?

I actually tested it (and just re-tested it) on two different connections -- cable connection going through a router (has UPnP) and a DSL connection going through a gateway (no UPnP).

[blueskined]

I imported to brand new scene, both on pc, and mac. same result, will that be possible some setting of my route is wrong? but the old version does work properly...

[ArenMook]

Where is it failing with "invalid arguments"? It should show you the info.

When in doubt, also make sure to delete "server.dat" file prior to starting up the server.

[blueskined]

I start a new scene, so there shouldn't be a server.dat file, but after last time I tested the scene, a dat file do generated, I deleted it.
start, same again, the invald arguments didn't show in console, instead, it actually showed in the lable...
here is the screenshot I captured.


it's really weird...

[blueskined]

I think it might be something to do with TNUdp Lobby Client script on TNManager. I am turning it on and off, the list working for 1 time!!!!!! displayed the correct ip, and shortly not working again...

[ArenMook]

That text label is set on line 174 of ExampleMenu (OnNetworkConnect function). My guess is that you are getting an error in TcpProtocol line 171, which goes into the catch() block below. It first tries to connect to your remote IP (if you see it wait for 3 seconds it means it tries and fails). It then tries connect to your local IP (192.168.x.x). Check what the "mFallback" is set to in TcpClient.CancelConnect.

[blueskined]

I am not sure what is that mean

what I am experience is, when I click "Start a Local Server", it keeps me wait quite long, about 3 seconds.
then the list page popup, with the wrong IP.

but everything is from assetstore, I didn't touch anything! why it can be some callback issue?
anyone else got the same problem? or just me!?
how lucky i am...

[ArenMook]

The fact that it can't connect to your PC on the first try tells me that the router you have doesn't support address loopback (the ability to connect to your computer using the external address from the inside) -- which is generally a sign of a poor router. Regardless though, it should still work on the second attempt when it tries to connect using the local IP. The fact that it fails at that stage tells me that your network configuration is something I haven't encountered before, so the only way I can help out is if you give me more information, such as the address it tries to connect to. You can get it by adding a Debug.Log statement to the TcpProtocol.Connect -- what is the internal IP?

[blueskined]

the internal ip is 192.168.1.6.
I am not sure what router that is, the server supplier installed it when they setup the service. I never touch it after that. however, I just tried this again in my company- with my mac laptop which is brand new download from assetstore (the previous try were on my PC and MAC desktop at home yesterday)
and still I only got the company's external ip.
(mac powerbook retina with wifi)
I will try more later at home with debug info, have to back to work for now...

[blueskined]

if it's the router's problem....
1.3 does run properly!!!!!!

[ArenMook]

1.3 doesn't have IP discovery or UPnP features that interact with the router.

As I mentioned, you will have to add Debug.Logs to figure out what the issue is. I can't reproduce it here, so I can't debug it or fix it.