<?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 FMC Soft parser: Custom protocol between L2 and L3 or before L2 in P-Series</title>
    <link>https://community.nxp.com/t5/P-Series/FMC-Soft-parser-Custom-protocol-between-L2-and-L3-or-before-L2/m-p/593722#M3532</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello!&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a problem in configuring PCD soft parser for following purpose.&lt;/P&gt;&lt;P&gt;We have to place custom protocol after Ethernet frame and before any higher level container (VLAN, MPLS, IP, etc.) and furthermore classify and/or distribute such frames basing on L3/L4 fields (e.g. ipv4.src or udp.dport).&lt;/P&gt;&lt;P&gt;The protocol has it's own Ether Type and contains in it's fields (in the last field) Ether Type of the next protocol.&lt;/P&gt;&lt;P&gt;When I try to write policy/custom prot.&amp;nbsp;files as it explained in documentation (I could not found detailed document, only briefs),&amp;nbsp;I successfully classified frames by (first) Ether Type, but I have not found the way to detect next protocols: How to send FMC the place of next protocol Ether Type?&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Processor used: T4240RDB, SDK: 1.9.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I attach config, policy and protocol definition.&lt;/P&gt;&lt;P&gt;With this configuration all frames reaches distribution "stack" (fqid = 0x1520), but desired distribution is "dist" (fqid 0x1501, 0x1502).&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The netx protocol Ether Type placed in "et" field.&lt;/P&gt;&lt;P&gt;Please help me with more detailed documentation about Soft Parser or explain which variables lihe "$shimoffset_1" need to be changed or something else.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The model form&amp;nbsp;&lt;A _jive_internal="true" href="https://community.nxp.com/external-link.jspa?url=https%3A%2F%2Fwww.nxp.com%2Ffiles%2Ftraining_pdf%2FWBNR_FTF11_NET_F0414.pdf%3Flang_cd%3Dja" rel="nofollow" target="_blank"&gt;presentation&lt;/A&gt;&amp;nbsp;(page 42) would be suitable for us, but unfortunately protocol xml example given below is not for this case.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-337217"&gt;policy.xml.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-337217"&gt;prt.xml.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-337217"&gt;config.xml.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 05 Sep 2016 15:59:38 GMT</pubDate>
    <dc:creator>dmitryslezkin</dc:creator>
    <dc:date>2016-09-05T15:59:38Z</dc:date>
    <item>
      <title>FMC Soft parser: Custom protocol between L2 and L3 or before L2</title>
      <link>https://community.nxp.com/t5/P-Series/FMC-Soft-parser-Custom-protocol-between-L2-and-L3-or-before-L2/m-p/593722#M3532</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello!&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a problem in configuring PCD soft parser for following purpose.&lt;/P&gt;&lt;P&gt;We have to place custom protocol after Ethernet frame and before any higher level container (VLAN, MPLS, IP, etc.) and furthermore classify and/or distribute such frames basing on L3/L4 fields (e.g. ipv4.src or udp.dport).&lt;/P&gt;&lt;P&gt;The protocol has it's own Ether Type and contains in it's fields (in the last field) Ether Type of the next protocol.&lt;/P&gt;&lt;P&gt;When I try to write policy/custom prot.&amp;nbsp;files as it explained in documentation (I could not found detailed document, only briefs),&amp;nbsp;I successfully classified frames by (first) Ether Type, but I have not found the way to detect next protocols: How to send FMC the place of next protocol Ether Type?&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Processor used: T4240RDB, SDK: 1.9.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I attach config, policy and protocol definition.&lt;/P&gt;&lt;P&gt;With this configuration all frames reaches distribution "stack" (fqid = 0x1520), but desired distribution is "dist" (fqid 0x1501, 0x1502).&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The netx protocol Ether Type placed in "et" field.&lt;/P&gt;&lt;P&gt;Please help me with more detailed documentation about Soft Parser or explain which variables lihe "$shimoffset_1" need to be changed or something else.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The model form&amp;nbsp;&lt;A _jive_internal="true" href="https://community.nxp.com/external-link.jspa?url=https%3A%2F%2Fwww.nxp.com%2Ffiles%2Ftraining_pdf%2FWBNR_FTF11_NET_F0414.pdf%3Flang_cd%3Dja" rel="nofollow" target="_blank"&gt;presentation&lt;/A&gt;&amp;nbsp;(page 42) would be suitable for us, but unfortunately protocol xml example given below is not for this case.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-337217"&gt;policy.xml.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-337217"&gt;prt.xml.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-337217"&gt;config.xml.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Sep 2016 15:59:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/FMC-Soft-parser-Custom-protocol-between-L2-and-L3-or-before-L2/m-p/593722#M3532</guid>
      <dc:creator>dmitryslezkin</dc:creator>
      <dc:date>2016-09-05T15:59:38Z</dc:date>
    </item>
    <item>
      <title>Re: FMC Soft parser: Custom protocol between L2 and L3 or before L2</title>
      <link>https://community.nxp.com/t5/P-Series/FMC-Soft-parser-Custom-protocol-between-L2-and-L3-or-before-L2/m-p/593723#M3533</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Discussion of this issue may require sharing NDA-covered materials which is not possible in public Forums. Please&amp;nbsp; open a Support Case for it. Instructions can be found at the link below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/docs/DOC-329745"&gt;https://community.nxp.com/docs/DOC-329745&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Sep 2016 09:23:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/FMC-Soft-parser-Custom-protocol-between-L2-and-L3-or-before-L2/m-p/593723#M3533</guid>
      <dc:creator>bpe</dc:creator>
      <dc:date>2016-09-08T09:23:43Z</dc:date>
    </item>
  </channel>
</rss>

