© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Thank you for your response. It looks like this is fixed in Wily then, which is on 3.2.26, so this bug affects 14.04 only?
I'm concerned that this changes library behaviour. How can we be sure that no existing users of libnl will not be regressed by this change in behaviour if we backport this to 14.04?
> To summarize, if an application on the system chooses manually a port id (because it does not use the libnl or because it sets it manually), it may conflict with applications that use libnl and prevent them to work properly.
Thanks, this is useful. But can you take us through to actual user impact of this bug, please? I'm sure you have a concrete case for wanting this, but so far this explanation is hypothetical. In what concrete case on 14.04 does an application manually chose a port id that then causes a conflict and causes a problem for a user?