Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Simon Rozman <simon@rozman.si>
To: Ludwig Herzog <ludwig.herzog@web.de>,
	"wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH wireguard-windows] Calculate the actual route metric by summing interface and route metric.
Date: Wed, 1 Apr 2020 06:46:11 +0000	[thread overview]
Message-ID: <EE280F52-484A-4C40-BBF3-F23D0E19CFC9@rozman.si> (raw)
In-Reply-To: <e7f67006-09a0-e775-5f7d-4d0c8e7e271a@web.de>

[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]

Hi Ludwig,

Would a support for ExecPostUp/ExecPreDown satisfy your need?

Regards, Simon

-----Original Message-----
From: WireGuard <wireguard-bounces@lists.zx2c4.com> on behalf of Ludwig Herzog <ludwig.herzog@web.de>
Date: Tuesday, 31 March 2020 at 05:33
To: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH wireguard-windows] Calculate the actual route metric by summing interface and route metric.

    Hi,
    
    I'm reading this maillist since a longer time and was never brave enough
    to mention my problem since I'm not a developer or programmer and don't
    know if I can describe it properly. Now this windows/metric stuff came
    up, so I take a heart ;-)
    
    In short: I have windows 10 client softwares which only work properly
    with manually set adapter and gateway metrics in the VPN network
    adapter, what works for openVPN (even better for a logmein test setup)
    but not for wireguard, since manual metric settings are not recognized /
    overwritten by the windows wireguard app. Is it possible to set the
    metrics somehow in the config file? Or prevent the windows wireguard app
    from overwriting?
    
    Regards
    
    Ludwig
    

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2965 bytes --]

  reply	other threads:[~2020-04-01  6:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-27 17:07 Philipp Czerner
2020-03-30  5:31 ` Jason A. Donenfeld
2020-03-30  8:40   ` Ludwig Herzog
2020-04-01  6:46     ` Simon Rozman [this message]
2020-03-31 12:56   ` Philipp Czerner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=EE280F52-484A-4C40-BBF3-F23D0E19CFC9@rozman.si \
    --to=simon@rozman.si \
    --cc=ludwig.herzog@web.de \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).