Messages

1

24.7 Production Series / Re: DNSCrypt-Proxy logs no longer show after upgrade to 24.7

« on: September 25, 2024, 08:58:28 am »

There was a recent submission which probably fits here...

https://github.com/opnsense/core/commit/2a1ccae9

# opnsense-patch 2a1ccae9


Cheers,
Franco

This solves the issue for me, thanks! 

2

24.7 Production Series / Re: 24.7.3 clean install & DNSCrypt proxy logs

« on: September 22, 2024, 06:02:35 pm »

I'm seeing the same issues on OPNsense 24.7.4_1-amd64. However, even when setting no limit and selecting all categories via multi-select, no logs are shown. Any idead how to fix this?

3

23.7 Legacy Series / Re: Dpinger broken

« on: December 31, 2023, 01:52:03 pm »

Well, turns out this one is a combined OPNsense AND layer 8 issue:
https://github.com/opnsense/core/issues/6907
Increasing "Time period" to a higher value allowed Dpinger to come up again.

4

23.7 Legacy Series / Re: OPNSense and Vodafone Cabel disconnects every ~4h

« on: December 22, 2023, 02:55:12 pm »

Hi,
my OPNsense looses internet connection every 3-4h. Restarting the box fixes the issue.

Are you a customer of Vodafone West (former Unitymedia) by any chance?
You could try adding

Code: [Select]

supersede dhcp-server-identifier 255.255.255.255 under Interfaces->Your WAN Interface->DHCP client configuration (Advanced)->Option Modifiers

This worked for me as Vodafone is doing funky stuff with their DHCP (it's hidden behind a relay causing IP renew request going to the wrong server, thus triggering an IP lease timeout).

5

23.7 Legacy Series / Re: Dpinger broken

« on: November 23, 2023, 02:15:59 pm »

Hi,

the issue persists in OPNsense 23.7.9.
Unfortunately logging is proving less than helpful. Any idea on how to diagnose this?
As it stands, Multi-WAN failover is broken because of this issue.

6

23.7 Legacy Series / Re: Dpinger broken

« on: November 11, 2023, 02:29:47 pm »

Hi,

just updated to OPNsense 23.7.8, unfortunally the issue persists
Any ideas on how to proceed as I can't seem to get any useful info from logs?

Thanks!

7

23.7 Legacy Series / Re: Dpinger broken

« on: October 26, 2023, 08:20:07 pm »

good day
I have the same problem with my gateway, I already updated the latest version today, and I still have the same problem

Hi,
the issues are different as I don't get such an error message. Hence, I suspect different root causes.

8

23.7 Legacy Series / Re: Dpinger broken

« on: October 24, 2023, 09:46:57 pm »

Hi,

sorry for the delayed reply, it's been a busy start of the week!

- Is DPinger still "RUNNING" in services or stopped?
- Does it help to restart it?
- Is there any information in your log file about dpinger when you reconnect?
- What kind of IPs are you pinging? Is it the next hop or some far host?

-Dpinger is still listed as running, in fast the second interface is being monitored as always.
-The Dpinger attached to the affected WAN interface is stopped and doen't come up when restarted (tried via GUI).
-The only informating from the gateway log is "Reloaded gateway watcher configuration on SIGHUP".
-The monitoring IPs used are 8.8.8.8, 1.1.1.1 and others. I tried several to no avail.

Long time no see. Hope you are doing good!

Can you be a little more specific?

What's the error message? What does it try to start on the command line? How are your gateways set up (far gateway used)?

Thank you very much I'm well! I hope the same is true for you
It's been quite some time indeed, one could say OPNsense has been running too well 

Oh I wish there was an error message Other than "Reloaded gateway watcher configuration on SIGHUP" I can't see anything, even directly from the command line. A second dpinger thread required for the affected WAN simply never comes online. 

The affected WAN gateway (Vodafone Germany, DOCSIS 3.1, TC4400 modem) is setup as upstream and far. This worked for years before the update but one should never discount the possibility of the ISP breaking things... Thus I played around with several variations of these settings as well as "disable host route" just to be sure. The WAN gateway that isn't affected (i.e. failover 5G) is configured as far gateway and nothing else.

For me, enabling 'Disable Host Route' on my problematic gateway (I think) helped.

Maybe my setup is similar to yours:
- 2 ISP connections
- 2 separate opnsense routers
- Failover network between them, to facilitate 'cross' failover if 1 ISP is down

Thanks for chiming in!
My setup is quite different as both ISP uplinks are attached to the same OPNsense box with the second OPNsense box (just one ISP) at another independent location.

Right now I can only test on the primary box as messing around with gateways breaks remote access.

9

23.7 Legacy Series / [SOLVED] Dpinger broken

« on: October 22, 2023, 01:32:01 pm »

Hi,

since around 23.7.4 dpinger is broken for an IPv4 Gateway on two of my machines. Hardware is entirely different (Intel CPU + NIC vs. AMD CPU + Mellanox NIC).
I can't see anything in the logs that would help identify the root cause. This is particularly annoying as one system is setup with a gateway group to allow failover to another WAN interface.
Oddly enough, the other WAN interface (also IPv4) doesn't exhibit this issue. Could this be related to the interface settings? At least those are a factor that's identical in both systems experiencing this issue (ISP Vodafone Germany, supersede dhcp-server-identifier 255.255.255.255, reject leases 192.168.100.1, custom MAC address).
Patches fb336e3 and 89ee410 didn't solve this either.

Any support to get to the bottom of this is highly appreciated!

10

22.7 Legacy Series / Re: 22.7.8: freeradius and bash issues

« on: November 20, 2022, 01:07:34 pm »

Hi, this fixed it for me:
https://forum.opnsense.org/index.php?topic=31101.msg150007#msg150007

11

21.7 Legacy Series / Re: Unbound custom options via community repo

« on: May 22, 2022, 01:12:24 pm »

Hm, maybe I missed it during rebase for .pkg extension

Any chance it's coming back?

12

21.7 Legacy Series / Re: Unbound custom options via community repo

« on: May 18, 2022, 06:17:37 pm »

As no SSL code is involved inside the plugin it will also work with libre (I just tested it)

Sorry for reviving this old thread, but was the plugin removed from your comunity repo? For some reason I can't seem to find it anymore

13

22.1 Legacy Series / Re: os-ddclient

« on: April 08, 2022, 02:50:41 pm »

That's exactly what I use and the exact setup.  I have my host.domain.tld and the associated password generated for that host and that's what I use for username and password, works for me.

Ah, so you're using host.domain.tld for both host- and username. Now it works for me as well! Thanks!
Previously I set username to the username for logging into HE's DNS service.

Now I'm just stuck at adding Noip as a secondary service

14

22.1 Legacy Series / Re: os-ddclient

« on: April 07, 2022, 11:31:59 am »

Are you using HE or HE TunnelBroker ?  Really depends which service you're using and what you're using to check the IP to update to their DNS.

If using dns.he.net to manage DNS, the record must be in place and set as a 'dynamic' record.

What steps have you done so far?

I'm using HE's DynDNS service.

• Service: HE.net
• Username: HE Login Username
• Password: HE Login Password
• Hostname: myhostname.com
• Check ip method: Interface
• Force SSL: Yes
• Interface to monitor: WAN_Interface

The log says "Bad authorization (username or password)", regardless if I use the HE login password or the specific DDNS key.

15

22.1 Legacy Series / Re: os-ddclient

« on: April 05, 2022, 02:51:14 pm »

I can't seem to get this working with Hurricane Electric. It would be great if anyone who did could share their configuration

Also, it would be great if there were an indicator showing the currently cached IP, just like with the old dynDNS solution. Just so it's easy to check if IPs are being updated successfully.