Summary: | net-misc/netifrc-0.6.1: WireGuard interfaces do not set mtu | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | tastytea <gentoo> |
Component: | netifrc | Assignee: | netifrc Team <netifrc> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | josch09, sam, volkov |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | netifrc:wg | ||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 662808 |
Description
tastytea
2019-02-16 23:06:56 UTC
*** Bug 677940 has been marked as a duplicate of this bug. *** I have the same issue on all of my Gentoo machines. Additionally, after a recent update (?) the MTU is no longer set correctly automatically, causing breakage. This means that every single time I boot any of my devices I have to log in as root and manually correct the MTU. From what I can tell, netifrc is attempting to set the MTU before the interface has even been created, suggesting that this is not a Wireguard bug, but rather a netifrc bug. Either way, it's a problem... Does the workaround from bug 677940 work for you? It works for me with netifrc 0.7.3. postup() { case ${IFACE} in wg*) ip link set mtu 1400 dev ${IFACE} ;; esac } Alternative solution that works for me is changing wireguard_depend() function in /lib/netifrc/net/wireguard to: wireguard_depend() { program /usr/bin/wg before interface } |