Bug 448208 - Default route not set for static IP address
Summary: Default route not set for static IP address
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-network
Version: 8
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-05-24 13:04 UTC by Robin Green
Modified: 2013-01-13 13:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-01-09 06:32:52 UTC
Type: ---

Attachments (Terms of Use)
/etc/sysconfig/network-scripts/ifcfg-wlan0 (370 bytes, text/plain)
2008-05-24 13:04 UTC, Robin Green
no flags Details

Description Robin Green 2008-05-24 13:04:24 UTC
Description of problem:
I am connecting to a Macbook running Mac OS 10.5 which has a shared Internet
connection. For some reason, Mac OS 10.5 does not seem to start a DHCP server
when sharing the Internet connection, so I used static IP settings. However, the
routing got set up incorrectly - the route for the local network was missing,
and the default route was also missing (probably as a consequence, because if
you try to add the latter route manually at the command line, without first
adding the former, you get an error message).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Type in settings as in attached config file
2. Activate interface
3. route -n
Actual results:
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface   U     0      0        0 eth1     U     0      0        0 wlan0

Expected results:
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface   U     0      0        0 wlan0   U     0      0        0 eth1     U     0      0        0 wlan0         UG    0      0        0 wlan0

Additional info:
The Macbook has two IP addresses assigned to its wireless interface. I don't
know why, and I don't have a clue how Fedora assigns one route based on the
Macbook's *other* IP address!

This was the only workaround that worked for me: Save the following as
#! /bin/bash -eup
if [ "$1" = "wlan0" ]; then
  route add -net netmask dev wlan0
  route add default gw

and make it executable.

Comment 1 Robin Green 2008-05-24 13:04:24 UTC
Created attachment 306579 [details]

Comment 2 Bug Zapper 2008-11-26 10:46:12 UTC
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 3 Bug Zapper 2009-01-09 06:32:52 UTC
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.