Playing arround with NAT, advanced outbound NAT, Virtual IPs and Rules.
I'm trying to open FTP and SMTP port in my firewall and redirect to my
internal server and still won't work.
Outgoing Connection to single WAN is working, but Incoming Connection is
zero.
It seems more easy with iptables
First of all, maybe youy should try pfsense beta2
2006/3/3, Agi Subagio [EMAIL PROTECTED]:
Playing arround with NAT, advanced outbound NAT, Virtual IPs and Rules.I'm trying to open FTP and SMTP port in my firewall and redirect to my
internal server and still won't work.
You can check the Faq
After final release are there any thoughts about submitting PFSENSE
to ICSA Labs for certification testing?
Does Beta2 have fixed
mobile IPSEC problem that was related with ipsec-tools-0.6.5?
De: Tommaso Di
Donato [mailto:[EMAIL PROTECTED]
Enviada em: quinta-feira, 2 de
março de 2006 12:58
Para: support@pfsense.com
Assunto: Re: [pfSense Support]
Problem with ipsec tunnel
Yes it
pfSense Beta 2 was released to the mirrors last night, and is currently
available for download. Scott will be posting the change log and other
related information on the release on our blog some time today. He
tried last night, but blogger was down. Please watch
http://pfsense.blogspot.com
Alejandro Lengua wrote:
The problem would be, how much does ICSA Labs charge for their certification
and how the project could raise money to afford it.
$25K USD per year per certification. i.e. if you want a certified
firewall, and IPsec, then it's $50K. Add another $25K for each
Title: Configuration sync problem
Hello all.
I'm having a problem with the xmlrpc sync between two nodes. It just doesn't happen. On node 1, it gives an error on system log:
php: : An error code was received while attempting XMLRPC sync with http://10.10.10.2:80 - Code 104: XML error:
Mismatching passwords between the firewalls and or mismatched access
type (http/https).
On 3/3/06, Amorim, Nuno Alexandre (ext) [EMAIL PROTECTED] wrote:
Hello all.
I'm having a problem with the xmlrpc sync between two nodes. It just doesn't
happen. On node 1, it gives an error on system
Same passwords and both nodes in HTTP. Tried also with different passwords on
the nodes.
This happens in all versions I have tried (beta1, snapshot 2-19-06, snapshot
2-20-06 and now in beta2)
Right now I have node 1 with lots of rules and alias, and carp enabled. Node 2
is completely blank,
Generally when that error comes up its one of the two. I have syncing
enabled here at work and home, so I know it works...
On 3/3/06, Amorim, Nuno Alexandre (ext) [EMAIL PROTECTED] wrote:
Same passwords and both nodes in HTTP. Tried also with different passwords on
the nodes.
This happens
I'm not doubting that it works, because I've not found anything about this
error in the mailing list and in the forum.
What is code 104? And the line that it is refering to, is in what file?
I've noticed that when I change the password, the error line also changes.
-Original Message-
See http://cvstrac.pfsense.com/tktview?tn=831,6 for more information.
On 3/3/06, Amorim, Nuno Alexandre (ext) [EMAIL PROTECTED] wrote:
I'm not doubting that it works, because I've not found anything about this
error in the mailing list and in the forum.
What is code 104? And the line that it
Is this the correct place to report bugs in pfsense?
/Peter
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
It's a good start, yeah. We may ask you to file a ticket in cvstrac
if they are indeed real bugs :)
Scott
On 3/3/06, Peter Curran [EMAIL PROTECTED] wrote:
Is this the correct place to report bugs in pfsense?
/Peter
--
This message has been scanned for viruses and
dangerous content by
On Friday 03 March 2006 19:45, Scott Ullrich wrote:
It's a good start, yeah. We may ask you to file a ticket in cvstrac
if they are indeed real bugs :)
Thats OK - some of them seem to be listed in the changelog for BETA2, so I
will redo my testing of this afternoon once I have upgraded and
It may help to do a fresh install if you are getting php dynamic
loading errors, we have modified the defaults.
On 3/3/06, Peter Curran [EMAIL PROTECTED] wrote:
On Friday 03 March 2006 19:45, Scott Ullrich wrote:
It's a good start, yeah. We may ask you to file a ticket in cvstrac
if they
Thanks!!
On 3/3/06, Peter Curran [EMAIL PROTECTED] wrote:
Yes - I will install from scratch rather than upgrade.
I think that one of the bugs I got that was not listed in the BETA2 change
occurs if you assign a network range as a virtual ip. I will try and load
this into a new VM tonight
I dont see a release of 0.6.5
released yet on their webpage unless its recently available in
their cvs
Did you try checking the Prefer Old
SA option (whose value is reverse making it prefer new sas see
previous thread between me and bill) since checking this my tunnels have been
very
I looked through the change log but didnt see if the
reversal bug for the Prefer Old IPsec SA was corrected or its
default behavior changed in beta2?
Thanks
John
Same behaviour currently. I'll probably end up just changing the
wording of that option, not the behaviour as I'm not willing to break
peoples existing configs. This might get changed for a potential
Beta3 (I wouldn't be surprised if we have one as we have more work to
do on the shaper that
Okay no prob, just wanted to know which setting was going to be the one
that works for me.
John
-Original Message-
From: Bill Marquette [mailto:[EMAIL PROTECTED]
Sent: Friday, March 03, 2006 3:43 PM
To: support@pfsense.com
Subject: Re: [pfSense Support] Was the IPSec Prefer old SA bug
I'm just trying now: now I have prefer old SA checked, and I still have problems...SPD and SAD seem to be right, but still no traffic.. Any ideas?Here are my logs:Mar 3 22:13:50 racoon: ERROR: such policy does not already exist:
172.16.2.0/24[0] 10.0.0.0/24[0] proto=any dir=out Mar 3 22:13:50
22 matches
Mail list logo
