Messages

1

24.7 Production Series / Re: PSA: Test kernel with Intel fixes is available for testing

« on: November 04, 2024, 03:19:17 pm »

Running Intel4 after running Intel3 for 1.5 weeks.
No issues so far!

2

24.7 Production Series / Re: Traceroute / ICMP issue after 24.7.1 update

« on: August 20, 2024, 10:11:46 am »

Running ICMP2 kernel for 22 hours now and not seeing any reconnect from the Chromecast!
I think my Chromecast is the problem.

3

24.7 Production Series / Re: Traceroute / ICMP issue after 24.7.1 update

« on: August 18, 2024, 07:59:02 pm »

With icmp2 kernel i see multiple reconnects of a google chromecast "google tv" in my unifi dashboard.

Running kernel pf4 for a while now. And it looks like the reconnects are gone.

Maybe the reverts are the best for 24.7.2

4

24.7 Production Series / Re: Traceroute / ICMP issue after 24.7.1 update

« on: August 15, 2024, 09:06:11 am »

Ship the fix!

5

24.7 Production Series / Re: Traceroute / ICMP issue after 24.7.1 update

« on: August 14, 2024, 05:54:46 pm »

And a Confirmation from my side as well!

Windows 11 pro traceroute via IPv6 AND IPv4 is working fine!

6

24.7 Production Series / Re: Traceroute / ICMP issue after 24.7.1 update

« on: August 12, 2024, 10:25:05 am »

Great!

Can't help you with that.
But if more testing is needed today i can help.

7

24.7 Production Series / Re: Traceroute / ICMP issue after 24.7.1 update

« on: August 12, 2024, 10:20:09 am »

opnsense-update -zkr 24.7.1-pf4 restores traceroute functionality.

8

24.7 Production Series / Re: Traceroute / ICMP issue after 24.7.1 update

« on: August 08, 2024, 07:42:30 pm »

Experiencing the same behaviour here.

9

24.1 Legacy Series / Re: Requesting the TXT record for DHL.com : unbound, connection resets.

« on: February 09, 2024, 04:43:07 pm »

Yes over IPv6!
Tried IPv4, also all records available.

10

24.1 Legacy Series / Re: Requesting the TXT record for DHL.com : unbound, connection resets.

« on: February 09, 2024, 04:27:10 pm »

Windows 10 22h2, OPNsense 24.1.1

11

24.1 Legacy Series / Re: Requesting the TXT record for DHL.com : unbound, connection resets.

« on: February 09, 2024, 04:16:09 pm »

All records are comming through here!

Code: [Select]

Non-authoritative answer:
dhl.com text =

        "google-site-verification=MKYejQl1Mh9fB5dwrsO9d6xADpVZellFYmDBs6uHvI4"
dhl.com text =

        "mongodb-site-verification=0Crz9iHBXaQyTii6NECBJXDlmyUup51q"
dhl.com text =

        "ms-domain-verification=5253e385-6b1f-4621-b0a0-090e374e40ea"
dhl.com text =

        "Dynatrace-site-verification=8a64ad24-3b3a-4665-b8ac-0975fa5be9f6__a5mepuk85f2o7egbq5cmmlp8tu"
dhl.com text =

        "google-site-verification=HUVzQJOJmKyha5LCFbvFwjCDh5JMkC-85K5C-s44Lt0"
dhl.com text =

        "v=spf1 include:dpdhl._spf.dhl.com include:3a._spf.dhl.com include:3b._spf.dhl.com include:3c._spf.dhl.com include:3d._spf.dhl.com include:3e._spf.dhl.com include:3f._spf.dhl.com include:mrsc._spf.dhl.com include:e2ma.net include:spf.mandrillapp.com ~all"
dhl.com text =

        "docusign=6d733f59-f916-4426-9028-c800fc5e2ba1"
dhl.com text =

        "adobe-idp-site-verification=00c0593e27f3b625df20796c2aea6a9d18005694df716a444a53ac7242f672a1"
dhl.com text =

        "atlassian-domain-verification=mmsERGyn2rlOT8eOe12PbNcvgZ4mxzeOq+e75gQbAYUO3cOhU4Fr7+UfTRKRzrfs"
dhl.com text =

        "facebook-domain-verification=8vnu10tvn6novixz0fkg8ybx26kz1f"
dhl.com text =

        "amazonses:gtMOfHHBB2nwFoX+iXEWovWkRf66WFugJgKxjzCN9Rg="
dhl.com text =

        "onetrust-domain-verification=86d6b6dd18a743d9a30cf4cb40017e84"
dhl.com text =

        "nintex.625eb685a1608f0070bca981"
dhl.com text =

        "atlassian-domain-verification=zCudhHQPIDjcXLKuYWm5QqU2aeaWx4Ccq7RcoJj1KtTXDqxaYKpdcqkH3PnT8C8f"
dhl.com text =

        "cisco-ci-domain-verification=6f8bf0505ee35b0a464c20a0520dd8fd2da5bbfaa26ad53d20d6dc33cd536ab1"
dhl.com text =

        "smartsheet-site-validation=BwFwvtcb2t5Uqeanz8SefQ_4lIZvRQLd"
dhl.com text =

        "Dynatrace-site-verification=f913d8c2-f6d5-4265-9c7f-aae8784c0652__4u08f5qon49tv8mngsmruso1b0"
dhl.com text =

        "pardot1024731=05ff64dc9fea2fd92da4238a7c431480cd48736d513a8dfdeebf552c939afcd0"
dhl.com text =

        "sending_domain1024731=7b1368b64c62a7e74ebee33ffba6d1f1ea1a51f29564c1195a486733b0bc813f"
dhl.com text =

        "hm5bpdz3w772wpzb4xbw649h5dd7f6xs"
dhl.com text =

        "google-site-verification=QsnKi52v6M1z-N3dtyxAopCglJmE4GiEipCLZJxna1Y"
>

12

23.7 Legacy Series / [Solved] ACME 3.20 plugin multi domain (SAN) dns alias mode

« on: January 26, 2024, 01:25:56 pm »

Hi,

When i try to issue an certificate for *.example1.com and *.example2.com with DNS alias mode enabled the CN name could not be verified.

It looks like the ACME client is generating twice a txt to the DNS alias provider.
This should be one so the cname record on example1 and 2 is the same and could be verified.

Temp solution
When issuing a certificate without an alternate name set it works.
Right after that adding the alternate name again is works! (Because the first domain is already verified.)


After all it was DuckDNS which doesnt support multiple txt records!
Now using "desec.io" and everything is working fine!

13

23.7 Legacy Series / Re: How do I get rid of the suffix making my FQDNs resolve incorrectly?

« on: January 05, 2024, 11:48:16 am »

Add an trailing dot!

nslookup
google.com.

14

23.7 Legacy Series / Re: ACME Plugin does not use new settings, until reboot.

« on: December 16, 2023, 09:11:41 am »

Not tried an reboot yet but experiencing the same problems.

https://forum.opnsense.org/index.php?topic=37470.0

If i have some spare time left i will try to reboot.

15

23.7 Legacy Series / Re: Acme client 3.0.7 and Synology automation

« on: December 14, 2023, 10:57:53 am »

Also unable to deploy certificate to a Synology with 2fa enabled.

When running
acme.sh --home /var/etc/acme-client/home --deploy --deploy-hook synology_dsm -d "*.domain.com"

I am unable to authenticate against my Synology nas.

Is there way to run the automation settings in the CLI ?

Digging further is see that the config file isnt changed at all after modifying the device ID in the gui.
I have 2 certificates, the domain.conf of 1 has a device_id and device_name but with a wrong id.
The other domain doesnt have the device_id and device_name set.