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

Update ipv6 forwarding rules from add-on #1592

Closed
GabrielePicco opened this issue Mar 16, 2020 · 5 comments
Closed

Update ipv6 forwarding rules from add-on #1592

GabrielePicco opened this issue Mar 16, 2020 · 5 comments

Comments

@GabrielePicco
Copy link

GabrielePicco commented Mar 16, 2020

Hi,

I'm trying to create a Wireguard client add-on that require to updated some forwarding rules. On the startup of the add-on, I get the following error:
Setting key "net.ipv6.conf.default.forwarding": Read-only file system.
Manually launching the container with --priviled works, but with hassio it doesn't seem possible. Is there an alternative solution? mounting a device?

Possible related issue: #201

Thanks in advance.

@frenck
Copy link
Member

frenck commented Mar 16, 2020

You are opening the same issue now again.

Duplicate of: #1588

@frenck frenck closed this as completed Mar 16, 2020
@GabrielePicco
Copy link
Author

@frenck the issue is different.
I'm asking if anyone knows of an alternative for updating the ipv6 forwarding rules (knowing that I can't run an addon with --privileged).
Please reopen the issue, maybe someone has an alternative solution.

@frenck
Copy link
Member

frenck commented Mar 16, 2020

I did answer your question already: you can't.

@GabrielePicco
Copy link
Author

GabrielePicco commented Mar 16, 2020

I guess it is possible to mount a device in a similar way to what they did in #201 to overcame the issue, since the error is Setting key "net.ipv6.conf.default.forwarding": Read-only file system.
Don't be arrogant and reopen the issue. Maybe someone knows a workaround.

@frenck
Copy link
Member

frenck commented Mar 16, 2020

Don't be arrogant and reopen the issue.

It is a read-only file system...

We don't provide means for it in the ecosystem.

Please don't call me out arrogant, because the answer didn't isn't what you wanted to hear. That was not called for.

@home-assistant home-assistant locked as too heated and limited conversation to collaborators Mar 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants