Unity hangs when TNet server is stopped

[ArenMook]

I don't see a delay in that remove port mapping aside from a few milliseconds... which begs the question -- where does it really hang? Hmm...

[masterhyjinx]

I'm not sure.  The pause is before the DeletePortMapping occurs.  I wish I understood more networking at this point because swapping out routers fixes the issue so the after mucking with it and experimenting the Scientific Method leaves me to believe that the DLink router is the issue or it's interaction with my two particular computers is the issue.

So at this point we either move on (which is a total bummer because it isn't solved), continue to debug like this if you have any ideas, OR I send you this router so you can look at it yourself.  I'm starting to get the feeling after all this that the problem is external to your code.

[masterhyjinx]

I was at a friend's house doing some programming.  This issue cropped up again.  I was using my Macbook Pro in OS X, he uses the brand new Apple Airport Extreme as his router.  Verified it in the example menu project as well.  If I launch the server in the Example Menu, stopping the server caused an indefinite hang.  Launching the server via terminal in OS X would result in the External IP and Internal IP being displayed but then the program would stop there.  The gateway would never resolve and no client could actually connect to it.  Oddly enough, if I booted into Windows 8, and launched the server via command prompt, it worked fine.

Aside from that we were having a myriad of issues all around.  Including if one computer starts the server we can all connect, but if another were to start it, no one can connect.  Is there something hardware wise we need to be looking for that would prevent TNet from working?  Is there something on my system that could be screwing TNet up?

[ChemiKhazi]

I'm afraid I can't give any additional technical details but I'd also like to chime in that this happens to me as well. When I'm working in the office with a DLink router I sometimes get the hanging issue but at home with a Linksys router I have no issues at all.

[ArenMook]

I heard about this happening with the Failport Extreme from another user. So it seems something is different with DLink and Failport type routers that's causing this.

And the thing about Failport is that it doesn't support UPnP at all.

[masterhyjinx]

Well luckily for me I can't tell my clients the same thing if they don't have supported hardware.  I understand networking is probably one of the most difficult programming endeavors to get right.  I understand a lot of work has been put into TNet on topics I'm not completely familiar with and I like the ease of use of TNet but I have to ask, how many other devices are unsupported?  It would be unfortunate if we chose TNet to deploy a match making server after this demo and find that multiple users cannot connect and start a network game when pretty much every other piece of software on their machine works fine.

[ArenMook]

I promised to the other user that I will have this issue fixed along with the planned list of features for TNet in October, and I fully plan on doing it. if I have to buy a Failport, I will. Right now I am 100% focused on the upcoming GUI system however (Unite is coming up in 2.5 weeks) so I can't jump on it until later.

[masterhyjinx]

I understand.  Right now my naughty DLink router is just sitting there because I've replaced it.  Where do you live?  Would you like me to ship you a router that doesn't play well with TNet so that you have a better chance of diagnosing problems and fixing them?  I'd only ask that you ship it back to me when you're done

[ArenMook]

I'm up in Richmond Hill, ON, Canada -- but nah no need. I'll grab a Failport, fix it, then return it.

[pyscho2day]

Right now I am 100% focused on the upcoming GUI system however (Unite is coming up in 2.5 weeks) so I can't jump on it until later.

You have my interest on this one.