Cannot connect to server (cliche?) internet only

[sockduck]

Well!
I am hosted with fasthost.co.uk - they sadly provide no support, or clues as to running a game server.

Problem is: server setup, fine ; server run, fine; connect to server from internet, uh-ho!
Tried gametiger.com, nothing really comes up apart from IP address with lots of ??'s.

I think it might have something to do with their routing. I have two ips, but only using one for the server.

dump of ifconfig - a:

Code:

eth0      Link encap:Ethernet  HWaddr 00:11:11:4F:DA:A5
          inet addr:213.171.205.126  Bcast:213.171.207.255  Mask:255.255.252.0
          inet6 addr: fe80::211:11ff:fe4f:daa5/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:720184 errors:0 dropped:0 overruns:0 frame:0
          TX packets:450823 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:773417210 (737.5 Mb)  TX bytes:40958892 (39.0 Mb)

eth0:0    Link encap:Ethernet  HWaddr 00:11:11:4F:DA:A5
          inet addr:213.171.205.125  Bcast:213.171.207.255  Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:2111 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2111 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2233651 (2.1 Mb)  TX bytes:2233651 (2.1 Mb)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

Could be a bad thing posting that

iptables -L dump:

Code:

Chain INPUT (policy DROP)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere            state RELATED,ESTABLISHED
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:ssh state NEW
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:http state NEW
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:https state NEW
ACCEPT     udp  --  anywhere             anywhere            udp dpt:domain state NEW
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:domain state NEW
ACCEPT     udp  --  anywhere             anywhere            udp dpt:tftp state NEW
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:tftp state NEW
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:smtp state NEW
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:pop3 state NEW
ACCEPT     udp  --  anywhere             anywhere            udp dpt:ntp state NEW
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:ftp-data state NEW
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:ftp state NEW
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:mysql state NEW
ACCEPT     udp  --  anywhere             anywhere            udp dpt:mysql state NEW
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:5555 state NEW
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:8002 state NEW
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:9001 state NEW
DROP       all  --  anywhere             anywhere
ACCEPT     udp  --  anywhere             anywhere            udp dpts:27000:27015
ACCEPT     udp  --  anywhere             anywhere            udp spts:27000:27015
ACCEPT     tcp  --  anywhere             anywhere            tcp dpts:27030:27039 flags:SYN,RST,ACK/SYN
ACCEPT     tcp  --  anywhere             anywhere            tcp spts:27030:27039 flags:SYN,RST,ACK/SYN
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:27015 flags:SYN,RST,ACK/SYN
ACCEPT     tcp  --  anywhere             anywhere            tcp spt:27015 flags:SYN,RST,ACK/SYN

Chain FORWARD (policy DROP)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere            state NEW,RELATED,ESTABLISHED

Chain RH-Firewall-1-INPUT (0 references)
target     prot opt source               destination

Wow i really am giving a lot away

If someone could take the time to read over this i would be very grateful!
Also, if i have missed something then can you please tell me!

Or if your sick of ppl like me posting, ignore

Thanks!!

[sockduck]

Obviously im phrasing the question wrongly!

Can anyone give me the commands for iptables which will allow me to open the ports i need for a specific ip address. More than likely im behind a NAT btw!

Thanks

[snewo]

First off - turn iptables off and see if you still have a problem.

If not, then I suggest wandering about 3 posts up (or down) and looking for the topic on iptables. I posted my iptables section for the ports HL2 needs in there.

If you still have a problem then it might be a physical router. I'd try a program like nmap to port scan the server to see what gets blocked. Do that with iptables off btw.


Snewo

[sockduck]

thanks mate!! it actually works now iptables is turned off!

Though another problem i have is

bad challenge xxx.xxx.xxx.xxx
no challenge xxx.xxx.xxx.xxx

Argh, the annoyance.
Thing is, i can join the server fine, no probs. Restarted to see if there was an update, but nada!

Anyone else want to try it:
213.171.205.125:27015

[snewo]

I don't recommend running very long with iptables off, that was just a troubleshooting step. Try to implement the iptables setup from the other thread. Let me know if it isn't working.

The bad challenge thing is normal. You can get rid of it by entering "sv_enableoldqueries 1" in your server.cfg file. Valve recommends you don't though and hopefully the writers of the scripts making those queries will change. The new method is an improvement.


Snewo