Menu

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.

Show posts Menu

Topics - Manual6938

#1
I have a similar rule as described here to redirect any DNS request from my network to local DNS servers. : https://forum.opnsense.org/index.php?topic=9245.0

However this only works properly when the DNS is redirected to the gateway itself or to an external DNS server. If I provide an internal IP for my local DNS server, all of the DNS requests fail to resolve. In the DNS server log, it sees the requests and shows that it has responded, but the connection times out at the client side and it never resolves.

I tried both an Unbound DNS server and a Pi Hole, and both have the same behavior. If the client sets the local DNS manually and the firewall rule is disabled, the connection is fine, so it's definitely something with this redirection that is breaking it.

Is there any additional rule I would need to create?
#2
23.7 Legacy Series / Trouble with Traffic Shaping
November 10, 2023, 07:51:41 PM
Hi there,

I'm trying to set up my traffic shaping to prioritize up/down traffic from my desktop and deprioritize everything else. My network speed is 1200Mbps/35Mbps. I have configured a 1200Mbps pipe down and 35Mbps pipe up, with a priority and nonpriority queue for each of them (priority weight = 10, nonpriority weight =1). I have also set up the rules for each of the clients to be sent to each queue correctly which I can see in the status.

However, when I run a speedtest with these queues and rules enabled, I can only pull about 600Mbps down (even as the only client downloading). If I increase the pipe to ~1800 down, then it pulls my full network speed but I'm assuming the shaping wouldn't work in this case. Is there anything obvious I'm missing?
#3
EDIT: Never mind,  it now allows me to after fully toggling Wireguard off and on. I did a system restart as well as a restart through the widget but it seems like those two were not sufficient.

Hello,

I am coming from pfSense and I'm following this guide to set up VPN routing: https://docs.opnsense.org/manual/how-tos/wireguard-selective-routing.html

I've made it through to creating the gateway (Step 6) and I can see handshakes happening in the WG status. However I'm unable to assign an IP address to the gateway because the interfaces has IPv4 type set to "None" which the guide instructs to do. This is the error given when attempting creating the gateway:
The following input errors were detected:
    Cannot add IPv4 Gateway Address because no IPv4 address could be found on the interface.

Am I missing something obvious? Any help would be appreciated very much.