Messages

1

24.7 Production Series / Re: DDNS with Porkbun - Req to update API hostname

« on: November 07, 2024, 08:45:07 pm »

Thank you both for your replies.

I've currently switched to Caddy to avoid any timing issues if the plugin isnt updated in time.  The maintainers at ddclient seem to be slow to get the commit merged.

2

24.7 Production Series / DDNS with Porkbun - Req to update API hostname

« on: November 06, 2024, 11:48:26 pm »

I've been using the ddclient backend with Porkbun for some time now and its been working flawlessly.  I've recently have been getting notifications from my Porkbun account that the API Hostname is going to be changed and that if I dont update the API hostname that the API will cease to work and it gives me a deadline of 12/1/24 to sort this out.

Is it possible someone can update the os-ddclient plugin to reflect this change please?  The letter I received is pasted below.

Code: [Select]

Hello there,

The reason you are receiving this email is because you have an API key associated with your account and are sending commands to a deprecated API hostname. We sent a previous warning on 2024-10-11. In order to ensure that any apps or tools you may have that utilize our API continue to work, we wanted to let you know about some upcoming critical updates.

We know these kinds of changes are annoying but the time has come to separate the processing of incoming API commands from our website. In previous documentation the hostname porkbun.com was used for the API but we have recently updated it to api.porkbun.com and in the near future will start enforcing its use. Please update the hostname for our API to api.porkbun.com as soon as possible.

CRITICAL UPDATE DETAILS

Type: API Hostname Change

Old Value: porkbun.com

New Value: api.porkbun.com

Deadline: 2024-12-01 00:00:00 UTC

Please note that after the deadline, API calls made to the old hostname will no longer be allowed. If you have any questions or concerns please contact support.


Thank you,
The Porkbun Team

3

24.7 Production Series / Re: UPnP no sessions appearing

« on: September 21, 2024, 04:50:43 pm »

Check your port forward rules, looks like one of your redirects is causing a conflict.

4

24.7 Production Series / Re: Disable hardware checksum offload

« on: September 21, 2024, 04:44:40 pm »

If you have SSH or console access, you  can select Option 13 and choose a backup prior to the changes that locked you out.

5

General Discussion / Re: UPnP service doesn't seem to work

« on: September 04, 2024, 11:56:16 pm »

Have you tried using the following port range?

allow 88-65535 192.168.1.100 88-65535

Source ports are randomized so using a static port wont match unless you've made a specific static outbound NAT rule.  And check off Log Packets if you like.

My UPnP Service Status shows multiple connections to the Gaming Consoles I use UPnP for.

6

24.7 Production Series / Re: FQ-Codel for bufferbloat reduces upload speed by 4

« on: August 21, 2024, 05:03:02 am »

I have the same config as you with some minor differences in the bandwidth speeds and I don't use ECN within the Queues.  ECN is only enabled on the Pipes.  I'm not seeing the symptoms you're seeing though.  How's your CPU usage when running these speedtests?

7

24.7 Production Series / Re: Problem with DDClient and its new Widget.

« on: August 07, 2024, 07:15:13 pm »

Everything is working properly and my DNS entries at my registrar get updated as well if there is an IP change.  There just isnt a time or an IP updated in the Opnsense plugin.

If you go into the SSH shell and issue this command:

Code: [Select]

configctl ddclient statistics
Do you get any statistics back? I get this while using duckdns:

I get this

{"hosts": {"host.domain.com host.domain.com\n": {"host": "host.domain.com host.domain.com\n"}}, "version": "ddclient-3.11.2", "updated": 1722864864}

8

24.7 Production Series / Re: Problem with DDClient and its new Widget.

« on: August 06, 2024, 11:50:51 pm »

PM Sent, thank you.

9

24.7 Production Series / Problem with DDClient and its new Widget.

« on: August 06, 2024, 08:01:24 pm »

I get this with the new widget in the attached picture, a blank space with no IP for Current IP or a Date and Time for Updated.  I've obscured the hostname.  I'm pretty sure there's just an issue with how the ddclient.cache file is generated on my opnsense.  I've uninstalled and reinstalled the plugin but I still get this blank in the plugin.  Everything is working fine with ddclient otherwise and I'm getting successful updates in the logs using Porkbun API as a service.

My ddclient.cache file looks like this:

## ddclient-3.11.2
## last updated at Mon Aug  5 09:34:24 2024 (1722864864)
host=host.domain.com host.domain.com


In Services: Dynamic DNS: Settings, the Current IP and Dated are blank there as well.

Code: [Select]

2024-08-06T12:48:22-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T11:48:21-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T10:48:21-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T09:48:20-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T08:48:20-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T07:48:19-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T06:48:18-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T05:48:17-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T04:48:16-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T03:48:15-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T02:48:14-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T01:48:13-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-06T00:48:12-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-05T23:48:11-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-05T22:48:10-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-05T22:34:37-04:00 Notice ddclient SUCCESS: updating ipv4: skipped: host.domain.com address was already set to xxx.xxx.xxx.xxx.
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: {"status":"SUCCESS","cloudflare":"enabled","records":[{"id":"399246864","name":"host.domain.com","type":"A","content":"xxx.xxx.xxx.xxx","ttl":"600","prio":"0","notes":null}]}
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE:
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: content-language: en-US, en
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: referrer-policy: origin
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: x-xss-protection: 1; mode=block
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: x-content-type-options: nosniff
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: x-frame-options: sameorigin
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: strict-transport-security: max-age=63072000; includeSubDomains; preload
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: pragma: no-cache
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: cache-control: no-store, no-cache, must-revalidate
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: expires: Thu, 19 Nov 1981 08:52:00 GMT
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: set-cookie: BUNSESSION2=ck1; path=/; secure; HttpOnly; SameSite=Lax
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: server: openresty
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: set-cookie: AWSALBCORS=ck1; Expires=Tue, 13 Aug 2024 02:34:37 GMT; Path=/; SameSite=None; Secure
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: set-cookie: AWSALB=ck1; Expires=Tue, 13 Aug 2024 02:34:37 GMT; Path=/
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: content-type: application/json
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: date: Tue, 06 Aug 2024 02:34:37 GMT
2024-08-05T22:34:37-04:00 Notice ddclient RECEIVE: HTTP/2 200
2024-08-05T22:34:37-04:00 Notice ddclient SENDING: data="{\"secretapikey\":\"sk1\",\"apikey\":\"pk1\"}"
2024-08-05T22:34:37-04:00 Notice ddclient SENDING: header="Content-Type: application/json"
2024-08-05T22:34:37-04:00 Notice ddclient SENDING: url="https://porkbun.com/api/json/v3/dns/retrieveByNameType/domain.com/A/host"
2024-08-05T22:34:37-04:00 Notice ddclient SENDING: request=POST
2024-08-05T22:34:37-04:00 Notice ddclient SENDING: max-time=120
2024-08-05T22:34:37-04:00 Notice ddclient SENDING: connect-timeout=120
2024-08-05T22:34:37-04:00 Notice ddclient SENDING: user-agent="ddclient/3.11.2"
2024-08-05T22:34:37-04:00 Notice ddclient SENDING: include
2024-08-05T22:34:37-04:00 Notice ddclient SENDING: silent
2024-08-05T22:34:37-04:00 Notice ddclient SENDING: Curl system cmd to https://porkbun.com
2024-08-05T22:34:37-04:00 Notice ddclient UPDATE: updating host.domain.com
2024-08-05T22:34:37-04:00 Notice ddclient INFO: setting ipv4 address to xxx.xxx.xxx.xxx for host.domain.com
2024-08-05T22:34:37-04:00 Notice ddclient WARNING: 'if-skip' is deprecated and does nothing for IPv4


10

24.7 Production Series / Re: New Dashboard short-comings

« on: August 06, 2024, 07:35:36 pm »

Disregard, started a proper new thread.

11

24.7 Production Series / Re: New Dashboard

« on: July 26, 2024, 04:00:41 am »

Everything is running good and its looking good now too  .   Thank you for all your hard work.

I wanted to point out that CPU widget says I have 8 cores 4 threads.

Its an E3-1240v3.  It should say 4 Cores 8 Threads.

Anyone else seeing this swap in Cores vs Threads?

12

24.1 Legacy Series / Re: Duplicate and growing number of entries in Universal Plug and Play: Status

« on: May 28, 2024, 03:04:42 am »

Please keep us updated on all the upcoming details.  I got my popcorn ready.   

13

24.1 Legacy Series / Re: Duplicate and growing number of entries in Universal Plug and Play: Status

« on: May 26, 2024, 07:02:03 am »

Is this the same problem in pfSense?  Seems Mr. Provost is pretty active over there, hmmmmm.


https://redmine.pfsense.org/issues/15470

14

24.1 Legacy Series / Re: Duplicate and growing number of entries in Universal Plug and Play: Status

« on: May 15, 2024, 09:22:20 pm »

Does this not affect anyone using vanilla FreeBSD?  Seems to be no incentive in updating the port even though miniupnpd has been updated 3 times since the last port was updated a year ago. 

15

24.1 Legacy Series / Re: Delete old OpenVPN interface under Firewall Rules

« on: April 24, 2024, 01:27:44 pm »

Is it listed when you go to the Shell and run the ifconfig command?