/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! */ I've just spent some time examining the masqing code. Does anyone know why the above restriction exists? As far as I can tell there should rarely be a case a packet matching both and if it does, what's the harm in replacing both the sender and receiver? Removing this restriction would also solve some problems that have been brought up here. For example, you wouldn't need something like Rolf Braun's 2-dir port forwarding patch since mfw or portfw would be enough. Also this should solve problems with online games that send UDP among all players. Currently, for example, two players behind the same masq box have problems joining the same battle.net game. I'd imagine that this problem would go away if the above restriction was removed. So please help me to understand why thing are this way. -- Michael Best _______________________________________________ Masq maillist - [EMAIL PROTECTED] Admin requests can be handled at http://www.indyramp.com/masq-list/ -- THIS INCLUDES UNSUBSCRIBING! or email to [EMAIL PROTECTED] PLEASE read the HOWTO and search the archives before posting. You can start your search at http://www.indyramp.com/masq/ Please keep general linux/unix/pc/internet questions off the list.
