On Mon, 2009-10-05 at 15:03 -0400, Gene Czarcinski wrote: > On Monday 05 October 2009 13:21:46 Dan Williams wrote: > > On Mon, 2009-10-05 at 13:07 -0400, John Mahoney wrote: > > > On Sun, Oct 4, 2009 at 1:56 AM, Martyn J. Pearce > > > <[email protected]> wrote: > > > Apogolies if re-asked, I have searched the mailing-list > > > archive to no avail. > > > > > > I am running a new ubuntu install on a netbook (Eeepc surf), > > > with wired & > > > wireless networking available, both domestic > > > manually-configured networks (no > > > dhcp). I have added Manual profiles to both wired & > > > wireless. I cannot get > > > the default gateway (192.168.0.12) to configure, however. > > > > > > I add two routes in the route config panel; one for > > > 192.168.0.0/255.255.255.0 > > > (no gateway), and one for 0.0.0.0/0.0.0.0 (gateway > > > 192.168.0.12). Having left > > > the edit dialogue, and applied, there is no difference to the > > > routing table as > > > displayed with route -n. If I re-enter the routes edit panel, > > > I find that > > > it's collapsed the routes into one, being > > > 192.168.0.0/255.255.255.0 (gateway > > > 192.168.0.12); but there's no hint of the gateway in the route > > > config. > > > > > > > > > Did you try adding the Default gateway to the Addresses section of the > > > ipv4 settings tab instead of the routes section. > > > Also, If you have both wired and wireless interfaces active, I > > > believe, it will always use the wired default route first if possible. > > > > The routes dialog doesn't take 0.0.0.0, because that's the default > > route, and NM manages the default route. Here's what you do... > > > > Set up your IP address and static routes. By default, the wired device > > will always get the default route. If there is a device (any device) > > that you do *not* want to have the default route at any point, check the > > "Use this connection only for resources on its network" checkbox in the > > "Routes" dialog of the IPv4 page. > > > > That checkbox ensures that that connection (and thus any device that has > > been activated using that connection) will not be the default route. > > Nice in theory but this does not work in practice on with Fedora 11 or Fedora > 12 -- https://bugzilla.redhat.com/show_bug.cgi?id=523875 > > As I see it, there is one and possible two problems: > > 1. The "connection only" does not stay checked (and, I assume, the > appropriate > parameter does not get set). > > 2. If "connection only" checkbox be made to work, is the default route set > properly. > > IMHO, this is an important problem that needs fixing .. in at least F12 if > not > in F11. > > OK, there are only so many hours in a day and the maintainers/developers of > NetworkManager have a lot to do ... and, from the looks of it, NetworkManager > is a lot of code. > > So, I am willing to put some time in on this. I downloaded and installed the > F12 source rpm. As I said, NetworkManager is a lot of code and I would > prefer to spend my time constructively rather than learning about all of > NetworkManager. Could someone provide some guidance as to where (what source > files) I should be looking?
Which specific NM SRPM? Ideally you have: http://kojipkgs.fedoraproject.org/packages/NetworkManager/0.7.996/4.git20091002.fc12/src/NetworkManager-0.7.996-4.git20091002.fc12.src.rpm You might also try to update to the packages here: http://koji.fedoraproject.org/koji/buildinfo?buildID=134947 and see if you can reproduce the issue on F12, which would help. F12 builds have had a fwe issues the past couple weeks that would have prevented the "available to all users" checkbox from sticking, but which are unrelated to anything in F11. Once we've confirmed versions, I can point you to the right places. Thanks! Dan _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
