Development discussion of WireGuard
 help / color / mirror / Atom feed
* wireguard and iptables redirect not work
@ 2020-08-24  1:43 Jérémy Prego
  0 siblings, 0 replies; only message in thread
From: Jérémy Prego @ 2020-08-24  1:43 UTC (permalink / raw)
  To: wireguard

hello all,

I am experiencing behavior that I do not want when I use wireguard as a
vpn client with the output at

I can no longer use iptables rules like thi:
iptables -t nat -A OUTPUT -p tcp -d -j REDIRECT --to-ports 10001

I have a daemon which listens in localhost on port 10001 and when I
activate wireguard, it receives nothing when I do a curl on ip

I specify that I use wg-quick with a relatively simple configuration
~# cat /etc/wireguard/vpn0.conf
Address =

PublicKey = XXXXXXX
AllowedIPs =
Endpoint = xxxxxxx:51820

if you have a solution so that I can do my iptables redirect with
wireguard enabled, I'm interested :)



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

only message in thread, other threads:[~2020-08-27  8:29 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-08-24  1:43 wireguard and iptables redirect not work Jérémy Prego

Development discussion of WireGuard

This inbox may be cloned and mirrored by anyone:

	git clone --mirror

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 wireguard wireguard/ \
	public-inbox-index wireguard

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone