Bug #4240
closed
2.2 IPv6 radvd RDNSS Issue
0%
Description
I'm have a 2.2 box running 10.1-RELEASE-p4 FreeBSD 10.1-RELEASE-p4 #0 36d7dec(releng/10.1)-dirty: Fri Jan 16 12:38:50 CST 2015.
I have configured 2 WAN interfaces, one of which has DHCPv6 enabled (TWC).
Internally, I have 3 networks defined: LAN, Guest & DMZ. LAN & Guest have track interface configured, tracking the TWC WAN interface, and each obtaining a /64. I have configured the DNS resolver (unbound) to listen on the three internal interfaces as well as localhost.
The /var/etc/radvd.conf does show that the RDNSS for the Guest network to be the Guest IPv6 interface IP, and the LAN interface to be the LAN interface IPv6 IP. However, LAN clients are receiving the Guest interface IPv6 IP as their DNS server and not the LAN interface IP.
Files
| Guest-int-status.png (404 KB) Guest-int-status.png | |||
| LAN-int.png (419 KB) LAN-int.png | |||
| Guest-int.png (420 KB) Guest-int.png | |||
| lan-pc-client-status.png (744 KB) lan-pc-client-status.png | |||
| LAN-int-status.png (403 KB) LAN-int-status.png |
Updated by Adam Fathauer almost 10 years ago
- File Guest-int-status.png Guest-int-status.png added
- File LAN-int.png LAN-int.png added
- File Guest-int.png Guest-int.png added
- File lan-pc-client-status.png lan-pc-client-status.png added
- File LAN-int-status.png LAN-int-status.png added
attached screenshots
Updated by Chris Buechler over 9 years ago
- Status changed from New to Feedback
Not seeing how that could happen. Not replicable in a similar config. Maybe your VLANs are interconnected somehow so the RAs from guest are also going out LAN? If this is still replicable on 2.2.4, what does a packet capture of the RA traffic look like?
Updated by Chris Buechler almost 9 years ago
- Status changed from Feedback to Not a Bug
- Affected Version deleted (
2.2)
radvd's config and behavior is correct in this circumstance.