- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- GRE Monitor utilitiy
Operating System - Linux
1819682
Members
3575
Online
109605
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2008 09:41 PM
06-17-2008 09:41 PM
Hi All,
There are two network having GRE tunnel using linux boxes (router & NAT) in between them.
1) Encapsulation/Decapsulation of IP header, GRE header, MPLS header - does the stack support all three or just IP and GRE?
2)DF bit setting of encapulating IP header
3)Tunnel status monitoring
Is there any utilities to monitor GRE tunnel like DSCP marking of encapsulating IP header, Configurable MTU , Path MTU Discovery etc?
Please suggest.
Thanks,
MKS
There are two network having GRE tunnel using linux boxes (router & NAT) in between them.
1) Encapsulation/Decapsulation of IP header, GRE header, MPLS header - does the stack support all three or just IP and GRE?
2)DF bit setting of encapulating IP header
3)Tunnel status monitoring
Is there any utilities to monitor GRE tunnel like DSCP marking of encapsulating IP header, Configurable MTU , Path MTU Discovery etc?
Please suggest.
Thanks,
MKS
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2008 07:03 AM
06-18-2008 07:03 AM
Solution
1.) MPLS??? As far as I know, the standard Linux kernel has no native support for MPLS yet.
Of course, if your linux boxes are specially designed to work as routers, they may contain special hardware & software for MPLS support. If this is the case, see the documentation of your system.
2.) This is used by the Path MTU Discovery, which is enabled by default in all modern operating systems (it was standardized in 1990, as RFC1191). So I'd expect the DF bit to be always set in practice.
3.) A GRE tunnel is stateless, so there is no "status" to monitor. There are only configuration settings, and they won't change unless you make the change using the appropriate commands.
The tunnel is presented to the OS tools as equivalent to a normal network interface, so you can use tools like iptables to manipulate the DSCP markings if the defaults do not work for you. The MTU of the tunnel device can be adjusted using "ifconfig" or "ip" tools.
In Linux, you cannot enable or disable Path MTU Discovery separately for each NIC (or tunnel). It's all or nothing: by default, Path MTU discovery is enabled for all interfaces.
If you wish to disable Path MTU Discovery for the entire box, you can use:
echo 1 >/proc/sys/net/ipv4/ip_no_pmtu_disc
If you would need to selectively disable Path MTU Discovery, you could use the TCPMSS target of iptables instead. Something like:
iptables -t mangle -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
See "man iptables" for more information.
MK
Of course, if your linux boxes are specially designed to work as routers, they may contain special hardware & software for MPLS support. If this is the case, see the documentation of your system.
2.) This is used by the Path MTU Discovery, which is enabled by default in all modern operating systems (it was standardized in 1990, as RFC1191). So I'd expect the DF bit to be always set in practice.
3.) A GRE tunnel is stateless, so there is no "status" to monitor. There are only configuration settings, and they won't change unless you make the change using the appropriate commands.
The tunnel is presented to the OS tools as equivalent to a normal network interface, so you can use tools like iptables to manipulate the DSCP markings if the defaults do not work for you. The MTU of the tunnel device can be adjusted using "ifconfig" or "ip" tools.
In Linux, you cannot enable or disable Path MTU Discovery separately for each NIC (or tunnel). It's all or nothing: by default, Path MTU discovery is enabled for all interfaces.
If you wish to disable Path MTU Discovery for the entire box, you can use:
echo 1 >/proc/sys/net/ipv4/ip_no_pmtu_disc
If you would need to selectively disable Path MTU Discovery, you could use the TCPMSS target of iptables instead. Something like:
iptables -t mangle -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
See "man iptables" for more information.
MK
MK
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP