hardware:gatewaynetflow
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
hardware:gatewaynetflow [2019/01/03 18:29] – [Then setup the Port NAT] veera | hardware:gatewaynetflow [2019/01/03 18:35] – [How to redirect Netflow to Trisul across network segments using NAT] veera | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== How to redirect Netflow to Trisul across network segments using NAT ====== | ====== How to redirect Netflow to Trisul across network segments using NAT ====== | ||
- | In some customers, Trisul is on a separate segment from the production routers. These sites often have a gateway device that be be used to access. | + | In some customers, Trisul is often deployed |
{{: | {{: | ||
- | This HOWTO explains how to use Linux IPTABLES NAT to move between | + | This HOWTO explains how to use Linux IPTABLES NAT to solve the issue. |
===== IPTABLES Port based NAT ===== | ===== IPTABLES Port based NAT ===== | ||
Line 13: | Line 13: | ||
==== Shutdown ufw or disable firewalld ==== | ==== Shutdown ufw or disable firewalld ==== | ||
+ | since we are working directly with iptables. | ||
< | < | ||
Line 31: | Line 32: | ||
< | < | ||
- | $ iptables -t nat -A PREROUTING -p udp --dport 2055 -j DNAT --to-destination 10.10.10.17: | + | $ iptables -t nat -A PREROUTING -p udp \ |
+ | | ||
</ | </ | ||
Line 38: | Line 40: | ||
- | <note important> | + | <note important> |
</ | </ | ||
==== Useful commands ==== | ==== Useful commands ==== | ||
Line 48: | Line 50: | ||
'' | '' | ||
==== Reference ==== | ==== Reference ==== | ||
- | |||
- | How to redirect incoming traffic on a port to another IP https:// | ||
- | |||
+ | Forwarding and NAT with IPTABLES : Redhat https:// |
hardware/gatewaynetflow.txt · Last modified: 2019/01/07 11:45 by veera