-
Notifications
You must be signed in to change notification settings - Fork 103
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
WireGuard and TUN interfaces should be ignored by default #302
Comments
Currently, dhcpcd ignores an interface by checking its name. However, the interface can be renamed, at least on FreeBSD and DragonFly BSD. And then the ignoring rules would just not work. I think an interface should be ignored by checking its type (e.g., Any ideas? |
IFT_BRIDGE and others are checked here: I'll remove bridge and others with a note that we check the IFT equivalent where we can. As on interface renaming, yeah it's a nasty problem. IMO if an interface can be renamed is MUST have a mechanism to get the original name. |
Hi @rsmarples, thank you for the prompt reply 😄.
Cool. I didn't know that
That would be better and avoid such confusions.
Yes, I totally agree. There should be an ioctl command to get this basic information by giving the interface name, including the base name (e.g., Do you have any ideas ready? I think we can propose such a request to FreeBSD and DragonFly BSD. I'll certainly implement it in DragonFly 😃. Regards. |
According to the current code, TAP interfaces are ignored by default, but TUN interfaces are not. Why?
In addition, given the availability of WireGuard on various OSes, the WireGuard interfaces should also be ignored by default.
Regards.
The text was updated successfully, but these errors were encountered: