Comment 1 for bug 95023

This is confirmed, however there has been some obscurity with regard to what the actual problem is.

Quite simply, when an interface is placed under Network Manager's control by checking "Enable roaming mode" for that interface under "Admin > Networks", Network Manager will attempt to connect the interface with DHCP ("dynamic IP"), and if there is no response it calls itself connected by filling in the connection information with null IPs (0.0.0.0) (it isn't really connected). There is no opportunity to tell Network Manager that the network instead requires a static IP.

The only way to configure an interface with a static IP is the old fashioned way, without Network Manager (by unchecking "roaming mode" in "Admin > Networks" and filling in the required configuration). This allows the interface to connect, and Network Manager knows it is connected and hence displays the "connected" notification icon, however because the interface is not under Network Manager's control it does not show the blinking screens for network activity.

For those switching between static and dynamic IP (DHCP) networks, you should save a "location" in "Admin > Networks" for each static IP network with the interfaces properly configured for, and another with the interfaces configured for "roaming mode" for when you are in a dynamic IP network.

All in all this could be considered a bug or perhaps Network Manager was never supposed to handle static IP networks (hence leaving it to the "Admin > Networks" dialog). Either way it does not prevent users from connecting to their networks and hence not a critical problem.

And if there is any error in my clarification PLEASE point it out!