Currently, the vde service is set to start after net.${VDE_TAP}. If I understand it correctly, the tap interface is supposed to be created by the vde service, so the "after" should be changed to "before". Reproducible: Always
If you create a tap interface yourself it needs to be done BEFORE vde runs ==> after net.${VDE_TAP}. If there is no net.${VDE_TAP} then there is no wait. So IMHO it should be after.
Well, here's my use case: I let the vde service creates a tap0 interface, have a config for tap0 in /etc/conf.d/net, and have both vde and net.tap0 at the default runlevel. For this to work, I need "before net.${VDE_TAP}".
if it needs to be configurable then maybe it needs to go to the /etc/conf.d/net either: RC_AFTER_tap0="vde" or: RC_BEFORE_tap0="vde" so anyone can decide which one is needed. maybe an example needs to be added to /etc/conf.d/net?
net.${VDE_TAP} is fully capable of creating the tap device, so it shouldn't be necessary to have vde create it, and you shouldn't even have to change anything in the vde config file. I'm not sure it's desirable to add that kind of complexity to vde, since it works fine either with or without a net.${VDE_TAP} device. Do you have a scenario where it can't be made to work? If so, could you detail it for me?
> net.${VDE_TAP} is fully capable of creating the tap device That's the part I don't quite understand (as mentioned in the bug description). How do I get a tap0 interface without running vde_switch tap0 first? My current setup is rather simple: 1. cd /etc/init.d; ln -s net.lo net.tap0 2. rc-update add net.tap0 default 3. rc-update add vde default 4. echo "config_tap0="192.168.4.1/24"" >> /etc/conf.d/net 5. sed -i -e "s|after net|before net|" /etc/init.d/vde
adding tuntap_tap0=tap to /etc/conf.d/net creates a tap0 device with all strings attached.
Didn't know that. Works great :)
It's in the net.example (although that's harder to find in baselayout2...) So, not a bug, then, I believe. Re-open if it's still and issue.
