Messages

This may be a futile battle: Your receiver seems to be optimized for (car) navigation. It may not even be capable to serve as a precise time source.

What you could try:

- Disable all PPS processing on the client. Even if the receiver should "emulate" this signal over USB, it won't be reliable.

- Limit message types on the receiver to only the NMEA types required for timing. This will "free up" bandwidth and maybe enable the receiver to report more often, giving a more plausible signal to the client.

- Increase comm speed from 4800 to something higher on the receiver. Same as before, this may enable the receiver to give more regular reports.

- Make sure the receiver has a good signal. If it looses the signal every now and then, the client will tend to view it as unreliable.

... but again, consider whether it's worth your time: You won't get precise timing out of this device anyway, you might be better off using internet time servers in the first place.

Mornin' All,

I noted that in Services/Router Advertisements you can only specify two IPv6 DNS server addresses. I would like to use more than that.

Is there a reason for this limitation, or is it just the UI?

Regards

Hi,

I'm using OPNsense as a VM on a Proxmox host. A single NIC is "passed through" to the VM as a PCI device. OPNsense then uses a number of VLANs on this connection and is routing between them.

This works great, but it also makes the VM "non-migrateable" because VMs using PCI devices directly can't be moved to another Proxmox host on-the-fly. The alternative would be to give up on the pass-through device and instead provide a Linux Bridge to the VM. This could easily be mirrored on a second host if the need should arise.

But that would be a totally new device to OPNsense and I expect that it would completly screw up its interface mapping. Is there a way to manage this (swap out A for B in some INI file) or would I need to do the whole setup from scratch?

Regards

The DNS server(s) may be set either system-wide or individually for each DHCP-enabled interface:

System/Settings/General allow to specify "system DNS", which OPNsense itself will use and which are passed on to DHCP-enabled interfaces by default

Services/DHCPv4/[Interface] allows to specify the DNS server(s) passed to this interface only. If nothing is defined here, the system DNS servers are used.

If both are blank, you can enable Unbound to resolve DNS names (Services/Unbound). In that case, you can additionally set a "Query Forwarding" for your local domain to point to the Windows DCs.

Regards