Re: roaming and ddns dynamic ip

2017-11-22 19:59 GMT+08:00 Jason A. Donenfeld : > Hello, > > This is not a bug. DNS resolution is not done by the WireGuard module, > but rather by the configuration tool. If you want to update an IP, > you'll need to devise a mechanism for this. One popular one is this > example

Re: roaming and ddns dynamic ip

2017-11-22 23:49 GMT+08:00 Lonnie Abelbeck <li...@lonnie.abelbeck.com>: > > On Nov 22, 2017, at 6:51 AM, d tbsky <tbs...@gmail.com> wrote: > >> 2017-11-22 19:59 GMT+08:00 Jason A. Donenfeld <ja...@zx2c4.com>: >>> Hello, >>> >>> This is n

Re: multi-home difficulty

2017-11-23 7:35 GMT+08:00 Jason A. Donenfeld <ja...@zx2c4.com>: > On Tue, Nov 21, 2017 at 3:35 PM, d tbsky <tbs...@gmail.com> wrote: >> thanks for the quick reply. my wireguard configuration is in the >> previous mail, so I think the linux firewall part is what you wan

Re: multi-home difficulty

2017-11-23 7:35 GMT+08:00 Jason A. Donenfeld <ja...@zx2c4.com>: > On Tue, Nov 21, 2017 at 3:35 PM, d tbsky <tbs...@gmail.com> wrote: >> thanks for the quick reply. my wireguard configuration is in the >> previous mail, so I think the linux firewall part is what you wan

Re: multi-home difficulty

2017-11-29 22:10 GMT+08:00 Jason A. Donenfeld : > Hi tbskyd, > > This is on 4.14.2. Would you confirm that this is an issue on your > kernel by actually _running that script and sending the output to the > list_? It would also be helpful to have the output of uname -a. > > Jason

Re: multi-home difficulty

2017-11-29 21:51 GMT+08:00 Jason A. Donenfeld : > Hi, > > I made a small script in order to reproduce this issue, but I was not > able to replicate the results. Would you spend some time with the below > code tweaking it so that it exhibits the broken behavior you're seeing? > >

Re: multi-home difficulty

2017-11-30 14:22 GMT+08:00 d tbsky <tbs...@gmail.com>: > 2017-11-30 14:15 GMT+08:00 d tbsky <tbs...@gmail.com>: >> 2017-11-29 22:49 GMT+08:00 Jason A. Donenfeld <ja...@zx2c4.com>: >>> On Wed, Nov 29, 2017 at 3:16 PM, d tbsky <tbs...@gmail.com> wrote: >&

Re: multi-home difficulty

2017-11-29 22:49 GMT+08:00 Jason A. Donenfeld <ja...@zx2c4.com>: > On Wed, Nov 29, 2017 at 3:16 PM, d tbsky <tbs...@gmail.com> wrote: >> sorry I misunderstand you. you mean I modify the script and run >> in my environment to reveal the problem? >> ok I will t

Re: multi-home difficulty

2017-11-30 14:15 GMT+08:00 d tbsky <tbs...@gmail.com>: > 2017-11-29 22:49 GMT+08:00 Jason A. Donenfeld <ja...@zx2c4.com>: >> On Wed, Nov 29, 2017 at 3:16 PM, d tbsky <tbs...@gmail.com> wrote: >>> sorry I misunderstand you. you mean I modify the script and

Re: multi-home difficulty

2017-11-29 22:49 GMT+08:00 Jason A. Donenfeld <ja...@zx2c4.com>: > On Wed, Nov 29, 2017 at 3:16 PM, d tbsky <tbs...@gmail.com> wrote: >> sorry I misunderstand you. you mean I modify the script and run >> in my environment to reveal the problem? >> ok I will t

Re: multi-home difficulty

2017-11-21 22:15 GMT+08:00 Jason A. Donenfeld <ja...@zx2c4.com>: > On Tue, Nov 21, 2017 at 2:21 PM, d tbsky <tbs...@gmail.com> wrote: >> so at first client 2.2.2.2:51820 connect to server 1.1.1.1:51820 >> but then server use 172.18.1.254(lan ip address) to reply and 5

multi-home difficulty

Hi: I tested wireguard and the speed is amazing. but when I try to deploy it to our real linux firewall, I found it is hard to make it work. our current linux firewall have multiple interface and multiple routing tables. local program will get lan ip address and nat to correct wan ip

Re: Feature Request for Multihomed Endpoints

Markus Grundmann > I wish the endpoint was able to pick a explicit outgoing IP address to > connect the other endpoint over the 802.3ad interface but the uplink > interface address is not recommend for me. What do you think about it? if you search the mail list, you will find this had been