/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! */



>M2 sends a packet M2:6112 -> EXT:61001. This packet hits the fw and is
>demasq'd to M2:6112 -> M1:6112. This is *bad*. I really want this packet to
>be EXT:61002 -> M1:6112.

You might be able to setup an EXPLICT forward rule WITHOUT the MASQ
attribute to fix this.  Your gonna have to play with this for a 
while though to see if it will work.


>I was able to get the thing to work by hacking ip_forward.c. For the above
>case I set fw_res = FW_MASQUERADE & skipped the check for IPSKB_MASQUERADED
>around line 225 (I don't have the original source). Things worked if I put
>the card in promiscuous mode.

Which card?  The internal one?  I would definately recommend AGAINST using
promiscuous modem though you did do your homework here.  Good job!


>Anyone have any documentation for the masq stuff in the kernel? There are a
>few comments here and there, but any additional help would be appreciated.

I'm not qualified to really help you here but you should re-post this
to the masq-dev list.  People there can help you better with the code.

--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/
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.

Reply via email to