Bug 677042 - isolated networks should not have a default route
Summary: isolated networks should not have a default route
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Michal Privoznik
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-12 20:16 UTC by Brian J. Murrell
Modified: 2011-07-14 21:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-14 21:28:21 UTC


Attachments (Terms of Use)

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.


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