How to enable IPv6 on MB PRO2
Posted: Mon Jun 15, 2026 5:03 am
Hey folks,
I recently acquired a MB PRO2 and figured out how to enable IPv6 on it.
The OpenWrt base apps are configured for IPv6 already. This includes the HTTP server and avahi, so mDNS will respond to IPv6 mDNS queries and responses will return IPv6 addresses. Once enabled you can go to 'mbpro2.local' in your web browser and access the admin interface over IPv6. The settings are stored with the rest of the OpenWrt settings and will survive reboots.
WARNING: Changing the network config of the PRO2 improperly could render it inaccessible. Back up configurations before proceeding.
To enable IPv6 on the PRO2 on a network set for either SLAAC or Managed addresses using DHCPv6, ssh in as root and run these commands:
Once the network restart completes, you can run and see your new IPv6 addresses.
Options are available for a static address, or generating a predictable address, if needed.
EDIT: IPv6 would work on events if it wasn't getting deprioritized by a command line option. Can we get a way to remove the --prefer-family option from the wget call so events will use IPv6 if available? I can hack around it by adding a AAAA-only DNS name for my server so wget will use IPv6, but that removes the IPv4 fallback path. I could also hack around it with a shell script replacing wget-ssl that strips the option...
/home/openssl/wget-ssl --content-on-error --no-check-certificate -U meteobridge --no-http-keep-alive --prefer-family=IPv4 -nv -T 13 -t 1 -o /home/meteohub/.wgeterr -O /home/meteohub/.wgetres '...'
EDIT 2: Looks like weather network uploads call wget for any HTTP type submission, so a shell script to strip that pesky --prefer-family option switches those over too. Only things left sending IPv4 traffic on my MB PRO2 are DNS, PurpleAir sensor queries, and DHCPv4, and that's fine with me. Weather network updates are using DNS64/NAT64 for those that are IPv4 only.
I recently acquired a MB PRO2 and figured out how to enable IPv6 on it.
The OpenWrt base apps are configured for IPv6 already. This includes the HTTP server and avahi, so mDNS will respond to IPv6 mDNS queries and responses will return IPv6 addresses. Once enabled you can go to 'mbpro2.local' in your web browser and access the admin interface over IPv6. The settings are stored with the rest of the OpenWrt settings and will survive reboots.
WARNING: Changing the network config of the PRO2 improperly could render it inaccessible. Back up configurations before proceeding.
To enable IPv6 on the PRO2 on a network set for either SLAAC or Managed addresses using DHCPv6, ssh in as root and run these commands:
Code: Select all
# uci set network.lan6=interface
# uci set network.lan6.proto='dhcpv6'
# uci set network.lan6.device='@lan'
# uci set network.lan6.reqaddress='none'
# uci commit network.lan6
# service network restart
Code: Select all
ip addr showOptions are available for a static address, or generating a predictable address, if needed.
EDIT: IPv6 would work on events if it wasn't getting deprioritized by a command line option. Can we get a way to remove the --prefer-family option from the wget call so events will use IPv6 if available? I can hack around it by adding a AAAA-only DNS name for my server so wget will use IPv6, but that removes the IPv4 fallback path. I could also hack around it with a shell script replacing wget-ssl that strips the option...
/home/openssl/wget-ssl --content-on-error --no-check-certificate -U meteobridge --no-http-keep-alive --prefer-family=IPv4 -nv -T 13 -t 1 -o /home/meteohub/.wgeterr -O /home/meteohub/.wgetres '...'
EDIT 2: Looks like weather network uploads call wget for any HTTP type submission, so a shell script to strip that pesky --prefer-family option switches those over too. Only things left sending IPv4 traffic on my MB PRO2 are DNS, PurpleAir sensor queries, and DHCPv4, and that's fine with me. Weather network updates are using DNS64/NAT64 for those that are IPv4 only.