WireGuard Archive on lore.kernel.org
 help / color / Atom feed
* Trouble with WG on Synology NAS
@ 2019-07-06 11:15 Berend D.
  0 siblings, 0 replies; only message in thread
From: Berend D. @ 2019-07-06 11:15 UTC (permalink / raw)
  To: wireguard

[-- Attachment #1.1: Type: text/plain, Size: 1687 bytes --]

I am using WireGuard on my Synology 415+ NAS which runs Linux kernel
3.10.105.

I tried a couple versions of wireguard now, using
https://github.com/runfalk/synology-wireguard as inspiration to compile
them, but none of them seem to work.

The problem I experience is that everything is seemingly correctly set up
(I have a Linux server elsewhere to compare configs with) but after
connecting to Wireguard, the server only seems to be able to receive
packets, not send them: when pinging the NAS I can see the ifconfig RX
packet counter go up, and at the same time the TX error counter as well.

wg0       Link encap:UNSPEC  HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:192.168.33.1  P-t-P:192.168.33.1  Mask:255.255.255.0
          UP POINTOPOINT RUNNING NOARP  MTU:1420  Metric:1
          RX packets:5 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:21 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:564 (564.0 B)  TX bytes:124 (124.0 B)

I ran over my config multiple times now but I can not spot a difference to
my working setup on the other server. I also tried various clients
(Android, Ubuntu, Windows 10 both the WG client and an alternative
implementation).

Tested versions:
- 0.0.20190227-2
- 0.0.20190601
- 0.0.20190 <https://git.zx2c4.com/WireGuard/tag/?h=0.0.20190601>702

The only thing the Synology build changes is to force memneq on since its
not supported (the 'ifeq' in Kbuild.include is removed via patch so its
always included).

I can not find a way to make it all more verbose to figure out why the
packets are dropped by WG.

What can I try to debug this?

Cheers,
Berend

[-- Attachment #1.2: Type: text/html, Size: 2556 bytes --]

<div dir="ltr">I am using WireGuard on my Synology 415+ NAS which runs Linux kernel 3.10.105.<div><br></div><div>I tried a couple versions of wireguard now, using <a href="https://github.com/runfalk/synology-wireguard">https://github.com/runfalk/synology-wireguard</a> as inspiration to compile them, but none of them seem to work.</div><div><br></div><div>The problem I experience is that everything is seemingly correctly set up (I have a Linux server elsewhere to compare configs with) but after connecting to Wireguard, the server only seems to be able to receive packets, not send them: when pinging the NAS I can see the ifconfig RX packet counter go up, and at the same time the TX error counter as well.</div><div><br></div><div>wg0       Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00<br>          inet addr:192.168.33.1  P-t-P:192.168.33.1  Mask:255.255.255.0<br>          UP POINTOPOINT RUNNING NOARP  MTU:1420  Metric:1<br>          RX packets:5 errors:0 dropped:0 overruns:0 frame:0<br>          TX packets:2 errors:21 dropped:0 overruns:0 carrier:0<br>          collisions:0 txqueuelen:0<br>          RX bytes:564 (564.0 B)  TX bytes:124 (124.0 B)<br></div><div><br></div><div>I ran over my config multiple times now but I can not spot a difference to my working setup on the other server. I also tried various clients (Android, Ubuntu, Windows 10 both the WG client and an alte<font face="arial, sans-serif">rnative implementation).</font></div><div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">Tested versions:</font></div><div><font face="arial, sans-serif"><span style="color:rgb(3,47,98);white-space:pre">- 0.0.20190227-2</span> </font></div><div><font face="arial, sans-serif">- 0.0.20190601</font></div><div><font face="arial, sans-serif">- </font><a href="https://git.zx2c4.com/WireGuard/tag/?h=0.0.20190601" style="color:black;text-decoration-line:none;font-family:sans-serif;font-size:13.3333px;white-space:nowrap;background-color:rgb(247,247,247)">0.0.20190</a>702</div><div><br></div><div>The only thing the Synology build changes is to force memneq on since its not supported (the &#39;ifeq&#39; in Kbuild.include is removed via patch so its always included).</div><div><br></div><div>I can not find a way to make it all more verbose to figure out why the packets are dropped by WG.</div><div><br></div><div>What can I try to debug this?</div><div><br></div><div>Cheers,</div><div>Berend</div><div> <br></div></div>

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, back to index

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-06 11:15 Trouble with WG on Synology NAS Berend D.

WireGuard Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
		wireguard@lists.zx2c4.com zx2c4-wireguard@archiver.kernel.org
	public-inbox-index wireguard


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/com.zx2c4.lists.wireguard


AGPL code for this site: git clone https://public-inbox.org/ public-inbox