/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! */
>ipchains -A input -p tcp -m 1 --sport 1024: -d xxx.xxx.xxx.3 http -j ACCEPT
>ipchains -A input -p tcp -m 2 --sport 1024: -d xxx.xxx.xxx.4 ssh -j ACCEPT
>ipmasqadm mfw -I -m 1 -r yyy.yyy.yyy.3
>ipmasqadm mfw -I -m 2 -r yyy.yyy.yyy.4
Curious, why did you go the packet label (mfw) route? Personally, I
think its an elegant way to do things but I've stuck with PORTFW.
>Everything works perfectly (except incoming passive FTP).
There is a ALPHA ip_masq_ftp module that might fix this issue for you
though I haven't heard a whole lot of infomation back from the
testers.
>Paying close attention to my IPchains accounting shows that the outbound
traffic
>going from yyy.yyy.yyy.4 _ISN'T EVEN HITTING THE FORWARD CHAIN_. _Everything_
>from the Linux box is masq'ed, not just the specific services I indicated (via
>fascist masqing), and the packet/byte counters from ipchains -L -v -n do not
>show corresponding activity.
Try doing the forwarding to a NON-Aliased IP address. This might fix it.
As it stands, MASQ does not always play well with ALIASed IPs. Just try
it and let us know.
PS. What do you think of the IPROUTE2 package? Difficult to figure out?
Good/Bad documentation, etc?
--David
.----------------------------------------------------------------------------.
| David A. Ranch - Linux/Networking/PC hardware [EMAIL PROTECTED] |
!---- ----!
`----- For more detailed info, see http://www.ecst.csuchico.edu/~dranch -----'
_______________________________________________
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.
