Messages in this thread | | | Subject | NAT + IPsec in 2.6.0-test2 | From | Tom Sightler <> | Date | 12 Aug 2003 00:35:06 -0400 |
| |
OK, I finally got racoon to work and have IPsec working great with a 2.6.0-test2-mm1 kernel on my home Internet gateway system. However, I've hit another issue. In my previous setup with the 2.4.20 kernel and SuperFreeS/WAN it looked like this
10.0.0.0/8--205.242.242.161<-IPsec->66.3.2.1--{10.250.1.129/32}--192.168.1.0/24
Basically the IPsec tunnel had only a single IP address on the remote end then any packets from the home internal network (192.168.1.0) were SNAT to the 10.250.1.129 before being sent via the tunnel. This hid my home network behind a valid IP at my work network and worked flawlessly with 2.4 and SuperFreeS/WAN.
I've got the identical setup with kernel 2.6 and racoon. I get the tunnel up and everything works great from the gateway system, but none of the systems on my home network can access the systems on the work network. It seems that packets passing via IPsec are bypassing the NAT rules, although that's mostly just a guess at this point.
Is there anything written that describes how the kernels IPsec implementations interacts with iptables? I've searched the linux-kernel archives and Google but turned up empty (although I found the question asked one time before). Any help would be greatly appreciated.
Later, Tom
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |