Coming soon - Get a detailed view of why an account is flagged as spam!
view details

This post has been de-listed

It is no longer included in search results and normal feeds (front page, hot posts, subreddit posts, etc). It remains visible only via the author's post history.

0
setting up tunneling for docker containers
Post Flair (click to view more posts with a particular flair)
Post Body

I want to use wireguard to restrict access to my containers. I have a couple of services running on the host (which is behind a NAT) and has the IP 192.168.206.35.

So I setup wireguard and able to successfully connect to it. Here's the server's config:

[Interface]
Address = 10.13.13.1
ListenPort = 51820
PrivateKey = 
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o eth  -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o eth  -j MASQUERADE

[Peer]
# peer1
PublicKey = 
PresharedKey = 
AllowedIPs = 10.13.13.2/32

I want to access other services as 10.13.13:<portNO> but only 192.168.206.35<portNO> works...

I want to do this as a way of restricting access within the virtual LAN. As presently anyone within the physical LAN can access.

Author
Account Strength
100%
Account Age
5 years
Verified Email
Yes
Verified Flair
Yes
Total Karma
4,632
Link Karma
1,783
Comment Karma
2,616
Profile updated: 4 days ago
Posts updated: 1 month ago

Subreddit

Post Details

We try to extract some basic information from the post title. This is not always successful or accurate, please use your best judgement and compare these values to the post title and body for confirmation.
Posted
1 year ago