[pfSense-discussion] Problem with ipsec

2006-08-09 Thread Carlos Julio Sánchez [ACC-SIS]
Hello! anybody can help me please? I have an error when I set up vpn with ipsec, my computer A have pfsense and my computer B have Centos(Linux) In the ipsec logs I have: racoon: ERROR: failed to get sainfo. racoon: ERROR: failed to get sainfo. racoon: ERROR: failed to

Re: [pfSense-discussion] Problem with ipsec

2006-08-09 Thread Scott Ullrich
On 8/9/06, Carlos Julio Sánchez [ACC-SIS] [EMAIL PROTECTED] wrote: Hello! anybody can help me please? I have an error when I set up vpn with ipsec, my computer A have pfsense and my computer B have Centos(Linux) In the ipsec logs I have: racoon: ERROR: failed to get sainfo. racoon:

RE: [pfSense-discussion] Problem with ipsec

2006-08-09 Thread Carlos Julio Sánchez [ACC-SIS]
If i dont have remote subnet but in the pfsense i must to write something in the textbox REMOTE SUBNET in the configuration of ipsec vpn. What I have to write in? -Original Message- From: Scott Ullrich [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 09, 2006 4:31 PM To:

Re: [pfSense-discussion] Problem with ipsec

2006-08-09 Thread Chris Buechler
Carlos Julio Sánchez [ACC-SIS] wrote: If i dont have remote subnet but in the pfsense i must to write something in the textbox REMOTE SUBNET in the configuration of ipsec vpn. If you're doing a site to site VPN, you *have* to have a remote subnet. It's the network on the other end that

RE: [pfSense-discussion] Problem with ipsec

2006-08-09 Thread Holger Bauer
It's the remote LAN that you want to reach through the tunnel at the other end. HOlger -Original Message- From: Carlos Julio Sánchez [ACC-SIS] [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 09, 2006 11:57 PM To: discussion@pfsense.com Subject: RE: [pfSense-discussion] Problem

RE: [pfSense-discussion] Problem with ipsec

2006-08-09 Thread Carlos Julio Sánchez [ACC-SIS]
actibts1 racoon: ERROR: xxx.xxx.xxx.xxx give up to get IPsec-SA due to time up to wait. Double check your phase 2 settings on both hosts. There is a mismatch somewhere. Scott __ NOD32 1.1699 (20060809) Information __ This message was checked by NOD32 antivirus system