Messages

Hi @maurice

Could you please also enable this update for aarch64?

"check for update" doesn't load the updated plugin (while it works for the x64 repo counterpart)

Danke schön


Edit:
Discussed offline with @maurice, this will be featured in next update for aarch64

Cheers

Dear all,

Quick update on this issue.
PR raised and merged: https://github.com/opnsense/plugins/pull/4913

Expected to be fixed in next update.

Great learning opportunity for me.
Sorry for missing action on the dev cycle
Kudos to Franco reactivity and support

Slashing: maybe mark this thread as solved?

If someone needs it and doesn't want to mess around, here's a quick-dirty solution.
Delete the files:

Code Select Expand

/etc/rc.conf.d/shadowsocks_libev
/etc/rc.conf.d/ss_local
/usr/local/etc/rc.d/opnsense-ss-local
/usr/local/opnsense/service/templates/OPNsense/Shadowsocks/shadowsocks_libev
/usr/local/opnsense/service/templates/OPNsense/Shadowsocks/ss_local
/usr/local/opnsense/service/templates/OPNsense/Shadowsocks/ss_local.conf
And copy the files from the attachment. A reboot may be necessary.

Thanks for this, this works (tested on both x64 and aarch64)

Can you provide a PR? I'd rather move this forwards than backwards ;)

FWIW, this should work for now:

# pkg install shadowsocks-libev
# opnsense-revert -r 25.7.1 os-shadowsocks


Cheers,
Franco

Hi Franco,

I did a PR to match the content provided by slashing
https://github.com/opnsense/plugins/pull/4913

My first PR

@eguun Let me guess what happened here:

os-shadowsocks-devel 1.2 (which uses shadowsocks-rust) was released about a month ago with 25.1.12. Since no issues were reported, it was now moved to production in 25.7.2.

Since you initiated the switch, expectations were that you test the devel version and report potential issues. It seems this didn't happen.

Probably a misunderstanding?

Cheers
Maurice

Hi,

Spot on!
Big misunderstanding indeed: I was eagerly waiting for this release and only saw the new rust version pop in 25.7.2. I totally missed the memo that there's a devel/test version in the backstage.

Sorry to have dropped the ball here, I'll work on this PR to fix

Cheers

[1- OPNSense GUI still reference the libev filepath and needs update]

Hi,

To second this,

The "broken" shadowsocks correlates when shadowsocks plugin moved from deprecated libev to current rust, ref: https://github.com/opnsense/plugins/issues/4662

2 updates on OPNSense seems to still be required to finalize port from libev to rust:

1- OPNSense GUI still reference the libev filepath and needs update
when shadowsocks plugin is fresh installed in OPNSense GUI,
the page updating the settings (Services > ShadowSocks > Server) saves its content into /usr/local/etc/shadowsocks-libev/config.json instead of /usr/local/etc/shadowsocks-rust/config.json


2- demon start doesn't work from gui - but succeed from cli
Lobby > Dashboard > Services
shadowsocks daemon marked as down - clicking the start button doesn't succeed at launching the deamon


But overall the rust version seems to work:
Assuming settings are properly configured into the OPNSense GUI (Services > ShadowSocks > Server)
Launching this command successfully launches the process

Code Select Expand

/usr/local/bin/ssserver -c /usr/local/etc/shadowsocks-libev/config.json
Any advise on the process to get these updates into a future release/hotfix?

Cheers

Thanks Maurice for the quick response, clear.

Hi Maurice,

Thanks for your work here!

Any plans to publish zfs versions for aarch64?

Thanks

Ah ... I have BIND installed, sorry.

drill is the base system replacement for dig.

Many thanks!
Was exactly what I was after :)

Thanks for the response.

But dig also seems missing from out of the box.

What's the recommendation towards my initial question?

dear all,

looking for advise

I'm surprized that the nslookup tool isn't available out-of-the-box on opnsense.

What's the recommended/pragmatic way to make simple resolve of fqdn from the command line?
Is there a tool I oversaw?
Should I install nslookup from /usr/port?

Thanks

Many thanks for the response.

To help any other people having this issue and finding this thread.

I managed to make it work via 2 options:
1- I build a oneliner- script to use openssl base64. I named the script base64 and redirect args towards openssl - following fabian's pointers
2- I downloaded the compiled binary from lilsense link: https://freebsd.pkgs.org/12/freebsd-amd64/base64-1.5_1.txz.html - worked right out of the box!

Both solution works.

There is still a 3rd way which would have been to compile from source ... but I haven't gone through this.

My warm thanks for the support!

my bash script (named base64 and placed in /root/bin):

Code Select Expand

#!/usr/local/bin/bash
/usr/bin/openssl base64 "$@"

Okay many thanks, I can work with this

Sorry for the late response, I hadn't been notified on the activity here.

Thanks for your reply.

I can't find the tool handy in the pkg library.

These 2 options you recommend, would you please be kind to share a link there where I can learn more how to work with ports or openssl to achieve this result?

Thanks

Hello,

I am struggling to find an actionable way to get the tool base64 on opnsense

for reference: https://linux.die.net/man/1/base64
This is the tool to encode/decode string from the shell.

I can't find it in packages, it's not installed by default ...
Am I missing something easy and obvious to get it ?

Any pointers would be welcome.

Thanks