1IPSEC_TNCFG(5)                                                  IPSEC_TNCFG(5)
2
3
4

NAME

6       ipsec_tncfg  -  lists  IPSEC virtual interfaces attached to real inter‐
7       faces
8

SYNOPSIS

10       ipsec tncfg
11              cat/proc/net/ipsec_tncfg
12
13

OBSOLETE

15       Note that tncfg is only supported on the classic KLIPS stack. It is not
16       supported  on  any other stack and will be completely removed in future
17       versions. A replacement command still needs to be designed
18
19

DESCRIPTION

21       /proc/net/ipsec_tncfg is a read-only file which lists which IPSEC  vir‐
22       tual  interfaces  are  attached to which real interfaces, through which
23       packets will be forwarded once processed by IPSEC.
24
25
26       Each line lists one ipsec I/F. A table entry consists of:
27
28
29       +      an ipsec virtual I/F name
30
31
32       +      a visual and machine parsable  separator  '->',  separating  the
33              virtual I/F and the physical I/F,
34
35
36       +      a  physical I/F name, to which the ipsec virtual I/F is attached
37              or NULL if it is not attached,
38
39
40       +      the keyword mtu=,
41
42
43       +      the MTU of the ipsec virtual I/F,
44
45
46       +      the automatically adjusted effective MTU for PMTU discovery,  in
47              brackets,
48
49
50       +      a  visual  and  machine  parsable separator '->', separating the
51              virtual I/F MTU and the physical I/F MTU,
52
53
54       +      the MTU of the attached physical I/F.
55
56

EXAMPLES

58       ipsec2 -> eth3 mtu=16260(1443) -> 1500
59
60
61
62       shows that virtual device ipsec2 with an MTU of 16260 is  connected  to
63       physical  device eth3 with an MTU of 1500 and that the effective MTU as
64       a result of PMTU discovery has been automatically set to 1443.
65
66
67       ipsec0 -> wvlan0 mtu=1400(16260) -> 1500
68
69
70
71       shows that virtual device ipsec0 with an MTU of 1400  is  connected  to
72       physical  device  wvlan0  with  an MTU of 1500 and no PMTU packets have
73       gotten far enough to bump down the effective MTU from  its  default  of
74       16260.
75
76
77       ipsec3 -> NULL mtu=0(0) -> 0
78
79
80
81       shows  that  virtual device ipsec3 is not connected to any physical de‐
82       vice.
83
84

FILES

86       /proc/net/ipsec_tncfg, /usr/local/bin/ipsec
87
88

SEE ALSO

90       ipsec(8), ipsec_manual(8),  ipsec_eroute(5),  ipsec_spi(5),  ipsec_spi‐
91       grp(5),    ipsec_klipsdebug(5),    ipsec_tncfg(8),    ipsec_version(5),
92       ipsec_pf_key(5)
93
94

HISTORY

96       Written for  the  Linux  FreeS/WAN  project  <http://www.freeswan.org/:
97       http://www.freeswan.org/> by Richard Guy Briggs.
98
99
100
101
102                                                                IPSEC_TNCFG(5)
Impressum