adam:ONE® v4.11.1-240 Rapid Release

[David]

Version 4.11.1-240 has been published to Rapid Release on pfSense, VyOS and ASUS.

This is a release with important improvements to the prior rapid release (4.11.1-43).

• Added support for FreeBSD 15 (pfSense® 24.03 base OS version)
• Added support for MyTools to identify endpoint incorrect DNS server usage

Note that muscle features often make an appearance before the feature is rolled out on the dashboard as is the case for MyTools DNS server detection.

This Rapid Release: Rollout begins 29 April 2024

Scheduled Release for pfSense 24.03: 29 April 2024
Scheduled Release for all other platforms/versions: as soon as 13 May 2024

Use Rapid Release if you’re adventurous or directed by our support team.

Installation steps are at https://adamnet.io/rrhowto

Thank you

– Adam Networks team

[edanpedragosa]

Hi!

After upgrading today, adam-one does not want to run anymore…

Any idea?

I had to ssh run:
curl -sS https://dl.adamnet.works/pfsense/install4 | sh -s

then followed by:
service anmuscle.sh start

then it comes back to life again.

[edanpedragosa]

Interestingly, after upgrading:

1. MULTI-WAN no longer works.
2. Active Directory resolution stopped working too.
   Forwarding rule does not work.

[24.03-RELEASE][root@s.aimsnet.site]/var/log: grep "test.aimsnet.site" /var/log/anmuscle.log
D 2/5 17:43:10.961311 47743 services::DnsResolver::AsyncResolve() query 0x37aaebe584c0 + 0x37aaebe586f0 | A test.aimsnet.site
I 2/5 17:43:10.961338 47743 DNS? 172.27.77.0@50060 UDP4 test.aimsnet.site A | [DNS]
T 2/5 17:43:10.961344 47743 DNS+ 172.27.77.0@50060 UDP4 test.aimsnet.site A | flags [Q,RD] | answers 0 | authorities 0 | additionals 0
D 2/5 17:43:10.961381 47743 services::DnsProcessorTriggerEntities::Process() not found for test.aimsnet.site or test
D 2/5 17:43:14.284974 47743 DisplayHttpRequest() raw path /isblocked?path=test.aimsnet.site
D 2/5 17:43:14.284985 47743 DisplayHttpRequest() variable path = test.aimsnet.site
D 2/5 17:43:23.747531 47743 services::DnsResolver::AsyncResolve() query 0x37aaebe584c0 + 0x37aaebe586f0 | A test.aimsnet.site
I 2/5 17:43:23.747557 47743 DNS? 172.27.77.0@56914 UDP4 test.aimsnet.site A | [DNS]
T 2/5 17:43:23.747564 47743 DNS+ 172.27.77.0@56914 UDP4 test.aimsnet.site A | flags [Q,RD] | answers 0 | authorities 0 | additionals 0
D 2/5 17:43:23.747600 47743 services::DnsProcessorTriggerEntities::Process() not found for test.aimsnet.site or test
D 2/5 17:43:23.776900 47743 DisplayHttpRequest() raw path /isblocked?path=test.aimsnet.site
D 2/5 17:43:23.776911 47743 DisplayHttpRequest() variable path = test.aimsnet.site

3. mytools.management becomes inaccessible as well

Hence, I uninstalled adam:one for now and set back to default pure PFSense without filtering until everything is back to normal again.

Is there a way to downgrade to the previous rapid-release version or hopefully to a fixed version?

Thanks in advance!

[David]

@edanpedragosa each pfSense upgrade does require a re-install of adam:ONE® so that is expected.

For the forwarding issue, could you try and install again but capture log-level 6 and run adamone-issue that includes a forwarded query/result that didn’t work?

I will also create an internal ticket to invite you to a remote session to troubleshoot.

[edanpedragosa]

Hi David, it appears that the issue this time is the domain in the General Setup in PFSense.

Once I changed it to a different domain, adam:ONE lived happily ever after again in my network.

I am now a happy camper again.

Thank you too for your time this morning.

[David_Hofer]

wow ,thats impressive speed

[David]

Thank you for testing and validating @edanpedragosa … that fix is now in the latest rapid release, show notes going up momentarily!