Project

General

Profile

Actions

Bug #3163

closed

XS4All IPv6 does not work

Added by Rob J. Epping about 11 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
-
Start date:
08/26/2013
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

Ever since 2.1-RC1 my IPv6 connection (XS4all DHCPv6-PD) is broken.
I use a Vigor120 ADSL modem as PPPoA to PPPoE bridge and an ALIX 2D13 with pfSense.

Somehow the physical interface connecting to the vigor is detected as the ipv6 interface (interface statement in /var/etc/dhcp6c_wan.conf)
This should be the PPPoE interface.

It worked with the last set of 2.1-RC0 images I used.

What is going on here?


Files

dhcp6c_debug.log (26.3 KB) dhcp6c_debug.log Wouter Snels, 08/31/2013 04:15 AM
Actions #1

Updated by Wouter Snels about 11 years ago

I think this is related to the item I posted 2 days ago on the forum, I also have native ipv6 issue it used to work and it doesn't now anymore, ..

Starting DHCPv6 relay service...
Warning: array_unique() expects parameter 1 to be array, null given in /etc/inc/services.inc on lin0
Configuring firewall.....0 table deleted.
.done.

this is the error i found, .. for some reason the ipv6 assigned to pppoe doesn't show in the web interface, and dhcp client doesn't start there for the routing can't be added through bgp

i have the same hardware as you and i've got edpnet ipv6 used to work before i upgraded as well.

Actions #2

Updated by Wouter Snels about 11 years ago

edit: http://forum.pfsense.org/index.php/topic,65832.msg359062.html#msg359062 starting the dhcp6c client manually made it work again, .. however it crashes that very same instant. At least for me the dynamic route was added which made my ipv6 prefix work for me.

Actions #3

Updated by Rob J. Epping about 11 years ago

Also posted on the forum.

It looks to me like the setup of the ipv6 WAN interface is broken.
Instead of configuring pppoe0 in the appropriate files the underlying physical interface is used (vr2 in my case)

After manually changing vr2 to pppoe0 in /var/etc/dhcp6c_wan.conf and /var/etc/dhcp6c_wan_script.sh ipv6 and starting dhcp6c like above ipv6 addresses are assigned and used by clients.
Then the default has to be changed since that also is set to vr2 instead of pppoe0

Actions #4

Updated by Rob J. Epping about 11 years ago

avink in the forum is right. Checking the box "Use IPv4 connectivity as parent interface" makes the config files use the correct interface.

Wording is BAD as there is no IPv4 involved. Its IPV6CP in the same PPP tunnel as IPCP.

Actions #5

Updated by Wouter Snels about 11 years ago

i have that checked all the time ! no that doesn't make it right

Actions #6

Updated by Wouter Snels about 11 years ago

maybe the output of the dhcp6c helps.

Actions #7

Updated by Wouter Snels about 11 years ago

adding version couldn't hurt either I suppose.

FreeBSD xxxx.xxxxxx.xxx 8.3-RELEASE-p10 FreeBSD 8.3-RELEASE-p10 #0: Mon Aug 26 00:33:25 EDT 26

Actions #8

Updated by Chris Buechler about 9 years ago

  • Category set to Interfaces
  • Status changed from New to Feedback

Can anyone on that ISP try with 2.2.5 and report back? Suspect this is something that's long since been fixed.

Actions #9

Updated by Chris Buechler almost 9 years ago

  • Status changed from Feedback to Resolved

variety of dhcp6c related changes in other tickets since then. No recent reports of dhcp6c crashes like were seen here

Actions

Also available in: Atom PDF