Comment 3 for bug 969422

I accept this decision but I completely disagree with it. Forbidding me entering a totally valid configuration for whatever reason but forcing me to enter an invalid one absolutely does not sound right to me.

Analyzing the use case also does not tell me this is a right solution. Those without strong knowledge of networking will most probably ask someone else what data to enter (how the heck could they figure it out themselves), so most probably they will be told the gateway address as well. So what this "feature" is protecting them is that when they enter the addresses they were told they simply forget one of them. I find it very unlikely. Also they could do a lot other mistakes there - entering wrong numbers, swapping the ip and the gw addresses, etc.

Also, what if they really do not have a gw address for that interface? There is absolutely no indication that that is the reason for the button to be disabled. It took me 10 minutes to figure it out. At least please enable the button and complain about the missing gw when it is pressed.

I could also accept that the gw is required for the _first_ interface, but not for additional ones (like in my case).