I can connect locally too, as well as away from the network. Perhaps I'll
get some time and put a copy of my configs on here which you may try?  Or a
link to them rather so I dont take up too much space.  It really annoyed me,
and then I got it working, and I hope that this can get resolved soon
because it is such a... well u know what I want to say.  The initial list of
CVARS really is the determining factor of sv_region, did you do "log 3"
(minus the quotes) in the server.cfg and check that way?  Now personally,
Scott what u said about Slackware looking like a nightmare to install... Its
a breeze, the text menus make it go faster for setup, and slackware IMHO
commands are important because it teaches you some valuable Linux lessons
through experience.  I tried Mandrake 1st, about 3 years ago, and I got
frustrated in a week, if that.  Slackware is the one that teaches you
because you gotta use some commands, although it still comes with X for the
desktop (and most CS server set up work).  But don't run out on a good
working server just yet, your friend connects which means there is absolute
potential.  Try again, and I'll get my cfg's to ya somehow soon.
----- Original Message -----
From: "Kerry Dorsey" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, January 05, 2005 10:19 AM
Subject: Re: [hlds_linux] WARNING: UDP_OpenSocket: port: 27015 bind: Cannot
assign requested


> Nathan Marcus wrote:
>
> >I am too behind a firewall, and router.  I found this forum post a while
ago
> >which helped a lot.
> >http://server.counter-strike.net/forums/showthread.php?s=&threadid=32243
> >read it for what its worth, it helped me.
> >----- Original Message -----
> >From: "Scott Ahlbrandt" <[EMAIL PROTECTED]>
> >To: <[email protected]>
> >Sent: Monday, January 03, 2005 5:33 PM
> >Subject: Re: [hlds_linux] WARNING: UDP_OpenSocket: port: 27015 bind:
Cannot
> >assign requested
> >
> >
> >On Monday 03 January 2005 21:47, Nathan Marcus wrote:
> >Nathan I'm behind a firewall so I have to specify an ip, my pf.conf is
> >below.
> >
> ># $OpenBSD: pf.conf,v 1.21 2003/09/02 20:38:44 david Exp $
> >#
> ># See pf.conf(5) and /usr/share/pf for syntax and examples.
> ># Required order: options, normalization, queueing, translation,
> >filtering. # Macros and tables may be defined and used anywhere.
> ># Note that translation rules are first match while filter rules are
> > last match.
> >
> ># Macros: define common values, so they can be referenced and changed
> >
> >
> >>>>easily. SYN_ONLY="S/FSRA"
> >>>>ext_if="xl0" # replace with actual external interface name i.e., dc0
> >>>>int_if="xl1" # replace with actual internal interface name i.e., dc1
> >>>>internal_net="192.168.1.1/16"
> >>>>#external_addr="192.168.1.1"
> >>>>
> >>>># Tables: similar to macros, but more flexible for many addresses.
> >>>>#table <foo> { 10.0.0.0/8, !10.1.0.0/16, 192.168.0.0/24,
> >>>>
> >>>>
> >192.168.1.18 }
> >
> >
> >>>># Options: tune the behavior of pf, default values are given.
> >>>>set timeout { interval 10, frag 30 }
> >>>>set timeout { tcp.first 120, tcp.opening 30, tcp.established 86400 }
> >>>>set timeout { tcp.closing 900, tcp.finwait 45, tcp.closed 90 }
> >>>>set timeout { udp.first 60, udp.single 30, udp.multiple 60 }
> >>>>set timeout { icmp.first 20, icmp.error 10 }
> >>>>set timeout { other.first 60, other.single 30, other.multiple 60 }
> >>>>set timeout { adaptive.start 0, adaptive.end 0 }
> >>>>set limit { states 10000, frags 5000 }
> >>>>set loginterface $ext_if
> >>>>set optimization normal
> >>>>set block-policy drop
> >>>>set require-order yes
> >>>>set fingerprints "/etc/pf.os"
> >>>>
> >>>># Normalization: reassemble fragments and resolve or reduce traffic
> >>>>ambiguities.
> >>>>scrub in all
> >>>>
> >>>># Queueing: rule-based bandwidth control.
> >>>>#altq on $ext_if bandwidth 2Mb cbq queue { dflt, developers, marketing
> >>>>} #queue dflt bandwidth 5% cbq(default)
> >>>>#queue developers bandwidth 80%
> >>>>#queue marketing bandwidth 15%
> >>>>
> >>>># Translation: specify how addresses are to be mapped or redirected.
> >>>># nat: packets going out through $ext_if with source address
> >>>>$internal_net will
> >>>># get translated as coming from the address of $ext_if, a state is
> >>>>created for # such packets, and incoming packets will be redirected to
> >>>>the internal address.
> >>>>nat on $ext_if from $internal_net to any -> ($ext_if)
> >>>>
> >>>>
> >>>># rdr: packets coming in on $ext_if with destination
> >>>>$external_addr:1234 will # be redirected to 10.1.1.1:5678. A state is
> >>>>created for such packets, and # outgoing packets will be translated as
> >>>>coming from the external address. #rdr on $ext_if proto tcp from any
> >>>>
> >>>>
> >to
> >
> >
> >>>>$external_addr/32 port 1234 -> 10.1.1.1 port 5678
> >>>>rdr on $ext_if proto { tcp, udp } from any to 68.231.121.45/32 port
> >>>>27000:27040
> >>>>-> 192.168.1.23 port 27000:27040
> >>>>
> >>>>
> >
> >
> >
> >>Yes, try not to specify an IP in the command line and see if you can get
> >>through.  I got this a few times if I specified a wrong ip that was
> >>essentially a typo when I started it.
> >>----- Original Message -----
> >>From: "Scott Ahlbrandt" <[EMAIL PROTECTED]>
> >>To: <[email protected]>
> >>Sent: Monday, January 03, 2005 8:09 PM
> >>Subject: [hlds_linux] WARNING: UDP_OpenSocket: port: 27015 bind: Cannot
> >>assign requested
> >>
> >>
> >>
> >>>address FATAL ERROR (shutting down): Couldn't allocate dedicated
> >>> server IP port 27015.
> >>>Date: Mon, 3 Jan 2005 11:10:56 -0700
> >>>User-Agent: KMail/1.6.2
> >>>MIME-Version: 1.0
> >>>Content-Disposition: inline
> >>>Content-Type: text/plain;
> >>>  charset="us-ascii"
> >>>Content-Transfer-Encoding: 7bit
> >>>Message-Id: <[EMAIL PROTECTED]>
> >>>
> >>>Has anyone come across this when trying to get your server to show up
on
> >>>
> >>>
> >>the
> >>
> >>
> >>
> >>>master list.?
> >>>
> >>>_______________________________________________
> >>>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
> >
> >
> >_______________________________________________
> >To unsubscribe, edit your list preferences, or view the list archives,
please visit:
> >http://list.valvesoftware.com/mailman/listinfo/hlds_linux
> >
> >
> I had the same issue on my Windowz box. I'm behind a firewall, used to
> specify IP and all ran fine. After one of the recent updates in
> December, I could no longer use the "+ip" switch. The exact same error
> you mentioned appeared.
>
> Simply removing that command switch cleared up the problem...but I now
> have a new issue: my internal machine (also behind the same firewall)
> cannot connect to my own server. All external clients connect perfectly.
> Steam resolves the IP of the server (seen as our external address) when
> starting the game service and posts it in the server list. If you
> "status" on your console, you'll see the local IP. The problem is that
> Steam sees both the game session of my server and my client's attempt to
> play at the same IP and refuses the connection. Valve's suggestion was
> to specify my server's local IP in my favorites and connect that way. No
> good.The final suggestion involved funky routing that shouldn't be
> necessary and would be disruptive to other "real" business applications
> running here. So, now I can't play on my own server from the
> office...but the server posts perfectly on the server list. *sigh*
>
> If your server is remotely hosted, you'll be fine. If not, then be
> prepared to have local client connection issues.
>
> Kerry
>
> _______________________________________________
> 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

Reply via email to