VXLAN decapsulation for tenant-to-tenant flow data

Open
#528 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
networking

Research direction

The report concerns the BaseLayer check, which hides inner IP, port and protocol fields once a custom LayerStack parser hands off to Ethernet after UDP. Start by reading how the layer stack passes the next parser and where that check gates field extraction. The issue asks for a supported decapsulation design, not a patch, so done means a maintainer-agreed approach for tunnelled flows.

Written by the indexing model from the issue text.

Description

enhancement

I created a custom parser to decapsulate VXLAN flows with a new LayerStack after UDP where I set next parser to Ethernet. Unfortunately it's not enough because once the flow enters the inner Ethernet and subsequent layers, the inner IP/port/protocol fields are gated behind the BaseLayer check.

It'd be useful to have a supported way to decapsulate any tunneling protocol to that end without downstream field silently being suppressed.

Dominant language
Go
Stars
817
Forks
182
Avg merge
4h 18m
Merged PRs (30d)
6

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from netsampler/goflow2

All issues in netsampler/goflow2

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.