Development discussion of WireGuard
 help / color / mirror / Atom feed
From: lejeczek <peljasz@yahoo.co.uk>
Cc: wireguard@lists.zx2c4.com
Subject: Re: error - ? - Address already in use
Date: Thu, 14 Apr 2022 04:14:54 +0100	[thread overview]
Message-ID: <20ec95e3-ce3e-8fc7-4e46-c379e719a665@yahoo.co.uk> (raw)
In-Reply-To: <20220414024510.4f980d24@inspiro.localdomain>



On 13/04/2022 20:45, Shulhan wrote:
> On Wed, 13 Apr 2022 18:45:24 +0100
> lejeczek <peljasz@yahoo.co.uk> wrote:
>
>> Hi guys
>>
>> what is below error the symptom of?
>>
>> -> $ wg-quick up wg-r2
>> [#] ip link add wg-r2 type wireguard
>> [#] wg setconf wg-r2 /dev/fd/63
>> [#] ip -4 address add 10.3.3.254/24 dev wg-r2
>> [#] ip link set mtu 1320 up dev wg-r2
>> RTNETLINK answers: Address already in use
>> [#] ip link delete dev wg-r2
>>
>> I'll only add that I looked into "obvious" places and found
>> nothing.
>> many thanks, L.
> My guess is another wg network is already up using the same IP address.
> You may check using `wg show` to see the active endpoint or other
> net tools like `ip` or `ifconfig` to list of active net devices.
>
This message is _pretty_ deceptive as it's the 'port' which 
is the culprit - if used already by instantiated wg iface.

btw. @mailman admins - this mailing list has DMARC breaking, 
those of us who use yahoo, delivery of own messages.

thanks, L

      reply	other threads:[~2022-04-14  3:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <077cdb1c-e06c-d2fd-1475-269ed744d5ca.ref@yahoo.co.uk>
2022-04-13 17:45 ` lejeczek
2022-04-13 19:45   ` Shulhan
2022-04-14  3:14     ` lejeczek [this message]

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=20ec95e3-ce3e-8fc7-4e46-c379e719a665@yahoo.co.uk \
    --to=peljasz@yahoo.co.uk \
    --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).