Tremulous Forum

Community => Servers => Topic started by: MechWarrior001 on August 21, 2010, 11:38:54 pm

Title: Heartbeats not reaching master server
Post by: MechWarrior001 on August 21, 2010, 11:38:54 pm
I'm trying to run a dedicated server using the MG's tremded, but when I set dedicated 2 and start it, it automatically resolves master.tremulous.net to 69.175.114.216:30710, and my heartbeats never reach it. I have a Netgear WGR614v7 and I have forwarded port 30710 on TCP/UDP but it still doesn't work. I also set net_port to 54689. Any ideas why its not connecting?
Title: Re: Heartbeats not reaching master server
Post by: DraZiLoX on August 21, 2010, 11:41:19 pm
Hold on. Should net_port be the ip your forwarded?
Title: Re: Heartbeats not reaching master server
Post by: MechWarrior001 on August 21, 2010, 11:44:47 pm
Not sure. My dg is 10.0.0.1, and the server tuts said I should have a static IP so I set mine in windows to be 10.0.0.32. I also tried forwarding port 30710 (UDP) in Windows Firewall, but didn't seem to do much.
Title: Re: Heartbeats not reaching master server
Post by: Aelita on August 22, 2010, 02:35:15 am
The heartbeats reach the server fine, you don't need to forward an outgoing port. You need to forward 54689, not 30710.

Also, why are you using a whole class A for your home?
Title: Re: Heartbeats not reaching master server
Post by: MechWarrior001 on August 22, 2010, 02:56:21 am
Thanks for the help. Also, What do you mean "a whole class A"?
Title: Re: Heartbeats not reaching master server
Post by: superspirality on August 22, 2010, 08:20:45 am
Also, why are you using a whole class A for your home?
1) Almost no one uses IP classes now, CIDR supersedes it.
2) Seems like it's an intra-net address.
Title: Re: Heartbeats not reaching master server
Post by: Aelita on August 22, 2010, 03:26:19 pm
still can apply A=/8 B=/16 C=/24 terms. but there's no reason to use an entire /8 for a home network.
Title: Re: Heartbeats not reaching master server
Post by: superspirality on August 22, 2010, 06:22:23 pm
still can apply A=/8 B=/16 C=/24 terms. but there's no reason to use an entire /8 for a home network.
Sure. There's actually a little chance it is /8. If it is, the guy is lucky.
Title: Re: Heartbeats not reaching master server
Post by: Aelita on August 22, 2010, 06:35:16 pm
It's a private range. 10.0.0.0/8 is non-routable on the public internet.
Title: Re: Heartbeats not reaching master server
Post by: MechWarrior001 on August 22, 2010, 09:54:33 pm
I still don't get what you guys mean by A=/8, B=/16 and C=/24
Title: Re: Heartbeats not reaching master server
Post by: Crava_Loft on August 22, 2010, 11:44:16 pm
an ipv4 address is 4 bytes and each byte is 8 bits. in total you have 32 bits
a.b.c.d/15 is an ip range. first 15 bits must be the same as a.b.c.d and rest of the bits can be anything.
for example a.b.c.d/24 is a.b.c.* (remeber that each bit is 8 bits so first 24/8=3 bytes must be the same and the 4th can be anything)
Title: Re: Heartbeats not reaching master server
Post by: David on August 22, 2010, 11:54:38 pm
Ignore the class A stuff.  What internal IP's are used is mostly arbitrary.
Of course, trying to look smart somewhat backfires when it's obvious you have no clue...


Anyway, you need to forward the port the server is on, in this case 54689, and leave 30710 alone.
It's possible you'll never see it on the list from within your house, as some routers do funny stuff with port forwarding.

You can use http://master.tremulous.net/list/ to see if it's on the list (updates every 5 min) or look at http://master.tremulous.net/logs69.php to see the last ~20min of what you said to/from the master.  If it makes no sense wait a few min for it to all be there and post it here.
Title: Re: Heartbeats not reaching master server
Post by: Crava_Loft on August 22, 2010, 11:57:54 pm
Oh noes you gave the real answer now we can't fill his brain with useless - half correct info about IPs
btw I found this link quite useful:
http://www.nataliedee.com/archives/2006/Jun/
Title: Re: Heartbeats not reaching master server
Post by: MechWarrior001 on August 23, 2010, 01:30:55 am
http://master.tremulous.net/logs69.php (http://master.tremulous.net/logs69.php) returned this:

Code: [Select]
[19:23:12] D << 76.236.29.200:60573: 'xffxffxffxffheartbeat Tremulousn'
[19:23:12] D >> 76.236.29.200:60573: "xffxffxffxffgetinfo |t<'Cj0bsg2v"
[19:23:18] V 76.236.29.200:60573 dropped: no response (172)
[19:26:32] D << 76.236.29.200:60660: 'xffxffxffxffheartbeat Tremulousn'
[19:26:32] D >> 76.236.29.200:60660: 'xffxffxffxffgetinfo v67anvVr5yh}'
[19:26:37] V 76.236.29.200:60660 dropped: no response (173)
Title: Re: Heartbeats not reaching master server
Post by: David on August 23, 2010, 12:05:00 pm
Looks like the port forwarding isn't working.
Title: Re: Heartbeats not reaching master server
Post by: Aelita on August 23, 2010, 01:28:33 pm
Ignore the class A stuff.  What internal IP's are used is mostly arbitrary.
Of course, trying to look smart somewhat backfires when it's obvious you have no clue...

The heartbeats reach the server fine, you don't need to forward an outgoing port. You need to forward 54689, not 30710.

Did I not give him the correct answer? I hardly see how I have no clue.


Also:
Most routers I've used give you an option for protocol and sometimes port translation. Make sure (if they're there) both ports are what you had net_port set to, and the protocol (if it's there) is set to UDP.
Even better, but slightly risky, there may be an option known as DMZ on your router. This makes it so you don't have to forward any ports. You shouldn't use this permanently but for testing it's acceptable. If you can enable DMZ and get the server's heartbeat replies, then you know it's a port forwarding issue. Otherwise it's your router. And don't forget to disable DMZ!

Edit: If possible could you take a screenshot of the port forward configuration page? Censor out any private details etc.
Title: Re: Heartbeats not reaching master server
Post by: David on August 23, 2010, 01:38:19 pm
The "no clue" was more aimed at superspirality's not knowing about 10/8 being rfc1918 space.
Title: Re: Heartbeats not reaching master server
Post by: Aelita on August 23, 2010, 01:42:50 pm
Oh, my bad. :)
Title: Re: Heartbeats not reaching master server
Post by: superspirality on August 23, 2010, 04:59:07 pm
The "no clue" was more aimed at superspirality's not knowing about 10/8 being rfc1918 space.
Eh?
2) Seems like it's an intra-net address.
That isn't me trying to look smartby harassing other people. I output the things I know.
Title: Re: Heartbeats not reaching master server
Post by: MechWarrior001 on August 24, 2010, 03:42:26 am
Here's my Port Forward screen if you need it. I have Port Triggering disabled, if that effects this at all.

Edit: Tried the DMZ method. Still getting dropped connection messages from http://master.tremulous.net/logs69.php (http://master.tremulous.net/logs69.php)
Title: Re: Heartbeats not reaching master server
Post by: Aelita on August 24, 2010, 06:13:13 am
Does your cable/DSL/etc modem possibly have a router built in? Some do and also have NAT, causing serious issues with port forwarding. If not, the most I can say is your router is probably garbage. :P
Title: Re: Heartbeats not reaching master server
Post by: MechWarrior001 on August 24, 2010, 06:28:46 am
We use a Speedstream 4100 DSL modem. Other than that, I'm not to sure. If it helps, my PSP reports our connection of using NAT Type 3.

(http://img.auctiva.com/imgdata/1/0/2/8/3/3/1/webimg/275988468_tp.jpg)
Title: Re: Heartbeats not reaching master server
Post by: gimhael on August 24, 2010, 10:39:06 am
These port forwarding instructions for Quake3 (http://portforward.com/english/routers/port_forwarding/Siemens/4100/Quake_3.htm) should work for Tremulous too, except that the Tremulous server uses the port number 30720 instead of the Quake 3 port numbers.
Title: Re: Heartbeats not reaching master server
Post by: David on August 24, 2010, 10:48:21 am
Just noticed, the master log you posted shows heartbeats from port 60573 and 60660.  So my guess is your router is changing the port on the way through.  AFAIK there's not really any fix other than get better NAT.
Title: Re: Heartbeats not reaching master server
Post by: Aelita on August 24, 2010, 06:27:12 pm
I'd invest in a Linksys WRT54GL or similar. If you can, put DD-WRT on them, they make very good stable routers.
Title: Re: Heartbeats not reaching master server
Post by: MechWarrior001 on August 25, 2010, 03:22:35 pm
Yay! I got it working! Check it out:

Code: [Select]
[09:35:57] D << 76.248.171.160:30720: 'xffxffxffxffheartbeat Tremulousn'
[09:35:57] D >> 76.248.171.160:30720: 'xffxffxffxffgetinfo ^5Ae*4yz-z9j'
[09:35:57] D << 76.248.171.160:30720: 'xffxffxffxffinfoResponsen\game\base\maxPing\250\voip\1\pure\1\sv_maxclients\32\clients\0\mapname\atcs\hostname\^3M^7echWarrior ^3A^7rena\protocol\69\challenge\^5Ae*4yz-z9j'
[09:35:57] V << 76.248.171.160:30720: infoResponse: verified, added to list (182)

Apparently on my DSL modem I had to set it to allow LAN devices to use the public IP address.

So, check out the MechWarrior Arena when you can. For the time being it's all custom maps. Rotation is as follows:

Code: [Select]
citadel
  dreamstation-final
  ethereal
  fatalerror-beta1
  gamma_core-final
  mccfinal
  omega_b1
  pushcannon_b3
  rotcannon_b11
  station15-beta3
  supremacy_v1
  UTCS
  bluedragon

Let me know how if there's anything wrong performance-wise and I'll adjust accordingly.
Title: Re: Heartbeats not reaching master server
Post by: Aelita on August 26, 2010, 04:01:45 am
We use a Speedstream 4100 DSL modem. Other than that, I'm not to sure. If it helps, my PSP reports our connection of using NAT Type 3.

(http://img.auctiva.com/imgdata/1/0/2/8/3/3/1/webimg/275988468_tp.jpg)
Does your cable/DSL/etc modem possibly have a router built in? Some do and also have NAT, causing serious issues with port forwarding. If not, the most I can say is your router is probably garbage. :P

Yep. Speedstream modems have firmware that handles NAT and such built in.
Title: Re: Heartbeats not reaching master server
Post by: ULTRA Random ViruS on November 14, 2010, 08:52:25 am
Yay! I got it working! Check it out:

Code: [Select]
[09:35:57] D << 76.248.171.160:30720: 'xffxffxffxffheartbeat Tremulousn'
[09:35:57] D >> 76.248.171.160:30720: 'xffxffxffxffgetinfo ^5Ae*4yz-z9j'
[09:35:57] D << 76.248.171.160:30720: 'xffxffxffxffinfoResponsen\game\base\maxPing\250\voip\1\pure\1\sv_maxclients\32\clients\0\mapname\atcs\hostname\^3M^7echWarrior ^3A^7rena\protocol\69\challenge\^5Ae*4yz-z9j'
[09:35:57] V << 76.248.171.160:30720: infoResponse: verified, added to list (182)

Whats with that gibberish every here and there? If your hiding ur name you could do something like 'bob' or 'user' instead of liasug fvlaisurg valk ugha.
Title: Re: Heartbeats not reaching master server
Post by: Aelita on November 14, 2010, 08:59:00 am
It's protocol data.