Em 12-03-2014 16:33, sven falempin escreveu:
> On Wed, Mar 12, 2014 at 2:01 PM, Stuart Henderson <st...@openbsd.org> wrote:
>> On 2014/03/12 13:47, sven falempin wrote:
>>>> You might do better with qemu socket network devices (or the L2TPv3
>>>> support that was recently added to qemu head), which should allow a
>>>> "direct" connection between the virtual interfaces, rather than using
>>>> a bridge device that exists outside the VMs.
>>>>
>>> qemu is 1.7.0
>>>
>>> something like :
>>>
>>> vio0(bsd1) <---> socket client 127.0.0.1:5000 <---> socket server
>>> 127.0.0.1:5000 <---> vio0(bsd2)
>> The sockets just talk directly to each other, you don't need a server.
>
> Because i am an idiot and do not listen GOOD advice, i created two
> ethernet tunnel with almighty SSH.
>
> But apparently LACP is not forwarded, (the round robin works just
> fine), here is the trunk with the two link0 tun
> and the LACP packet sended to LACP <slow protocol>
>
>
> tun0: flags=9943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,LINK0,MULTICAST> mtu 
> 1500
>         lladdr fe:e1:ba:d1:62:79
>         priority: 0
>         trunk: trunkdev trunk0
>         groups: tun
>         status: active
>         inet6 fe80::f044:d4c2:63de:2fc4%tun0 prefixlen 64 scopeid 0x8
> tun1: flags=9943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,LINK0,MULTICAST> mtu 
> 1500
>         lladdr fe:e1:ba:d1:62:79
>         priority: 0
>         trunk: trunkdev trunk0
>         groups: tun
>         status: active
>         inet6 fe80::f044:d4c2:63de:2fc4%tun1 prefixlen 64 scopeid 0xa
> trunk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         lladdr fe:e1:ba:d1:62:79
>         priority: 0
>         trunk: trunkproto lacp
>         trunk id: [(0000,00:00:00:00:00:00,0000,0000,0000),
>                  (0000,00:00:00:00:00:00,0000,0000,0000)]
>                 trunkport tun1 collecting,distributing
>                 trunkport tun0 collecting,distributing
>         groups: trunk
>         media: Ethernet autoselect
>         status: active
>         inet 172.18.1.2 netmask 0xffff0000 broadcast 172.18.255.255
>         inet6 fe80::fce1:baff:fed1:6279%trunk0 prefixlen 64 scopeid 0xb
> #  tcpdump -tteni tun0
> tcpdump: listening on tun0, link-type EN10MB
> 1394652132.550634 fe:e1:ba:d7:fb:2e 01:80:c2:00:00:02 8809 124:
> LACPv1, length: 110
> 1394652159.024470 fe:e1:ba:d1:62:79 01:80:c2:00:00:02 8809 124:
> LACPv1, length: 110
>
>
> I guess 01:80:c2:00:00:02 is not sent to the other side ???? is this
> normal , a tun should forward broadcast, should it not ?
>
> *go read qemu socket node*
>
If it is configured with the link0 option, yes.

-- 
Giancarlo Razzolini
GPG: 4096R/77B981BC

Reply via email to