|
|||||||||||
|
Re: linux-ipsec: privately-numbered subnets behind linux-ipsec gateways
From: Henry Spencer <henry(at)spsystems.net>
Date: Mon Jan 25 1999 - 20:28:37 EST
Unfortunately true. The trouble is that it's *really* easy for people to misconfigure routing, etc., in such a way that they can't get packets from S to T at all... and then they blame IPSEC for it. Hence the very strong recommendation to debug the basic network setup first. > So the question arises: can the freeswan system handle this?
Yes, definitely. But debugging it is considerably harder than the case where the networking can be tested first, because there are so many more things that can go wrong on the first attempt. > I am telling
A subtle point: G and H should be able to talk to each other before the activation of IPSEC. That is, they should have routes for each other. Pluto doesn't set up its own routing until it is setting up connections, as I recall, and it can't do that if it can't talk to the other Pluto. (The existence of such routes is, of course, automatically guaranteed by good old step 1. More generally, even if you can't get packets from S to T before checking out IPSEC, you certainly should verify that you can get them from G to H.) >...Specifically, tcpdump doesn't see any IP packets at all coming
Careful here -- are you running tcpdump on G, or on a separate machine that's listening to the G-M wire? Unfortunately, it *can* make a difference. > Suggestion: It would be nice to have documentation and testing tools that
The docs definitely need attention in this area. I don't know how much we can do on the testing front, but we'll look at it. Thanks for pointing this out.
Henry Spencer
henry@spsystems.net
(henry@zoo.toronto.edu)
Received on Mon Jan 25 21:03:12 1999This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 12:59:29 EDT |
||||||||||
|
|||||||||||