From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050323 Firefox/1.0.2 Fedora/1.0.2-1.3.1

Description of problem:
When adding an explicit static route to a network interface, if the
"Gateway" field is left blank the program does not complain, but a
subsequent invocation of system-config-network will complain about
an invalid static route file.  The route file with no "GATEWAYn="
entry works just fine when bringing upt the interface, but is
rejected for subsequent editing.

Version-Release number of selected component (if applicable):
system-config-network-1.3.22-1

How reproducible:
Always

Steps to Reproduce:
1. Run system-config-network.
2. Select an existing interface and click on "Edit".
3. Select the "Route" tab and click on "Add...".
4. Enter a valid Address and Subnet mask, but leave the Gateway field blank.
5. Click on "OK" in the Add/Edit dialog and in the Route dialog.
6. In the main dialog, select "Save" from the "File" menu.
7. Quit from the program.
8. Run system-config-network again.
  

Actual Results:  An error message popup appears stating, "Static routes file {interface_name} is invalid."  Upon entering the edit dialog again, the previously entered static route will be missing.

Expected Results:  The program should produce a static route file that it is able to parse.

Additional info:

The workaround is to always fill in the Gateway field even though the program does not complain about the blank field when saving the file.