I use FFW (http://www.zelow.no/floppyfw/index.html) as my firewall/dhcp/nat and what Elmer has posted for ports is about what I have set in the iptables for forwarding to my server. I can see the server on the internet list, the local list, doesn't matter.
----- Original Message ----- From: "Elmer Fudd" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, March 16, 2005 3:36 PM Subject: Re: [hlds_linux] Server Behind NAT > my listen/dedicated servfer wouldnt show up on the list until i > forwarded these ports also > * > > 2710-27012 | UDP > * > > 5273-5273 | TCP > * > > 7002-7002 | TCP > * > > 27020-27020 | TCP and UDP > * > > 27015-27015 | UDP > * > > 1200-1200 | UDP > * > > 27000-27015 | TCP and UDP > * > > 27030-27030 | TCP and UDP: > > > On Wed, 16 Mar 2005 18:29:12 -0500, Nathan Marcus > <[EMAIL PROTECTED]> wrote: >> BTW, here is what was also a good post, not "the one", but worthy >> http://server.counter-strike.net/forums/showthread.php?t=30409 >> ----- Original Message ----- >> From: "Nathan Marcus" <[EMAIL PROTECTED]> >> To: <[email protected]> >> Sent: Wednesday, March 16, 2005 6:16 PM >> Subject: Re: [hlds_linux] Server Behind NAT >> >> > Okay, I knew you were on a BSD box. This problem only occurs on >> > Linux/BSD >> > routers, I have right now a linux router myself, there is a definate >> > problem >> > somewhere with these routers when hosting any HLDS (UT2004 is like >> > butter >> > for me!), but I persist on. >> > >> > I know that ip thing sounds wrong, but can people still join from the >> > outside? I can prove my point here, just not in precise words. If you >> > pay >> > close attention to the startup log, in the middle it should state your >> > ip, >> > as you entered it. But it wont, it turns it (for god knows why), into >> > an >> > incorrect decimal ip. I appologize I do not remember exactly where to >> > look. >> > But take it out of your server.cfg, your autoexec.cfg, your startup. >> > OUT >> > OUT OUT!!! As long as people can direct connect from outside, it is >> > alright >> > at this point. >> > >> > I KNOW EXACTLY WHAT YOU MEAN ABOUT DIRECT CONNECTING, my head almost >> > blew >> > up. I knew the server I had was setup right, and I'm like "Why the >> > heck >> > isn't it showing up now?" Now, I'm guessing here, but I think** the >> > port >> > is >> > like 1423 to open? Its something that is way off in TCP, but it has to >> > do >> > with the listing of the server. >> > >> > What I meant by listening on both, which in my context was wrong, was >> > frankly the machine is physically located inside of the LAN. If you >> > specify >> > an internal address, it will cause a conflict with the router itself, >> > and >> > put you back a month or so. I am loookin for that post, it solved all >> > my >> > problems. But do not hesitate to keep asking, I hate reading with >> > these >> > routers when people say "All fixed." And dont say squat on how!!!!!! >> > (I >> > believe some frankly give up) >> > >> > ----- Original Message ----- >> > From: "Miles Crawford" <[EMAIL PROTECTED]> >> > To: <[email protected]> >> > Sent: Wednesday, March 16, 2005 4:11 PM >> > Subject: Re: [hlds_linux] Server Behind NAT >> > >> > >> >> >> >> Nathan, >> >> >> >> Thanks, but I'm having mixed results. My problem is that my server >> >> does >> >> not >> >> show up in the browser. It appears that people can join just fine >> >> using >> >> the >> >> direct IP address and port. So let's see: >> >> >> >>> when you specify an ip, it only begins listening on that ip, which is >> >>> outside of your LAN, then you connect, and it gets messed up. When >> >>> you >> >>> dont >> >>> define an ip, it will listen to LAN and WAN equally, assuming you >> >>> have >> >>> ALL >> >> >> >> This doesn't make much sense in terms of networking - the server only >> >> has >> >> one >> >> IP, a LAN ip of 192.168.0.2. It can't listen on both equally. >> >> >> >> I was using the +IP option because I read that it was used to inform >> >> the >> >> master server what IP to list in the server browser. Is that not >> >> true? >> >> >> >> >> >>> B) WATCH ALL OF YOUR STARTUP CVARS CLOSELY, ESPECIALLY SV_REGION, >> >>> when >> >>> you >> >> >> >> Okay - I will set these up as you describe. >> >> >> >> >> >>> C)CHECK YOUR ROUTER, THEN ASK A FRIEND TO CHECK YOUR ROUTER, AND >> >>> CHECK >> >>> YOUR >> >> >> >> My router is a BSD machine, and I have all blocked connections logged. >> >> I'm >> >> pretty sure that the router is NOT blocking any packets used for the >> >> game. >> >> Also, since people can connect to the server I think that's working. >> >> Again, >> >> is there something I can do to the router to get my server in the >> >> browser? >> >> >> >> >> >>> I will do my best to locate that post on the Steam Forums. Good >> >>> Luck! >> >> I would love to read it. >> >> >> >> Thanks! >> >> -Miles >> >> >> >> _______________________________________________ >> >> To unsubscribe, edit your list preferences, or view the list archives, >> >> please visit: >> >> http://list.valvesoftware.com/mailman/listinfo/hlds_linux >> >> >> > >> > >> > _______________________________________________ >> > To unsubscribe, edit your list preferences, or view the list archives, >> > please visit: >> > http://list.valvesoftware.com/mailman/listinfo/hlds_linux >> > >> >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> http://list.valvesoftware.com/mailman/listinfo/hlds_linux >> > > > -- > Cheers! > > -- Elmer Fudd > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
