[TOR] Plugin binding to Virtual IP only when LAN interface selected

[wrobelda]

Important notices Before you add a new report, we ask you kindly to acknowledge the following:

• [x] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
• [x] I have searched the existing issues, open and closed, and I'm convinced that mine is new.
• [x] The title contains the plugin to which this issue belongs

Describe the bug I am trying to bind TOR plugin to LAN, but it seems it binds to a wrong IP. Specifically, I have a Virtual IP configured as well on the interface and that is the only IP it binds to.

To Reproduce Steps to reproduce the behavior:

1. Set up a Virtual IP on LAN interface
2. Bind Tor plugin to LAN
3. sockstat -l will show tor binding to that Virtual IP only, but not the actual LAN address

Moreover, since I have configured the Virtual IP to disallow binding of the services, I believe Virtual IP should not be bound at all in my case, the LAN IP issue notwithstanding.

Expected behavior Tor should bind to the actual LAN IP, and not the Virtual IP unless the latter is configured to allow so.

OPNsense 22.1.5

[wrobelda]

Looking at the sourcecode at https://github.com/opnsense/plugins/blob/16f3522d08d30919b17e66bdec38352ef4c75208/security/tor/src/opnsense/service/templates/OPNsense/Tor/torrc#L18 , I don't see why would the LAN IP address be omitted. Any ideas how to debug this?

[OPNsense-bot]

This issue has been automatically timed-out (after 180 days of inactivity).

For more information about the policies for this repository, please read https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md for further details.

If someone wants to step up and work on this issue, just let us know, so we can reopen the issue and assign an owner to it.