On Sun, Dec 5, 2010 at 2:02 AM, David Burgess wrote:
>
> But openconnect works, at least for me on Linux, and from what I
> gather it's available for FreeBSD too. What are the chances of
> installing openconnect on pfsense as a package to this end?
>
There is a port for it, that should do it. sec
On Sun, Dec 5, 2010 at 12:00 AM, Chris Buechler wrote:
> On Sun, Dec 5, 2010 at 1:21 AM, David Burgess wrote:
>> Is there a way to connect pfsense with an Anyconnect server?
>
> No, that's Cisco proprietary.
But openconnect works, at least for me on Linux, and from what I
gather it's available f
On Sun, Dec 5, 2010 at 1:21 AM, David Burgess wrote:
> Is there a way to connect pfsense with an Anyconnect server?
No, that's Cisco proprietary.
-
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands,
Is there a way to connect pfsense with an Anyconnect server? Google
isn't turning up much for me.
-
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com
Commercial supp
I just upgraded from a working pfsense 1.23 to 2.0-BETA4 latest build all
went well except for all my RRD graphs except for system are showing the
following error "There has been an error creating the graphs, please check
your system logs"
I would like to keep my RRD data is there a work around
On Sat, Dec 4, 2010 at 2:35 PM, Evgeny Yurchenko wrote:
> I would suggest to tcpdump. This way you for sure will know where these
> packets are coming from.
Thanks for the hint. tcpdump confirms that these are coming from
pppoe0, so I'll be talking to my ISP.
db
--
On 10-12-04 04:26 PM, David Burgess wrote:
My WAN is mlppp with a static public IP address. pfSense is 2.0 beta4.
Out of curiosity I disabled the check box on the WAN config page to
block private networks. I then created an alias for RFC1918 and
loopback addresses and manually created a logging
My WAN is mlppp with a static public IP address. pfSense is 2.0 beta4.
Out of curiosity I disabled the check box on the WAN config page to
block private networks. I then created an alias for RFC1918 and
loopback addresses and manually created a logging reject rule at the
top of the WAN rules for t
