Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Allow multiple input ports for Mullvad #1184

Closed
mikewilzn opened this issue Oct 4, 2022 · 4 comments
Closed

Feature request: Allow multiple input ports for Mullvad #1184

mikewilzn opened this issue Oct 4, 2022 · 4 comments

Comments

@mikewilzn
Copy link

mikewilzn commented Oct 4, 2022

What's the feature 🧐

Mullvad allows you to have multiple forwarded ports for a single Wireguard configuration, however it seems that the FIREWALL_VPN_INPUT_PORTS variable only accepts one value.

Extra information and references

I tried various yaml formats such as

FIREWALL_VPN_INPUT_PORTS: "12345;54321"

and

FIREWALL_VPN_INPUT_PORTS:
               - 12345
               - 54321

but it did not want to accept it. Looking at ports.go it seems only one value is accepted anyway.

@olvier
Copy link

olvier commented Oct 4, 2022

#196 (comment)

@qdm12
Copy link
Owner

qdm12 commented Oct 31, 2022

Thanks @olvier

@mikewilzn as described in the wiki at https://github.com/qdm12/gluetun/wiki/Firewall-options it's a comma separated value (not semi-colon). Also the code reading the env variable is at

vpnInputPortStrings := envToCSV("FIREWALL_VPN_INPUT_PORTS")
and the function is envToCSV so it's a comma separated value (csv).

@qdm12 qdm12 closed this as completed Oct 31, 2022
@varunpan
Copy link

Should be cancelled, mullvad no longer supports port forwarding :(

@GlassedSilver
Copy link

Should be cancelled, mullvad no longer supports port forwarding :(

Not supported, but still works. Also why burn this bridge, any VPN could at any moment support multi-port forwarding per connection. We don't need to argue about the likelihood, all that matters is that it's pointless to kill syntax support for something that can change any moment for the better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants