Re: [Qemu-devel] [Bug 1362755] [NEW] QEmu +2 does not route VLAN tagged packets, that are originated within the Hypervisor itself.

2014-10-22 Thread Martinx - ジェームズ
On 19 October 2014 03:30, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Oops! It seems to be working now! :-D This that I just said: I tried to disable tso/gso/tx at another guest, of vlan100 net, didn't worked either. Isn't true... I created a new guest, side-by-side with guest-fw-1

Re: [Qemu-devel] [Bug 1362755] [NEW] QEmu +2 does not route VLAN tagged packets, that are originated within the Hypervisor itself.

2014-10-18 Thread Martinx - ジェームズ
Hey Vlad, Sorry about this delay... I tried the following commands within the guest (that router/firewall guest-fw-1.domain.com): root@guest-fw-1:~# ethtool -K eth1 tso off root@guest-fw-1:~# ethtool -K eth1 gso off root@guest-fw-1:~# ethtool -K eth1 tx off But it did not fixed the problem...

Re: [Qemu-devel] [Bug 1362755] [NEW] QEmu +2 does not route VLAN tagged packets, that are originated within the Hypervisor itself.

2014-10-18 Thread Martinx - ジェームズ
Oops! It seems to be working now! :-D This that I just said: I tried to disable tso/gso/tx at another guest, of vlan100 net, didn't worked either. Isn't true... I created a new guest, side-by-side with guest-fw-1, on vlan100, and after disabling `tso/gso/tx`, its connectivity becomes