On 8/11/05, Scott Ullrich <[EMAIL PROTECTED]> wrote:
>
> I spoke too soon. OpenVPN is not the problem itself, its the GUI +
> Backend PHP code in pfSense.
>
Right, the author he was speaking of that hasn't sent patches is the
author of the GUI and backend PHP code in m0n0wall, not the author of
On 8/11/05, Scott Ullrich <[EMAIL PROTECTED]> wrote:
> On 8/11/05, James Yonan <[EMAIL PROTECTED]> wrote:
> > Scott,
> >
> > We're planning on releasing 2.0.1 next week, most likely. When are you
> > planning on freezing?
>
> Sometime next week, so this is perfect timing.
>
> > I'm on vacation r
On 8/11/05, James Yonan <[EMAIL PROTECTED]> wrote:
> Scott,
>
> We're planning on releasing 2.0.1 next week, most likely. When are you
> planning on freezing?
Sometime next week, so this is perfect timing.
> I'm on vacation right now, so I didn't have a chance to go back and read
> the origina
On Thu, 11 Aug 2005, Scott Ullrich wrote:
> On 8/11/05, James Yonan <[EMAIL PROTECTED]> wrote:
> > I'm the author of OpenVPN.
>
> Great!
>
> > Please give me more info on this and/or any patches you might have so we
> > can fix this.
> >
> > For example, you say that "I blew up a firewall in
On 8/11/05, James Yonan <[EMAIL PROTECTED]> wrote:
> I'm the author of OpenVPN.
Great!
> Please give me more info on this and/or any patches you might have so we
> can fix this.
>
> For example, you say that "I blew up a firewall in 2 minutes flat" -- but
> what do you mean by this? What did
>The author is very aware of us wanting an updated version but I have
>not heard back from him. The reason that we removed openvpn from
>pfSense is due to its nature of trashing optional interfaces
>configurations. I blew up a firewall in 2 minutes flat by just
>enabling the service and rebooti
The author is very aware of us wanting an updated version but I have
not heard back from him. The reason that we removed openvpn from
pfSense is due to its nature of trashing optional interfaces
configurations. I blew up a firewall in 2 minutes flat by just
enabling the service and rebooting.
I think it was more along the lines of "it didn't work and we had too
many other things to fix"
--Bill
On 8/11/05, Rui Correia <[EMAIL PROTECTED]> wrote:
> Fernando Costa gmail.com> writes:
>
> >
> > Hello all,
> >
> >I may say we have made a mistake over here. That is probably my
> > fault
Fernando Costa gmail.com> writes:
>
> Hello all,
>
>I may say we have made a mistake over here. That is probably my
> fault. I´m not sure about pfSense, but I thought m0n0 used to be based
> on OpenVPN 1.6, and its not. Here it goes:
>
> Aug 11 09:41:50 openvpn[833]: OpenVPN 2.0 i386
Hello all,
I may say we have made a mistake over here. That is probably my
fault. I´m not sure about pfSense, but I thought m0n0 used to be based
on OpenVPN 1.6, and its not. Here it goes:
Aug 11 09:41:50 openvpn[833]: OpenVPN 2.0 i386-unknown-freebsd4.11
[SSL] built on May 8 2005
M0n
Scott Ullrich gmail.com> writes:
>
> We are waiting for the author to release newer patches but am not sure
> of the timeframe.
Hi Scott,
Thanks for clarifying this issue.
Anyway, the lack of OpenVPN2 support is what is currently keeping me from using
pfSense on a general basis on our customers
11 matches
Mail list logo
