[pfSense Support] Latest 2.0 Beta4 snapshot update broke new IPSEC configuration

2010-12-11 Thread Mark Street
Hi, I just updated 2.0 Beta4 tonight with the latest snapshot and something broke IPSEC configuration. When clicking on a new IPSEC tunnel the following error appears. Parse error: syntax error, unexpected '=' in /usr/local/www/vpn_ipsec_phase1.php on line 515 -- Mark Street, D.C., RHCE

Re: [pfSense Support] RE: Openvpn routing config help

2010-12-11 Thread Chris Buechler
On Sat, Dec 11, 2010 at 11:32 AM, Joseph L. Casale wrote: >>Make sure you follow all the steps here (order doesn't matter if you've >>already done some/most) >>http://doc.pfsense.org/index.php/OpenVPN_Traffic_Filtering_on_1.2.3 > > All done, and double checked. I actually use this for a standard

Re: HA: Re: [pfSense Support] 2.0 - don't work Ipsec!

2010-12-11 Thread st41ker
Sure it can. Only government and business enterprises have to follow this "rules". For more information you should contact a lawyer. I'm sorry for off-topic here. 11.12.2010 19:04, Evgeny Yurchenko пишет: On 10-12-11 06:46 AM, st41...@st41ker.net wrote: Hi, JFYI: you must use only those cryp

Re: HA: Re: [pfSense Support] 2.0 - don't work Ipsec!

2010-12-11 Thread Evgeny Yurchenko
On 10-12-11 06:28 AM, drova...@kaluga-gov.ru wrote: Hi, pfsense not send and recived ipsec message to remote gateway! [snip] Just do tcpdump on WAN and see whether you receive anything from remote site on port 500. - To uns

Re: HA: Re: [pfSense Support] 2.0 - don't work Ipsec!

2010-12-11 Thread Evgeny Yurchenko
On 10-12-11 06:46 AM, st41...@st41ker.net wrote: Hi, JFYI: you must use only those cryptographic services\alrorithms which has been sertified by "ФСБ" and\or "ФСТЭК" (I'm not sure how it sounds in English). It seems like blowfish is under question in your case. Hi, just curious, can private com

RE: [pfSense Support] RE: Openvpn routing config help

2010-12-11 Thread Joseph L. Casale
>Make sure you follow all the steps here (order doesn't matter if you've >already done some/most) >http://doc.pfsense.org/index.php/OpenVPN_Traffic_Filtering_on_1.2.3 All done, and double checked. I actually use this for a standard road warrior setup for my first openvpn config running on 1194,

Re: HA: Re: [pfSense Support] 2.0 - don't work Ipsec!

2010-12-11 Thread st41ker
Hi, JFYI: you must use only those cryptographic services\alrorithms which has been sertified by "ФСБ" and\or "ФСТЭК" (I'm not sure how it sounds in English). It seems like blowfish is under question in your case. On Sat, 11 Dec 2010 14:28:26 +0300, drova...@kaluga-gov.ru wrote: > Hi, pfsense not

Re: HA: Re: [pfSense Support] 2.0 - don't work Ipsec!

2010-12-11 Thread James Bensley
The IPSec site-to-site link I have in place between two sites runs over ADSL which I get from two different providers, one at each end. One of them (BT) is blocking traffic on UDP port 500 and 4500. I suspect the technical reasoning for this is because they are twats...None the less, I have to use

HA: Re: [pfSense Support] 2.0 - don't work Ipsec!

2010-12-11 Thread drovalev
Hi, pfsense not send and recived ipsec message to remote gateway! Network topology: 192.168.8.0/24(LAN)-Pfsense 2.0 -(WAN)192.168.180.1192.168.180.13(WAN)-monowall -(LAN)172.20.34.0/24 1.) If inicial coonections from remote net to local net (172.20.34.0/24 -> 192.168.8.0

Re: [pfSense Support] CARP support broken in kernel?

2010-12-11 Thread st41ker
Hello, Understood. The requested changes has been made and the result is the same. Please, clarify, what exactly statistics do you need? Here is complete output of netstat -ss #uptime; netstat -ss 12:28PM up 33 mins, 2 users, load averages: 0.23, 0.23, 0.11 tcp: 14643 packets sent

Re: [pfSense Support] RE: Openvpn routing config help

2010-12-11 Thread Chris Buechler
On Sat, Dec 11, 2010 at 1:52 AM, Joseph L. Casale wrote: >>What has to be done to let LAN clients access resources across the tunnel now >>from the pfsense side of the config? > > Found http://forum.pfsense.org/index.php/topic,12888.0.html which worked well. > I didn't use client-to-client and di