Messages

1

24.1 Legacy Series / Dynamic DNS - cpanel update

« on: February 17, 2024, 10:54:11 am »

Now the old dynamic dns plugin does not work with 24.1, I'm stuck regarding how to update using the cpanel method, which is like this:

https://host.com/cpanelwebcall/<random string>

Which returns:

ipv4: xxx.xxx.xxx.xxx

I've tried working through google and some of the examples but I cannot obviously work out how this is supposed to work.

Can someone give an idiots guide to getting cpanel dynamic IP working again?

Thanks.

2

23.7 Legacy Series / Re: 23.7 upgrade from 23.1 results in DNS issues

« on: September 21, 2023, 01:19:49 pm »

Finally managed to look into this today.

Upgrading to: OPNsense 23.7.1_3-amd64 from 23.1.11_2 via the GUI.

In SERVICES: UNBOUND DNS: GENERAL

--> Enable Unbound - Gets unchecked during the upgrade

Checking this allows for DNS resolution to work again but not device.customdomain.

--> Register DHCP Static Mappings however also gets unchecked during the upgrade.

Checking that gets me back to how it was in 23.1 in that device.customdomain works.

Edit: It sounds like the above from Franco will resolve this issue. I've still got my 23.1 VM so I'll try the fix when 23.7.5 comes out by doing a full upgrade again.

3

23.7 Legacy Series / Re: 23.7 upgrade from 23.1 results in DNS issues

« on: September 07, 2023, 10:53:31 pm »

I’ll spend a bit of time messing about with this this weekend to get answers.

Couldn’t turn the internet off yet, I’d get an unhappy other half. 

4

23.7 Legacy Series / Re: 23.7 upgrade from 23.1 results in DNS issues

« on: September 07, 2023, 11:32:58 am »

Seems like a pretty significant bug if multiple users have seen it happen 

As for custom domain, I think the only place it is set is here:

SYSTEM: SETTINGS: GENERAL

Domain "customdomain"

I'll have to boot back into 23.7 to get some unbound logs.

5

23.7 Legacy Series / Re: 23.7 upgrade from 23.1 results in DNS issues

« on: September 04, 2023, 09:51:06 pm »

Just waiting patiently

There are currently no open issues regarding DNS post 23.7.3

This may be the case, but the upgrade for me has caused two different issues, both DNS related.

Some guidance as to why the domain stuff isn’t working (or what to look for) may yield clues, but for now I’m sticking with 23.1.

Edit: Switched between 23.7.3 and 23.1 a few times. Black and white working/not working for me.

23.1.11 device.customdomain works
23.7.3 device.customdomain does NOT work

So there is clearly something between 23.1.11 and 23.7.3 that is causing this, if someone can provide some guidance as to where the problem might lie then I can do some more digging.

6

23.7 Legacy Series / 23.7 upgrade from 23.1 results in DNS issues

« on: September 03, 2023, 12:57:08 pm »

I've been running opnsense 23.1 flawlessly I think pretty much from release (I have had the odd issue with opnsense prior to 23.1, but effectively 99.9% uptime for many years since switching from pfsense).

Yesterday I updated to 23.7.3 and immediately starting having issues.

First off was that I was not getting any DNS responses (I could connect via IPs OK) - for some reason "Enable Unbound" was not ticked anymore. Ticked, now getting DNS responses once unbound started.

HOWEVER, how my custom domain does no longer work.

For example, if I had server1.customdomain it would originally have responded with the IP address.

Now I get:

Server:      10.10.1.1
Address:   10.10.1.1#53

** server can't find server1.customdomain: NXDOMAIN


server1.local DOES however work.

All my overrides still work too.



Thankfully as I run this as a VM I rebooted into my 23.1 instance - everything working again.


What has changed in 23.7 that A) meant that unbound DNS did not automatically start because it had been unchecked to do so and B) Why is my custom domain stuff working?

In the mean time I've reverted back to 23.1, as a number of things rely on the device.customdomain tag and thus dont work properly...!

I've had a fiddle, but at the end of the day this is a home setup so I've run out of debug time and skills!

Many Thanks!

7

22.1 Legacy Series / Re: 22.1.6 Update - Cannot access certain websites/services

« on: April 19, 2022, 11:32:13 pm »

If Twitter.com and Tiktok.com work while others like Facebook.com do not, this would lead me to believe that IPv6 connectivity is broken while IPv4 works.

Why? Twitter and Tiktok rely solely on IPv4, while many others also use IPv6. IPv6 having the higher priority, this could mean that the IPv6 DNS addresses are resolved (possibly via IPv4) but cannot be reached for one reason or the other.

This can easily be checked by "ping -4 facebook.com" and "ping -6 facebook.com". Should IPv6 really be the culprit, one can then check every single building block (i.e. DNS, routing, firewall) and see what is the root cause - or disable IPv6 altogether.

Thought that might be the problem, but I totally disabled IPV6, no change...! Although I did not try pinging ipv6 but given nothing had an IPV6 address I can't see how it would be?

8

22.1 Legacy Series / Re: 22.1.6 Update - Cannot access certain websites/services

« on: April 19, 2022, 11:11:36 pm »

Checked all the above, no dice.

Also updated to 22.1.4 - same issue.

Absolutely nothing obvious, so going to stick with 22.1.3.

This is obviously a major bug because the only way out so far is to reinstall a earlier version.

9

22.1 Legacy Series / Re: 22.1.6 Update - Cannot access certain websites/services

« on: April 17, 2022, 09:30:58 pm »

I've had the same thing, I've had to reinstall and put a config on from 22.1 but can't put it all back as can't reinstall the packages.

From what I can tell on boot up on the console I see some DNS config issue (looks like it flashes past saying error in DNS config) after the upgrade which then appears OPNSense can't do any DNS look up's after upgrade.

I was just using unbound as a forwarder for DNS but I've changed to do the look ups and going to set the system DNS to 127.0.0.1 to see if this works but having kids constantly using the internet it's difficult to be able to try things!

You can specify a version via the firmware settings and 'other' option, I used "22.1/MINT/22.1.3/OpenSSL" and its updated everything to 22.1.3 and allowed me to install my plugins. I suggest you try the same.

I also tried a factory reset on 22.1.6 but then DNS servers would not start "no such user: dhcpd". So I had to reinstall then to the USB image of 22.1.2.

Are you seeing more firewall blocking? I thought i'd seen more default deny happening in real time.

Yes, randomly I would see LAN to WAN blocked in the lists even though no LAN routes had changed (Allow all to everything!)

Something very broken in 22.1.5/6 for me, not going to risk 22.1.4 for the moment. Reverting is a pain as you can't do it via the revert command as it can't contact the servers!

Sadly you can't seem to make a 22.1.6 USB easily so I can't even try a live boot.

10

22.1 Legacy Series / 22.1.6 Update - Cannot access certain websites/services

« on: April 17, 2022, 07:46:35 pm »

Updated today to 22.1.6, however once I had done that I loose access to random areas of the internet.

Gmail/Exhange - Fine, iCloud/IMAP - Nope!
Certain websites load, others don't
DNS resolves to the IP correctly, but website itself doesn't load. I can ping it, just not visit it (starts to load, then stops).

Even opnsense can't even check for updates, rollback using opnsense-revert, just continually tries "....".

I've reverted back to 22.1.2 by reinstalling via USB and reloading my config.

Absolutely nothing in the logs to indicate anything wrong. But the problem now is I can't even install all my plugins as...

Installation out of date. The update to opnsense-22.1.6 is required.

However, if I update to 22.1.6 then it all falls apart again.

What has changed in the last two or three versions that would make a connection partially work?

Never had an update issue before with opnsense but this one was totally crippling given opnsense itself couldn't contact its servers to roll anything back!

Any suggestions?

Edit: Updated to 22.1.3 via 'other' = 22.1/MINT/22.1.3/OpenSSL and installed all my missing plugins. All is OK on this version too. Going to leave updating for now...

11

21.1 Legacy Series / Freedns Updates now fail after update

« on: June 02, 2021, 03:32:38 pm »

Updated over the weekend to:

PNsense 21.1.6-amd64
FreeBSD 12.1-RELEASE-p16-HBSD
OpenSSL 1.1.1k 25 Mar 2021

Only to find that Dynamic DNS with freedns has stopped working...

2021-06-02T13:11:21   config[74506]   /services_dyndns_edit.php: Dynamic DNS (----.com via freeDNS): _update() starting.   
2021-06-02T13:11:21   config[74506]   /services_dyndns_edit.php: Dynamic DNS (----.com): running dyndns_failover_interface for wan. found pppoe0   
2021-06-02T13:11:21   config[74506]   /services_dyndns_edit.php: Dynamic DNS (----.com):**IP** extracted   
2021-06-02T13:11:21   config[74506]   /services_dyndns_edit.php: Dynamic DNS: updatedns() starting
2021-06-02T13:11:23   config[74506]   /services_dyndns_edit.php: Dynamic DNS (----.com): (Unknown Response)   
2021-06-02T13:11:23   config[74506]       
2021-06-02T13:11:23   config[74506]   /services_dyndns_edit.php: Dynamic DNS (----..com): PAYLOAD: Error 404 : Page not found   
2021-06-02T13:11:23   config[74506]   /services_dyndns_edit.php: Dynamic DNS (----..com): Current Service: freedns   
2021-06-02T13:11:23   config[74506]   /services_dyndns_edit.php: Dynamic DNS (----..com): _checkStatus() starting.

This has been working perfectly up to that point, and having changed the key, reinstalled and deleted/re-entered the setup it still isn't working again.

Manually updating via the website works just fine.

What has broken?

Thanks!