servers not appearing

[DrDoom]

My fault. Im getting lots of

Code: Select all

Montag Januar 28, 2008 18:47:55 Unrecognized attempt blocked from 129.241.210.90:27950 to 89.245.165.247 UDP:51534
Montag Januar 28, 2008 18:47:55 Unrecognized attempt blocked from 64.22.107.125:27950 to 89.245.165.247 UDP:51534
Montag Januar 28, 2008 18:48:00 Unrecognized attempt blocked from 129.241.210.90:27950 to 89.245.165.247 UDP:51534
Montag Januar 28, 2008 18:48:00 Unrecognized attempt blocked from 64.22.107.125:27950 to 89.245.165.247 UDP:51534
Montag Januar 28, 2008 18:48:01 Unrecognized attempt blocked from 69.59.212.88:27950 to 89.245.165.247 UDP:51534
Montag Januar 28, 2008 18:48:03 Unrecognized attempt blocked from 129.241.210.90:27950 to 89.245.165.247 UDP:51534
Montag Januar 28, 2008 18:48:03 Unrecognized attempt blocked from 64.22.107.125:27950 to 89.245.165.247 UDP:51534
Montag Januar 28, 2008 18:48:03 Unrecognized attempt blocked from 69.59.212.88:27950 to 89.245.165.247 UDP:51534
Montag Januar 28, 2008 18:48:06 Unrecognized attempt blocked from 129.241.210.90:27950 to 89.245.165.247 UDP:51534
Montag Januar 28, 2008 18:48:06 Unrecognized attempt blocked from 64.22.107.125:27950 to 89.245.165.247 UDP:51534


when trying to get a server list.
I modified the firewall rule to only use UDP and opened a wider range of ports, because my Nexuiz client also binds to ports between 50000 and 60000:

Code: Select all

trigger: 26000-27950 UDP
public ports: 26000-27950, 50000-65000  all  UDP
public trigger: UDP

btw: My router is a D-Link DI-524 if anyone has experience with that device.

[DrDoom]

Public port range needs to be 30000-40000. 50000-65000 are the NAT'ed ports.
But that doesnt help.

[divVerent]

Obviously, your router sucks. For routers that suck, there is one thing you can do:

Make a new file "autoexec.cfg" next to your config.cfg
Inside that file, write:

cl_port 26006

Then, open the router configuration, and set up a port forwarding from UDP port 26006 to your PC. That should fix it for you.

[DrDoom]

Yup. That doest it. Many thanks!
Too bad my router obviously cant do that with a trigger based rule. Ill ask their support whether this can be somehow fixed.

[divVerent]

I don't think trigger based rules are supposed to make this work, so actually D-Link is doing a good job there.

However, with a good router, Nexuiz would automatically work... the problem you have means that your router has no NAT support for UDP.

[DrDoom]

To my opinion at least a trigger based rule for a fixed client port should work. Maybe getting responses from multiple hosts is the problem.
Im quiete content with the DI-524 though. It can do a lot more than my old IPCOP could. (and the additional latency caused by the router is much lower).

[PinkRobot]

My router refused to do more then a little with Nexuiz until a few months ago. Play over the router was laggy no matter what settings/forwarding I tried and after a few games it would just use the up connection to the server [not the down one, as I could still see what was going on around me...] then after a while I would lose that too and the server list would not come up again either. I had some problems with other apps too by the way. Then they released a new firmware and all was good. Not a single problem has occurred since I upgraded it. Which only leads me to believe I bought a completely broken product which they only bothered to fix after months and months of it being in the shops.

So what I am trying to say is, sometimes a piece of hardware just IS crap and if you're lucky the company will bother to fix it.

[AU]

My router is DI-624; I haven't any problems with nexuiz, firewall, etc... But, actually, router has big problems with pptp and pppoe (I think it doesn't support any kind of encryption, and firmware upgrade doesn't change anything), which was perfect in DI-524