Project

General

Profile

Bug #2414

IPv6 DHCP WAN, issue routing firewall-generated traffic

Added by Jim Pingle over 8 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Routing
Target version:
Start date:
05/08/2012
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.1-IPv6
Affected Architecture:

Description

From Seth:

There is a problem where pfSense itself can not reach the ipv6 internet [with a DHCPv6 WAN] leading to issues with anything that attempts to load remote ipv6 content causing issues in dns, http etc. This could be the DHCP6 client setting the routes too strict, or the firewall rules itself on pfSense are too strict to get out. This might be specific to the dhcp6 client setup.

When I tried this, my WAN received a prefixlen of 128, not sure if that's related.

Split off from #2347

Associated revisions

Revision 63127eee (diff)
Added by Seth Mos about 8 years ago

Make sure that we configure the track interface from the DHCP6 wan, correct typo.
Redmine ticket #2414

Revision 61c4383d (diff)
Added by Seth Mos about 8 years ago

A few launch improvements so that configuring the DHCP6 client on the WAN it immediately kicks in.
With the fixed rc.newwanipv6 it should immediately spring to life.
Redmine ticket #2414

History

#1 Updated by Seth Mos about 8 years ago

Just tested a upgrade from a 2.0.2 VM to 2.1, configured WAN for DHCP6 and LAN as track, prefix id. 0
Does not bring up a DHCP6 address on the WAN or a prefix on the LAN.

Reboot the router with those settings and it comes up without issue. Maybe firewall rules for DHCP6 not being applied yet?

#2 Updated by Chris Buechler over 7 years ago

  • Affected Version set to 2.1-IPv6

#3 Updated by Ermal Lu├ži over 7 years ago

  • Status changed from New to Feedback

#4 Updated by Jim Pingle over 7 years ago

At some point this was fixed or some other change fixed it, as it still shows /128 prefix but it works fully now. A router behind a PD setup gets a DHCPv6 WAN IP and also has full IPv6 connectivity outbound.

#5 Updated by Chris Buechler over 7 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF