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. It was not a pretty sight.
Scott On 8/11/05, Bill Marquette <[EMAIL PROTECTED]> wrote: > 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 <cusquinho <at> 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-unknown-freebsd4.11 > > > [SSL] built on May 8 2005 > > > > > > M0n0wall is based on openvpn 2.0 and it work just fine with my windows > > > 2.0 version of openvpn client. The main problem I was having is that > > > beta9 has a bug in the openvpn.inc which wont let you use TCP ports, I > > > had to create an alternative image. > > > > > > Not sure if its so simple, but I guess if pfSense copies openvpn incs > > > and ports image to its file, openvpn 2.0 will work just fine. Not sure > > > about kernel issues tho. > > > > > > Fernando Costa > > > > Hi Fernando, > > > > That's interesting as I thought m0n0 was using OVPN1.6 too. > > And I also didn't know that the bug in m0n0 1.2b9 was as a bad openvpn.inc. > > Nevertheless I was under the impression that OVPN was dropped on pfSense > > project > > because _it_caused_issues_with_other_packages_. > > Let's see if Scott or Chris can bring us up to speed on this one ;). > > > > Cheers > > > > >
