IPv6 on StarHub 1G Fiber Broadband?

[xiaofan]

I think
@firesong
had some issues with starhub fibre ipv6 on pfsense, he ended up switching to something else...
https://forums.hardwarezone.com.sg/threads/starting-pfsense-for-new-users.6390714/post-148202586
Edit2: Eh lmao it's also in the 2nd post of this thread.

But I believe that was based on older version of pfSense which uses older version of FreeBSD. pfSense CE 2.7.0 is using 14-Current which is the cutting edge version of FreeBSD. Hopefully it will sort out the issue.

 

[firesong]

But I believe that was based on older version of pfSense which uses older version of FreeBSD. pfSense CE 2.7.0 is using 14-Current which is the cutting edge version of FreeBSD. Hopefully it will sort out the issue.

It didn't.

 

[xxnewbiexx]

Any advantage on configuring IPv6? For me a miss configure pfsense for IPv6 cause more performance problem than just a plain IPV4 env

 

[xiaofan]

Any advantage on configuring IPv6? For me a miss configure pfsense for IPv6 cause more performance problem than just a plain IPV4 env

If IPv6 causes problem for you then just disable it. But it is strange to hear that pfSense has issues with Starhub IPv6 when other routers are fine.

As for the benefits of IPv6, you can find various posts by @bert64.

Example threads or posts.
https://forums.hardwarezone.com.sg/threads/fyi-use-of-ipv6-for-singapore-sg.6891747/
https://forums.hardwarezone.com.sg/...rnet-service-provider.6892699/#post-147165368
https://forums.hardwarezone.com.sg/...rnet-experience.6786682/page-5#post-144979475

I am using Singtel which has poor IPv6 implementation as of now (6rd) and that is why I do not really see the real benefits of IPv6 as of now. But there is a chance that Singtel users may get native IPv6 in the future.

 

[xiaofan]

Youtube Video which is for IPv6


Counter example -- he is not saying IPv6 is not good but rather there is an issue that individuals can not be assigned a /48 and bring to an ISP.

 

[darkarn]

Not sure why but now my pfSense need to check the tickboxes for the following for IPV6 to work

Send IPv6 prefix hint
Do not wait for a RA

 

[xiaofan]

Not sure why but now my pfSense need to check the tickboxes for the following for IPV6 to work

Send IPv6 prefix hint
Do not wait for a RA

Thanks for the report. So with the above two settings Starhub IPv6 is working reliably with your pfSense setup, right?

Do you see any speed difference or latency differences when using IPv6 vs IPv4?

 

[darkarn]

Thanks for the report. So with the above two settings Starhub IPv6 is working reliably with your pfSense setup, right?

Do you see any speed difference or latency differences when using IPv6 vs IPv4?

So far I at least can get IPV6 reliably, before that the IPV6 like almost non-existant for quite some time already. Not sure if Starhub did something at the back end recently to require these new settings; last time I just set bogon network off can liao as instructed here and on Zit Seng's blog

I can't test much about speed difference or latency between the two unfortunately but at least it feels snappier? Will need some more time to see how

 

[Mach3.2]

So far I at least can get IPV6 reliably, before that the IPV6 like almost non-existant for quite some time already. Not sure if Starhub did something at the back end recently to require these new settings; last time I just set bogon network off can liao as instructed here and on Zit Seng's blog

I can't test much about speed difference or latency between the two unfortunately but at least it feels snappier? Will need some more time to see how

does it work if you send a prefix hint of 63? I suppose not right?

 

[darkarn]

does it work if you send a prefix hint of 63? I suppose not right?

iirc it is set at 64 but what does that do btw?

 

[Mach3.2]

iirc it is set at 64 but what does that do btw?

request for a /63 prefix from the ISP upstream DHCPv6 server.

Basically the idea there is to test whether Starhub will delegate a prefix larger than /64 (1 subnet).

a /63 contains 2* /64, which is 2 subnets.

 

[darkarn]

That one didn't work but recently my IPV6 all go missing again

 

[A7997A]

request for a /63 prefix from the ISP upstream DHCPv6 server.

Basically the idea there is to test whether Starhub will delegate a prefix larger than /64 (1 subnet).

a /63 contains 2* /64, which is 2 subnets.

Typically common values are /60, /56, /52. /64 I think works for M1.

 

[sglandscape]

Typically common values are /60, /56, /52. /64 I think works for M1.

Only /64 works if you're on M1, they refuse to give a larger subnet

 

[darkarn]

Reporting back here again after upgrading my pfSense's NIC to 10gbe card

After the upgrade, could get IPV6 straightaway without further tweaking. Will have to see over the weeks if the IPV6 vanish again

Mobile devices on wifi still cannot get IPV6 though

EDIT: Nvm just jinxed myself, IPV6 went missing again

EDIT2: Renewing IP lease got my IPV6 back again. This is getting curiouser...

EDIT3: I am seeing these patterns
1. DNS don't matter, and on a sidenote, pfBlocker being activated or not (and therefore whether you use its DNS) don't matter
2. Need to keep releasing WAN and relinquishing leases until Starhub decides to give a working IPV6 IP
3. Restarting the pfSense machine can kill off the IPV6 lease or even stranger, give it when before reboot there is no IPV6

Now question is, how long does the lease last?