Messages

In my OPNsense, I use Ubound.
If I add a specific domain to be resolved by a particular DNS in Query Forwarding, it works.
However, adding DNS over TLS doesn't work.

Why?

I'm looking for a solution to the same problem.
I came across pfSense, which recently allowed you to use different hw if you have the same names: wan=WAN, lan=LAN, opt1=Sync, opt2=DMZ (https://docs.netgate.com/pfsense/en/latest/highavailability/settings.html#configuration-synchronization-settings-xmlprc-sync).

Is there anything like that in OPNSense, or is the idea to replicate the same behavior?

Thank you.

<gateways>
    <gateway_item>
      <interface>wan</interface>
      <gateway>xx.xx.xx.xx</gateway>
      <name>WAN_GWv4</name>
      <priority/>
      <weight/>
      <ipprotocol>inet</ipprotocol>
      <interval/>
      <descr/>
      <defaultgw>1</defaultgw>
    </gateway_item>
    <gateway_item>
      <interface>opt2</interface>
      <gateway>xx.xx.xx.5xxgateway>
      <name>xxxxxx_GWv4</name>
      <priority>255</priority>
      <weight>1</weight>
      <ipprotocol>inet</ipprotocol>
      <interval/>
      <descr>GW Wireiguard</descr>
    </gateway_item>
    <gateway_item>
      <interface>opt5</interface>
      <gateway>xx.xx.xx.xx</gateway>
      <name>xxxxx_GWv4</name>
      <priority>255</priority>
      <weight>1</weight>
      <ipprotocol>inet</ipprotocol>
      <interval/>
      <descr/>
      <monitor>xx.xx.xx.xx</monitor>
      <fargw>1</fargw>
    </gateway_item>
    <gateway_item>
      <interface>opt6</interface>
      <gateway>xx.xx.xx.xx</gateway>
      <name>xxxxx_GWv4</name>
      <priority>255</priority>
      <weight>1</weight>
      <ipprotocol>inet</ipprotocol>
      <interval/>
      <descr>GW Wireiguard 2 </descr>
    </gateway_item>
  </gateways>

WAN_GWv4 was the one deleted during update.

Can you provide a config.xml partial dump of the removed gateway_item sections only? The migration is discarding them for a specific reason.


Thanks,
Franco

After updating to the latest version (OPNsense 23.1_6-amd64), the Services widget shows the dd-client as stopped, but going into the dd-client page, it appears as running.

I have the same problem too. Trying from the command line, I get:

Code Select Expand

# /usr/local/etc/rc.filter_synchronize
send >>>
Host: xxx.xxx.xxx.xxx
User-Agent: XML_RPC
Content-Type: text/xml
Content-Length: 117
Authorization: Basic xxxxxxxxxxxxxxxxxxxxx
<?xml version="1.0"?>
<methodCall>
<methodName>opnsense.firmware_version</methodName>
<params>
</params></methodCall>received >>>
error >>>
fetch error. remote host down?

How can I solve the issue?

Hi all,
I tied to find a solution, but I was not able.
Is there a way to enable and use the APU2 hardware watchdog in OPNSense?

This is very helpful if you have units that are not physically managed.

Please let me know.
Thank you.
Best,

Hi all,
I have an issue with a Wireguard site-to-site VPN.

Here is the situation:
- I have two OPNsense boxes (A and B).
- I set up box A a dynamic DNS service.
- Box B is behind a provider NAT, and I can't reach from outside.
- I set up Wireguard in both machines to have box B connect to box A.
- Everything works perfectly but:
when the IP of box A changes, the Dynamic DNS is updated, but the connection between the two boxes is not restored until I reboot box B (I haven't tested rebooting only Wierguard service at the moment).

Where is the problem?
How can I solve that?
May I add a script to reboot Wireguard when the remote IP changes or try to force it to reconnect when it loses the connection?

Thank you.
best,

Hi all,
The FreeRadius plugin, available in the OPNSense, doesn't support the XML-RPC when you have HA.
Is there any plan to support soon?

Thank you.
Best,