-steamport xxxxx (At least I believe this is what it was.)
-- Cc2iscooL Head Admin/Owner http://www.cc2iscool.com On Sat, Jul 11, 2009 at 8:21 AM, Shane Arnold <[email protected]>wrote: > Yeah well, my dad's sister's aunty's uncle can cook a mean bacon > omelette... > > _______________________________________________________ > > Shane Arnold - [email protected] > > "For want of a nail, the horseshoe was lost. For want of a horseshoe, the > horse was lost. For want of a horse, the messenger was lost. For want of a > messenger, the message was not delivered. For want of an undelivered message > the war was lost." > > > > Mike Zimmermann wrote: > > My dad can beat up both of your dads. > > > > -Mike > > > > > > On Fri, Jul 10, 2009 at 8:50 AM, Shane Arnold <[email protected] > >wrote: > > > > > >> So because someone has only set up 1 or 2 servers, they would know > >> nothing about basic routing for a supposed 500+ servers? > >> > >> I'd hate to break it to you friend but you aren't the only person out > >> there that can divide subnets and filter bogons... > >> > >> And yes I could of helped with the problem if you stated it first off, > >> but seeing as you are being so unhelpful I might just keep that > >> knowledge to myself. > >> > >> _______________________________________________________ > >> > >> Shane Arnold - [email protected] > >> > >> "For want of a nail, the horseshoe was lost. For want of a horseshoe, > the > >> horse was lost. For want of a horse, the messenger was lost. For want of > a > >> messenger, the message was not delivered. For want of an undelivered > message > >> the war was lost." > >> > >> > >> > >> Thomas Hjorth wrote: > >> > >>> And it helps you how? Im asking for a cmdline option, not workaround > >>> based on knowledge of a small 1-2 servers setup. > >>> > >>> Although, if someone have a good workaround for all the problems with > >>> steam software I would be happy to hear about it. > >>> > >>> Regards Thomas @ DSRack.com > >>> > >>> On Fri, 2009-07-10 at 19:38 +0800, Shane Arnold wrote: > >>> > >>> > >>>> If you had of told us this in your original email, we probably could > of > >>>> helped you better... > >>>> > >>>> Regards, > >>>> > >>>> _______________________________________________________ > >>>> > >>>> Shane Arnold - [email protected] > >>>> > >>>> "For want of a nail, the horseshoe was lost. For want of a horseshoe, > >>>> > >> the horse was lost. For want of a horse, the messenger was lost. For > want of > >> a messenger, the message was not delivered. For want of an undelivered > >> message the war was lost." > >> > >>>> > >>>> Thomas Hjorth wrote: > >>>> > >>>> > >>>>> I dont use iptables in this setup. I know plenty about TCP/IP which > >>>>> > >> isnt > >> > >>>>> the issue either. > >>>>> > >>>>> I wanna know the port, so I can make sure I NAT the same external IP > to > >>>>> just the masterservers, but not VAC servers. Since I cant just > get/find > >>>>> a list of the different IPs and target them like that, the next > option > >>>>> is to use the source port as base for my filtering. > >>>>> > >>>>> Regards Thomas @ DSRack.com > >>>>> > >>>>> > >>>>> On Fri, 2009-07-10 at 17:29 +0800, Will Dowling wrote: > >>>>> > >>>>> > >>>>> > >>>>>> To the best of my knowledge, when opening a socket to a remote > >>>>>> > >> service, > >> > >>>>>> your SOURCE port IS randomised. This is done to prevent a number of > >>>>>> attacks at the TCP level. > >>>>>> > >>>>>> Is your issue with iptables? If so, the problem isn't with the > >>>>>> application - you should be able to filter by the destination port. > If > >>>>>> you're worried about the return traffic, you should either do a > source > >>>>>> port check for the remote host, or use the iptables conntrack helper > >>>>>> module for ESTABLISHED connections. > >>>>>> > >>>>>> Again, some context as to what you're trying to acheieve by setting > >>>>>> > >> the > >> > >>>>>> source port would probably help get the right answer. > >>>>>> > >>>>>> Hope this helps. > >>>>>> > >>>>>> > >>>>>> Will Dowling > >>>>>> > >>>>>> T: +61 (0407) 421 559 > >>>>>> F: +61 (08) 6364 4881 > >>>>>> E: [email protected] > >>>>>> > >>>>>> > >>>>>> _______________________________________________ > >>>>>> 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 > >>> > >>> > >>> > >>> > >> _______________________________________________ > >> 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
