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
