[Bug 684424] Re: Bridges are not transparent for packets
If this is an Opinion please do not call the whole thing bridge. Bridges are transparently connecting networks at layer 2. An non- transparent bridge can't be called a bridge. Whatever it is. It's not a bridge as bridge meant in networking terminology. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/684424 Title: Bridges are not transparent for packets -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 684424] Re: Bridges are not transparent for packets
@Thomas, can you try 'brctl stp br0 on' in the VM? I reproduced your setup using an lxc container connected to a bridge, and a separate network namespace inside the container. With stp off, I could not ping the host or the outside world (without setting routes). With stp on, I could ping the host, ping google.com, and ssh to other laptops on the same subnet. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/684424 Title: Bridges are not transparent for packets -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 684424] Re: Bridges are not transparent for packets
** Changed in: libvirt (Ubuntu) Importance: Undecided = Low ** Changed in: libvirt (Ubuntu) Status: New = Opinion -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. https://bugs.launchpad.net/bugs/684424 Title: Bridges are not transparent for packets -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 684424] Re: Bridges are not transparent for packets
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. https://bugs.launchpad.net/bugs/684424 Title: Bridges are not transparent for packets -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 684424] Re: Bridges are not transparent for packets
Setting promiscuous mode for all devices connected to the bridge does not help. Trying to ping any system from the guest only shows the system not reachable. This error is, in my opinion, not only an annoying bug! It renders kvm, qemu, xen, ... useless. It is something that has to be fixed! The idea route add default gw 192.168.1.4 and then trying ping google.com succeeds. But ping 192.168.1.1 does not. Quite clear: 192.168.1.1 lies within network 192.168.1.0/26! The host *can* reach the gateway --- no routing necessary (for google.com it was necessary: the answering host does not match the netmask. Packets go out to 192.168.1.4, which in tune routes them to 192.168.1.1, which in tune routes them to google.com --- but we're just avoiding the bridge because it does not work as expected). Because icmp-messages Who has do not make their way trough the bridge there will never be an answer. Quite correct from the clients standpoint to tell host not available! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. https://bugs.launchpad.net/bugs/684424 Title: Bridges are not transparent for packets -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
