Messages

Well, under the ShadowSocks: Local I have server address and port set, and local address 10.0.0.1 and local port 1080. I can see in the logs it's binding to 127.0.0.1 port 1080.
The server is set to 127.0.0.1 and port 8388.

I have not changed the config since it was working for the past couple years and use it with FoxyProxy on some of my machines.

I even checked the config.xml and it's correct. For now I was able to rig it to work with port forwarding but that's not ideal.

So this was fun, i checked github before here. I'm still having trouble however, sslocal is only listening on 120.0.0.1 not my lan ip that I have set in the conf.

<29>1 2025-08-27T19:15:40-04:00 OPNsense.mid-earth.net daemon 8434 - [meta sequenceId="13"] 2025-08-27T19:15:40.957292457-04:00  INFO shadowsocks local 1.23.4 build 2025-08-21T03:52:31.256707422+00:00
<29>1 2025-08-27T19:15:40-04:00 OPNsense.mid-earth.net daemon 8434 - [meta sequenceId="14"] 2025-08-27T19:15:40.957724556-04:00  INFO shadowsocks socks TCP listening on 127.0.0.1:1080
<29>1 2025-08-27T19:15:40-04:00 OPNsense.mid-earth.net daemon 8434 - [meta sequenceId="15"] 2025-08-27T19:15:40.957743247-04:00  INFO shadowsocks socks5 UDP listening on 127.0.0.1:1080

I have no idea but this needs to be better documented for opnsense. I spent way too long trying to get port forwarding to work until I saw you post and tried to set it to listen to 1 interface only (localhost).

For timescale you need to use netflow/insight.
Traffic Reporting is only for having a quick lock what happens right now

Not necessarily, I mean you might want the last 1min, 5min, 10min left on the graph while it is open as an example. It would be amazing to have it able to tie into other things like netflow though, since it is the traffic page ;-)

Just wanted to comment, it's pretty, but wow it's amazingly useless. It would also be nice to see previous history, or let the user pick a time scale.

Still an issue a year later...

I know this is old, but has anyone come up with an easy solution? It would be really nice if it could use the dhcp static lease file as filter as well, so known devices don't get logged.

Would be nice to also get an interface to assign the client a static ip and not have to use the ifconfig-push line in advanced.

The only thing I can think of is a clear way to see when a goal is punted, maybe only if it's close to release? Maybe notes at the bottom, like "Due to x, y feature has been moved to 19.1"

Oh. Wanted to add: This kind of stuff happens all the time when released are made on a schedule. If a feature isn't ready it gets punted, totally normal. Apple, MS, etc often push features back if they aren't ready.

The only thing I can think of is a clear way to see when a goal is punted, maybe only if it's close to release? Maybe notes at the bottom, like "Due to x, y feature has been moved to 19.1"