Bug #7093
closed
"Outgoing Network Interfaces" is broken in dns resolver settings
0%
Description
The "Outgoing Network Interfaces" incorrectly applies the WAN ipv6 link-local when ALL is not selected and also when ipv6 link-local is not selected.
This is different behaviour to the "Network Interfaces" setting which behaves properly,so as such this looks like a clear bug.
Updated by
Updated by Jim Pingle almost 9 years ago
- Status changed from New to Rejected
- Assignee changed from Jim Pingle to Chris Collins
- Target version deleted (
2.4.0)
I cannot reproduce this on current 2.4 snapshots. I have tried a variety of outgoing and other interface configurations with static and DHCP IPv6 assignments and the behavior is correct in each case. You will need to supply the specific details of your interface, routing, and unbound configuration and the exact steps to reproduce, preferably with a copy of your config or status output (/status.php, download the .tgz file) while it's in the broken state.
Updated by Chris Collins almost 9 years ago
is it sufficient to do a backup of the config and send you that backup?
The setup is this.
Dns resolver enabled dns forwarder disabled.
WAN ipv4 is DHCP, there is dhcp-options configured to send authentication to the isp in the dhcp packets.
WAN ipv6 is DHCP6.
Track IPV6 is enabled in LAN network settings on part of advanced setup, so a ipv6 is assigned to the pfSense box.
There is a custom route configured to access a 2nd lan subnet on my modem so I can access the modem over WAN cable.
I do currently have some custom settings in unbound however those do not cause the bug, it occurs when the custom box is blank.
I will try to write a detailed document including steps to reproduce but I cannot put a timescale on when this will be done.
Sadly I cannot remember if this was a problem on pfSense 2.2.
Updated by Jim Pingle almost 9 years ago
The configuration is not enough on its own because your interfaces are DHCP. We need to see the addresses on the interface, routing tables, etc.