Did you reboot the device that was having connection issues?

or do an ipconfig /release ipconfig /renew (and maybe even a ipconfig /flushdns)

I've spent the past couple of weeks on and off trying to get IPv6 working with my Hyper-V/pfSense2.3 (and 2.4) setup over UFB. Sadly, after many reboots, no success.

Following the instructions by OP, here are my WAN settings:

On the LAN interface page, I have IPv6 Configuration Type set to track the WAN interface. pfSense only seems to assign itself an IPv6 address beginning with fe80::

On one occasion, pfSense did get an IPv6 address assigned by Bigpipe and devices on my network were also assigned Bigpipe addresses. This happened after I switched back to my usual pfSense 2.3 VM after trying the pfSense 2.4 beta on a  separate VM (which also had no luck aquiring an address). After booting 2.3, it took a long time (2-3 minutes) to get an IPv4 address when it's usually completed within seconds. When it did finally get our static IPv4 address, magically the IPv6 address was assigned and had picked up the v6 DNS servers too. I've never been able to get this back after rebooting (and not changing any settings).

Anyone else had a similar experience or figured out why pfSense is so problematic with this setup?

edit: I've also allowed ICMP to WAN and LAN addresses for IPv6 packets in the firewall rules.

random173:

 

Anyone else had a similar experience or figured out why pfSense is so problematic with this setup?

 

Your experience is consistent with what I was seeing. I also managed to get an IPv6 address twice, but it would not stick.

There were a number of possible causes and solutions (including the firewall rules you mentioned), none of which resolved the issue for me.

If it is of any assistance, my setup is using the em driver for the WAN and LAN interfaces, and VLAN 10 for Bigpipe.

SirHumphreyAppleby:

 

 

 

If it is of any assistance, my setup is using the em driver for the WAN and LAN interfaces, and VLAN 10 for Bigpipe.

 

Interesting. I see that someone else has been successful using pfSense but they were using ASDL, I wonder what differences that may make. I don't use VLAN with our setup, I think we requested to remove that last year some time.

Hi all, I have been on the Bigpipe IPv6 trial since day 1.  My tp-link router works well with IPv6, but I have problems with an Edgerouter Lite 3.  The ERL is running firmware versin 1.9.1 but the hardware itself has the old logo on it.

Here is the config of my ERL.  eth0 is WAN, eth1 is my LAN, eth2 is configured but nothing connected to it.  I connect my laptop to LAN1 via an unmanaged switch (sometime I connect it directly to eth1 without the switch).

**********

firewall {
    all-ping enable
    broadcast-ping disable
    ipv6-name WANv6_IN {
        default-action drop
        description "WAN inbound traffic forwarded to LAN"
        enable-default-log
        rule 10 {
            action accept
            description "Allow established/related sessions"
            state {
                established enable
                related enable
            }
        }
        rule 20 {
            action drop
            description "Drop invalid state"
            state {
                invalid enable
            }
        }
    }
    ipv6-name WANv6_LOCAL {
        default-action drop
        description "WAN inbound traffic to the router"
        enable-default-log
        rule 10 {
            action accept
            description "Allow established/related sessions"
            state {
                established enable
                related enable
            }
        }
        rule 20 {
            action drop
            description "Drop invalid state"
            state {
                invalid enable
            }
        }
        rule 30 {
            action accept
            description "Allow IPv6 icmp"
            protocol ipv6-icmp
        }
        rule 40 {
            action accept
            description "allow dhcpv6"
            destination {
                port 546
            }
            protocol udp
            source {
                port 547
            }
        }
    }
    ipv6-receive-redirects disable
    ipv6-src-route disable
    ip-src-route disable
    log-martians enable
    name WAN_IN {
        default-action drop
        description "WAN to internal"
        rule 10 {
            action accept
            description "Allow established/related"
            state {
                established enable
                related enable
            }
        }
        rule 20 {
            action drop
            description "Drop invalid state"
            state {
                invalid enable
            }
        }
    }
    name WAN_LOCAL {
        default-action drop
        description "WAN to router"
        rule 10 {
            action accept
            description "Allow established/related"
            state {
                established enable
                related enable
            }
        }
        rule 20 {
            action drop
            description "Drop invalid state"
            state {
                invalid enable
            }
        }
    }
    receive-redirects disable
    send-redirects enable
    source-validation disable
    syn-cookies enable
}
interfaces {
    ethernet eth0 {
        description "Internet (PPPoE)"
        duplex auto
        pppoe 0 {
            default-route auto
            dhcpv6-pd {
                pd 0 {
                    interface eth1 {
                        host-address ::1
                        prefix-id :0
                        service slaac
                    }
                    interface eth2 {
                        host-address ::1
                        prefix-id :1
                        service slaac
                    }
                    prefix-length /60
                }
                rapid-commit enable
            }
            firewall {
                in {
                    ipv6-name WANv6_IN
                    name WAN_IN
                }
                local {
                    ipv6-name WANv6_LOCAL
                    name WAN_LOCAL
                }
            }
            ipv6 {
                dup-addr-detect-transmits 1
                enable {
                }
            }
            mtu 1492
            name-server auto
            password ****************
            user-id bigpipe
        }
        speed auto
    }
    ethernet eth1 {
        address 192.168.11.41/24
        description Local
        duplex auto
        speed auto
    }
    ethernet eth2 {
        address 192.168.12.1/24
        description "Local 2"
        duplex auto
        speed auto
    }
    loopback lo {
    }
}
protocols {
    static {
        interface-route6 ::/0 {
            next-hop-interface pppoe0 {
            }
        }
    }
}
service {
    dhcp-server {
        disabled false
        hostfile-update disable
        shared-network-name LAN1 {
            authoritative enable
            subnet 192.168.11.0/24 {
                default-router 192.168.11.41
                dns-server 203.96.123.1
                dns-server 203.96.123.2
                lease 10800
                start 192.168.11.70 {
                    stop 192.168.11.89
                }
            }
        }
        shared-network-name LAN2 {
            authoritative enable
            subnet 192.168.12.0/24 {
                default-router 192.168.12.1
                dns-server 203.96.123.1
                dns-server 203.96.123.2
                lease 10800
                start 192.168.12.70 {
                    stop 192.168.12.89
                }
            }
        }
        use-dnsmasq disable
    }
    dns {
        forwarding {
            cache-size 150
            listen-on eth1
            listen-on eth2
        }
    }
    gui {
        http-port 80
        https-port 443
        older-ciphers disable
    }
    nat {
        rule 5010 {
            description "masquerade for WAN"
            outbound-interface pppoe0
            type masquerade
        }
    }
    ssh {
        port 22
        protocol-version v2
    }
    ubnt-discover {
        disable
    }
}
system {
    host-name myerl3
    login {
        user thedr {
            authentication {
                encrypted-password ****************
                plaintext-password ****************
            }
            level admin
        }
    }
    ntp {
        server 0.ubnt.pool.ntp.org {
        }
        server 1.ubnt.pool.ntp.org {
        }
        server 2.ubnt.pool.ntp.org {
        }
        server 3.ubnt.pool.ntp.org {
        }
    }
    offload {
        hwnat disable
        ipv4 {
            forwarding enable
            pppoe enable
        }
    }
    syslog {
        global {
            facility all {
                level notice
            }
            facility protocols {
                level debug
            }
        }
    }
    time-zone UTC
}


**********

I used the basic wizard to generate a generic config with IPv6 enabled.  Then followed Michael Murphy's tutorial to remove the IPv6 related stuff (dhcpv6-pd on pppoe0, ipv6 on eth1, ipv6 on eth2).  Then reboot.  Then add dhcpv6-pd back on pppoe0, added a v6 static route, and reboot again).

So, after the reboot (I actually rebooted a few times), I checked the content of /etc/radvd.conf.

**********
interface eth1 {
#   This section was automatically generated by the Vyatta
#   configuration sub-system.  Do not edit it.
#
#   service type [slaac]
#
    IgnoreIfMissing on;
    AdvSendAdvert on;
    RDNSS 2403:9800:c041:1000::a 2403:9800:c041:1000::b  { };
    AdvManagedFlag off;
    AdvOtherConfigFlag off;
    prefix ::/64 {
          AdvOnLink on;
          AdvAutonomous on;
    };
};
interface eth2 {
#   This section was automatically generated by the Vyatta
#   configuration sub-system.  Do not edit it.
#
#   service type [slaac]
#
    IgnoreIfMissing on;
    AdvSendAdvert on;
    RDNSS 2403:9800:c041:1000::a 2403:9800:c041:1000::b  { };
    AdvManagedFlag off;
    AdvOtherConfigFlag off;
    prefix ::/64 {
          AdvOnLink on;
          AdvAutonomous on;
    };
};
**********

Now, here are the outputs I got from the CLI of the ERL.

Here is the output of "show interfaces".  xxx.xxx.xxx.xxx is the static IP address I have with bigpipe.  The IPv6 address is the funny part.  The last three octets of the address (the "madd" parts) is actually the MAC address of my tp-link's WAN interface.  Even though I am using my ERL here, bigpipe still give me the same IPv6 address, without updating the last three octets.

Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface    IP Address                        S/L  Description
---------    ----------                        ---  -----------
eth0         -                                 u/u  Internet (PPPoE)
eth1         192.168.11.41/24                  u/u  Local
             2403:9800:xxxx:xxx0::1/64
eth2         192.168.12.1/24                   u/D  Local 2
             2403:9800:xxxx:xxx1::1/64
lo           127.0.0.1/8                       u/u
             ::1/128
pppoe0       xxx.xxx.xxx.xxx                   u/u
             2403:9800:xxxx:xxxx:xxxx:madd:madd:madd/128


**********

Here is the output of "show ip route".

Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
       O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       > - selected route, * - FIB route, p - stale info
IP Route Table for VRF "default"
K    *> 0.0.0.0/0 [0/0] via pppoe0
C    *> 127.0.0.0/8 is directly connected, lo
C    *> 192.168.11.0/24 is directly connected, eth1
C    *> xxx.xxx.xxx.xxx/32 is directly connected, pppoe0
C    *> xxx.xxx.xxx.254/32 is directly connected, pppoe0

xxx.xxx.xxx.xxx is the static IP address I have with bigpipe.
The last one (.254) is the IPv4 gateway.

**********

Here is the output of "show ipv6 route".

IPv6 Routing Table
Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
       IA - OSPF inter area, E1 - OSPF external type 1,
       E2 - OSPF external type 2, N1 - OSPF NSSA external type 1,
       N2 - OSPF NSSA external type 2, B - BGP
Timers: Uptime
IP Route Table for VRF "default"
K      ::/0 [0/1024] via fe80::e2ac:f1ff:fe81:a101, pppoe0, 00:11:11
C      ::1/128 via ::, lo, 00:17:32
C      2403:9800:xxxx:xxxx:xxxx:madd:madd:madd/128 via ::, pppoe0, 00:11:16
C      2403:9800:xxxx:xxx0::/64 via ::, eth1, 00:11:14
C      fe80::/10 via ::, pppoe0, 00:11:42
C      fe80::/64 via ::, eth1, 00:17:00

**********

Here is the content of /etc/resolv.conf

search bigpipe.co.nz.
search bigpipe.co.nz.
nameserver 2403:9800:c041:1000::a
nameserver 2403:9800:c041:1000::b
nameserver 203.96.123.1 # nameserver added by pppoe0
nameserver 203.96.123.2 # nameserver added by pppoe0

**********

I can use linux's host command to do a DNS lookup.

thedr@myerl3:~/zone$ host www.geekzone.co.nz
www.geekzone.co.nz has address 104.24.3.14
www.geekzone.co.nz has address 104.24.2.14
www.geekzone.co.nz has IPv6 address 2400:cb00:2048:1::6818:20e
www.geekzone.co.nz has IPv6 address 2400:cb00:2048:1::6818:30e

**********

However, if I do the same using bigpipe's DNSv6 servers, it said the servers cannot be reached.

thedr@myerl3:~/zone$ host www.geekzone.co.nz 2403:9800:c041:1000::a
;; connection timed out; no servers could be reached
thedr@myerl3:~/zone$ host www.geekzone.co.nz 2403:9800:c041:1000::b
;; connection timed out; no servers could be reached

**********

But the v4 version of DNS servers work.

thedr@myerl3:~/zone$ host www.geekzone.co.nz 203.96.123.1
Using domain server:
Name: 203.96.123.1
Address: 203.96.123.1#53
Aliases:

www.geekzone.co.nz has address 104.24.3.14
www.geekzone.co.nz has address 104.24.2.14
www.geekzone.co.nz has IPv6 address 2400:cb00:2048:1::6818:20e
www.geekzone.co.nz has IPv6 address 2400:cb00:2048:1::6818:30e
thedr@myerl3:~/zone$ host www.geekzone.co.nz 203.96.123.2
Using domain server:
Name: 203.96.123.2
Address: 203.96.123.2#53
Aliases:

www.geekzone.co.nz has address 104.24.2.14
www.geekzone.co.nz has address 104.24.3.14
www.geekzone.co.nz has IPv6 address 2400:cb00:2048:1::6818:30e
www.geekzone.co.nz has IPv6 address 2400:cb00:2048:1::6818:20e

**********

Now, if I do a traceroute (v4) to www.geekzone.co.nz, it cannot resolve the address.

thedr@myerl3:~/zone$ traceroute www.geekzone.co.nz
traceroute: bad address 'www.geekzone.co.nz'

**********

Same for traceroute6.

thedr@myerl3:~/zone$ traceroute6 www.geekzone.co.nz
traceroute6: bad address 'www.geekzone.co.nz'

**********

But if I do a tracerote using geekzone's IP address, it works.

thedr@myerl3:~/zone$ traceroute 104.24.2.14
traceroute to 104.24.2.14 (104.24.2.14), 30 hops max, 38 byte packets
 1  xxx.xxx.xxx.254 (xxx.xxx.xxx.254)  4.852 ms  4.796 ms  4.875 ms
 2  122.56.60.68 (122.56.60.68)  5.989 ms  4.927 ms  4.667 ms
 3  122.56.60.69 (122.56.60.69)  5.194 ms  5.402 ms  5.401 ms
 4  122.56.118.145 (122.56.118.145)  5.010 ms  4.717 ms  5.133 ms
 5  122.56.119.53 (122.56.119.53)  4.673 ms  4.752 ms  4.706 ms
 6  122.56.119.82 (122.56.119.82)  27.438 ms  27.780 ms  122.56.127.94 (122.56.127.94)  28.925 ms
 7  122.56.127.214 (122.56.127.214)  29.222 ms  122.56.119.86 (122.56.119.86)  27.973 ms  122.56.119.77 (122.56.119.77)  28.208 ms
 8  103.26.68.78 (103.26.68.78)  30.831 ms  30.679 ms  28.204 ms
 9  104.24.2.14 (104.24.2.14)  27.696 ms  28.087 ms  103.26.68.78 (103.26.68.78)  28.205 ms

**********

traceroute6 works too if I use an ip address.

thedr@myerl3:~/zone$ traceroute6 2400:cb00:2048:1::6818:20e
traceroute to 2400:cb00:2048:1::6818:20e (2400:cb00:2048:1::6818:20e), 30 hops max, 16 byte packets
 1  fe80::e2ac:f1ff:fe81:a101%pppoe0 (fe80::e2ac:f1ff:fe81:a101%pppoe0)  4.834 ms  5.527 ms  4.932 ms
 2  2403:9800:c041:ffff:122:56:60:4444 (2403:9800:c041:ffff:122:56:60:4444)  5.488 ms  4.960 ms  4.469 ms
 3  2403:9800:c041:ffff:122:56:60:4445 (2403:9800:c041:ffff:122:56:60:4445)  5.225 ms  4.938 ms  4.967 ms
 4  2403:9800:2::169 (2403:9800:2::169)  4.460 ms  4.715 ms  4.463 ms
 5  2403:9800:0:10::14d (2403:9800:0:10::14d)  4.720 ms  4.728 ms  4.436 ms
 6  2403:9800:0:10::e2 (2403:9800:0:10::e2)  27.496 ms  27.341 ms  27.227 ms
 7  2403:9800:0:10::1aa (2403:9800:0:10::1aa)  27.710 ms  27.363 ms  27.461 ms
 8  2405:9000:1000:402c::1 (2405:9000:1000:402c::1)  27.471 ms  27.640 ms  27.471 ms
 9  2405:9000:1000:1012::2 (2405:9000:1000:1012::2)  28.721 ms  29.041 ms  28.731 ms
10  2402:7800:0:1::65 (2402:7800:0:1::65)  28.244 ms  28.253 ms  28.221 ms
11  *  *  2402:7800:0:1::82 (2402:7800:0:1::82)  145.694 ms
12  2402:7800:0:2::2ce (2402:7800:0:2::2ce)  29.460 ms  28.200 ms  28.216 ms
13  2400:cb00:26:1024::6ca2:f86a (2400:cb00:26:1024::6ca2:f86a)  27.486 ms  27.702 ms  27.725 ms

**********

And here is the output of "show dns forwarding nameservers".

-----------------------------------------------
   Nameservers configured for DNS forwarding
-----------------------------------------------
2403:9800:c041:1000::a available via 'system'
2403:9800:c041:1000::b available via 'system'
203.96.123.1 available via 'ppp pppoe0'
203.96.123.2 available via 'ppp pppoe0'

**********

Also, my laptop have problems loading webpages.  It could load a few pages to start with (but very slowly):
testip.geekzone.co.nz
www.geekzone.co.nz (the ipv6 logo is on)
ipv6.google.com

However, many website would not load:
test-ipv6.com
nzherald.co.nz
www.cnn.com
www.guardian.co.uk

If I search "what is my ip address" in google, it does give me an ip address.

**********

To try to fix the problems, I did try:
- reboot ERL a few times using the reboot command in CLI
- disconnect pppoe0 and connect pppoe0 a few times (and I watched the IPv6 route table being updated)
- i even tried disconnect dhcp-v6, delete duid, and renew dhcp-v6


Also, on my laptop, I tried the following many time.  But the problems are still there (web pages not loading most of times)
ipconfig /release
ipconfig /flushdns
ipconfig /renew

However, the problems are still there.

Can anyone tell me what I did wrong?  And what I should I do next?

@AKLwestie

For the record I have no experience with Edgerouters, but I have been troubleshooting networks on and off for the last 20 years or so. Anyway hope either something below either helps you or prompts a wiser soul to correct me :)

1. I'd ditch the IPv6 DNS servers to get things going.  They're unnecessary and probably complicating things at this point.

2. Probably no need for a static IPv6 default route.  It's not hurting (I'd leave it there till things are working), but I'd want it populated via RAs from Bigpipe.

3. Bigpipe didn't assign you the /128 public on your PPPoE interface.  They assign you a /60 to do with what you will. Your router decided to allocate that address.  Using the MAC is fine for the last 48bits of the address, and is expected behavior.  I'm more interested that it allocated a public address to that interface, as your config doesn't seem to request it and technically it's not necessary.  Probably an edgerouter quirk and unlikely to be hurting anything as it's a /128.

4. Your ERL isn't showing any link-local IPv6 addresses in the "show interfaces" which is strange. I'd expect pppoe, eth0 and eth1 all to show fe80:: addresses. It's as though IPv6 isn't properly enabled on these interfaces. That said pppoe would need some sort of address to get it's prefix over DHCP. Maybe ERL hides link local addresses by default??? If so I'd look for a more verbose version of the command.

5. Not sure how the edgerouter firewall works, but in general you need to create the state entries before you can set a rule for "established" replies.  In your case I'd expect a "permit any" firewall rules on eth1 and eth2 to create the firewall state table entries for those replies. Probably something an Edgerouter specialist needs to confirm.

6. I haven't had consistent results with ipconfig /release and ipconfig /renew when using SLAAC, and not sure if they're even meaningful in this context.  Personally I don't trust this to get you to a sane state, and prefer disabling and re-enabling the interface.

7. What are your clients looking like? Does a "route -6 print" show a default route?  What happens when you tracert to an IPv6 address from a client box?

@AKLWestie there are a few problems with your configuration. The following should fix it as it sounds like a MTU issue - also don't forget about offloading:

configure
edit interface ethernet eth0
set mtu 1508
delete pppoe 0 mtu
set pppoe 0 mtu 1500
top
edit interface ethernet eth1
set mtu 1508
top
edit interface ethernet eth2
set mtu 1508
top
set system offload ipv4 vlan enable
set system offload ipv6 forwarding enable
set system offload ipv6 vlan enable
set system offload ipv6 pppoe enable
commit
save

Reboot your router and give it another go.

Thanks to @hashbrown and @michaelmurfy, my ERL is working fine now.  I changed MTU of the pppoe0 interface to 1500, and all the eth interfaces to 1508.

In this way, it works fine using my laptop.  However, host lookup and traceroute / traceroute6 are still having problems from ERL's CLI.

Then, I added the prefix-only option for the dhcpv6-pd part.  Now, host lookup and traceroute / traceroute6 work fine on ERL's CLI.

Using an HK659b as an access point at the moment.  All my devices (laptops, 2x android phones, 2x ipads) are working well.

Thanks a lot!  =-)

By the way, I tried to set MTU of pppoe0 to 1492 and ethx to 1500 but it was not working.  Anyone know why?

hi so i trying to setup ipv6 on my asus rt-ac58u router and it get the ipv6 address but when i try load the bigpipe app or reach there web site it wont load and the app say network error.

Bbut when i disable ipv6 it will  load both. when geekzone the wee green ipv6 logo comes up and ipv6 test say 10/10 your ipv6 ready.

i can not work as it not happening to any others websites

What can i narrow down it issues.

haysking:

hi so i trying to setup ipv6 on my asus rt-ac58u router and it get the ipv6 address but when i try load the bigpipe app or reach there web site it wont load and the app say network error.

Bbut when i disable ipv6 it will  load both. when geekzone the wee green ipv6 logo comes up and ipv6 test say 10/10 your ipv6 ready.

i can not work as it not happening to any others websites

What can i narrow down it issues.

 

 

haysking:

 

hi so i trying to setup ipv6 on my asus rt-ac58u router and it get the ipv6 address but when i try load the bigpipe app or reach there web site it wont load and the app say network error.

 

Bbut when i disable ipv6 it will  load both. when geekzone the wee green ipv6 logo comes up and ipv6 test say 10/10 your ipv6 ready.

 

i can not work as it not happening to any others websites 

 

So other services (either v4 or v6) for you work as expected when you have v6 enabled, except for the Bigpipe app and www.bigpipe.co.nz? Is that correct?

IPv6pipe:

 

haysking:

 

 

 

hi so i trying to setup ipv6 on my asus rt-ac58u router and it get the ipv6 address but when i try load the bigpipe app or reach there web site it wont load and the app say network error.

 

 

 

Bbut when i disable ipv6 it will  load both. when geekzone the wee green ipv6 logo comes up and ipv6 test say 10/10 your ipv6 ready.

 

 

 

i can not work as it not happening to any others websites 

 

 

 

 

 

 

So other services (either v4 or v6) for you work as expected when you have v6 enabled, except for the Bigpipe app and www.bigpipe.co.nz? Is that correct?

 

yes another services work but will but that router back confirm that    

haysking:

 

IPv6pipe:

 

haysking:

 

 

 

hi so i trying to setup ipv6 on my asus rt-ac58u router and it get the ipv6 address but when i try load the bigpipe app or reach there web site it wont load and the app say network error.

 

 

 

Bbut when i disable ipv6 it will  load both. when geekzone the wee green ipv6 logo comes up and ipv6 test say 10/10 your ipv6 ready.

 

 

 

i can not work as it not happening to any others websites 

 

 

 

 

 

 

So other services (either v4 or v6) for you work as expected when you have v6 enabled, except for the Bigpipe app and www.bigpipe.co.nz? Is that correct?

 

Correct
I can't ping or tracert it

 

yes another services work but will but that router back confirm that    

 

so not sure now

The Bigpipe website isn't IPv6 enabled, and doesn't reply to pings. A traceroute to the Bigpipe website not completing is normal regardless of whether you've got IPv6 enabled. :)

You should be able to view the Bigpipe website, and use the Bigpipe app regardless of whether or not the device you're connecting from has IPv6 connectivity. If both work with your Fritzbox, but not your Asus router you may have uncovered an odd bug with the Asus router.

Edit: I've been in touch with another user with the same router. Their router doesn't respond to DNS queries for bigpipe.co.nz sent from a connected PC, but queries sent directly to DNS servers from their computer do. From this it does indeed look like there's a bug with that particular Asus router.

Try manually setting the IPv4 DNS servers on your router to 203.96.123.1 and 203.96.123.2, and if possible the IPv6 DNS servers to 2403:9800:c041:1000::a and 2403:9800:c041:1000::b

If that doesn't work, check if there's a firmware update for your Asus router, and apply it if it's available.

If you still have trouble you can assign the DNS servers on your devices manually. This should get around it.

haysking:

 

haysking:

 

IPv6pipe:

 

haysking:

 

hi so i trying to setup ipv6 on my asus rt-ac58u router and it get the ipv6 address but when i try load the bigpipe app or reach there web site it wont load and the app say network error.

 

Bbut when i disable ipv6 it will  load both. when geekzone the wee green ipv6 logo comes up and ipv6 test say 10/10 your ipv6 ready.

 

i can not work as it not happening to any others websites 

 

 

So other services (either v4 or v6) for you work as expected when you have v6 enabled, except for the Bigpipe app and www.bigpipe.co.nz? Is that correct?

 

Correct
I can't ping or tracert it

 

yes another services work but will but that router back confirm that    

 

it not even getting address for ipv6 but it is working on FRITZ!BOX 7490 

 

so not sure now

 

It's probably a long shot, but you don't have the LAN 'Domain Name' on your ASUS RT-AC58U router set to 'bigpipe.co.nz' by any chance do you? That may cause a problem like your seeing.

If it is set to bigpipe, empty the field which is the default I think, or setting it to something like 'home.local'.