On Monday 05 October 2009 15:01:59 Dan Williams wrote: > On Mon, 2009-10-05 at 14:37 -0400, Gene Czarcinski wrote: > > On Sunday 04 October 2009 01:56:25 Martyn J. Pearce 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. > > > > > > I have tried checking and unchecking the "use this connection only for > > > resources on its network" (I'm sure it should be unchecked, but I tried > > > both); it makes no difference. > > > > > > I'm sure I'm being stupid, could somebody take pity and enlighten me as > > > to what I'm doing wrong? > > > > > > I attach the relevant lines from /var/log/daemon.log (grep > > > NetworkManager), I've checked the one bug mentioned therein; that is > > > related to publishing of offline mode rather than setting of default > > > gateways. > > > > > > Thanks, > > > > > > [please cc: me on replies, I am not subscribed to the list] > > > > This may be related to the following -- > > https://bugzilla.redhat.com/show_bug.cgi?id=523875 > > I need to get around to testing that one out; is the connection that it > doesn't stay checked for a system connection? I can't imagine what > would be wrong if it's just a user connection. I have the problem on both F11 and F12 but lets stick to F12 for now. -->> Should I file a second BZ report for this bug with rawhide specified instead of F11? To me, the bug appears to be the same but that does not make it so. On my qemu-kvm F12 guest I have two NICs defined: eth0 on a "private" (non-NAT or host only) qemu network and eth1 on the "default" NAT qemu network which will give me access to my local network and ultimately the Internet. I am attaching the definition file for the "private" qemu network which goes in /etc/libvirt/qemu/networks/. As described, the default route is to eth0 whereas I want it to be on eth1. If I reverse the two definitions (easy to do with qemu-kvm), then the default is still eth0 but this time it is correct. [when fooling with NIC definitions, remember to delete /etc/udev/rules.d/70- persistent-net.rules so that ethX naming makes sense]. You will also neet to use system-config-network to get the definitions & MAC addresses correct. BTW, I do not run either networks or NetworkManager at bootup so that I can control what is going on. In all cases, I am using "System" definitions ... e.g., /etc/sysconfig/network- scripts/ifcfg-eth0 In all cases, the NIC I am trying to set the "connection only" checkbox is on the "private" network NIC. > > I've seen this problem on F12/rawhide but fixed it there, the cause in > F12 would be unrelated to anything in F11, which is what the bug was > filed against. They may be different but the result is the same. Gene
Attachment:
private.xml
Description: application/xml