lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALzJLG8Y3N2PqbJuLTSbfWcxbWJuugZ62nJvz0_Tq7hFSN7axA@mail.gmail.com>
Date:	Tue, 5 Jul 2016 11:11:05 +0300
From:	Saeed Mahameed <saeedm@....mellanox.co.il>
To:	domingo montoya <reach.domingomontoya@...il.com>
Cc:	Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: mlx5 SRIOV VLAN support

On Tue, Jul 5, 2016 at 10:37 AM, domingo montoya
<reach.domingomontoya@...il.com> wrote:
> Hi,
>
> Is VLAN supported in SRIOV mode for mlx5?
>

For VGT mode vlan is supported by default same as bare-metal.
For VST you need to use ip tool to configure VST vlan:  ip link set
eth<X> vf 1 vlan 2 qos 2

note: VGT mode will not work on VF if VST is configured on that VF.

>
> Can anyone please help me to:
>
> Enable VLAN guest tagging in mlx5 PF driver?
>
> Do I need to add any E-switch rules to do the same?
>

No,
Nothing is required for VGT mode, just create the vlan on guest VF
machine and work with it!
E-Swtich is automatically/dynamically configured.

>
> My requirement is something like this:
>
>
> mlx5 VF driver<--------------->mlx5 PF
> driver<------------------------->Network<-----------> mlx5 dedicated
> driver(non-sriov)
>
>
>
> I would like to be able to send ICMP traffic between mlx5 VF driver
> and mlx5 dedicated driver.
>
> My understanding is I should be able to do without adding any rules in
> the E-switch on the PF driver as by default all traffic is allowed.
>
> Is this correct?
>

correct.

>
>
> I tried but as this didn't work. I added ingress rules to allow VLAN
> traffic and also egress rules to the E-switch ACL tables.
>

How did you do this ? changed the code ? by default (no VST/no spoof
check) ACL tables should not be opened.

> But still i cannot see any traffic between mlx5 VF driver and mlx5
> dedicated driver.
>
> I can see that the packets reach the CX4 adapter (mlx5 VF/mlx5 PF) but
> they don't go out on the network.
>
> i tried configuring vlan using ip link add dev enp1s0f0 name
> enp1s0f0.100 type vlan id 100 on both the mlx5 vf driver and mlx5
> dedicated driver.
>
>

Strange, should work. Please make sure VST mode is off on the VF.
can you share some logs with us:
on PF/VF and remote dedicated driver:

ip link show <interface>
ethtool -k <interface>

Thanks,
Saeed.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ