wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Chris <wireguard@spam-free.eu>
To: wireguard@lists.zx2c4.com
Subject: lineageos 17.1 no incoming
Date: Thu, 1 Oct 2020 17:24:56 +0200	[thread overview]
Message-ID: <63eb4370-74b1-d139-41b9-12963aa25d96@spam-free.eu> (raw)
In-Reply-To: <mailman.0.1601114111.20018.wireguard@lists.zx2c4.com>

I'm running the f-droid repo of the wireguard client on lineageos 17.1
After the tunnel is up:
I can ping the wireguard client, and I can initiate an outgoing connection 
through the tunnel.

However, a process binding on all interfaces will not see any incoming traffic 
on tun0.
The same process works fine with incoming traffic on wlan0.

Sending the TCP SYN from the wireguard server through the tunnel, never receives 
an ACK.

Openvpn does not show this behaviour.

As the tun0 interface successfully reacts to pings, I guess it may be an 
iptables problem.
I.e. the traffic on tun0 is differently firewalled than the traffic on wlan0.


  parent reply	other threads:[~2020-10-01 15:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.0.1601114111.20018.wireguard@lists.zx2c4.com>
2020-09-26 10:40 ` lineageos 17.1after autostart on boot tunnel not functioning Chris
2020-10-01 14:42   ` Chris
2021-07-14  5:49   ` Android: more than one tunnel Chris
2021-07-14  9:06     ` Simon McNair
2021-07-14 22:09     ` Eric Light
2021-07-14 23:55       ` iiiiiiiiiiii
2021-07-15  6:25       ` Chris
2020-10-01 15:24 ` Chris [this message]
2020-10-05 13:51 ` wg-quick up (on linux) fails in case of several default routes Chris
2020-10-06 12:20   ` Jason A. Donenfeld
2020-10-06 13:33     ` Chris
2020-10-06 13:47       ` Jason A. Donenfeld
2020-10-06 13:54         ` Chris
2020-10-06 13:58           ` Jason A. Donenfeld
2020-10-06 17:51             ` Chris

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=63eb4370-74b1-d139-41b9-12963aa25d96@spam-free.eu \
    --to=wireguard@spam-free.eu \
    --cc=wireguard@lists.zx2c4.com \


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