Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Svenne Krap <svenne@kracon.dk>
To: wireguard@lists.zx2c4.com
Subject: Source IP for multihomed peer
Date: Thu, 14 Oct 2021 10:30:27 +0200	[thread overview]
Message-ID: <d0e1773d-80d5-7676-7943-2eff8d57beaa@kracon.dk> (raw)

Hi,

I have it a problem, that seems like the following is happening.


BoxA has multiple ip-addresses with different internet providers (i.e. 
multihomed)

BoxB is a normal single-homed dynamic peer (i.e. no fixed address), as 
is BoxC.

BoxB  and boxC both have hardcoded address1 ('boxA1')  as its peer


What seems to happen is:

1) BoxB writes sends to BoxA1  (address 1)

2) BoxA responds with BoxA2  (address 2)

3) BoxB disregards the traffic.


BoxC contacts boxA on BoxA1 and due to routing (due to BoxC's network) 
it gets replies with the right address ('boxA1'), and everything works 
as expected.



My question is twofold:

1) Does the above seem like a likely chain of events?

2) Is there any way to force the source ip of the connection from boxA 
to always use address boxA1 ?

 From the documentation Listenport only seems like the portnumber and 
there seems to be no way to set the source ip.


Regards


Svenne


             reply	other threads:[~2021-10-14 15:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14  8:30 Svenne Krap [this message]
2021-10-15  2:39 ` Benda Xu
2021-10-15  7:57   ` Chriztoffer Hansen
2021-10-15  8:25     ` Benda Xu
2021-10-15  8:54   ` Svenne Krap
2021-10-15 10:14 ` Toke Høiland-Jørgensen
2021-10-15 11:14   ` Chriztoffer Hansen

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=d0e1773d-80d5-7676-7943-2eff8d57beaa@kracon.dk \
    --to=svenne@kracon.dk \
    --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).