Comment 2 for bug 1775644

Slawek Kaplonski (slaweq) wrote :

Is this still an issue on current master release?
@Tamas: can You also check if that happens only when You try to bind it to wrong port type as Li mentioned in comment above?

For now I'm marking this as incomplete because:
1. It doesn't look like a bug as there is no any unhandled exception or something like that but there is error message returned. Maybe message could be a bit improved but nothing more than that IMO.
2. There is missing information about port's device type which You tried to bound with firewall group.