fastd/fastd
1
0
Fork 0
mirror of https://github.com/neocturne/fastd.git synced 2025-05-14 12:25:07 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

doc: remove now unused pmtu option

Browse source
This commit is contained in:
Matthias Schiffer 2015-01-26 04:03:16 +01:00
parent 712ed55c45
commit e7be1c8c26
4 changed files with 5 additions and 18 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
doc/examples/openwrt/fastd.config
View file

@ -82,9 +82,6 @@ config fastd sample_config
# If set to 1, the logs won't contain peers' MAC addresses
# option hide_mac_addresses '0'
# Read the documentation about this one. Only ever useful in severly broken networks.
# option pmtu ''
# command to configure IP addresses etc. after the tunnel interface is up; $1 will be the interface name (optional)
# option up ''

3
doc/examples/openwrt/fastd.init
View file

@ -73,7 +73,6 @@ config_string_peer_limit='peer limit $(guard_value "$value");'
config_string_user='user $(escape_string "$value");'
config_string_group='group $(escape_string "$value");'
config_string_status_socket='status socket $(escape_string "$value");'
config_string_pmtu='pmtu $(yes_no "$value");'
config_string_forward='forward $(yes_no "$value");'
config_string_hide_ip_addresses='hide ip addresses $(yes_no "$value");'
config_string_hide_mac_addresses='hide mac addresses $(yes_no "$value");'
@ -242,7 +241,7 @@ generate_config() {
append_options "$s" config \
config config_peer config_peer_dir bind method syslog_level mode interface mtu peer_limit \
user group status_socket pmtu forward hide_ip_addresses hide_mac_addresses secure_handshakes packet_mark \
user group status_socket forward hide_ip_addresses hide_mac_addresses secure_handshakes packet_mark \
on_pre_up on_up on_down on_post_down on_connect on_establish on_disestablish on_verify
config_get mode "$s" mode

13
doc/source/manual/config.rst
View file

@ -230,17 +230,8 @@ Example config:
| ``pmtu yes|no|auto;``
Enables or disables Path MTU detection for IPv4. If enabled, all packets are sent with DF set, and all
fragmentation happens on the sending host itself. If disabled, routers may fragment the packets themselves,
possibly leading to multiple fragmentation. In general, disabling this should not be necessary, but in some
networks ICMP MTU Too Big packets are lost, so PMTU detection doesn't work correctly.
If possible, fastd's mtu setting should be adjusted so the packets aren't fragmented at all instead of
relying on this option.
The default is auto, which uses the system default as specified in /proc/sys/net/ipv4/ip_no_pmtu_disc.
The pmtu option is available on Linux platforms only.
Does nothing; the ``pmtu`` option is only supported for compatiblity
with older versions of fastd.
| ``protocol "<protocol>";``

4
doc/source/manual/mtu.rst
View file

@ -2,8 +2,8 @@ MTU configuration
=================
The default MTU of fastd is 1500. This allows briding the fastd interface in TAP
mode with other interface with the same MTU, but will usually cause fastd's UDP
packets to be fragmented (see also the option :ref:`pmtu <option-pmtu>`). Fragmentation can lower the
performance or even cause connectivty problems when broken routers filter ICMP packets,
packets to be fragmented. Fragmentation can lower the
performance or even cause connectivity problems when broken routers filter ICMP packets,
so if possible the MTU should be chosed small enough so that IP fragmentation can be avoided.
Unlike OpenVPN, fastd doesn't support fragmentation itself, but relies on the IP stack to fragment packets when necessary.