1
22.1 Legacy Series / Re: OPNsense on Proxmox Freezing Every Few Nights
« on: August 05, 2022, 05:48:35 am »
Same issue here, did you ever figure out what the problem was?
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
Virtual private networks / Re: Wireguard Client -> Client not working
« on: July 12, 2022, 05:09:03 am »
I'm attempting to access the OPNSense web interface, the Unbound DNS server and also ping the wireguard tunnel address.
My understanding is that the "Tunnel Address" is attached to the wireguard adapter, e.g. wg1 on the OPNSense server in my case.
When using the web diagnostics I can ping the tunnel address 10.0.10.1, but from another wireguard client my packets get stopped somewhere. I can access other private networks just fine such as 192.168.90.0/24.
Basically, what I'm trying to do is to have all wireguard clients access each other (10.0.10.0/24) AND have all wireguard clients have access to the OPNSense tunnel address (10.0.10.1). This means that when I'm logged in as a wireguard client I can access the Unbound server on this address and also the OPNSense web gui.
My understanding is that the "Tunnel Address" is attached to the wireguard adapter, e.g. wg1 on the OPNSense server in my case.
When using the web diagnostics I can ping the tunnel address 10.0.10.1, but from another wireguard client my packets get stopped somewhere. I can access other private networks just fine such as 192.168.90.0/24.
Basically, what I'm trying to do is to have all wireguard clients access each other (10.0.10.0/24) AND have all wireguard clients have access to the OPNSense tunnel address (10.0.10.1). This means that when I'm logged in as a wireguard client I can access the Unbound server on this address and also the OPNSense web gui.
3
Virtual private networks / Re: Wireguard Client -> Client not working
« on: July 11, 2022, 05:30:36 pm »
Here's some screenshots of my rules. Everything seems super straightforward except this weird issue.
4
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.
Pages: [1]