Bug#454752: Sometimes an interface fails to be added to a bridge because of timing issues
As a workaround I was able to add a while loop waiting for the device to show up in /etc/network/if-pre-up.d/bridge so that bridge-utils would wait for the device to show up before adding it... I was going to implement a couple of things to satisfy the cases I can think of on this area, but I don't know if I'm getting all this way too complex. Can you send me your patch to get a closer idea of what you want? I'm still curious on what kind of interface will come up while we are waiting on a loop on the bridge-utils script :-? Maybe some changes I have already introduced already solve this kind of problems, can you please specify more on what are the devices causing this kind of problems? Regards... -- Manty/BestiaTester - http://manty.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#454752: Sometimes an interface fails to be added to a bridge because of timing issues
I have already implemented something hopefully on this spirit, it should be on the new 1.4-1 package when it is ready, here goes its description as I have written it for the new man page: bridge_waitport time [ports] wait for a max of time seconds for the specified ports to become available, if no ports are specified then those specified on bridge_ports will be used here. Specifying no ports here should not be used if we are using regex or all on bridge_ports, as it wouldn't work. Do you think this would be ok? Did I get the idea of what was wanted? Regards -- Manty/BestiaTester - http://manty.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#454752: Sometimes an interface fails to be added to a bridge because of timing issues
Package: bridge-utils Version: 1.2-1 Severity: normal Hi, I found that sometimes (and on some type of machines this tends to happen quite often) a bridge interface comes up without all its ports added because when the net script try to add them the underlying phisical interfaces are not there yet and are detected by the kernel too late. The resulting system has a bridge configured but the underlying phisical device is down and unconfigured (while being present, since it was later on detected). As a workaround I was able to add a while loop waiting for the device to show up in /etc/network/if-pre-up.d/bridge so that bridge-utils would wait for the device to show up before adding it... Would it be possible to add something like that (maybe a bit more complex, with a configurable timeout) to the default scripts? Thanks, Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
