SirHumphreyAppleby:

 

 

 

The issue I have is that I am not able to reliably get an IPv6 address assigned on the LAN interface. There are numerous threads about not getting addresses on the LAN, and a number of suggested causes, including the use of VLANs, a difference in expected command sequences between the DHCP client and server, the bogon network setting, the order settings are applied, and multiple instances of DHCP on the interface. None of the suggested solutions have worked for me.

 

Just chipping in to say I have the same problem as you running 2.3.3-RELEASE-p1 (amd64). Unfortunately I have had to give up for a bit as the only time I have to experiment is when the family are active online although I'll report back if anything changes.

Some parts of pfsense setup seem somewhat counter-intuitive to me to say the least...... :)

IPv6pipe:

 

That setup doesn't look correct. It appears from your screenshot that your router is configured for a tunnelling service, not the native v6 connectivity available from Bigpipe.

 

Your router needs to request a v6 prefix over DHCPv6-PD, and the request needs to come through over the same PPP session your v4 traffic is running over.

Heck he is using the old 6to4 service hosted at Unleash that I thought we decommissioned in 2012. Guess it is still running, not my problem now but it'll be quite slow (100Mbit connection) but either way this is not set up properly ;)

IPv6pipe:

 

That setup doesn't look correct. It appears from your screenshot that your router is configured for a tunnelling service, not the native v6 connectivity available from Bigpipe.

 

Your router needs to request a v6 prefix over DHCPv6-PD, and the request needs to come through over the same PPP session your v4 traffic is running over.

 

Oh dear! I'll try changing the setting to DHCPv6, but last night it failed to do anything. 

allio:

 

Detruire:

 

The router acts as a DNS proxy, and responds on its v6 address, but I'm not sure what it does in the background. I upgraded from a ~1 year old version to the latest one. The old one wouldn't save the IPv6 settings (JS error on the UI.)

 

 

Thanks for that. To make it a bit clearer - do you pass all three DNS tests at this site?

 

Might be time I upgraded to the latest version. 1.32 has been so stable I've been reluctant to.

 

It doesn't pass the v6 DNS two. Then it does. Then it doesn't. Like it's only using the v6 server when the v4 one fails to resolve a number of times.

Detruire:

 

It doesn't pass the v6 DNS two. Then it does. Then it doesn't. Like it's only using the v6 server when the v4 one fails to resolve a number of times.

 

Curious. That's a better result than I get (hard fails on the two V6 tests) but it's fair to say DNSv6 doesn't seem to be working entirely correctly in Tomato. Think I'll just define the servers manually on my clients for now.

FWIW I use TomatoUSB-Shibby v138 at home on an R7000. Dnsmasq runs on the router as a DNS server, and it responds to DNS queries sent to it either on the internal v4 IP, or its v6 address. v6 support on v138 isn't perfect (some of the advanced features don't work with v6), but the core routing functionality seems stable.

IPv6pipe:

 

Thanks for the offers of testing pfSense boxes. I may PM one of you about it in the near future, as I've been unable to find an unused dual NIC box. To those waiting for v6 activation: Check your PMs. :)

 

Is sending a NIC a viable alternative to sending complete computers?

I could send you a single port PCI-E Intel NIC that I've managed to find.

I also have an old 4 port PCI-X Intel NIC, but I doubt that would be much use as I've not had a system that could plug in to for years.

Netflix/Chromecast

I've ended up putting a firewall rule to stop our Chromecast using IPv6 as it seems to be choosing a IPv6 CDN at least 160ms away. Getting intermittent buffering and quality issues since turning on IPv6.

I do use OpenDNS which could be contributing, but I believe the Chromecast defaults to Google (8.8.8.8, 8.8.4.4) DNS, and it's never been an issue with IPv4.

hashbrown:

 

Netflix/Chromecast

 

I've ended up putting a firewall rule to stop our Chromecast using IPv6 as it seems to be choosing a IPv6 CDN at least 160ms away. Getting intermittent buffering and quality issues since turning on IPv6.

 

I do use OpenDNS which could be contributing, but I believe the Chromecast defaults to Google (8.8.8.8, 8.8.4.4) DNS, and it's never been an issue with IPv4.

 

Could be your DNS server, I've had netflix streaming on my chromecast for a couple of hours now for background noise with no issues at all. 

SirHumphreyAppleby: Is sending a NIC a viable alternative to sending complete computers?

All of the computers in the building are laptops. Thanks for the offer though.

IPv6pipe:

 

SirHumphreyAppleby: Is sending a NIC a viable alternative to sending complete computers?

 

All of the computers in the building are laptops. Thanks for the offer though.

 

I've put the card in my ESXi box, allowing me to run pfSense there, freeing up the router should you require it.

It probably shouldn't be your first choice as it's cobbled together with a 3D printed power supply bracket and hot melt glue, and stuck in a 1U case with limited ports exposed. It's not the most practical thing to use or ship, and certainly not guaranteed to arrive unscathed, but it's here if you need it (Auckland).

2a00:86c0:1029:1029::147 

Taubin:

 

hashbrown:

 

Netflix/Chromecast

 

I've ended up putting a firewall rule to stop our Chromecast using IPv6 as it seems to be choosing a IPv6 CDN at least 160ms away. Getting intermittent buffering and quality issues since turning on IPv6.

 

I do use OpenDNS which could be contributing, but I believe the Chromecast defaults to Google (8.8.8.8, 8.8.4.4) DNS, and it's never been an issue with IPv4.

 

 

 

 

Could be your DNS server, I've had netflix streaming on my chromecast for a couple of hours now for background noise with no issues at all. 

 

Must have been a transient thing. Issues now gone, and both Chromecast and Win 10 Netflix app getting content from addresses like the ones below which are <30ms away.  I'm guessing Sydney. 

2a00:86c0:1028:1028::149

2a00:86c0:1029:1029::147 

  
 ethernet eth0 {  
     description "Internet (PPPoE)"  
     duplex auto  
     pppoe 0 {  
         default-route auto  
         dhcpv6-pd {  
             pd 0 {  
                 interface eth1 {  
                     host-address ::1  
                     prefix-id :1  
                     service slaac  
                 }  
                 interface eth2 {  
                     host-address ::1  
                     prefix-id :2  
                     service slaac  
                 }  
                 interface eth3 {  
                     host-address ::1  
                     prefix-id :3  
                     service slaac  
                 }  
                 interface eth4 {  
                     host-address ::1  
                     prefix-id :4  
                     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 Bigpipe  
         user-id Bigpipe  
     }  
     speed auto  
 }  
 ethernet eth1 {  
     description Local  
     duplex auto  
     speed auto  
 }  
 ethernet eth2 {  
     description Local  
     duplex auto  
     speed auto  
 }  
 ethernet eth3 {  
     description Local  
     duplex auto  
     speed auto  
 }  
 ethernet eth4 {  
     description Local  
     duplex auto  
     speed auto  
 }  
 loopback lo {  
 }  
 switch switch0 {  
     address 192.168.1.1/24  
     description Local  
     mtu 1500  
     switch-port {  
         interface eth1 {  
         }  
         interface eth2 {  
         }  
         interface eth3 {  
         }  
         interface eth4 {  
         }  
         vlan-aware disable  
     }  
 }  

  
 static {  
     interface-route6 ::/0 {  
         next-hop-interface pppoe0 {  
         }  
     }  
 }  

  
 ethernet eth0 {  
     description "Internet (PPPoE)"  
     duplex auto  
     pppoe 0 {  
         default-route auto  
         dhcpv6-pd {  
             pd 0 {  
                 interface switch0 {  
                     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 Bigpipe  
         user-id Bigpipe  
     }  
     speed auto  
 }  
 ethernet eth1 {  
     description Local  
     duplex auto  
     speed auto  
 }  
 ethernet eth2 {  
     description Local  
     duplex auto  
     speed auto  
 }  
 ethernet eth3 {  
     description Local  
     duplex auto  
     speed auto  
 }  
 ethernet eth4 {  
     description Local  
     duplex auto  
     speed auto  
 }  
 loopback lo {  
 }  
 switch switch0 {  
     address 192.168.1.1/24  
     description Local  
     mtu 1500  
     switch-port {  
         interface eth1 {  
         }  
         interface eth2 {  
         }  
         interface eth3 {  
         }  
         interface eth4 {  
         }  
         vlan-aware disable  
     }  
 }  

  
Interface    IP Address                        S/L  Description                   
---------    ----------                        ---  -----------                   
eth0         -                                 u/u  Internet (PPPoE)              
eth1         -                                 u/u  Local                         
eth2         -                                 u/u  Local                         
eth3         -                                 u/u  Local                         
eth4         -                                 u/u  Local                         
lo           127.0.0.1/8                       u/u                                
             ::1/128                            
pppoe0       100.64.52.151                     u/u                                
switch0      192.168.1.1/24                    u/u  Local                       

@carlwithaK Yes your configuration is looking right. One thing I would change is the MTU as if you're using UFB you can have a MTU of 1508 on Ethernet interfaces and 1500 on the PPPoE interface. Ensure you reboot after setting up IPv6 a good couple of times. You'll also want to specify your main network interface (I assume this is switch0 looking at your config).

If you have no luck with any of this we could arrange a remote support connection to see where you're going wrong, just flick me a direct message on here.

michaelmurfy:

 

@carlwithaK Yes your configuration is looking right. One thing I would change is the MTU as if you're using UFB you can have a MTU of 1508 on Ethernet interfaces and 1500 on the PPPoE interface.

 

Out of curiosity, why those values for the MTU? I thought BigPipe used 1492.