Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update from update/networkservicemesh/sdk-vpp #130

Merged
merged 1 commit into from
Nov 22, 2021

Conversation

nsmbot
Copy link
Contributor

@nsmbot nsmbot commented Nov 22, 2021

Update go.mod and go.sum to latest version from networkservicemesh/sdk-vpp@main
PR link: networkservicemesh/sdk-vpp#452
Commit: 7958db6
Author: Ed Warnicke
Date: 2021-11-22 09:09:20 -0600
Message:

  • Fix for mtu issues with kernelvethpair (# 452)
    This probably fixes:
    1st fragment dropped on VxLAN connection sdk#1148
    The underlying issue was that the end of the vethpair to which
    VPP was attaching with afpacket was not getting its MTU set correctly.
    As a result, if an oversized packet was sent over it, it would be fragmented
    by the kernel to a size that matches the mtu on the end of the veth pair
    that was in the NSC network namespace.
    The resulting packet would still be to large for the MTU of the end of the
    vethpair attached to the VPP instance, and would be dropped there.
    The second fragment, being smaller, would be smaller than the MTU of the
    end of the vethpair to which VPP was attached with af-packet, and so get
    through.

…k-vpp@main

PR link: networkservicemesh/sdk-vpp#452

Commit: 7958db6
Author: Ed Warnicke
Date: 2021-11-22 09:09:20 -0600
Message:
  - Fix for mtu issues with kernelvethpair (#452)
This *probably* fixes:
networkservicemesh/sdk#1148

The underlying issue was that the end of the vethpair to which
VPP was attaching with afpacket was not getting its MTU set correctly.
As a result, if an oversized packet was sent over it, it would be fragmented
by the kernel to a size that matches the mtu on the end of the veth pair
that was in the NSC network namespace.

The resulting packet would *still* be to large for the MTU of the end of the
vethpair attached to the VPP instance, and would be dropped there.

The second fragment, being smaller, would be smaller than the MTU of the
end of the vethpair to which VPP was attached with af-packet, and so get
through.

Signed-off-by: NSMBot <[email protected]>
@github-actions github-actions bot merged commit 175b8db into main Nov 22, 2021
nsmbot pushed a commit that referenced this pull request Apr 23, 2024
This PR syncs files with https://github.com/networkservicemesh/cmd-template

Revision: https://github.com/networkservicemesh/cmd-template/commits/7369b5fd24fe89c8021d5dcf3f5aea3393a64805

commit 7369b5fd24fe89c8021d5dcf3f5aea3393a64805
Author: Nikita Skrynnik <[email protected]>
Date:   Tue Apr 23 20:12:10 2024 +0700

    Delete check-release-branch job from release workflow (#130)

    * Delete check-release-branch job from release workflow

    Signed-off-by: NikitaSkrynnik <[email protected]>

    * minor fixes

    Signed-off-by: NikitaSkrynnik <[email protected]>

    ---------

    Signed-off-by: NikitaSkrynnik <[email protected]>

Signed-off-by: NSMBot <[email protected]>
nsmbot added a commit that referenced this pull request Apr 23, 2024
This PR syncs files with https://github.com/networkservicemesh/cmd-template

Revision: https://github.com/networkservicemesh/cmd-template/commits/7369b5fd24fe89c8021d5dcf3f5aea3393a64805

commit 7369b5fd24fe89c8021d5dcf3f5aea3393a64805
Author: Nikita Skrynnik <[email protected]>
Date:   Tue Apr 23 20:12:10 2024 +0700

    Delete check-release-branch job from release workflow (#130)

    * Delete check-release-branch job from release workflow

    Signed-off-by: NikitaSkrynnik <[email protected]>

    * minor fixes

    Signed-off-by: NikitaSkrynnik <[email protected]>

    ---------

    Signed-off-by: NikitaSkrynnik <[email protected]>

Signed-off-by: NSMBot <[email protected]>
Co-authored-by: NSMBot <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant