| To: | "'Claus Grill'" <c.grill,AT,ecka-granules,DOT,com> |
| Subject: | RE: Routing between VPN subnets |
| From: | "Mark" <msalists,AT,gmx,DOT,net> |
| Date: | Wed, 8 Dec 2004 09:39:38 -0800 |
| Cc: | <cipe-l,AT,inka,DOT,de> |
| Importance: | Normal |
| In-reply-to: | <200412080900.34656.c.grill@ecka-granules.com> |
Yeah, I guess either that or configuring the routing on each node separately rather than just in the router. That would be ok too as long as everything is batch-configured automatically using cfengine or other tools, so I don't have to change each node manually in case changes are needed in the future... Thanks, MARK > -----Original Message----- > From: owner-cipe-l,AT,inka,DOT,de [mailto:owner-cipe-l,AT,inka,DOT,de On > Behalf Of Claus Grill > Sent: Wednesday, December 08, 2004 12:01 AM > To: cipe-l,AT,inka,DOT,de > Subject: Re: Routing between VPN subnets > > > Hi, > > > * > > What do I have to do to fix this problem? I figured it > would be easiest to > > just have the origin node use its VPN address as origin > address rather than > > its official address - the question is how do I do that? I > tried changing > > the subnet mask of location A to /16 rather than /24, but > that didn't > > change anything. > > * > > Maybe SNAT to the desired IP on both ends solves your > Problem. That way the > one side won't get to see the real official IP of the other. > > Greetings, > > Claus > > -- > Message sent by the cipe-l,AT,inka,DOT,de mailing list. > Unsubscribe: mail majordomo,AT,inka,DOT,de, "unsubscribe cipe-l" in body > Other commands available with "help" in body to the same address. > CIPE info and list archive: > <URL:http://sites.inka.de/~bigred/devel/cipe.html> >