<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: S32G3 Linux PFE libfci_cli: L2 Bridge in FW_ONLY(static) Mode in S32G</title>
    <link>https://community.nxp.com/t5/S32G/S32G3-Linux-PFE-libfci-cli-L2-Bridge-in-FW-ONLY-static-Mode/m-p/2332620#M16118</link>
    <description>Thank you for your response.&lt;BR /&gt;Have a nice day!</description>
    <pubDate>Fri, 13 Mar 2026 11:37:07 GMT</pubDate>
    <dc:creator>minJ</dc:creator>
    <dc:date>2026-03-13T11:37:07Z</dc:date>
    <item>
      <title>S32G3 Linux PFE libfci_cli: L2 Bridge in FW_ONLY(static) Mode</title>
      <link>https://community.nxp.com/t5/S32G/S32G3-Linux-PFE-libfci-cli-L2-Bridge-in-FW-ONLY-static-Mode/m-p/2322312#M16046</link>
      <description>&lt;P&gt;I have a question regarding the S32G3 Linux PFE L2 bridge configuration in FW_ONLY(static) mode.&lt;/P&gt;&lt;P&gt;The broadcast MAC address (ff:ff:ff:ff:ff:ff) is automatically registered in the MAC table, so broadcast packets such as ARP requests are delivered normally.&lt;BR /&gt;However, if I do not register the destination PC’s unicast MAC address using bd-stent-add, unicast packets (such as ping) to that PC are not delivered.&lt;/P&gt;&lt;P&gt;My questions are:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;In FW_ONLY(static) mode, is it mandatory to pre-register the MAC addresses of all devices (such as PCs) that will communicate, since dynamic MAC learning is completely disabled? In other words, do I need to know all unicast MAC addresses in advance for communication to work?&lt;/LI&gt;&lt;LI&gt;If so, in a real network environment where it is not possible to know the MAC addresses of all peers beforehand, is there any recommended way to handle this situation? (For example, is there any method for automatic registration or workaround when using fw_only mode?)&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Wed, 25 Feb 2026 06:42:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/S32G3-Linux-PFE-libfci-cli-L2-Bridge-in-FW-ONLY-static-Mode/m-p/2322312#M16046</guid>
      <dc:creator>minJ</dc:creator>
      <dc:date>2026-02-25T06:42:22Z</dc:date>
    </item>
    <item>
      <title>Re: S32G3 Linux PFE libfci_cli: L2 Bridge in FW_ONLY(static) Mode</title>
      <link>https://community.nxp.com/t5/S32G/S32G3-Linux-PFE-libfci-cli-L2-Bridge-in-FW-ONLY-static-Mode/m-p/2323574#M16059</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/260071"&gt;@minJ&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for your post.&lt;/P&gt;
&lt;P&gt;The FW_ONLY mode means l&lt;SPAN class="fontstyle0"&gt;earning disabled, forwarding enabled, the&lt;/SPAN&gt;&lt;BR /&gt;traffic is forwarded only if its both source and destination MAC addresses are known to the bridge, so if they are not registered, the unicast packets would not be delivered as expected.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;Chenyin&lt;/P&gt;</description>
      <pubDate>Thu, 26 Feb 2026 11:07:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/S32G3-Linux-PFE-libfci-cli-L2-Bridge-in-FW-ONLY-static-Mode/m-p/2323574#M16059</guid>
      <dc:creator>chenyin_h</dc:creator>
      <dc:date>2026-02-26T11:07:32Z</dc:date>
    </item>
    <item>
      <title>Re: S32G3 Linux PFE libfci_cli: L2 Bridge in FW_ONLY(static) Mode</title>
      <link>https://community.nxp.com/t5/S32G/S32G3-Linux-PFE-libfci-cli-L2-Bridge-in-FW-ONLY-static-Mode/m-p/2332620#M16118</link>
      <description>Thank you for your response.&lt;BR /&gt;Have a nice day!</description>
      <pubDate>Fri, 13 Mar 2026 11:37:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/S32G3-Linux-PFE-libfci-cli-L2-Bridge-in-FW-ONLY-static-Mode/m-p/2332620#M16118</guid>
      <dc:creator>minJ</dc:creator>
      <dc:date>2026-03-13T11:37:07Z</dc:date>
    </item>
  </channel>
</rss>

