Wireguard not coming up on DD-wrt

Dennis van J. dennis_20 at yahoo.com
Wed Oct 10 16:52:19 CEST 2018


Thanks, we have not tried that yet, but certainly something to do. Have
to do it later next week though. I'll let the list know how that went.


Dennis


Op 10-10-2018 om 16:44 schreef Sebastian Gottschall:
>
> okay. this is mips32 big endian and i also have this device for
> testing. have you also tried a more recent version to ensure that its
> no regression with some sort of wireguard version?
> you may also start a private conversation on my email direct to check
> if the keys you used are all correct. so maybe a private teamviewer
> session etc if you are willing to . personally i tried already
> connections between 2 dd-wrt devices without any issues so far
>
>
> Sebastian
>
> Am 10.10.2018 um 15:31 schrieb Dennis van J.:
>>
>> It is running on a TP-LINK WDR-4300 (v1).
>>
>>
>> Op 10-10-2018 om 09:06 schreef Sebastian Gottschall:
>>>
>>>
>>> Am 10.10.2018 um 08:00 schrieb Dennis van J.:
>>>>
>>>> Hi Sebastian,
>>>>
>>>> I took care of the FW problems. An iptables --list shows that the
>>>> udp port is open.
>>>>
>>>> DD-wrt is running using: Firmware:DD-WRT v3.0-r36645 std (08/19/18).
>>>>
>>> okay and finally. which hardware do you run it?
>>>>
>>>> Cheers,
>>>>
>>>> Dennis
>>>>
>>>>
>>>> Op 9-10-2018 om 18:29 schreef Sebastian Gottschall:
>>>>>
>>>>> just to make sure. since i'm updating wireguard in dd-wrt very
>>>>> often to the latest state of art code from git. which dd-wrt
>>>>> version did you use for establishing the connection?
>>>>>
>>>>> did you also take care about usual firewall problems? by default
>>>>> the the firewall is closed on wan, so no inbound connection is
>>>>> possible
>>>>>
>>>>>
>>>>> Sebastian
>>>>>
>>>>> Am 09.10.2018 um 17:06 schrieb Dennis van J.:
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I have setup Wireguard on a Gentoo box, compiled it into the
>>>>>> kernel using instructions on the wireguard website. Got my mobile
>>>>>> to connect using 4G to this box fine, so I wanted to test further
>>>>>> with a friend of mine who has a DD-wrt installation on his
>>>>>> router. Wireguard is integrated into the DD-wrt build, we set it
>>>>>> up, but the tunnel does not come up. On the server I only see this:
>>>>>>
>>>>>> Oct  9 16:45:34 omega kernel: [178809.449718] wireguard: wg0:
>>>>>> Receiving handshake initiation from peer 10 (x.169.86.x:22300)
>>>>>> Oct  9 16:45:34 omega kernel: [178809.449721] wireguard: wg0:
>>>>>> Sending handshake response to peer 10 (x.169.86.x:22300)
>>>>>> Oct  9 16:45:34 omega kernel: [178809.450130] wireguard: wg0:
>>>>>> Keypair 32179 destroyed for peer 10
>>>>>> Oct  9 16:45:34 omega kernel: [178809.450131] wireguard: wg0:
>>>>>> Keypair 32180 created for peer 10
>>>>>> Oct  9 16:45:39 omega kernel: [178814.519668] wireguard: wg0:
>>>>>> Receiving handshake initiation from peer 10 (x.169.86.x:22300)
>>>>>> Oct  9 16:45:39 omega kernel: [178814.519671] wireguard: wg0:
>>>>>> Sending handshake response to peer 10 (x.169.86.x:22300)
>>>>>> Oct  9 16:45:39 omega kernel: [178814.520062] wireguard: wg0:
>>>>>> Keypair 32180 destroyed for peer 10
>>>>>> Oct  9 16:45:39 omega kernel: [178814.520063] wireguard: wg0:
>>>>>> Keypair 32181 created for peer 10
>>>>>> Oct  9 16:45:44 omega kernel: [178819.579701] wireguard: wg0:
>>>>>> Receiving handshake initiation from peer 10 (x.169.86.x:22300)
>>>>>> Oct  9 16:45:44 omega kernel: [178819.579704] wireguard: wg0:
>>>>>> Sending handshake response to peer 10 (x.169.86.x:22300)
>>>>>> Oct  9 16:45:44 omega kernel: [178819.580094] wireguard: wg0:
>>>>>> Keypair 32181 destroyed for peer 10
>>>>>> Oct  9 16:45:44 omega kernel: [178819.580095] wireguard: wg0:
>>>>>> Keypair 32182 created for peer 10
>>>>>> Oct  9 16:45:50 omega kernel: [178824.910142] wireguard: wg0:
>>>>>> Receiving handshake initiation from peer 10 (x.169.86.x:22300)
>>>>>> Oct  9 16:45:50 omega kernel: [178824.910145] wireguard: wg0:
>>>>>> Sending handshake response to peer 10 (x.169.86.x:22300)
>>>>>> Oct  9 16:45:50 omega kernel: [178824.910535] wireguard: wg0:
>>>>>> Keypair 32182 destroyed for peer 10
>>>>>> Oct  9 16:45:50 omega kernel: [178824.910536] wireguard: wg0:
>>>>>> Keypair 32183 created for peer 10
>>>>>> Oct  9 16:45:55 omega kernel: [178829.950001] wireguard: wg0:
>>>>>> Receiving handshake initiation from peer 10 (x.169.86.x:22300)
>>>>>> Oct  9 16:45:55 omega kernel: [178829.950003] wireguard: wg0:
>>>>>> Sending handshake response to peer 10 (x.169.86.x:22300)
>>>>>> Oct  9 16:45:55 omega kernel: [178829.950406] wireguard: wg0:
>>>>>> Keypair 32183 destroyed for peer 10
>>>>>> Oct  9 16:45:55 omega kernel: [178829.950407] wireguard: wg0:
>>>>>> Keypair 32184 created for peer 10
>>>>>>
>>>>>> Port on the server is open (since the 4G test works). We can
>>>>>> reach the 22300 port on his side. Checked the pub/private keys as
>>>>>> well.
>>>>>>
>>>>>> wg show on server:
>>>>>>
>>>>>> interface: wg0
>>>>>>   public key: <pubkey server>
>>>>>>   private key: (hidden)
>>>>>>   listening port: 51820
>>>>>>
>>>>>> peer: <pubkey of mobile>
>>>>>>   endpoint: x.200.39.x:8971
>>>>>>   allowed ips: 0.0.0.0/0
>>>>>>   latest handshake: 8 hours, 1 minute, 43 seconds ago
>>>>>>   transfer: 384.24 KiB received, 2.74 MiB sent
>>>>>>
>>>>>> peer: <pubkey of dd-wrt>
>>>>>>   endpoint: x.169.86.x:22300
>>>>>>   allowed ips: 192.168.1.0/24, 10.100.0.3/32
>>>>>>   transfer: 2.00 MiB received, 1.24 MiB sent
>>>>>>
>>>>>> On DD-wrt router:
>>>>>>
>>>>>> interface: oet1
>>>>>>   public key: <pubkey dd-wrt>
>>>>>>   private key: (hidden)
>>>>>>   listening port: 22300
>>>>>>
>>>>>> peer: <pubkey of server>
>>>>>>   endpoint: x.197.199.x:51820
>>>>>>   allowed ips: 0.0.0.0/0
>>>>>>   transfer: 0 B received, 777.43 KiB sent
>>>>>>   persistent keepalive: every 25 seconds
>>>>>>
>>>>>> We are trying to get logging to work on that DD-wrt box, that
>>>>>> should contain some more clues but maybe any of you have an idea?
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Dennis
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> WireGuard mailing list
>>>>>> WireGuard at lists.zx2c4.com
>>>>>> https://lists.zx2c4.com/mailman/listinfo/wireguard
>>>>
>>>>
>>>> _______________________________________________
>>>> WireGuard mailing list
>>>> WireGuard at lists.zx2c4.com
>>>> https://lists.zx2c4.com/mailman/listinfo/wireguard
>>
>>
>> _______________________________________________
>> WireGuard mailing list
>> WireGuard at lists.zx2c4.com
>> https://lists.zx2c4.com/mailman/listinfo/wireguard

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zx2c4.com/pipermail/wireguard/attachments/20181010/e24607ef/attachment-0001.html>


More information about the WireGuard mailing list