I had the same problem but the cause and solution is different.
Perhaps it's a Mandriva thing, but the tun module is loaded in the
default.nodes list in /etc/udev.devices.d. These are created
independently at udev startup and so never go through the main rules -
they all have permissions of 0600.
when I said the module was loaded in the default.nodes list, I really
meant that the node that tun uses is created here.
--
Cannot change /dev/net/tun file permissions with udev
https://bugs.launchpad.net/bugs/265138
You received this bug notification because you are a member of Ubuntu
Bugs,
when I said the module was loaded in the default.nodes list, I really
meant that the node that tun uses is created here.
--
Cannot change /dev/net/tun file permissions with udev
https://bugs.launchpad.net/bugs/265138
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: udev (Ubuntu)
Status: Incomplete = Won't Fix
--
Cannot change /dev/net/tun file permissions with udev
https://bugs.launchpad.net/bugs/265138
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I had the same issue. In my installation, the file
/etc/udev/rules.d/60-vboxdrv.rules already existed (I'm using VBox
2.02).
I added the line per the above comment:
KERNEL==tun, OWNER=root, GROUP=vboxusers, MODE=0660
rebooted, and the problem went away - permissions are now correct. I
didn't
It will definitely not work if you edit 20-names.rules to have this line
(since that is copied to the initramfs)
It should work if you extend 40-permissions.rules, but don't do that,
add your own file as you've done.
It's also worth noting that you have to load the tun module for it to
have any
Please ensure your rules are in their own file, and run:
modprobe tun
And see whether the permissions are correct.
If not, attach the output of udevtest /devices/virtual/misc/tun
** Changed in: udev (Ubuntu)
Status: New = Incomplete
--
Cannot change /dev/net/tun file permissions
Ah! I had the exact same problem. If you boot your system without quiet
and splash you can see that it's trying to change the permissions but
says unknown group vboxusers. I cannot understand why though.
If you instead of changing that file (or in addition to) add a rules
file called
