<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Ipsec vpn client to certain IP range only]]></title><description><![CDATA[<p dir="auto">I'm looking at implementing pfsense on x86 hw in several locations I work with.</p>
<p dir="auto">What I would like to know:</p>
<p dir="auto">I need to run an ipsec vpn client on the router that routes all outbound traffic headed to a certain class B network (xxx.xxx.0.0) through the vpn tunnel, but all other traffic through the normal WAN. It would be nice if the tunnel opened and closed itself as needed, but that's not necessary.</p>
<p dir="auto">Is this possible/feasible/reasonably straightforward to implement? Also, how would this be affected by a Multi-WAN setup?</p>
]]></description><link>https://forum.netgate.com/topic/21797/ipsec-vpn-client-to-certain-ip-range-only</link><generator>RSS for Node</generator><lastBuildDate>Sun, 07 Jun 2026 13:43:55 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/21797.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 28 Feb 2010 04:35:17 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Ipsec vpn client to certain IP range only on Mon, 15 Mar 2010 13:48:04 GMT]]></title><description><![CDATA[<p dir="auto">This shouldn't be a problem. Read the guides or buy the pfSense book.</p>
<p dir="auto">In a Multi-WAN setup, you would need to use only one WAN for the tunnels. This info is listed in the docs also.</p>
<p dir="auto">http://doc.pfsense.org/index.php/Category:Howto</p>
]]></description><link>https://forum.netgate.com/post/226158</link><guid isPermaLink="true">https://forum.netgate.com/post/226158</guid><dc:creator><![CDATA[bkm]]></dc:creator><pubDate>Mon, 15 Mar 2010 13:48:04 GMT</pubDate></item></channel></rss>