/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! /* ALSO: Don't quote this header. It makes you look lame :-) */
The reason is found. it should be ipchains -A input instead of INPUT, :-) BTW, am I right that IP-masq can NOT deal with traffic originning from the same machine where IP-masq is running? Why not? Ronghua On Thu, 7 Nov 2002, Fuzzy Fox wrote: > Ronghua Zhang <[EMAIL PROTECTED]> wrote: > > > > ipchains: No target by that name (Maybe this kernel doesn't support > > transparent proxying?) > > That seems to indicate that you don't have the option in your kernel. > > > but I did enable the IP_TRANSPARENT_PROXY option when I compiled the > > kernel. The following is part of the options used to compile the kernel. > > Not to sound silly, but are you sure that the kernel you booted from is > the one you built? Your copied the kernel to /boot, and ran lilo to > point it to the new kernel? It's easy to make that mistake. > > That's all I can think of at the moment. I don't think there is a /proc > entry that you can examine to see if this option was built into your > running kernel. > > _______________________________________________ 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.
