/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! /* ALSO: Don't quote this header. It makes you look lame :-) */
Ronghua Zhang <[EMAIL PROTECTED]> wrote: > > The reason is found. it should be ipchains -A input instead of INPUT, :-) Sorry, it's been a while on ipchains for me.. :) > BTW, am I right that IP-masq can NOT deal with traffic originning from > the same machine where IP-masq is running? Why not? I guess it depends on what you mean by "deal with." That is, what would the masq machine need to do to its own traffic that it originates? There is no need for the traffic to be masqueraded, because the real IP address really *does* belong to the machine, so it can use it directly. If you mean, can the traffic be filtered with input and output rules? Of course it can. And you should definitely do so. -- [EMAIL PROTECTED] (Fuzzy Fox) || "Good judgment comes from experience. sometimes known as David DeSimone || Experience comes from bad judgment." _______________________________________________ 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.
