beasthouse

edit: I was able to get something working by setting the DNS in Peer Settings and on the Client to 1.1.1.1, then tried my PiHole IP, and that works too. It was 10.253.0.1 that was not working. root@Odin:~# rm /var/log/wg-quick.log root@Odin:~# cat /var/log/wg-quick.log wg-quick down wg0 [#] ip link delete dev wg0 [#] logger -t wireguard 'Tunnel WireGuard-wg0 stopped' [#] iptables -t nat -D POSTROUTING -s 10.253.0.0/24 -o br0 -j MASQUERADE [#] ip -4 route flush table 200 [#] ip -4 route add unreachable default table 200 [#] ip -4 route add 10.0.0.0/24 via 10.0.0.1 dev br0 table 200 wg-quick up wg0 [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 10.253.0.1 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] ip -4 route add 10.253.0.2/32 dev wg0 [#] logger -t wireguard 'Tunnel WireGuard-wg0 started' [#] iptables -t nat -A POSTROUTING -s 10.253.0.0/24 -o br0 -j MASQUERADE [#] ip -4 route flush table 200 [#] ip -4 route add default via 10.253.0.1 dev wg0 table 200 [#] ip -4 route add 10.0.0.0/24 via 10.0.0.1 dev br0 table 200

I am getting the same issue as @x86intel - I followed what @erak had done and now my toggle bounces back to `inactive` when I attempt to set it to `active`. Output of the script below: ``` root@Odin:/tmp# php testnet.php Array ( [DHCP_KEEPRESOLV] => yes [DNS_SERVER1] => 10.0.0.1 [DNS_SERVER2] => 8.8.8.8 [DNS_SERVER3] => [DHCP6_KEEPRESOLV] => no [BONDING] => yes [BONDNAME] => bond0 [BONDNICS] => eth0,eth1 [BONDING_MODE] => 1 [BONDING_MIIMON] => 100 [BRIDGING] => yes [BRNAME] => br0 [BRNICS] => bond0 [BRSTP] => no [BRFD] => 0 [DESCRIPTION:0] => [PROTOCOL:0] => ipv4 [USE_DHCP:0] => no [IPADDR:0] => 10.0.0.10 [NETMASK:0] => 255.255.255.0 [GATEWAY:0] => 10.0.0.1 [METRIC:0] => [USE_DHCP6:0] => yes [IPADDR6:0] => [NETMASK6:0] => [GATEWAY6:0] => [METRIC6:0] => [PRIVACY6:0] => [MTU] => [TYPE] => access ) BRIDGING: 'yes' BRNAME: 'br0' BONDING: 'yes' BONDNAME: 'bond0' ethX: 'eth0' device: 'br0' ```