Ah, I see, looks like interest disappeared after RH changed centos release
policy.
That's why compilation fails under RHEL, while working out of the box under
ubuntu 😉
От: Damjan Marion
Отправлено: 23 сентября 2021 г. 18:06
Кому: Юрий Иванов
Копия: vpp-dev@list
Hi all,
As per previous announcement, I have pulled stable/2110 branch, laid
the tags and checked that the artifacts for 21.10-rc1 are available
from the usual location: https://packagecloud.io/fdio/2110
The master branch is open for all commits.
The stable/2110 branch is open for your bugfixes.
—
Damjan
> On 23.09.2021., at 15:00, Юрий Иванов wrote:
>
> Hi,
>
> I see there is no rdma plugin in prebuilded packages 21.06 version
> [suser@RockyVPP-1 ~]$ dnf repoquery -l vpp* | grep rdma | grep -P ".so$" |
> grep plugi
> Last metadata expiration check: 0:00:05 ago on Thu 23 Sep 2021
Hi Mohsin,
thanks for the patches. I've abandoned mine in favor of these.
On Thu, Sep 23, 2021 at 12:23 AM Mohsin Kazmi (sykazmi)
wrote:
> Hi Ivan,
>
>
>
> Thank you so much for reporting the issue. cxq_vring field is specific to
> virtio pci. It should not be accessed or set in tap driver.
>
>
Resolved.
VPP always generates new random mac address for outgoing IPs.
Weird but sometimes their are totally dofferent:
02:fe:b7:13:b8:a0 18.31.0.1
02:fe:0d:30:68:36 18.31.0.2
02:fe:b7:13:b8:a0 18.31.0.3
02:fe:cb:85:69:f7 18.31.0.4
02:fe:0d:30:68:36 18.31.0.5
02:fe:0d:30:68:36 18.31.0.6
02:fe:b7:1
Hi,
I see there is no rdma plugin in prebuilded packages 21.06 version
[suser@RockyVPP-1 ~]$ dnf repoquery -l vpp* | grep rdma | grep -P ".so$" | grep
plugi
Last metadata expiration check: 0:00:05 ago on Thu 23 Sep 2021 03:56:39 PM EEST.
[suser@RockyVPP-1 ~]$
But it exists in 21.06 packages vers
Hi Mark,
If you have a glean pointing out an interface, then you have an ipv6 address on
that interface. The presence of an address will ipv6 enable the interface, so
you don’t need that command as well.
Your errors are not necessarily signs of a bad config, but an indication that a
host on th
Hi neale,
Thanks for the info, is enabling ipv6 on interface with "enable ip6
interface" command is necessary? I saw before without it i could ping in a
very simple ipv6 scenario but can enabling ipv6 on interfaces help this
address overflow errors?
Best regards,
Mark
On Thu, Sep 23, 2021, 12:45
Hi Mark,
If traffic matches a ipv6-glean then it is destined to a host on an attached
subnet that does not yet have an ND entry. Matching the glean will generate an
ND solicitation to that host, but these are rate limited. An address overflow
can happen when:
1. when the rate limiting kicks
