lbailly/vxlan-router
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Archived. We won't implement our own vtep and prefer the uses of linux vteps.
This repository has been archived on 2025-03-02. You can view files and clone it, but you cannot make any changes to its state, such as pushing and creating new issues, pull requests or comments.
15 commits 1 branch 0 tags 61 KiB
Find a file
Exact
catvayor 70b06cb6ef
 feat: gateway 
untested
2025-02-21 16:42:55 +01:00
src feat: gateway 2025-02-21 16:42:55 +01:00
vm fix(test): desactivate offload to have good csum 2025-02-01 23:33:19 +01:00
.gitignore test(vm/containers): build network topology with containers 2025-01-30 23:18:54 +01:00
Cargo.lock feat: wip! wip! gateway for all VNIs 2025-02-12 00:12:55 +01:00
Cargo.toml feat: wip! wip! gateway 2025-02-19 16:31:34 +01:00
readme.md feat: gateway 2025-02-21 16:42:55 +01:00
shell.nix feat(test): script for simple connect to vm 2025-02-01 13:23:10 +01:00
vm.nix test: init vm config for mininet 2025-01-30 14:51:16 +01:00

readme.md

VXLAN-router

To use vxlan in isp, we need to implement a VTEP for vault01.

Roadmap

  1. Basic router which forward to every connected VTEP -> bad idea without mac learning
  2. Special case for when we are the target (internet, DNS)
  3. Mac learning
  4. DHCP, which removes user prefixes, (comes with ARP snooping ?)
  5. Reverse path checking, filter auto ip attribution
  6. [external] Patch hostapd to use VXLAN
  7. [external] Maybe patch radius to use all VNIs (if there's a limitation)
  8. Allow packets to cross VNIs (from an external decision, cached)
  9. Synchronisation between multiple instances