hardware:gretunnel
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| hardware:gretunnel [2023/04/10 19:46] – veera | hardware:gretunnel [2023/04/10 20:06] (current) – [Setting up a GRE Tunnel to send Netflow to remote machine] veera | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| This document explains how to setup a point to point GRE Tunnel which will be used to route Netflow packets to a remote Trisul. | 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. | + | 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. |
| Substitute the following settings in this guide to suit your environment | Substitute the following settings in this guide to suit your environment | ||
| Line 14: | Line 14: | ||
| + | ===== Ensure kernel module ip_gre is loaded | ||
| On the machine ensure the ip_gre kernel module is loaded. If you are using a LXC or Docker container ensure the kernel on the host has the module loaded | On the machine ensure the ip_gre kernel module is loaded. If you are using a LXC or Docker container ensure the kernel on the host has the module loaded | ||
hardware/gretunnel.1681136183.txt.gz · Last modified: 2023/04/10 19:46 by veera