<?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[Route specific IP Range via IPSEC VPN.]]></title><description><![CDATA[<p dir="auto">Hi</p>
<p dir="auto">I'm trying to work out how to route some traffic.</p>
<p dir="auto">I have an IPSEC VPN to a remote office. Traffic to and from the remote site is fine.</p>
<p dir="auto">Local IP - 192.168.16.0/24<br />
Remote Office IP - 192.168.19.0/24</p>
<p dir="auto">From the remote office is a VPN to a hosted data centre.<br />
Host IP - 10.0.0.0/24</p>
<p dir="auto">From my PC I can ping anything on the 192.168.19.0/24 network, but not on the 10.0.0.0/24 network.<br />
If I SSH to  device on 192.168.19.2 I can then ping 10.0.0.1</p>
<p dir="auto">From My PC if I traceroute 10.0.0.1 I see that attempt to route out via my broadband connection, so I assume I need to add a route to say any 10.0.0.0/24 traffic route via IPSEC VPN.</p>
<p dir="auto">Can some one advice how I do this ?<br />
Thanks</p>
]]></description><link>https://forum.netgate.com/topic/135327/route-specific-ip-range-via-ipsec-vpn</link><generator>RSS for Node</generator><lastBuildDate>Tue, 13 Oct 2026 21:45:26 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/135327.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 06 Sep 2018 13:50:26 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Route specific IP Range via IPSEC VPN. on Thu, 06 Sep 2018 16:02:50 GMT]]></title><description><![CDATA[<p dir="auto">You need to add Phase 2 entries to cover the traffic between 192.168.16.X and 10.0.0.X. Those need to be on both tunnels.</p>
<p dir="auto">Steve</p>
]]></description><link>https://forum.netgate.com/post/788054</link><guid isPermaLink="true">https://forum.netgate.com/post/788054</guid><dc:creator><![CDATA[stephenw10]]></dc:creator><pubDate>Thu, 06 Sep 2018 16:02:50 GMT</pubDate></item></channel></rss>