My bad,
Thanks Gary.
-W Wade Blackwell "Integrity is often more painful and always more profitable than perception management" -----Original Message----- From: Gary Buckmaster [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 29, 2008 2:24 PM To: support@pfsense.com Subject: Re: [pfSense Support] Re: PPTP & Ipsec Please don't do that. If someone has a response, they'll respond when they're able. Keep in mind that this is a free resource, and that help is on a voluntary basis. If this doesn't fit within the threshold you have for a solution, then please consider other options. Spamming the mailing list isn't the way. Wade Blackwell wrote: > Anyone....Bueler....Bueler....? > > -W > > On Tue, 2008-04-29 at 06:41 -0700, Wade Blackwell wrote: > >> Good morning PFsense fans, >> Greetings from the starting to get sunny Northwest. I am not sure if >> what I am trying can be done or not. In concept I know it's possible >> but I am not seeing the desired results where the rubber meets the road. >> Basic setup is this; >> >> Network A >> 1.1.1.1/24 >> | >> | >> | >> I-net----PF---PPTP clients 3.3.3.3/28 >> | >> | >> | >> IPsec tunnel to 2.2.2.0/24 >> >> Goal: To have PPTP clients connect in and connect to the PF and then >> have access to 2.2.2.0/24 over the IPsec tunnel. The tricky part (I >> am >> assuming) is that for the tunnel to come up the PPTP clients to bring >> the IPsec tunnel up they need to be sourced from 1.1.1.0/24. What I >> did, attempting to make this work, was to setup the advanced outbound >> NAT allowing all PPTP clients destined for 2.2.2.0/24 to be natted >> with the interface IP of network A. I am running 1.2-RC2 if that has any bearing. >> If anyone has tried this or has some insight I would be stoked. >> Thanks all. >> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
smime.p7s
Description: S/MIME cryptographic signature
