SRCDS Steam group


[SOLVED] "Server not responding" and local address if friends view my game info
#1
My setup:

Server: Ubuntu Server Edition 11.04
No firewalls

Game-PC: Win7 Ultimate Edition x64

Both connected to a D-LINK DIR825 router. A CISCO EPC3212 is connected to the router via wan-port.

No matter if I host l4d2, tf2 or dods using the linux dedicated server none of my friends can join me using the game info. But they can join the servers directly via external ip.
I can join the servers with local and external ip without a problem. Only if I host a l4d2 lobby using forceservers with the external address nothing happens. If I use the local ip, I can connect, but the others can't.
As long as someone else is the lobby-leader and connects to the server it works perfectly fine.

Ports forwarded for my server:
TCP: 1200,4380,6901,26901,27000-27051
UDP: 1200,3478,4379,4380,6901,26901,27000-27051

startl4d2server.sh:
Code:
export RDTSC_FREQUENCY=1870.000000
echo ""
echo "Starting Left4Dead 2 Dedicated Server"
echo ""
sleep 1
./srcds_run -console -game left4dead2 -secure +ip 192.168.0.103 +hostip **.***.***.** +hostport 27051 +clientport 27007 +map c1m1_hotel

l4d2server.cfg:
Code:
// % COPY BELOW THIS LINE %
//-----------------------------------------------------------
//--> This server.cfg is custom-created to assist server owners with
//--> setting up their server.cfg. You can copy/paste this text
//--> into your server.cfg or simply cookie cutter and use the
//--> parts that you would like to.
//-----------------------------------------------------------
//--> Updated 01/04/2010
//-----------------------------------------------------------

//--> This is the name for your server
hostname HOUSE of Rage

sv_steamgroup 1426533
sv_steamgroup_exclusive 0

//--> When Enabled, Steamgroup members take priority when joining
//--> The server. However, anyone may join as long as a steamgroup
//--> Member has joined first. Slots are only reserved while they
//--> Are available in this manner, and a minimum of 1 slot is
//--> Reserved, because when a steamgroup member connects to the
//--> Server, other players will be able to connect. If there are
//--> Other players connected and the steamgroup member disconnects
//--> A random player will qualify to fill the remaining slot.

//Allow connections without creating lobby
//--> "0" = Off
//--> "1" = On
sv_allow_lobby_connect_only 0

//--> Default is "0". When Enabled, cannot connect to
//--> Games currently in progress.

//--> All talk - Allow both teams to use audio chat to speak with each other
//--> "0" = Off
//--> "1" = On
sv_alltalk 0

//--> Region - This sets the lobby in which your server will be part of
//--> You will want to set this to the closest location to your server
//--> eastcoast - sv_region 0
//--> westcoast - sv_region 1
//--> south america - sv_region 2
//--> europe - sv_region 3
//--> asia - sv_region 4
//--> australia - sv_region 5
//--> middle east - sv_region 6
//--> africa - sv_region 7
//--> world - sv_region 255
sv_region 255

// Log Settings
sv_logfile 1
sv_logbans 1
sv_logecho 1
sv_log_onefile 0

sv_search_key "pprth"

setmaster add 68.142.72.250:27011
setmaster add 72.165.61.189:27011

// Execute ban files
exec banned_user.cfg
exec banned_ip.cfg
writeid
writeip
// % COPY ABOVE THIS LINE %

starttf2server.sh:
Code:
export RDTSC_FREQUENCY=1870.000000
echo ""
echo "Starting TF2 Dedicated Server"
echo ""
sleep 1
./srcds_run -console -autoupdate -game tf +ip 192.168.0.103 +hostip **.***.***.** -port 27051 +clientport 27007 +map cp_granary +maxplayers 24 -tickrate 66

tf2server.cfg:
Code:
// last modified 10:23 AM 6/4/2006

// **************************************
// server name
// **************************************
hostname "HOUSE of Rage - TF2 Server" // Name of the server.

// **************************************
// passswords
// **************************************
rcon_password "yourPASSWORDhere" // Remote control password.
sv_password "" // Server password for entry into multiplayer games. Password = private, no password = public.

// **************************************
// specific Day of Defeat: Source cvars
// **************************************
dod_bonusround "1" // If true, the winners of the round can attack in the intermission. Default: 1
dod_bonusroundtime "15" // Time after round win until round restarts. Default: 15
dod_enableroundwaittime "1" // Enable timers to wait between rounds. Default: 1
mp_allowrandomclass "1" // Allow players to select random class. Default: 1
mp_combinemglimits "0" // Set to 1 to combine the class limit cvars for mg34 and mg42. New limit is sum of two. Default: 0
mp_tickpointinterval "30" // Delay between point gives. Default: 30
mp_limit_allies_assault "-1" // Class limit for team: Allies class: Assault. Default: -1
mp_limit_allies_mg "-1" // Class limit for team: Allies class: Machinegunner. Default: -1
mp_limit_allies_rifleman "-1" // Class limit for team: Allies class: Rifleman. Default: -1
mp_limit_allies_rocket "-1" // Class limit for team: Allies class: Rocket. Default: -1
mp_limit_allies_sniper "-1" // Class limit for team: Allies class: Sniper. Default: -1
mp_limit_allies_support "-1" // Class limit for team: Allies class: Support. Default: -1
mp_limit_axis_assault "-1" // Class limit for team: Axis class: Assault. Default: -1
mp_limit_axis_mg "-1" // Class limit for team: Axis class: Machinegunner. Default: -1
mp_limit_axis_rifleman "-1" // Class limit for team: Axis class: Rifleman. Default: -1
mp_limit_axis_rocket "-1" // Class limit for team: Axis class: Rocket. Default: -1
mp_limit_axis_sniper "-1" // Class limit for team: Axis class: Sniper. Default: -1
mp_limit_axis_support "-1" // Class limit for team: Axis class: Support. Default: -1
mp_warmup_time "0" // Warmup time length in seconds. Default: 0
sv_autojointeam "0" // Skip the class and team menus and join a team immediately. Default: 0

// **************************************
// sv cvars
// **************************************
sv_allowdownload "1" // Allow clients to download files. Default: 1
sv_allowupload "1" // Allow clients to upload customizations files. Default: 1
sv_alltalk "0" // Players can hear all other players, no team restrictions. Default: 0
sv_cheats "0" // Allow cheats on server. Default: 0
sv_consistency "1" // Whether the server enforces file consistency for critical files. Default: 1
sv_gravity "800" // World gravity. Default: 800
sv_lan "0" // Server is a lan server (no heartbeat, no authentication, no non-class C addresses). Default: 0
sv_maxspeed "320" // Maximum speed a player can move. Default: 320
sv_pausable "0" // Is the server pausable. Default: 0
sv_region "1" // The region of the world to report this server in. Default: -1
sv_timeout "45" // After this many seconds without a message from a client, the client is dropped. Default: 65
sv_voiceenable "1" // Microphone communication. Default: 1

// **************************************
// mp cvars
// **************************************
mp_allowspectators "1" // Toggles whether the server allows spectator mode or not. Default: 1
mp_autokick "1" // Kick idle/team-killing players. Default: 0
mp_chattime "10" // Amount of time players can chat after the game is over. Default: 10
mp_flashlight "1" // Allow flashlight. Default: 0
mp_footsteps "1" // Players can hear footsteps. Default: 1
mp_forcecamera "1" // Restricts spectator modes for dead players. Default: 0
mp_fraglimit "0" // Max number of kills any player can accumulate before server changes maps. Default: 0
mp_friendlyfire "1" // Allow team damage. Default: 0
mp_limitteams "1" // Max # of players 1 team can have over another. Default: 2
mp_timelimit "45" // Game time per map in minutes. Default: 0
mp_winlimit "7" // Max number of rounds one team can win before server changes maps. Default: 0

// **************************************
// bandwidth and rates
// **************************************
sv_maxrate "30000" // Max bandwidth rate allowed on server, 0 = unlimited. Default: 0
sv_minrate "0" // Min bandwidth rate allowed on server, 0 = unlimited. Default: 0
sv_maxupdaterate "66" // Maximum updates per second that the server will allow. Default: 60
sv_minupdaterate "0" // Minimum updates per second that the server will allow. Default: 10
decalfrequency "10" // Amount of time in seconds a player can spray their decal. Default: 10
fps_max "300" // Frame rate limiter. Default: 300

// **************************************
// server logging
// **************************************
log "on" // Control logging. on = enable logs, off = disable logs.
sv_logbans "1" // Log server bans in the server logs. Default: 0
sv_logecho "1" // Echo log information to the console. Default: 1
sv_logfile "1" // Log server information in the log file. Default: 1
sv_log_onefile "1" // Log server information to only one file. Default: 0

// **************************************
// server admin contact
// **************************************
sv_contact "admin@domain.com" // Contact email for server sysop.

// **************************************
// web server (http) download URL
// **************************************
sv_downloadurl "" // Location from which clients can download missing files.

// **************************************
// security
// **************************************
exec "banned_user.cfg"
exec "banned_ip.cfg"
writeid
writeip

tbh I'm out of ideas. It got it to work on a windows-machine once, but since then I've already reset my router so it might be possible that there's a setting wrong.


Big fat thx for any advice that might save my ass! Ask if there are any questions.
Reply
#2
Which address do you use to connect to the server?
Slå den med jeres fiberforbindelser...

[Image: 1308107839.png]
Reply
#3
(06-07-2011, 06:55 AM)Cyba_Mephisto Wrote:  I can join the servers with local (192.168.0.103) and external ip (IP the isp gives me) without a problem. Only if I host a l4d2 lobby using forceservers with the external address nothing happens. If I use the local ip, I can connect, but the others can't.

I've also tried to connect through lobby via mm_dedicated_force_servers external:port|internal:port, as it's said in the command description, but that doesn't let me connect to the server at all.
Even added 27051 to the lan-ports via command, no difference.

If you meant that you want to know my external ip to test it, pm me and I'll give it to you. You'll see that others can connect via lobby without a problem using the force_servers command.

EDIT: I'm sorry. By "local ip" I mean the address the router gave to my server. (so "local ip"=internal ip, and not 127.0.0.1)
Reply
#4
By the way, delete the "+hostip. +clientport and -secure" stuff, its unnecessary. If you connect through the local IP-address, your friends will never be able to connect to it through friends (right-click and joining you) because they don't know about your LAN (192.168.0.0 network).

Also, i would probably just open port 27051 TCP&UDP, a whole port range is way too much. Have you tried to make some TCP-dumping?
Slå den med jeres fiberforbindelser...

[Image: 1308107839.png]
Reply
#5
Can you post a screenshot of your port forwarding.
Looking for a game server? Visit fullfrag.com and pick one up as low as $2.50 / mo!
Reply
#6
@lol554:

I've removed those unneccessary commands now and only forwarded 27051 TCP&UDP. Doesn't make a difference.
Even if I connect directly via WAN-IP and I get in the game, my friends only get the local ip of the server in the gameinfo. TS3-server works just fine and I connect with both ips. Friends can join my ts-server, too.

Screenshot:
http://h3.abload.de/img/portswcs1.jpg

About tcp-dumping:
I'm new to linux, so I googled what you meant by that. tcp-dump is installed on the system, but it would be nice if you could tell me what command I should use and if I should perform a certain action while it's logging.


EDIT:
And yes, the server's internal ip is 192.168.0.101 now because I flashed dd-wrt on the router in the meantime to test the server with some extra settings and flashed it back to stock firmware later on, since that didn't make a difference as well. Ah and DMZ doesn't solve the issues, too. So I guess it's not forwarding-related, but who knows.
Reply
#7
TCPDUMP:
Code:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
17:58:54.583406 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 194.0.168.192.in-addr.arpa. (44)
17:58:54.583461 IP HouseOfRage.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 194.0.168.192.in-addr.arpa. (44)
17:58:54.584102 IP HouseOfRage.local.52456 > 192.168.0.1.domain: 54189+ PTR? b.f.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.f.f.ip6.arpa. (90)
17:58:54.591157 IP 192.168.0.1.domain > HouseOfRage.local.52456: 54189 NXDomain 0/0/0 (90)
17:58:54.591378 IP HouseOfRage.local.35754 > 192.168.0.1.domain: 53983+ PTR? f.e.3.b.a.0.e.f.f.f.c.8.e.1.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. (90)
17:58:54.591996 IP 192.168.0.1.domain > HouseOfRage.local.35754: 53983 NXDomain 0/0/0 (90)
17:58:54.592141 IP HouseOfRage.local.38712 > 192.168.0.1.domain: 49900+ PTR? 251.0.0.224.in-addr.arpa. (42)
17:58:54.592702 IP 192.168.0.1.domain > HouseOfRage.local.38712: 49900 NXDomain 0/0/0 (42)
17:58:54.693067 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 251.0.0.224.in-addr.arpa. (42)
17:58:54.693103 IP HouseOfRage.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 251.0.0.224.in-addr.arpa. (42)
17:58:55.196417 ARP, Request who-has 192.168.0.105 tell 192.168.0.1, length 46
17:58:55.196431 ARP, Request who-has 192.168.0.104 tell 192.168.0.1, length 46
17:58:55.196435 ARP, Request who-has 192.168.0.103 tell 192.168.0.1, length 46
17:58:55.694233 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 251.0.0.224.in-addr.arpa. (42)
17:58:55.694272 IP HouseOfRage.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 251.0.0.224.in-addr.arpa. (42)
17:58:56.197447 ARP, Request who-has 192.168.0.102 tell 192.168.0.1, length 46
17:58:56.197460 ARP, Request who-has HouseOfRage.local tell 192.168.0.1, length 46
17:58:56.197465 ARP, Reply HouseOfRage.local is-at 00:1e:8c:0a:b3:ef (oui Unknown), length 28
17:58:56.197469 ARP, Request who-has 192.168.0.100 tell 192.168.0.1, length 46
17:58:56.197925 IP 192.168.0.1.1150 > HouseOfRage.local.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; UNICAST
17:58:56.198022 IP HouseOfRage.local.netbios-ns > 192.168.0.1.1150: NBT UDP PACKET(137): QUERY; POSITIVE; RESPONSE; UNICAST
17:58:56.482365 IP HouseOfRage.local.59443 > 192.168.0.1.domain: 54274+ PTR? 193.0.168.192.in-addr.arpa. (44)
17:58:56.482373 IP HouseOfRage.local.48694 > 192.168.0.1.domain: 7200+ PTR? 193.0.168.192.in-addr.arpa. (44)
17:58:56.505599 IP 192.168.0.1.domain > HouseOfRage.local.48694: 7200 NXDomain 0/1/0 (121)
17:58:56.506956 IP 192.168.0.1.domain > HouseOfRage.local.59443: 54274 NXDomain 0/1/0 (121)
17:58:56.606200 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 193.0.168.192.in-addr.arpa. (44)
17:58:56.606231 IP HouseOfRage.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 193.0.168.192.in-addr.arpa. (44)
17:58:57.435065 IP 192.168.0.100.27005 > 255.255.255.255.27015: UDP, length 33
17:58:57.607472 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 [2q] PTR (QM)? 193.0.168.192.in-addr.arpa. PTR (QM)? 251.0.0.224.in-addr.arpa. (62)
17:58:57.607512 IP HouseOfRage.local.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? 193.0.168.192.in-addr.arpa. PTR (QM)? 251.0.0.224.in-addr.arpa. (62)
17:58:57.965338 IP 192.168.0.100.27005 > 255.255.255.255.27015: UDP, length 33
17:58:58.466527 IP 192.168.0.100.27005 > 255.255.255.255.27015: UDP, length 33
17:58:59.718943 IP HouseOfRage.local.37151 > 192.168.0.1.domain: 55155+ PTR? 1.0.168.192.in-addr.arpa. (42)
17:59:04.742366 IP HouseOfRage.local.46389 > 192.168.0.1.domain: 22636+ PTR? 105.0.168.192.in-addr.arpa. (44)
17:59:04.751193 IP 192.168.0.1.domain > HouseOfRage.local.46389: 22636 NXDomain 0/1/0 (121)
17:59:04.851603 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 105.0.168.192.in-addr.arpa. (44)
17:59:04.851650 IP HouseOfRage.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 105.0.168.192.in-addr.arpa. (44)
17:59:05.852908 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 105.0.168.192.in-addr.arpa. (44)
17:59:05.852955 IP HouseOfRage.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 105.0.168.192.in-addr.arpa. (44)
17:59:06.530010 IP HouseOfRage.local.55800 > 192.168.0.1.domain: 456+ PTR? 191.0.168.192.in-addr.arpa. (44)
17:59:06.530019 IP HouseOfRage.local.58608 > 192.168.0.1.domain: 42610+ PTR? 191.0.168.192.in-addr.arpa. (44)
17:59:09.752461 IP HouseOfRage.local.47862 > 192.168.0.1.domain: 15827+ PTR? 104.0.168.192.in-addr.arpa. (44)
17:59:14.771292 IP HouseOfRage.local.42805 > 192.168.0.1.domain: 25990+ PTR? 103.0.168.192.in-addr.arpa. (44)
17:59:19.782119 IP HouseOfRage.local.54251 > 192.168.0.1.domain: 14439+ PTR? 102.0.168.192.in-addr.arpa. (44)
17:59:19.791720 IP 192.168.0.1.domain > HouseOfRage.local.54251: 14439 NXDomain 0/1/0 (121)
17:59:19.892022 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 102.0.168.192.in-addr.arpa. (44)
17:59:24.792567 IP HouseOfRage.local.36174 > 192.168.0.1.domain: 35747+ PTR? 100.0.168.192.in-addr.arpa. (44)
17:59:24.793311 IP 192.168.0.1.domain > HouseOfRage.local.36174: 35747 NXDomain 0/0/0 (44)
17:59:24.893727 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 100.0.168.192.in-addr.arpa. (44)
17:59:29.794211 IP HouseOfRage.local.49801 > 192.168.0.1.domain: 62142+ PTR? 255.255.255.255.in-addr.arpa. (46)
17:59:29.794951 IP 192.168.0.1.domain > HouseOfRage.local.49801: 62142 0/0/0 (46)
17:59:29.895303 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 255.255.255.255.in-addr.arpa. (46)
17:59:29.895344 IP HouseOfRage.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 255.255.255.255.in-addr.arpa. (46)
17:59:30.896514 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 255.255.255.255.in-addr.arpa. (46)
17:59:30.896550 IP HouseOfRage.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 255.255.255.255.in-addr.arpa. (46)
17:59:30.991911 IP HouseOfRage.local.27051 > 68.142.72.250.27011: UDP, length 2
17:59:30.991957 IP HouseOfRage.local.27051 > 72-165-61-189.dia.static.qwest.net.27011: UDP, length 2
17:59:31.623568 IP HouseOfRage.local.60109 > 192.168.0.1.domain: 3285+ PTR? 106.0.168.192.in-addr.arpa. (44)
17:59:34.796019 IP HouseOfRage.local.37207 > 192.168.0.1.domain: 12407+ PTR? 250.72.142.68.in-addr.arpa. (44)
17:59:34.796774 IP 192.168.0.1.domain > HouseOfRage.local.37207: 12407 NXDomain 0/0/0 (44)
17:59:34.897097 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 250.72.142.68.in-addr.arpa. (44)
17:59:34.897137 IP HouseOfRage.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 250.72.142.68.in-addr.arpa. (44)
17:59:35.095030 IP 192.168.0.100.27005 > HouseOfRage.local.27051: UDP, length 20
17:59:35.114171 IP HouseOfRage.local.27051 > 192.168.0.100.27005: UDP, length 39
17:59:35.128350 IP 192.168.0.100.27005 > HouseOfRage.local.27051: UDP, length 429
17:59:35.147467 IP HouseOfRage.local.27051 > 192.168.0.100.27005: UDP, length 10
17:59:35.757312 IP HouseOfRage.local.26901 > 79.141.174.8.27017: UDP, length 84
17:59:35.898303 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 250.72.142.68.in-addr.arpa. (44)
17:59:35.898334 IP HouseOfRage.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 250.72.142.68.in-addr.arpa. (44)
17:59:36.647383 IP HouseOfRage.local.59658 > 192.168.0.1.domain: 35755+ PTR? 186.0.168.192.in-addr.arpa. (44)
17:59:36.647392 IP HouseOfRage.local.40341 > 192.168.0.1.domain: 3518+ PTR? 186.0.168.192.in-addr.arpa. (44)
17:59:36.670058 IP 192.168.0.1.domain > HouseOfRage.local.59658: 35755 NXDomain 0/1/0 (121)
17:59:36.671135 IP 192.168.0.1.domain > HouseOfRage.local.40341: 3518 NXDomain 0/1/0 (121)
17:59:36.770381 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 186.0.168.192.in-addr.arpa. (44)
17:59:36.770413 IP HouseOfRage.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 186.0.168.192.in-addr.arpa. (44)
17:59:37.771632 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 186.0.168.192.in-addr.arpa. (44)
17:59:37.771669 IP HouseOfRage.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 186.0.168.192.in-addr.arpa. (44)
17:59:37.898970 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 250.72.142.68.in-addr.arpa. (44)
17:59:37.898999 IP HouseOfRage.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 250.72.142.68.in-addr.arpa. (44)
17:59:38.127428 IP 192.168.0.100.27005 > HouseOfRage.local.27051: UDP, length 20
17:59:38.143403 IP HouseOfRage.local.27051 > 192.168.0.100.27005: UDP, length 39
17:59:38.161008 IP 192.168.0.100.27005 > HouseOfRage.local.27051: UDP, length 429
17:59:38.176930 IP HouseOfRage.local.27051 > 192.168.0.100.27005: UDP, length 10
17:59:38.230680 IP 192.168.0.100.27005 > 255.255.255.255.27015: UDP, length 33
17:59:38.763688 IP 192.168.0.100.27005 > 255.255.255.255.27015: UDP, length 33
17:59:39.293700 IP 192.168.0.100.27005 > 255.255.255.255.27015: UDP, length 33
17:59:39.797342 IP HouseOfRage.local.44554 > 192.168.0.1.domain: 39654+ PTR? 189.61.165.72.in-addr.arpa. (44)
17:59:39.798319 IP HouseOfRage.local.47987 > 192.168.0.1.domain: 11368+ PTR? 8.174.141.79.in-addr.arpa. (43)
17:59:39.798978 IP 192.168.0.1.domain > HouseOfRage.local.47987: 11368 NXDomain 0/0/0 (43)
17:59:39.899325 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 8.174.141.79.in-addr.arpa. (43)
17:59:39.899365 IP HouseOfRage.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 8.174.141.79.in-addr.arpa. (43)
17:59:40.293848 IP 192.168.0.100.27005 > 255.255.255.255.27015: UDP, length 33
17:59:40.795870 IP 192.168.0.100.27005 > 255.255.255.255.27015: UDP, length 33
17:59:40.900537 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 8.174.141.79.in-addr.arpa. (43)
17:59:40.900572 IP HouseOfRage.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 8.174.141.79.in-addr.arpa. (43)
17:59:41.328335 IP 192.168.0.100.27005 > 255.255.255.255.27015: UDP, length 33
17:59:41.671525 IP HouseOfRage.local.42073 > 192.168.0.1.domain: 713+ PTR? 185.0.168.192.in-addr.arpa. (44)
17:59:46.682753 IP HouseOfRage.local.36899 > 192.168.0.1.domain: 17185+ PTR? 184.0.168.192.in-addr.arpa. (44)
17:59:46.683797 IP HouseOfRage.local.44322 > 192.168.0.1.domain: 31077+ PTR? 184.0.168.192.in-addr.arpa. (44)
17:59:46.692224 IP 192.168.0.1.domain > HouseOfRage.local.44322: 31077 NXDomain 0/1/0 (121)
17:59:46.693309 IP 192.168.0.1.domain > HouseOfRage.local.36899: 17185 NXDomain 0/1/0 (121)
17:59:46.792634 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 184.0.168.192.in-addr.arpa. (44)
17:59:46.792686 IP HouseOfRage.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 184.0.168.192.in-addr.arpa. (44)
17:59:47.793418 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 184.0.168.192.in-addr.arpa. (44)
17:59:47.793471 IP HouseOfRage.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 184.0.168.192.in-addr.arpa. (44)
17:59:49.794719 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 184.0.168.192.in-addr.arpa. (44)
17:59:49.794769 IP HouseOfRage.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 184.0.168.192.in-addr.arpa. (44)
17:59:51.693455 IP HouseOfRage.local.38933 > 192.168.0.1.domain: 18755+ PTR? 3.0.0.0.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.f.f.ip6.arpa. (90)
17:59:51.694492 IP HouseOfRage.local.37698 > 192.168.0.1.domain: 20223+ PTR? 3.0.0.0.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.f.f.ip6.arpa. (90)
17:59:51.703140 IP 192.168.0.1.domain > HouseOfRage.local.38933: 18755 NXDomain 0/1/0 (160)
17:59:51.703307 IP HouseOfRage.local.40864 > 192.168.0.1.domain: 19388+ PTR? c.a.4.b.2.5.e.6.b.5.b.2.1.1.9.b.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. (90)
17:59:51.704448 IP 192.168.0.1.domain > HouseOfRage.local.37698: 20223 NXDomain 0/1/0 (160)
17:59:51.704547 IP HouseOfRage.local.44681 > 192.168.0.1.domain: 63480+ PTR? c.a.4.b.2.5.e.6.b.5.b.2.1.1.9.b.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. (90)
17:59:51.711505 IP 192.168.0.1.domain > HouseOfRage.local.40864: 19388 NXDomain* 0/1/0 (125)
17:59:51.711715 IP HouseOfRage.local.38259 > 192.168.0.1.domain: 16222+ PTR? 180.83.142.68.in-addr.arpa. (44)
17:59:51.712732 IP 192.168.0.1.domain > HouseOfRage.local.44681: 63480 NXDomain* 0/1/0 (125)
17:59:51.712931 IP HouseOfRage.local.39038 > 192.168.0.1.domain: 32856+ PTR? 180.83.142.68.in-addr.arpa. (44)
17:59:51.720952 IP 192.168.0.1.domain > HouseOfRage.local.38259: 16222 NXDomain 0/1/0 (93)
17:59:51.724949 IP 192.168.0.1.domain > HouseOfRage.local.39038: 32856 NXDomain 0/1/0 (93)
17:59:51.822298 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 180.83.142.68.in-addr.arpa. (44)
17:59:51.822353 IP HouseOfRage.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 180.83.142.68.in-addr.arpa. (44)
17:59:51.830059 IP 192.168.0.100.27005 > 255.255.255.255.27015: UDP, length 33
17:59:52.331299 IP 192.168.0.100.27005 > 255.255.255.255.27015: UDP, length 33
17:59:52.822590 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 180.83.142.68.in-addr.arpa. (44)
17:59:52.822645 IP HouseOfRage.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 180.83.142.68.in-addr.arpa. (44)
17:59:52.861216 IP 192.168.0.100.27005 > 255.255.255.255.27015: UDP, length 33
17:59:53.394229 IP 192.168.0.100.27005 > 255.255.255.255.27015: UDP, length 33
17:59:53.785616 IP HouseOfRage.local.26901 > 79.141.174.8.27017: UDP, length 84
17:59:53.927247 IP 192.168.0.100.27005 > 255.255.255.255.27015: UDP, length 33
17:59:54.165735 IP 79.141.174.8.27017 > HouseOfRage.local.26901: UDP, length 36
17:59:54.427899 IP 192.168.0.100.27005 > 255.255.255.255.27015: UDP, length 33
17:59:54.823439 IP6 fe80::21e:8cff:fe0a:b3ef.mdns > ff02::fb.mdns: 0 PTR (QM)? 180.83.142.68.in-addr.arpa. (44)
17:59:54.823491 IP HouseOfRage.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 180.83.142.68.in-addr.arpa. (44)
17:59:54.928894 IP 192.168.0.100.27005 > 255.255.255.255.27015: UDP, length 33

What I did:

-opened up a terminal, entered "sudo tcpdump"
-started the l4d2 server
-connected from lobby via "force_servers externalip:port"
-waited till the game said that it couldn't find a server

gamepc's-ip: 192.168.0.100
router: 192.168.0.1
server(HouseOfRage): 192.168.0.101
Reply
#8
More detailed dump using "sudo tcpdump -tt -vvv -w /home/house/Desktop/log.bin" in the attachments.

Also, ifconfig:
Code:
house@HouseOfRage:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:1e:8c:0a:b3:ef  
          inet addr:192.168.0.101  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::21e:8cff:fe0a:b3ef/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:552850 errors:0 dropped:0 overruns:0 frame:0
          TX packets:296301 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:807888302 (807.8 MB)  TX bytes:40174333 (40.1 MB)
          Interrupt:18

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:96 errors:0 dropped:0 overruns:0 frame:0
          TX packets:96 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:6112 (6.1 KB)  TX bytes:6112 (6.1 KB)


Attached Files
.zip   log.zip (Size: 11.41 KB / Downloads: 4)
Reply
#9
Try this command line:
Code:
./srcds_run -console -game left4dead2 -ip 192.168.0.101 -secure +map c1m1_hotel

This command line is assuming that your servers IP is 192.168.0.101

As long as the ports are forwarded and the server isn't on the same computer you're playing on then there is no reason to define host ports and host IP's.

EDIT:
I mis-read your original post. I'm not too sure what your issue is. What you're describing seems typical of valves lobby system, at least from my experiences.
Looking for a game server? Visit fullfrag.com and pick one up as low as $2.50 / mo!
Reply
#10
Well, as long as I can connect to my l4d2 server with a full lobby without the others players getting kicked out, I'm happy.
And I was able to do that once when I was running windows on the server. And if I now use my win7 netbook and run srcds on it the issue persists. oO

I don't care about the game info issue, but I'm afraid both issues have the same cause.

EDIT: Noone has any clue about this? oO What about the tcp dumps?
Reply
#11
Solution:

It was a router problem. idk what it was exactly, but I couldn't alter the behavior of the router no matter which settings I altered.
I now flashed it to OpenWRT (use the newest trunk pls for the dlink dir-825 because otherwise wan-lan speeds are horrible!).
Beside two led-bugs it works perfectly fine now. (power-led is orange and the internet-led is off, but who cares, the leds are way too strong and are annoying at night)

Thanks to everyone who at least tried to help me. Hope this stays online as long as possible for other people who have this problem.
Reply


Forum Jump:


Users browsing this thread: 4 Guest(s)