5 unstable releases
0.4.0 | Jun 18, 2023 |
---|---|
0.3.1 | Jun 16, 2023 |
0.3.0 | Jun 16, 2023 |
0.2.3 | Jul 27, 2022 |
0.2.2 | Aug 10, 2021 |
#10 in #neighbor
40 downloads per month
52KB
1K
SLoC
Neighbor Discovery Proxy
This project is an implementaion of RFC 4861 section 7.2.8 written in Rust.
It is similar to another project called ndppd, but it provides an extra recipe called "rewrite", which may help people build IPv6-compatible overlay networks.
usage
Usage:
./ndproxy [OPTIONS]
proxies your neighbor discovery messages.
Optional arguments:
-h,--help Show this help message and exit
-c,--conf CONF The location of your config file. Default:
./ndproxy.toml
You can find an example of configuration file here.
extra recipe: rewrite the prefix
Let's say your network has multiple upstreams and relies on Network Prefix Translation (RFC 6296) (or NETMAP).
For instance:
2001:db8:1::/64 2001:db8:ffff::/64
↑ ↑ ↑
ISP1, translated via NETMAP ISP2, NPTv6 Other Users
|-------- fec1:2:3:4::/64 ---------|
↑
your local devices
To make your local devices available to both of your upstreams while not disturbing other users, you may want a config like:
[ndp]
[ndp.ISP1]
type = "forward"
proxied_prefix = "2001:db8:1::/64"
rewrite_method = "netmap"
local_prefix = "fec1:2:3:4::/64"
<redacted>
[ndp.ISP2]
type = "forward"
proxied_prefix = "2001:db8:ffff::/64"
rewrite_method = "npt"
local_prefix= "fec1:2:3:4::/64"
<redacted>
While running, ndproxy will monitor Neighobor Solicitations from both of your upstreams.
When it captures a valid NS, it will translate the Target Address of the NS to your own private address, and perform Neighbor Discovery locally.
If the requested neighbor exists, ndproxy will send a proxied Neighbor Advertisement back to the related interface.
Dependencies
~10–20MB
~274K SLoC