Closed war59312 closed 3 years ago
Should also mention I needed to do:
chmod 600 /etc/wireguard/wg0.conf
ip -a does not work either
Can just do ifconfig wg0
And to generate the private and pub key while in /etc/wireguard folder:
wg genkey | tee privatekey | wg pubkey > publickey
Well, it's not really working, probably config issue.
wg show is blank
Not sure why not working:
tcpdump port 16666
20:00:30.570112 IP ec2-52-202-215-126.compute-1.amazonaws.com.58971 > 192.168.10.50.16666: Flags [S], seq 842529555, win 26883, options [mss 1460,sackOK,TS val 1338607382 ecr 0,nop,wscale 7], length 0
Looks correct:
[Interface]
Address = 192.168.10.50/24
PrivateKey = theKey
ListenPort = 16666
PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o ovs_bond0 -j MASQUERADE; sleep 5; ip route add 192.168.10.50/32 dev wg0;
PostDown = iptables -D FORWARD -i wg0 -j ACCEPT; iptables -t nat -D POSTROUTING -o ovs_bond0 -j MASQUERADE
[Peer]
PublicKey = theKey
# AllowedIPs = 192.168.10.1/24
My home network is using 192.168.10.0/24. Using ovs_bond0 as yes lan ports 1 and 2 are bonded.
Port 16666 is open in firewall but still showing closed on can you see me
Reply from 192.168.10.50: bytes=32 time<1ms TTL=64
DS1815+ Works Great