[pfSense Support] pfSense 2.0 IPsec on Mac OS X 10.6

2011-04-11 Thread Paul Mather
I believe my previous message on this topic (http://www.mail-archive.com/support@pfsense.com/msg21912.html) may have been a victim of tl;dr. So, in hope of better success, I will restate my problem in a more positive light: Has anyone managed to get IPsec for mobile clients working with

Re: [pfSense Support] pfSense 2.0 IPsec on Mac OS X 10.6

2011-04-11 Thread Mike McLaughlin
I'm very happily using OpenVPN with Viscosity and TunnelBlick (clients) on many Mac 10.5-10.7 machines. I'm currently using 1.2.3 at the perimeter and a 2.0 box to manage my certs (which I hope to roll over to the perimeter box once we upgrade for the sake of being able to download the pre-loaded

[pfSense Support] Windows FTP issues

2011-04-11 Thread Jason Lixfeld
The FTP client built into my Mac is able to connect to ftp servers that live behind a pfSense 1.2.3 box no problem, but the built-in FTP client on my Windows XP SP3 box able to do directory listings on the same servers no matter if PASV or EPSV is set on the client before making the directory

Re: [pfSense Support] pfSense 2.0 IPsec on Mac OS X 10.6

2011-04-11 Thread Vick Khera
On Mon, Apr 11, 2011 at 11:19 AM, Paul Mather p...@gromit.dlib.vt.eduwrote: Has anyone managed to get IPsec for mobile clients working with pfSense 2.0 and Mac OS X 10.6? If so, which client are you using on the Mac OS X side? Is anything special needed on the pfSense side? I *used* to use

Re: [pfSense Support] pfSense 2.0 IPsec on Mac OS X 10.6

2011-04-11 Thread bsd
Install the open VPN client package on 2.0 - two clicks and you're done ! Viscosity is your best bet. So straightforward, your grandma could do It. ;-) Le 11 avr. 2011 à 18:19, Vick Khera a écrit : On Mon, Apr 11, 2011 at 11:19 AM, Paul Mather p...@gromit.dlib.vt.edu wrote: Has anyone

Re: [pfSense Support] pfSense 2.0 IPsec on Mac OS X 10.6

2011-04-11 Thread Paul Mather
On Apr 11, 2011, at 12:19 PM, Vick Khera wrote: On Mon, Apr 11, 2011 at 11:19 AM, Paul Mather p...@gromit.dlib.vt.edu wrote: Has anyone managed to get IPsec for mobile clients working with pfSense 2.0 and Mac OS X 10.6? If so, which client are you using on the Mac OS X side? Is anything

[pfSense Support] Incorrect Sort on 2.0-RC1

2011-04-11 Thread Dimitri Rodis
2.0-RC1 (i386) built on Mon Mar 14 17:33:11 EDT 2011 Log sorting is set to newest first, however, the log sort is randomly incorrect (see screen snippet). I didn't see anything in redmine, thought I would check here first.. [cid:image001.png@01CBF837.8BDBAAF0] Dimitri Rodis Integrita Systems

Re: [pfSense Support] pfSense 2.0 IPsec on Mac OS X 10.6

2011-04-11 Thread RB
I'm actually pretty interested in the fact that on the surface it looks like 2.0 can support the OS X 10.6 native Cisco VPN client out of the box. Has anyone had any success doing so? OpenVPN and Viscosity/Tunnelblick are nice, but not having to pay $9/client and not installing additional

Re: [pfSense Support] Incorrect Sort on 2.0-RC1

2011-04-11 Thread Jim Pingle
On 4/11/2011 1:59 PM, Dimitri Rodis wrote: *2.0-RC1 *(i386) built on Mon Mar 14 17:33:11 EDT 2011 Log sorting is set to newest first, however, the log sort is “randomly incorrect” (see screen snippet). I didn’t see anything in redmine, thought I would check here first.. The log isn't

[pfSense Support] WAN DHCP does not pull DNS server info on 2.0-RC1 build Apr 8 2011?

2011-04-11 Thread Josh Karli
Hello all I updated to the Friday April 8 2011 build via auto update. My WAN is connected to my internet modem and is configured by DHCP, and I am not part of a domain. After the update DNS name resolution did not work for internet addresses, and this was verified using the DiagnosticsDNS

Re: [pfSense Support] WAN DHCP does not pull DNS server info on 2.0-RC1 build Apr 8 2011?

2011-04-11 Thread Chris Buechler
On Mon, Apr 11, 2011 at 6:11 PM, Josh Karli josh.ka...@gmail.com wrote: Hello all I updated to the Friday April 8 2011 build via auto update. My WAN is connected to my internet modem and is configured by DHCP, and I am not part of a domain. After the update DNS name resolution did not work