Bug 463298
Summary: | virbr0 loses it's routing when managed by NetworkManager | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dan Yocum <dyocum> | ||||||
Component: | libvirt | Assignee: | Daniel Veillard <veillard> | ||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 9 | CC: | berrange, markmc, veillard, virt-maint | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2009-02-02 17:58:46 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Dan Yocum
2008-09-22 20:43:32 UTC
Can't reproduce here Could you try running these commands before and after you restart the connection: $> brctl show $> iptables -L -v -n $> ps -ef | grep dnsmasq $> ifconfig -a $> cat /proc/sys/net/ipv4/ip_forward I suspect it might be related to bug #467687 Created attachment 330653 [details]
before reconnecting w/ NM
Created attachment 330654 [details]
after reconnecting w/ NM
I recently upgraded to F10 and can't reproduce the problem, either. *shrug* Take a look at the attached files - I don't see a smoking gun, but it sure sounds like bug #467687 and this are related. Cheers, Dan (In reply to comment #4) > I recently upgraded to F10 and can't reproduce the problem, either. *shrug* > > Take a look at the attached files Ah, okay - these log files are from a system that the problem isn't occurring on > - I don't see a smoking gun, but it sure sounds like bug #467687 and this are > related. Yeah, I think we can be fairly certain that it was the same issue. Marking as duplicate, but do re-open if it comes back and looks different. *** This bug has been marked as a duplicate of bug 467687 *** |