BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
Hi all,
When I'm reading the ip4_input.c code, I'm confused about the following code.
vnet/vnet/ip/ip4_input.c:ip4_input_inline()
{
...
error0 = error1 = IP4_ERROR_NONE;
/* Punt packets with options. */
error0 =
(ip0-ip_version_and_header_length 0xf) != 5 ?
*What:*
*
*
Jenkins sandbox maintenance will be performed tomorrow***
*
*
*
*Migration to Auth0*
Linux Foundation will be performing maintenance to migrate to our new
SSO service in effort to roll out a more consistent login experience
across all Linux Foundation project services.
The login
It is not supported.
From: on behalf of Venkatarao M
Date: Monday, July 20, 2020 at 8:35 AM
To: "vpp-dev@lists.fd.io"
Cc: praveenkumar A S , Lokesh Chimbili
, Mahesh Sivapuram
Subject: [vpp-dev] How to do Bond interface configuration as
fail_over_mac=active in VPP
Hi all,
We are trying
Reminder
On 7/14/20 2:40 PM, Vanessa Valderrama wrote:
>
> *What: *LF will decomission the FD.io SonarQue instance
>
> *When:* 2020-07-22 at 1700 UTC
>
> *Impact: **sonar.fd.io and code quality reports and history will no
> longer be accessible*
>
> *Why: *LF has migrated to SonarCloud. All
Reminder
On 7/14/20 2:47 PM, Vanessa Valderrama wrote:
>
> *What: *LF will decomission the FD.io OpenGrok instance
>
> *When:* 2020-07-22 at 1700 UTC
>
> *Impact: opengrok**.fd.io will no longer be accessible*
>
> *Why: *After reviewing our inventory it doesn't appear OpenGrok is
> being
Hi all,
We are trying bond interface configuration with VPP and looking for
configuration as fail_over_mac=active as mentioned in below snippet.
We observed in VPP, default bond interface configuration is fail_over_mac =none
and couldn’t see any CLI in VPP to configure bond interface with fail
Hint: “pcap dispatch trace on max 1 buffer-trace 1000”,
then look at the resulting trace in wireshark. It will explain in excruciating
detail how packets flow through the graph.
D.
From: vpp-dev@lists.fd.io On Behalf Of
gerard.ke...@owmobility.com
Sent: Monday, July 20, 2020 9:18 AM
To:
> the value we get in *sl_index_iterate at line 870 is 0 rather than the 4.
The pointer sl_index_iterate points to what would be the next index in the list.
> why this is happening?
That is the normal thing for-loops [0] in C do, if break does not happen.
See [1].
A fix could be something
Thanks for the response Dave.
I don't see anything in our proprietary code that would cause this behaviour. I
did a clean checkout of stable/1908 to see if the same behaviour is present
without any of our code changes and I'm able to reproduce the behaviour using
the sample-plugin provided
We can merge the patch as soon as Neale removes his -2 from it... D.
-Original Message-
From: vpp-dev@lists.fd.io On Behalf Of Christian Hopps
Sent: Monday, July 20, 2020 7:50 AM
To: vpp-dev
Cc: Christian Hopps ; Neale Ranns (nranns)
Subject: [vpp-dev] Regarding new ipsec interface
Hi,
We are testing VAPI for sr policy.
We added two sr policies :-
Policy 1
bsid : 3d97:5fd3:fd2b:e77:a0:d358:c873:9a98
SID List at index 0 : 2001:19:a1::1,2001:19:a2::1,2001:19:a3::1
SID List at index 1 : 2001:19:b1::1,2001:19:b2::1,2001:19:b3::1
SID List at index 2 :
Hi vpp-dev,
In the interest of expressing the community support that Neale asked for
https://gerrit.fd.io/r/c/vpp/+/27795
Looks good to me.
It may need some minor additional development to polish some rough edges, but I
have been able to use it with a few IPTFS specific modifications to
Hi Srini,
To answer your question in the context of NAT.
1) ALGs are unwanted for modern applications. E.g for SIP, ICE/STUN has had to
put in ALG detection mechanisms to be able to deal with ALGs. NAT traversal
works best without ALGs
2) Applications have had 20 years to accommodate NAT (or
14 matches
Mail list logo
