Warning for "Binding" Network Definition to Interface
Astaro added the ability to bind a host/network definition to a specific interface for the rare situation where that might be useful. In reality, many admins are having strange routing problems caused by this. These problems are almost impossible to debug.
There are several places where the GUI warns the admin about deleting things. It should warn the admin that binding to anything other than <<Any>> is rarely neecessary and that doing so improperly can cause unpredictable routing problems.
Rather than layering things with warnings/popups, in UTM 9 we simply moved this to the advanced section so it isn’t apparent and readily-selectable. This solves this issue, so i’ll close it out. thanks for putting it in!
as i just try to understand the use and implications of binding a host definition to a specific interface but can't find substantial hints in the online manual.
Are the "known" problems still an issue or is it fixed in the meantime?
Help would highly be appreciated, thanks.
Am I wrong or this idea was marked as "completed"? I remember also an Angelo's post, but it is disappeared...
Bob Alfson commented
Great news, Angelo!