Gateway: None found

[Deozaan]

Is it a problem that the gateway is never found? I can't seem to get UPnP to work with the built-in TNServer.exe. My teammate and I have tried this on multiple machines, on multiple networks. We get an error:

ERROR: (UPnP) A connection attempt failed because the connected party did not pr
operly respond after a period of time, or established connection failed because
connected host has failed to respond
Gateway:  None found

Is this bad, or will it work with this error?

I don't know if this is related or not, but we have two lines of code, the SendQuickly doesn't work, but Send does:

1. //tno.Send("setPos", Target.OthersSaved, transform.position, transform.eulerAngles);  // this sends over tcp and works
2. tno.SendQuickly("setPos", Target.OthersSaved, transform.position, transform.eulerAngles); // this sends over udp and doesn't work
3.  

There are no errors. SendQuickly just doesn't update the position, but using Send, the position is updated.

[ArenMook]

Not all routers/modems support UPnP. Apple Failport Extreme doesn't, for example. Good majority of the ones from the past 5 years do though.

SendQuickly will only function if your UDP is functional. What's your build target and have you tried testing it with the built-in examples? (3 uses it for cube movement)

[Deozaan]

Not all routers/modems support UPnP. Apple Failport Extreme doesn't, for example. Good majority of the ones from the past 5 years do though.

SendQuickly will only function if your UDP is functional. What's your build target and have you tried testing it with the built-in examples? (3 uses it for cube movement)

I'm not sure which router my teammate is using, but I'm not using a Crapple Failport Extreme. I believe it's new this year, possibly last year. It's a Cisco DPC3825, the manual says it features "UPnP IGD 1.0"

Build target is Desktop (PC/Max/Linux). The interesting thing is that it appeared to be working for me when I ran two copies of the exe at the same time, but when my team mate and I both connect, it does not work. And it does not work at all for my team mate if he tries running two exes.

[ArenMook]

What doesn't work? UDP? I actually have two internet connections here -- cable, via a Netgear router (with UPnP support), and DSL via an old stock gateway device that can't do UPnP. The examples work as expected on both. On the DSL line it takes 3 seconds to connect because it first tries the external address, and without UPnP the port is blocked, so it fails. At that point it tries the internal address, and it succeeds.

Does the top left corner show "TCP+UDP" for you?

[Deozaan]

What doesn't work? UDP? I actually have two internet connections here -- cable, via a Netgear router (with UPnP support), and DSL via an old stock gateway device that can't do UPnP. The examples work as expected on both. On the DSL line it takes 3 seconds to connect because it first tries the external address, and without UPnP the port is blocked, so it fails. At that point it tries the internal address, and it succeeds.

Does the top left corner show "TCP+UDP" for you?

Top left corner shows "TCD+UDP" for both of us. But when we use SendQuickly, it never gets sent.

If I connect to his server with two of clients running on my own machine, then SendQuickly will work fine. But if I'm running a client on my machine connected to a server on his, and he's running a client on his machine connected to his own server, SendQuickly does not work.

EDIT: We just tried Example 3 and we don't see the cubes move as they're being dragged around. They just suddenly teleport to a new destination, probably once the other person lets go.

[Roidz]

after many more tests we get this results:

- example 3 worked once how it should. the rest of the times the cubes teleport instead of moving. We have no idea why it worked once. We didn't change anything.
- on all examples it shows tcp/udp.
- Using sendquickly instead of send doesn't return any errors, it just doesn't do anything,if we replace it with a normal Send, it works.
- on my router i have to open the ports manually, it doesn't open ports automatic, even with Upnp active. It also can't find the Gateway.

We're stuck with this problem , we would like to move on but this is holding us back. Help is appriciated !

[ArenMook]

Sounds like something is breaking your UDP traffic. UDP by nature is "fire and forget". TNet sends one packet, and if it gets through, it assumes that others will too and will use UDP when you ask it to. It seems for you the issue occurs after the first packet arrives safely. Without more details there isn't much I can do to investigate it unfortunately. Everything I try on my end works fine. If you can't debug it, your best bet would be to stick to TCP if you can.

[Deozaan]

Here's another pattern I noticed: If I test some code that's using SendQuickly, by running two EXEs on this machine, but connecting to the Server that Roidz is running, SendQuickly works fine. It's only when he is connected to his own server that things seem to get messed up somehow.

[ArenMook]

The UDP port that gets chosen by clients must be random, and must not conflict. Perhaps the same post gets chosen in your case?