Bug 227033 - vxlan(4) does not work with vni larger than 65535
Summary: vxlan(4) does not work with vni larger than 65535
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 11.1-RELEASE
Hardware: amd64 Any
: --- Affects Some People
Assignee: Qing Li
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-28 12:40 UTC by susurrus.silent
Modified: 2024-01-10 04:03 UTC (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description susurrus.silent 2018-03-28 12:40:33 UTC 
vxlan(4) does not work with vni >= 65536.

How to reproduce:

on host A:
ifconfig vxlan create inet 192.168.200.1/24 vxlanvni 65536 vxlanlocal 192.168.100.1 vxlanremote 192.168.100.2

on host B:
ifconfig vxlan create inet 192.168.200.2/24 vxlanvni 65536 vxlanlocal 192.168.100.2 vxlanremote 192.168.100.1

on host A:
ping -n 192.168.200.2

host B is unreachable as host B does not respond to arp request.
Comment 1 Sergey Akhmatov 2020-09-12 11:22:24 UTC 
Can confirm: the bug is still there in 12-STABLE (r364973)

I can see transmitted packets encapsulated in vxlan with correct VNI > 65535. It seems that receiving host can't decapsulate such packets.
Comment 2 Aleksandr Fedorov freebsd_committer freebsd_triage 2020-09-15 11:43:43 UTC 
This should be fixed in 13.0-CURRENT r364257, see:
https://reviews.freebsd.org/D26071

With this patch I can set VNI to 70000 and 2000000.

So, I think it should be MFC'd to 12-STABLE.
Comment 3 Sergey Akhmatov 2022-09-20 21:00:31 UTC 
It was fixes long time ago, I suggest closing this PR.
https://cgit.freebsd.org/src/commit/?id=a5154bb2e5d6f
https://reviews.freebsd.org/rS364257
Comment 4 Mark Linimon freebsd_committer freebsd_triage 2024-01-10 04:03:23 UTC 
^Triage: assign to committer that resolved back in 2020.