1
Virtual private networks / Wireguard Client -> Client not working
« on: July 11, 2022, 05:16:24 pm »
I'm using the RoadWarrior setup and it's working well.
Wireguard Network:
Tunnel IP - 10.0.10.1/24
Peer IP - 10.0.10.2/24
Allowed Networks - 10.0.10.0/24, 192.168.90.0/24
I would like to access the web interface at 10.0.10.1, but I can't seem to get access to this (either ping or access to the web ui).
I can access the webui using 192.168.90.2 but I want to access it via the Wireguard server ip: 10.0.10.1
When using IP tables i would have the following rule to allow this:
iptables -A FORWARD -i wg0 -o wg0 -j ACCEPT
I couldn't figure out how to get this same functionality in OPNsense. I couldn't any examples of people in the forums wanting wg->wg client functionality.
I've attempted to have a look for dropped packets in the firewall log, but I see nothing related to this interface, it's like the packets just disappear or are silently dropped for 10.0.10.1 (this includes when attempting to use this as the DNS server), using my lan ip for the dns server works just fine.
Wireguard Network:
Tunnel IP - 10.0.10.1/24
Peer IP - 10.0.10.2/24
Allowed Networks - 10.0.10.0/24, 192.168.90.0/24
I would like to access the web interface at 10.0.10.1, but I can't seem to get access to this (either ping or access to the web ui).
I can access the webui using 192.168.90.2 but I want to access it via the Wireguard server ip: 10.0.10.1
When using IP tables i would have the following rule to allow this:
iptables -A FORWARD -i wg0 -o wg0 -j ACCEPT
I couldn't figure out how to get this same functionality in OPNsense. I couldn't any examples of people in the forums wanting wg->wg client functionality.
I've attempted to have a look for dropped packets in the firewall log, but I see nothing related to this interface, it's like the packets just disappear or are silently dropped for 10.0.10.1 (this includes when attempting to use this as the DNS server), using my lan ip for the dns server works just fine.