Manually applying the fix in comment #12 gets the juju local provider
happy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/573461
Title:
UFW blocks libvirt bridged traffic
To manage notifications
This bug was fixed in the package ufw - 0.34~rc-0ubuntu3
---
ufw (0.34~rc-0ubuntu3) utopic; urgency=medium
* debian/patches/0005-lp573461.patch: adjust man page for libvirt
(LP: #573461)
* debian/patches/0006-check-for-newer-py3.patch: tests/check-requirements
updated for
The technique to use to make this work on 12.04 was to edit
/etc/ufw/sysctl.conf to have:
# Don't filter packets to our libvirt guests
net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0
The problem is on later releases of Ubuntu
FYI, I updated the ufw-framework.8 man page to mention libvirt and
bridging.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/573461
Title:
UFW blocks libvirt bridged traffic
To manage notifications
This just started happening to me after a recent apt-get update. It
rendered my KVM guests completely inaccessible. The only solution was to
disable/uninstall UFW.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Although I don't know this is a right way, setting
DEFAULT_FORWARD_POLICY=ACCEPT in /etc/default/ufw and restarting ufw
get through all bridged traffic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is indeed invalid. I agree that the solution is not immediately
apparent. However, read the comments and you will be able to properly
configure your system for this setup just as Jaime had to so painfully
explain it to me. I'm assuming it was painful for him anyway...
** Changed in: ufw
Ubuntu 10.04.1. Both of the above workarounds are not working for me.
I can connect to my server if ufw is disabled with ufw disable. But
as soon as I turn on ufw, I cannot connect to it. I have bridged
networking. (I use this server for both KVM and LXC, but during testing
I turned off all
Thanks for the workaround. This should be fixed.
I'm using LXC containers and this bug.
Jan 13 11:25:23 uv09 kernel: [5071210.955631] [UFW BLOCK] IN=br1 OUT=br1
PHYSIN=vethSjyOT7 PHYSOUT=eth1 SRC=172.16.20.10 DST=172.16.20.1 LEN=60
TOS=0x00 PREC=0x00 TTL=64 ID=6601 DF PROTO=TCP SPT=41445 DPT=22
Hmm I had a similar issue but came to a different conclusion.
I had done a libvirt + ufw lucid install and had some vms working --
traffic from vms to the outside world and replies would work, traffic
between vms would work etc. Basically things worked fine.
Then I wanted to map a host port to a
Loic, I think this is a different issue since it appears you are using
libvirt's NAT and not libvirt's bridging setup. If I am wrong, please
correct me.
Assuming you are using NAT, as you said libvirt is the one doing the
inserting of the rules in this case. ufw does have a 'MANAGE_BUILTINS'
Oh right, indeed, that's a NAT setup; I just confused because it's using
a bridge as the underlying to do the NAT-ing stuff; I filed bug #595501
Thanks!
--
UFW blocks libvirt bridged traffic
https://bugs.launchpad.net/bugs/573461
You received this bug notification because you are a member of
Just for clarification of what Jamie said. (Breaking it down the the
simplest form.)
vim /etc/ufw/before.rules
Add this line
-I FORWARD -m physdev --physdev-is-bridged -j ACCEPT
after *filter and before COMMIT.
--
UFW blocks libvirt bridged traffic
https://bugs.launchpad.net/bugs/573461
You
13 matches
Mail list logo
