Bug 677042

Summary: isolated networks should not have a default route
Product: [Community] Virtualization Tools Reporter: Brian J. Murrell <brian>
Component: libvirtAssignee: Michal Privoznik <mprivozn>
Status: CLOSED UPSTREAM QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: berrange, crobinso, dallan, xen-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-14 21:28:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Brian J. Murrell 2011-02-12 20:16:17 UTC
When one configures an "isolated" network with virtual-manager, dnsmasq sends a default route in the DHCP response.  It shouldn't.  It's an isolated network.

It should still provide a route for NAT style networks I think.

Comment 1 Cole Robinson 2011-07-13 01:34:21 UTC
I don't think this is virt-manager specific, reassigning to libvirt.

Comment 2 Michal Privoznik 2011-07-14 15:29:21 UTC
Brian, could you please note libvirt and dnsmasq versions you are experiencing this problem with? Libvirt already adds '--dhcp-option=3' to dnsmasq, which should mean 'no default route'. I've tried to reproduce with libvirt-0.9.3-2.el6.x86_64 and dnsmasq-2.48-4.el6.x86_64 and it really doesn't send default route for isolated network. And could you please show XML of the network? Thanks.

Comment 3 Cole Robinson 2011-07-14 21:28:21 UTC
Thanks for the info Michal. Looks like that commit was fairly recent though (released april 2011):

http://libvirt.org/git/?p=libvirt.git;a=commit;h=013427e6e733f7a662f4e8a9c11f7dad4cd65e3f

Which was also after Brian filed the bug. Closing as UPSTREAM. Brian, if you are using a distro and want this patch, please file a bug with them to backport the above commit.