Your message dated Tue, 20 Sep 2016 13:07:24 +0200
with message-id <20160920130724.231e2...@cecil.afaics.de>
and subject line Re: network-manager-strongswan no MTU parameter for tun0
has caused the Debian Bug report #809224,
regarding network-manager-strongswan no MTU parameter for tun0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
809224: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: network-manager-strongswan
version: 1.3.1-1 (maybe others)

it's really absolutely useless until there is an ability to set MTU (default is 1500) for tunX-interface as it's done in a similar network-manager-vpnc package. can you imagine:

1. you have to connect to IPsec server through a pppoe connection (mtu 1492 and below)? 2. you have to connect to IPv6 IPsec server through a ipv6-tunnel which is configured through pppoe (mtu 1480 and below) link? 3. does 1 and 2 really sound so fantastic? the rest of the world is connected through ethernet?

--
Vladislav Artemyev

--- End Message ---
--- Begin Message ---
Tags: wontfix

Hi Vladislav,

I asked Tobias Brunner about your suggestion. Here is his reply:

I doubt that changing the MTU would actually have any effect at all
because that interface (tun0) is not really used.  It is only created because
some versions of NM insisted on getting an interface back from the
plugin (we initially passed lo but NM started to change IPs etc. on it,
so we replaced that with that dummy TUN device, see [1] and [2]).  This
doesn't seem to be required anymore since [3], though, which is in the
current NM releases.  So we might as well stop creating that device and
passing it to NM (pushed another commit to the branch).

[1] 
https://bugs.launchpad.net/ubuntu/+source/plasma-widget-networkmanagement/+bug/872824
[2] https://wiki.strongswan.org/issues/294
[3] https://github.com/NetworkManager/NetworkManager/commit/de56f28db62d


I hope its OK to close this report with wontfix?


Regards
Harri

--- End Message ---

Reply via email to