wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
* Source IP for multihomed peer
@ 2021-10-14  8:30 Svenne Krap
  2021-10-15  2:39 ` Benda Xu
  2021-10-15 10:14 ` Toke Høiland-Jørgensen
  0 siblings, 2 replies; 7+ messages in thread
From: Svenne Krap @ 2021-10-14  8:30 UTC (permalink / raw)
  To: wireguard


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

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

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.



^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2021-10-15 11:16 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-10-14  8:30 Source IP for multihomed peer Svenne Krap
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

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).