On Mon, Mar 21, 2011 at 11:19 AM, David Burgess <[email protected]> wrote: > On Sun, Dec 5, 2010 at 12:10 AM, Chris Buechler <[email protected]> wrote: >> On Sun, Dec 5, 2010 at 2:02 AM, David Burgess <[email protected]> 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. security/openconnect/ > > I finally attempted this and it was surprisingly easy to do. > > The problem now is when I try to use the tunnel from the LAN. Of > course the AnyConnect server doesn't know how to route to my LAN, and > since I have no control over it the obvious answer is outbound NAT. > But since pfsense's web UI doesn't know about the tun0 interface, the > Outbound NAT page doesn't offer it as an option when creating a rule > (a similar problem will exist when trying to make firewall or traffic > shaper rules, but I'm not worried about that now). > > Can somebody point out a pattern for making an outbound NAT rule for > openconnect's tun0? >
Assign tun0 as an OPT interface. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] Commercial support available - https://portal.pfsense.org
