unless you are using pfSense to connect to another openVPN server you do not need to fill out the client tab.
On my pfSense box I has to add the following in the extra options box at the bottom of the server config tab: local xxx.xxx.xxx.xxx; to tell it what ip address to listen on. I made that the lan ip address and then created a rule on the wan tab that allowed the traffic through to the LAN interface. But I am on a network that uses all public ip so I could do that. In your case you will want to make it the WAN address. On Mon, Jun 23, 2008 at 7:54 AM, <[EMAIL PROTECTED]> wrote: >>> # openvpn --dev tun0 --mktun >>> # openvpn --remote <IP address> --dev tun0 --pkcs12 >>> <my cert + key + >> CA cert>.p12 --client --comp-lzo --tun-mtu 1500 >> >> >> your not putting this in the extra config section at the bottom of the >> OpenVPN config page are you?? > > no, this is at the command-line on the VPN client computer. > >> can you send a screen shot of the config page with pertinent info that >> doesn't need to be shared with the works blanked out. > > I've put screenshots at http://thegoldenear.org/pfsense-openvpn-config.html > > The only change in those screenshots to my usual configuration is Server > -> Local network being blank, as per Paul Mansfield's suggestion. > > (To my untutored eye Client -> Remote network looks like as though it > suggests it would cure my problem but it's greyed out). > > I've entered no Client-specific configuration. > > Pete Boyd > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Frank Lloyd Wright - "TV is chewing gum for the eyes." --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
