include/net/tun_proto.h
Source file repositories/reference/linux-study-clean/include/net/tun_proto.h
File Facts
- System
- Linux kernel
- Corpus path
include/net/tun_proto.h- Extension
.h- Size
- 1015 bytes
- Lines
- 51
- Domain
- Networking Core
- Bucket
- Sockets, Protocols, Packet Path, And Network Policy
- Inferred role
- Networking Core: implementation source
- Status
- source implementation candidate
Why This File Exists
Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.
- Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.
Dependency Surface
linux/if_ether.hlinux/types.h
Detected Declarations
function tun_p_to_eth_pfunction tun_p_from_eth_p
Annotated Snippet
#ifndef __NET_TUN_PROTO_H
#define __NET_TUN_PROTO_H
#include <linux/if_ether.h>
#include <linux/types.h>
/* One byte protocol values as defined by VXLAN-GPE and NSH. These will
* hopefully get a shared IANA registry.
*/
#define TUN_P_IPV4 0x01
#define TUN_P_IPV6 0x02
#define TUN_P_ETHERNET 0x03
#define TUN_P_NSH 0x04
#define TUN_P_MPLS_UC 0x05
static inline __be16 tun_p_to_eth_p(u8 proto)
{
switch (proto) {
case TUN_P_IPV4:
return htons(ETH_P_IP);
case TUN_P_IPV6:
return htons(ETH_P_IPV6);
case TUN_P_ETHERNET:
return htons(ETH_P_TEB);
case TUN_P_NSH:
return htons(ETH_P_NSH);
case TUN_P_MPLS_UC:
return htons(ETH_P_MPLS_UC);
}
return 0;
}
static inline u8 tun_p_from_eth_p(__be16 proto)
{
switch (proto) {
case htons(ETH_P_IP):
return TUN_P_IPV4;
case htons(ETH_P_IPV6):
return TUN_P_IPV6;
case htons(ETH_P_TEB):
return TUN_P_ETHERNET;
case htons(ETH_P_NSH):
return TUN_P_NSH;
case htons(ETH_P_MPLS_UC):
return TUN_P_MPLS_UC;
}
return 0;
}
#endif
Annotation
- Immediate include surface: `linux/if_ether.h`, `linux/types.h`.
- Detected declarations: `function tun_p_to_eth_p`, `function tun_p_from_eth_p`.
- Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
- Implementation status: source implementation candidate.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.