<?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[Found a possible bug.]]></title><description><![CDATA[<p dir="auto">I have a bridged lan interface using virtio nic and vlan on lagg interface. I was setting up a Wan failover and running into problems.</p>
<p dir="auto">When you setup a wan failover with two wans/gateways using a gateway group and change the gateway in the default lan -&gt; any rule from default to the group, the two lan interfaces that are bridged stop talking with each other (as in you can ping the pfsense box but can not ping machines on vlan from the virtio lan nor can virtio lan ping machines on vlan) But you are able to reach the internet. On the other hand if you switch it back to default, you are able to talk to each other but not reach the internet.</p>
<p dir="auto">I have<br />
net.link.bridge.pfil_member set 0<br />
and<br />
net.link.bridge.pfil_bridge set 1</p>
<p dir="auto">This seems to be a bug.</p>
]]></description><link>https://forum.netgate.com/topic/101577/found-a-possible-bug</link><generator>RSS for Node</generator><lastBuildDate>Wed, 22 Jul 2026 07:14:02 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/101577.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 16 Jun 2016 04:05:23 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Found a possible bug. on Wed, 22 Jun 2016 04:30:14 GMT]]></title><description><![CDATA[<p dir="auto">Just make sure your rules specifying a gateway are only matching traffic you want to force to that gateway (group). Add rule(s) above that to pass traffic between internal networks.</p>
]]></description><link>https://forum.netgate.com/post/633327</link><guid isPermaLink="true">https://forum.netgate.com/post/633327</guid><dc:creator><![CDATA[cmb]]></dc:creator><pubDate>Wed, 22 Jun 2016 04:30:14 GMT</pubDate></item><item><title><![CDATA[Reply to Found a possible bug. on Sat, 18 Jun 2016 08:47:34 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/cmb">@<bdi>cmb</bdi></a>:</p>
<blockquote>
<p dir="auto">Not a bug, nature of how policy routing works by design - it forces traffic to the specified gateway. Don't pass traffic between internal networks with a rule specifying a gateway.</p>
</blockquote>
<p dir="auto">Ok, so it's by design.<br />
Is there a proper way to allow traffic on a bridge with a gateway group set?</p>
]]></description><link>https://forum.netgate.com/post/632486</link><guid isPermaLink="true">https://forum.netgate.com/post/632486</guid><dc:creator><![CDATA[Mad Professor]]></dc:creator><pubDate>Sat, 18 Jun 2016 08:47:34 GMT</pubDate></item><item><title><![CDATA[Reply to Found a possible bug. on Thu, 16 Jun 2016 20:36:58 GMT]]></title><description><![CDATA[<p dir="auto">Not a bug, nature of how policy routing works by design - it forces traffic to the specified gateway. Don't pass traffic between internal networks with a rule specifying a gateway.</p>
]]></description><link>https://forum.netgate.com/post/632206</link><guid isPermaLink="true">https://forum.netgate.com/post/632206</guid><dc:creator><![CDATA[cmb]]></dc:creator><pubDate>Thu, 16 Jun 2016 20:36:58 GMT</pubDate></item></channel></rss>