Skip to content

Instantly share code, notes, and snippets.

@MCterra10
Last active March 19, 2025 12:03
Show Gist options
  • Save MCterra10/7e3930e54db0be10f42dd999e3263560 to your computer and use it in GitHub Desktop.
Save MCterra10/7e3930e54db0be10f42dd999e3263560 to your computer and use it in GitHub Desktop.
ndproxy Install Script for OPNSense (run with sudo)
#!/bin/sh
# save previous working directory to preserve state
PWD=$(pwd)
# download the opnsense OS source
echo ">>> Downloading OPNsense Source Code..."
rm -r /usr/src
git clone --recurse-submodules https://github.com/opnsense/src /usr/src
cd /usr/src
# Download the freebsd ports repo and get ready to build
echo ">>> Downloading FreeBSD Ports Repository..."
rm -r /usr/ports-upstream
git clone --recurse-submodules https://git.FreeBSD.org/ports.git /usr/ports-upstream
cd /usr/ports-upstream/net/ndproxy
# build and install ndproxy again
echo ">>> Building and Installing ndproxy..."
make clean
make install
echo ">>> Done. Cleaning Up..."
# restore PWD
cd $PWD
@MCterra10
Copy link
Author

@MCterra10 I just set the LAN interface address to one of the /64 ranges and enabled DHCPv6, everything seems to be working now and I got 10/10 on test-ipv6.com. What kind of caveats do you recall? Thanks again for the help :)

Sorry for over half a year to reply; the issues I was having is that the ndproxy module has no ability to set a network whitelist; it will respond to ALL neighbor discovery packets on the interface, regardless of whether you are actually using those addresses or not. Because my hosting provider OVH implements IPv6 horribly, I actually receive ND packets for other people's servers, and ended up inadvertently performing a router hijack on their servers 😂
Because of that I had my server shut off a couple of times, and was forced to start using a NAT setup instead, which is horrible but at least my server stays on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment