Nitro, on 16 July 2012 - 03:11 AM, said:
ok maybe I misunderstood the decision behind supporting home networks, thanks raider.
In that case tom I can give you the answer:
+set dedicated 2
decicated 1 = Broadcast to Local Area Network
dedicated 2 = Broadcast to Wide Area Network
@Nitro You didn't read what he posted. He has WAN set properly.
@texman
It's likely a routing issue.
Hitch warning is (simply) referring to CPU usage / script delay.. No biggy and it's to be expected.
Did you set port forwarding (Or DMZ) in your router to your servers local IP?
Are you using more than one router? (Is your modem bridged or routed?.. Does it give you a local address directly plugged into it?)
Most newer modems are routed instead of bridged to reduce IP (IP v4) usage.
Suggestions:
Routed Modem:
1: Connect server directly to routed modem.
2: Port forward or DMZ modem to local ip (ifconfig to get it)
Routed modem (single port):
1: Get a simple switch (4 port or less.. NOT a router or a Hub!)
2: Plug server and all other hard wired devices into switch
3: Follow instructions for routed modem.
If you have a router behind a routed modem, you are playing with fire unless you understand networking and it eccentricities.. I'm assuming that since you are here, networking is not your forte.
In that case, just follow the instructions above.My provider Time Warner Cable does not like to have "unauthorized" servers on it's networ so I had to do some adjusting myself :D
But, you can make it work :D
Also, one other suggestion, change your hostame to your ip address in the nix terminal. > hostname YourIpAddress
You may also want to manually set your external IP in the shell file (.sh) by adding +set net_ip YourIpAddress
Again, I don't know your entire network situation, but this should give you a good jump start on where to look and what to change :D
Other suggestions:
1: Be sure your filters (Empty / TDM) are not on in your client
2: Can you connect to it via external address? ( /connect youripaddress) and can others? (External can still be routed internally depending on net config)
3: Validate iptables (iptables -L); Make sure it is not blocking incoming packets/requests. Many Nix distros default to a strong security including blocking ICMP.. You could also validate that just by pinging it's local IP. If no request returns, you're likely to have iptables firewall conflict. But also check the iptables rules anyways to be sure it isn't blocking UDP connections.
This post has been edited by Pussnboots: 16 July 2012 - 05:12 AM