[PVE-User] Linux bridge, kvm, ipv6, intel 10gbe

[Sten Aus]

New information about this Intel 10Gbit network card.
We have managed to get our 10Gbe card working with both - IPv4 and IPv6, 
but only in kernel 3.10.9-pve and using *VEPA.* Downside is that patch 
does not work with kernel 2.6.32.
Tested driver versions 1.2.37 and 1.2.38.

Network setup on physical node:
1) switch - eth4 - vmbr40
2) switch - eth4 - eth4.40 - vmbr40

Patch can be found at https://patchwork.ozlabs.org/patch/470209/

And reading about VEPA can be done at 
http://www.networkworld.com/article/2197460/tech-primers/vepa--an-answer-to-virtual-switching.html

On 06.05.15 12:29, Sten Aus wrote:
>
> Hi
>
> Some new information about this topic. We did some new tests with this 
> Intel 10GBe network card.
>
> Debian 7.8, with kernel 4.0.1 and it seems that IPv6 neighbor 
> solicitation is working fine when using Linux bridges.
>
> It seems that Linus and his developers have used another driver, which 
> Intel does not provide:
>
> |root at debian ~ $ ethtool -i eth4
> driver: i40e
> version: 1.2.6-k
> firmware-version: f4.22 a1.1 n04.25 e8000143f
> |
>
> Still haven't tried this IPv4 bug, which I discovered in version 
> 1.2.37 (see my other Subject in this list: Intel X710 10Gbit network 
> card).
>
> What to do next? I don't know, actually. :)
>
> On 28.04.15 14:45, Sten Aus wrote:
>
>> Hi again
>>
>> No point making udev rule, because i40e driver is not working in my 
>> enivronment. Going to configure Linux bridges on 1G interface and 
>> report a bug for i40e driver.
>>
>> Tried also older OVS (which worked for me in January). And also 
>> oldest i40e driver which I found at Intel's webpage.
>>
>> Thanks to all and all the best!
>>
>> On 28.04.15 13:55, Alexandre DERUMIER wrote:
>>> Hi,
>>>
>>>>> Although udev is still a problem.
>>> you should be able to map macaddress to specific ethX  in
>>>
>>> /etc/udev/rules.d/70-persistent-net.rules
>>>
>>> ----- Mail original -----
>>> De: "Sten Aus" <sten.aus at eenet.ee>
>>> À: "Michael Rasmussen" <mir at miras.org>, "proxmoxve" 
>>> <pve-user at pve.proxmox.com>
>>> Envoyé: Mardi 28 Avril 2015 11:30:02
>>> Objet: Re: [PVE-User] Linux bridge, kvm, ipv6, intel 10gbe
>>>
>>>
>>>
>>> Hi
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> openvswitch is the way to go.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> I sure hope so. :)
>>>
>>> Open vSwitch has been in my mind for some months now. I’ve tested it 
>>> in January (ovs version 2.3.0-1) and got it to work, but as our 
>>> cluster is quite big, I planned to go to ovs in the future.
>>> Anyway it seems that on that node Open vSwitch it is not working as 
>>> fluently as it worked with other node in January. OVS is 2.3.1-1 and 
>>> now I’ve used 10G interface. Then I used 1G interface on motherboard.
>>>
>>> Problems:
>>>
>>>      *
>>>
>>> After reboot, my 10G interface (eth5) is not connected to the bridge 
>>> (udev changes interface names) and thus no packets go to network. As 
>>> soon as i put eth5 to vmbr1234 everything works: ovs-vsct add-port 
>>> vmbr1234 eth5 From dmesg I can see that 10G interface has names: 
>>> eth1 -> eth5 and 1G appears as eth2->rename4->eth0 Despite the fact 
>>> that /etc/rcS.d/ I can see that udev is 02, openvswitch 12 and 
>>> networking 13th in startup row. Awkward.
>>>      *
>>>
>>> Also, two OVSIntPorts will not come “up” (storage88 and storage84 - 
>>> maybe numbers in OVSIntPort name?).
>>>
>>>
>>> Okay, after some manual configuration I got OVS running, but:
>>>
>>>      *
>>>
>>> Regular/normal ping will lost 4 packets from time to time. For 
>>> example, at the beginning 0-3 packets are lost somewhere, I will 
>>> hear reply after 4th packet. And then same thing happens after 14th 
>>> packet or so.
>>>      *
>>>
>>> And within ovs 2.3.0 version I was able to create OVSIntPort with 
>>> “vmbr” name as well, now I need to add different name to my Internal 
>>> port (within one node).
>>>
>>>
>>> Solutions:
>>>
>>>
>>>      * Downgraded i40e driver from 1.2.38 (downloaded from Intel 
>>> webpage) to 1.1.23 and no OVS is almost working. Storage interfaces 
>>> are still pain. Ping works correctly, but no iscsi connections are 
>>> made.
>>>
>>>
>>> Although udev is still a problem.
>>>
>>> _______________________________________________
>>> pve-user mailing list
>>> pve-user at pve.proxmox.com
>>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>
>>
>>
>>
>> _______________________________________________
>> pve-user mailing list
>> pve-user at pve.proxmox.com
>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> ​
>
>
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.proxmox.com/pipermail/pve-user/attachments/20150525/785dd18a/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3242 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.proxmox.com/pipermail/pve-user/attachments/20150525/785dd18a/attachment.bin>