Workaround (RE: TCP connection via IPsec machine also running natd)

2002-01-07 Thread Cambria, Mike
I'm able to workaround the problem posted earlier by doing the following: Since the machine which "eats" the received esp packets after natd is a router for the subnet making natd necessary, I'm able to connect to this machine by establishing sessions to any of the IP addresses on the other side

Re: TCP connection via IPsec machine also running natd

2002-01-04 Thread Rogier R. Mulhuijzen
>As I said earlier, packets which route through ipfw/natd get unencrypted and >make it to the remote subnet just fine. > >Looking at 'ipfw -a l' it seems that the ESP packets are being received >_after_ being diverted to natd, but just >not sent to the socket: I'm no IPsec expert (still some