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

Should we accept VNI zero? #195

Open
daniel-noland opened this issue Feb 1, 2025 · 0 comments
Open

Should we accept VNI zero? #195

daniel-noland opened this issue Feb 1, 2025 · 0 comments
Labels
question Further information is requested

Comments

@daniel-noland
Copy link
Collaborator

I can't find anything in the official VXLAN spec (RFC7348) which precludes zero as a valid VNI.

It looks like the Linux kernel and OVS both accept 0 as a valid VNI, while Arista documentation states

VNI values range from 1 to 16777215

--- EOS 4.33.1F User Manual

Aruba also takes this stance

Range: 1 to 16777214.

--- Aruba Help Center - VNI

In a capricious deviation from the RFC, Cisco documentation states that

It is typically a 24-bit value part of the VXLAN header, which can support up to 16 million individual network segments. (Valid VNI values are from 4096 to 16,777,215.)

--- Implementing Data Center Overlay Protocols

We need to decide what we want to do here in terms of validity checks.

@daniel-noland daniel-noland added the question Further information is requested label Feb 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant