Local_network environment only allows one subnet about nordlynx-proxy HOT 2 CLOSED

tldr; multi local networks are not properly handled.

well, you are right, several problems raised by this issue:

• tinyproxy (proxy http): the local network is handled as if the is only one item.
• dante (proxy dante): the local_network is not used

I'll have a look on how to correct this.
For the moment consider the multi networks handling broken.

I suspect also a problem when nordvpn status's return cannot be parsed. (error line 229)
Could you execute a nordvpn status| grep -oP "(?<=IP: ).+" from the container when you have that error ?

from nordlynx-proxy.

Thanks for your fast reply:

without local network error:

nordvpn status| grep -oP "(?<=IP: ).+"
xx.xx.xx.xx

with local network error:

nordvpn status| grep -oP "(?<=IP: ).+"
xx.xx.xx.xx

xx.xx.xx.xx = showing nordvpn connected ip

I have now mitigated the issue by putting the proxy in another zone and use masquarade to change the source ip

from nordlynx-proxy.