<?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>T-SeriesのトピックRe: L2 switch not working after enabling IPTABLES</title>
    <link>https://community.nxp.com/t5/T-Series/L2-switch-not-working-after-enabling-IPTABLES/m-p/1223077#M3960</link>
    <description>&lt;P&gt;You need to insert the module uio_seville.ko into the kernel.&lt;/P&gt;
&lt;P&gt;In SDK 2.0 build environment, please run "bitbake uio-seville", you will get Kernel module in&amp;nbsp;build_t1040d4rdb/tmp/work/t1040d4rdb-fsl-linux/uio-seville/0.1-r0/image/lib/modules/4.1.35-rt41/extra/uio_seville.ko, please copy&amp;nbsp;uio_seville.ko to the target board and execute the following on the target board.&lt;/P&gt;
&lt;P&gt;root@t1040d4rdb:~# insmod uio_seville.ko&lt;BR /&gt;seville ffe800000.l2switch: Found Seville Switch, UIO device - IRQ 26, id 0x099530e9.&lt;BR /&gt;seville MAC address not found&lt;BR /&gt;phy_0: shared IRQ 17&lt;BR /&gt;phy_1: shared IRQ 17&lt;BR /&gt;phy_2: shared IRQ 17&lt;BR /&gt;phy_3: shared IRQ 17&lt;BR /&gt;phy_4: shared IRQ 17&lt;BR /&gt;phy_5: shared IRQ 17&lt;BR /&gt;phy_6: shared IRQ 17&lt;BR /&gt;phy_7: shared IRQ 17&lt;BR /&gt;root@t1040d4rdb:~# l2sw_bin -i /tmp/il2sw -o /tmp/ol2sw&amp;amp;&lt;BR /&gt;[1] 1861&lt;BR /&gt;fifo /tmp/il2sw is used for stdin&lt;BR /&gt;stdout is redirected to /tmp/ol2sw&lt;BR /&gt;Using UIO: /dev/uio0&lt;BR /&gt;Mapped register memory @ 0xb7d19000&lt;BR /&gt;Chipid: 099530e9&lt;BR /&gt;root@t1040d4rdb:~# ls /dev/uio0&lt;BR /&gt;/dev/uio0&lt;/P&gt;</description>
    <pubDate>Fri, 29 Jan 2021 06:18:18 GMT</pubDate>
    <dc:creator>yipingwang</dc:creator>
    <dc:date>2021-01-29T06:18:18Z</dc:date>
    <item>
      <title>L2 switch not working after enabling IPTABLES</title>
      <link>https://community.nxp.com/t5/T-Series/L2-switch-not-working-after-enabling-IPTABLES/m-p/1222564#M3958</link>
      <description>&lt;P&gt;We are using T1040 based board and linux 4.1.35. For testing L2 switch we used commands:&lt;/P&gt;&lt;P&gt;root@t1040d4rdb:-# l2sw_bin -i /tmp/il2sw -o /tmp/ol2sw&amp;amp;&lt;BR /&gt;[1] 2358&lt;BR /&gt;fifo /tmp/il2sw is used for stdin&lt;BR /&gt;stdout is redirected to /tmp/ol2sw&lt;BR /&gt;Using UIO: /dev/uio16&lt;BR /&gt;Mapped register memory @ 0x3fffa6889000&lt;BR /&gt;Chipid: 099530e9&lt;BR /&gt;root@t1040d4rdb:-# l2switch-cfg port all config show&lt;BR /&gt;l2switch&amp;gt;Port 0 state: enabled link: down mode: auto speed: ??? duplex: half&lt;BR /&gt;Port 1 state: enabled link: down mode: auto speed: ??? duplex: half&lt;BR /&gt;Port 2 state: enabled link: down mode: auto speed: ??? duplex: half&lt;BR /&gt;Port 3 state: enabled link: down mode: auto speed: ??? duplex: half&lt;BR /&gt;Port 4 state: enabled link: down mode: auto speed: ??? duplex: half&lt;BR /&gt;Port 5 state: enabled link: down mode: auto speed: ??? duplex: half&lt;BR /&gt;Port 6 state: enabled link: down mode: auto speed: ??? duplex: half&lt;BR /&gt;Port 7 state: enabled link: down mode: auto speed: ??? duplex: half&lt;BR /&gt;Port 8 state: enabled link: down mode: static speed: 2.5G duplex: full&lt;BR /&gt;Port 9 state: enabled link: down mode: static speed: 2.5G duplex: full&lt;/P&gt;&lt;P&gt;But after enabling Networking support/Networking options/Network packet filtering framework (Netfilter) option for using ip_tables and NAT modules, we are unable to test L2 switch.&lt;/P&gt;&lt;P&gt;Error what we are getting:&lt;/P&gt;&lt;P&gt;root@t1040d4rdb:~# l2sw_bin -i /tmp/il2sw -o /tmp/ol2sw&amp;amp;&lt;BR /&gt;[1] 2390&lt;BR /&gt;fifo /tmp/il2sw is used for stdin&lt;BR /&gt;stdout is redirected to /tmp/ol2sw&lt;BR /&gt;Unable to locate UIO device&lt;BR /&gt;: Success&lt;BR /&gt;root@t1040d4rdb:~# l2switch-cfg port all config show&lt;BR /&gt;l2sw_bin is not running&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please suggest what we can do for this issue.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jan 2021 09:31:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/L2-switch-not-working-after-enabling-IPTABLES/m-p/1222564#M3958</guid>
      <dc:creator>suchitasharma</dc:creator>
      <dc:date>2021-01-28T09:31:44Z</dc:date>
    </item>
    <item>
      <title>Re: L2 switch not working after enabling IPTABLES</title>
      <link>https://community.nxp.com/t5/T-Series/L2-switch-not-working-after-enabling-IPTABLES/m-p/1223077#M3960</link>
      <description>&lt;P&gt;You need to insert the module uio_seville.ko into the kernel.&lt;/P&gt;
&lt;P&gt;In SDK 2.0 build environment, please run "bitbake uio-seville", you will get Kernel module in&amp;nbsp;build_t1040d4rdb/tmp/work/t1040d4rdb-fsl-linux/uio-seville/0.1-r0/image/lib/modules/4.1.35-rt41/extra/uio_seville.ko, please copy&amp;nbsp;uio_seville.ko to the target board and execute the following on the target board.&lt;/P&gt;
&lt;P&gt;root@t1040d4rdb:~# insmod uio_seville.ko&lt;BR /&gt;seville ffe800000.l2switch: Found Seville Switch, UIO device - IRQ 26, id 0x099530e9.&lt;BR /&gt;seville MAC address not found&lt;BR /&gt;phy_0: shared IRQ 17&lt;BR /&gt;phy_1: shared IRQ 17&lt;BR /&gt;phy_2: shared IRQ 17&lt;BR /&gt;phy_3: shared IRQ 17&lt;BR /&gt;phy_4: shared IRQ 17&lt;BR /&gt;phy_5: shared IRQ 17&lt;BR /&gt;phy_6: shared IRQ 17&lt;BR /&gt;phy_7: shared IRQ 17&lt;BR /&gt;root@t1040d4rdb:~# l2sw_bin -i /tmp/il2sw -o /tmp/ol2sw&amp;amp;&lt;BR /&gt;[1] 1861&lt;BR /&gt;fifo /tmp/il2sw is used for stdin&lt;BR /&gt;stdout is redirected to /tmp/ol2sw&lt;BR /&gt;Using UIO: /dev/uio0&lt;BR /&gt;Mapped register memory @ 0xb7d19000&lt;BR /&gt;Chipid: 099530e9&lt;BR /&gt;root@t1040d4rdb:~# ls /dev/uio0&lt;BR /&gt;/dev/uio0&lt;/P&gt;</description>
      <pubDate>Fri, 29 Jan 2021 06:18:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/L2-switch-not-working-after-enabling-IPTABLES/m-p/1223077#M3960</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2021-01-29T06:18:18Z</dc:date>
    </item>
  </channel>
</rss>

