<?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[Packets to remote subnet not going through IPsec]]></title><description><![CDATA[<p dir="auto">Hi everyone,</p>
<p dir="auto">no sure if this topic belongs here or in the routing section, I'll just start here.</p>
<p dir="auto">We have a problem with the network setup described in the attached network plan. The Firewalls in the picture are pfSense 1.2.3.</p>
<p dir="auto">We would like to make HTTP accesses to the VOIP phones in the VOIP subnet (192.168.105.0/24) behind the left firewall from the LAN (192.168.120.0/24) behind the right firewall.<br />
There's an IPsec connection between the two firewalls, tunneling 192.168.100.0/21 and 192.168.120.0/21.</p>
<p dir="auto">The problem is that connections to a 192.168.105.x IP go out through the default route instead of going through the IPsec tunnel. Packets to the remote LAN (192.168.100.0/24) and the remote DMZ (not shown in the pic, 192.168.101.0/24) on the other hand happily travel through the tunnel.</p>
<p dir="auto">I'd be grateful if someone here could enlighten me about the reason for this.</p>
<p dir="auto">Cheers,</p>
<p dir="auto">Chris<br />
<img src="/public/_imported_attachments_/1/voip-problem.png" alt="voip-problem.png" class=" img-fluid img-markdown" /><br />
<img src="/public/_imported_attachments_/1/voip-problem.png_thumb" alt="voip-problem.png_thumb" class=" img-fluid img-markdown" /></p>
]]></description><link>https://forum.netgate.com/topic/25409/packets-to-remote-subnet-not-going-through-ipsec</link><generator>RSS for Node</generator><lastBuildDate>Mon, 15 Jun 2026 11:59:37 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/25409.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 30 Jul 2010 12:25:16 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Packets to remote subnet not going through IPsec on Fri, 30 Jul 2010 14:18:00 GMT]]></title><description><![CDATA[<p dir="auto">Gah, thanks for the clue-bat!</p>
]]></description><link>https://forum.netgate.com/post/241465</link><guid isPermaLink="true">https://forum.netgate.com/post/241465</guid><dc:creator><![CDATA[terranean]]></dc:creator><pubDate>Fri, 30 Jul 2010 14:18:00 GMT</pubDate></item><item><title><![CDATA[Reply to Packets to remote subnet not going through IPsec on Fri, 30 Jul 2010 14:06:12 GMT]]></title><description><![CDATA[<p dir="auto">But it doesn't. :-)</p>
<p dir="auto">192.168.100.0/21 really is 192.168.96.0 - 192.168.103.255.</p>
<p dir="auto">Run it through a subnet calculator and you'll see, it doesn't add up the way you think it does.</p>
]]></description><link>https://forum.netgate.com/post/241464</link><guid isPermaLink="true">https://forum.netgate.com/post/241464</guid><dc:creator><![CDATA[jimp]]></dc:creator><pubDate>Fri, 30 Jul 2010 14:06:12 GMT</pubDate></item><item><title><![CDATA[Reply to Packets to remote subnet not going through IPsec on Fri, 30 Jul 2010 13:59:43 GMT]]></title><description><![CDATA[<p dir="auto">That's a good idea, I'll definately try that. However, since the subnet masks for the tunnel match all involved subnets this shouldn't be necessary, right?</p>
]]></description><link>https://forum.netgate.com/post/241461</link><guid isPermaLink="true">https://forum.netgate.com/post/241461</guid><dc:creator><![CDATA[terranean]]></dc:creator><pubDate>Fri, 30 Jul 2010 13:59:43 GMT</pubDate></item><item><title><![CDATA[Reply to Packets to remote subnet not going through IPsec on Fri, 30 Jul 2010 13:53:38 GMT]]></title><description><![CDATA[<p dir="auto">You'll probably need a second IPsec tunnel then that will match the VOIP subnet on the left side.</p>
<p dir="auto">In 2.0 you can have multiple subnets for each tunnel; In 1.2.3 you need two separate tunnels.</p>
]]></description><link>https://forum.netgate.com/post/241459</link><guid isPermaLink="true">https://forum.netgate.com/post/241459</guid><dc:creator><![CDATA[jimp]]></dc:creator><pubDate>Fri, 30 Jul 2010 13:53:38 GMT</pubDate></item><item><title><![CDATA[Reply to Packets to remote subnet not going through IPsec on Fri, 30 Jul 2010 13:51:15 GMT]]></title><description><![CDATA[<p dir="auto">No multi-WAN and no gateway in any pf rule.</p>
]]></description><link>https://forum.netgate.com/post/241456</link><guid isPermaLink="true">https://forum.netgate.com/post/241456</guid><dc:creator><![CDATA[terranean]]></dc:creator><pubDate>Fri, 30 Jul 2010 13:51:15 GMT</pubDate></item><item><title><![CDATA[Reply to Packets to remote subnet not going through IPsec on Fri, 30 Jul 2010 13:38:23 GMT]]></title><description><![CDATA[<p dir="auto">Do you have multi-WAN or a gateway set on the rule for the VOIP phones on the LAN side of that firewall?</p>
<p dir="auto">A gateway in a pf rule can make traffic bypass the usual ways that traffic should pass, though I don't recall if that applies to IPsec offhand. IPsec usually grabs what it wants as long as the subnet matches.</p>
]]></description><link>https://forum.netgate.com/post/241453</link><guid isPermaLink="true">https://forum.netgate.com/post/241453</guid><dc:creator><![CDATA[jimp]]></dc:creator><pubDate>Fri, 30 Jul 2010 13:38:23 GMT</pubDate></item></channel></rss>