Messages

Hmm.. that's interesting. I did a factory reset and that made no difference. If I bypass opnsense and connect directly to my ISP router, then it works.

I might reinstall opnsense and see if that makes a difference.

Anyone have any idea on what might be causing this?

I recently started having a problem where I can't connect to discord through OPNSense. Not sure when exactly the problem may have started, since I did update OPNSense recently as well.

I am running the most current patches and updates.

I have tried connecting to Discord through PC and mobile, and neither works. If I bypass OPNSense (disabling wifi on mobile phone or connecting via eithernet directly to the ISP router that OPNSense is connected to), then Discord works fine, so it looks like the problem is definitely related to OPNSense.

I have tried factory resetting OPNSense back to defaults, but the problem still occurs.

The specific error I get is SSL_ERROR_RX_RECORD_TOO_LONG on Firefox and ERR_QUIC_PROTOCOL_ERROR on Edge. If I disable the QUIC protocol in Edge, I then get a ERR_SSL_PROTOCOL_ERROR instead.

Note, I have OPNSense setup in passthrough mode to the ISP router. Second note, Discord was working just fine until very recently (1-3 days ago).

Would appreciate any help on this!

Thanks.

I have a gateway group setup viz. WAN0, and WAN1.

The problem I noticed was that when WAN0 went down, DNS started failing. After much searching, the recommendations to fix this is to modify the default LAN rule and set the gateway to be the gateway group (from the default).

However, when I change the gateway for the default lan group, all DNS starts failing immediately (although traffic still seems to be working if the address has already been resolved).

Even if I set the default gateway to WAN0 for the rule (which is the default anyways), DNS still starts failing immediately.


Anyone have any ideas how to resolve this (or another option for getting DNS to work when WAN0 goes down)?

Note, I am using the resolver and not forwarding to any DNS servers.

Note... I am running the latest version of OPNsense.

I currently have a dual WAN setup with WAN0 being the primary, and WAN1 being the secondary / failover.

I would like to segment the traffic in my network such that the default gateway rule is that WAN0 is the primary, and WAN1 is the secondary, but for a subset of hosts (setup via an ALIAS), I would like the to invert the gateway rules so that WAN1 is the primary, and WAN0 is the secondary for that group.

Can someone point me in the right direction for how I could achieve this? Note, I am an OPNsense / router newbie.

I did manage to get a LAN rule working which allowed my ALIAS group to use WAN1 instead of the default WAN0, but I am not sure how to take the next step and have the ALIAS group also have WAN0 as the failover in case WAN1 goes down.

Thanks!