<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://www.trisul.org/devzone/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://www.trisul.org/devzone/feed.php">
        <title>Trisul Network Analytics &lt;br/&gt; Developer Zone  hardware</title>
        <description></description>
        <link>https://www.trisul.org/devzone/</link>
        <image rdf:resource="https://www.trisul.org/devzone/ww.trisul.org/devzone/lib/tpl/dokuwiki/images/favicon.ico" />
       <dc:date>2026-04-20T05:29:09+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://www.trisul.org/devzone/doku.php/hardware:erspan?rev=1525190901&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.trisul.org/devzone/doku.php/hardware:gatewaynetflow?rev=1546841719&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.trisul.org/devzone/doku.php/hardware:gretunnel?rev=1681137402&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.trisul.org/devzone/doku.php/hardware:shimtunnel?rev=1547210809&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.trisul.org/devzone/doku.php/hardware:shimtunnelintro?rev=1563023506&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://www.trisul.org/devzone/ww.trisul.org/devzone/lib/tpl/dokuwiki/images/favicon.ico">
        <title>Trisul Network Analytics <br/> Developer Zone </title>
        <link>https://www.trisul.org/devzone/</link>
        <url>https://www.trisul.org/devzone/ww.trisul.org/devzone/lib/tpl/dokuwiki/images/favicon.ico</url>
    </image>
    <item rdf:about="https://www.trisul.org/devzone/doku.php/hardware:erspan?rev=1525190901&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-05-01T21:38:21+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Configuring ERSPAN packet capture for Network Security Monitoring</title>
        <link>https://www.trisul.org/devzone/doku.php/hardware:erspan?rev=1525190901&amp;do=diff</link>
        <description>Configuring ERSPAN packet capture for Network Security Monitoring

ERSPAN  stands for Encapsulated Remote Switch Port ANalayzer or just Encapsulated RSPAN. This is feature available on some of the higher end platforms like Catalyst 6500 and 7500s, Nexus, and ASR platforms. Let us see how this feature can be useful in some scenarios.</description>
    </item>
    <item rdf:about="https://www.trisul.org/devzone/doku.php/hardware:gatewaynetflow?rev=1546841719&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-01-07T11:45:19+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>How to redirect Netflow to Trisul across network segments using NAT</title>
        <link>https://www.trisul.org/devzone/doku.php/hardware:gatewaynetflow?rev=1546841719&amp;do=diff</link>
        <description>How to redirect Netflow to Trisul across network segments using NAT

In some customers, Trisul is often deployed on a separate segment from the production routers or routers in the DMZ. These sites often have a gateway device that be be used to access.  The routers can reach the gateway to export NETFLOW but cannot reach the Trisul server directly. The picture below shows how the setup is.</description>
    </item>
    <item rdf:about="https://www.trisul.org/devzone/doku.php/hardware:gretunnel?rev=1681137402&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-04-10T20:06:42+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Setting up a GRE Tunnel to send Netflow to remote machine</title>
        <link>https://www.trisul.org/devzone/doku.php/hardware:gretunnel?rev=1681137402&amp;do=diff</link>
        <description>Setting up a GRE Tunnel to send Netflow to remote machine

This document explains how to setup a point to point GRE Tunnel which will be used to route Netflow packets to a remote Trisul.

The gateway machine is at one end of the tunnel, the Trisul server is at the other end. All  your routers can send Netflow to the Gateway machine on port 2055, or 5111. They will be send to the Trisul server through the tunnel.</description>
    </item>
    <item rdf:about="https://www.trisul.org/devzone/doku.php/hardware:shimtunnel?rev=1547210809&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-01-11T18:16:49+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Using a Shim Tunnel to send Netflow to a remote Trisul probe</title>
        <link>https://www.trisul.org/devzone/doku.php/hardware:shimtunnel?rev=1547210809&amp;do=diff</link>
        <description>Using a Shim Tunnel to send Netflow to a remote Trisul probe

A Shim tunnel encapsulates netflow payload inside a new UDP session by inserting a shim header ahead of the netflow header which will preserve the router/switch IP address. This is an alternative method when you cannot deploy  the other two methods</description>
    </item>
    <item rdf:about="https://www.trisul.org/devzone/doku.php/hardware:shimtunnelintro?rev=1563023506&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-07-13T18:41:46+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>When to use a SHIM tunnel</title>
        <link>https://www.trisul.org/devzone/doku.php/hardware:shimtunnelintro?rev=1563023506&amp;do=diff</link>
        <description>When to use a SHIM tunnel

Some highly secure environments do not allow general purpose tunnels like GRE or VPN. In those sites, the shim tunnel comes in handy. But the receiver needs to support detunneling.

This nfshim daemon adds a 12 byte shim header before the Netflow header.</description>
    </item>
</rdf:RDF>
