Pardon me to butt in since i'm catching up with this thread.

I personally can confirmed what ansonlos's findings on how to run pfSense 2.1.x & 2.2.x version with IPv6 supplied from TM by adjusting the MTU . I've tested on my Virtualbox (dual physical NIC bridged inside Virtualbox setup) on pfSense 2.2.1 and 2.1.5 both are working with some minor warning which i had on my box (YMMV as ansonlos did mention he/she didn't get any warning as i am). As of now, it's not too much to say that pfSense support TM IPv6.


Coming to @Moogle quote:

Btw @Moogle, i'm on Streamyx 8Mbps (Home) with DSL-526B (D-Link) Modem only. My pfSense is running Virtualbox via Win 7 64bit and i have 2 physical NIC (one onboard and another one is Mini-PCI card). If i may share my experience with pfSense physical setup. Well i do run into a bump whereby i ditch my physical hard disk due to pfSense doesn't like it . It was working quite fine in Linux environment and i have the idea it can work in Unix (FreeBSD too which pfSense base OS). But i was wrong when things gone bad for my HDD (SATA), i should've gone for a new HDD btw lol. If you want to build physical pfSense, i would suggest something like Dual Core spec or maybe Core 2 Duo. Pentium D is nice too btw. Surely it can handle with our TM connection generally (unless you're a home user not ISP level). Add more physical RAM if needed, my suggest maybe start off with 512MB DDR2 and go from there.

P/S: Pls do pardon me if i had the wrong idea on your question.


Regards

Yeah i guess you should stick to Asus AC. if you changed your mind, you can find a good old used cpu just under somewhere around rm 200 (cpu only with ram, decent hdd, dvdrom). i got mine in seremban 2 which is nearby from my home.

Just some updates on my progress as a pfSense users.

1. Always try to experiment on your MTU settings. I find that mine works quite good at 1480 (in line with what HE.Net offers on their service which 1480).

2. Im on Streamyx PPPoE 8Mbps Home package. So yeah you can have IPv6 on your Streamyx too (if available)

3. MTU of 1492 also works but you have to defined it inside WAN page as what @ansonlos pointed out, but YMMV. Not sure why the default settings (null value) doesn't work out of the box and yet have to defined it.

Further reading and knowledge sharing, pls refer to this link:

http://blog.ipspace.net/2013/01/mtu-issues...lamping-in.html


rgds

Updates:

pfSense just roll out it's latest version 2.2.2. I just finish testing the latest version and i can confirmed that pfSense has fully support IPv6 supplied by TM . Previously in this thread, me and @ansonlos stated that both of us had to define our MTU in pfSense WAN tab page. As of 2.2.2, i don't have to set/define my MTU anymore (although it's still 1492 coz of PPPoE overhead).

Just some updates too, Verizon, Comcast and other ISP already adhere to RFC 7368 and RFC 6177 (assignment of IPv6 address /56 prefix to customer/subscriber) . I'm in the process of urging ISP and telco in Malaysia to follow this standards too. The idea of using NAT (network address translation) is highly discouraged in IPv6 environment. Although this is not directly related to this thread, but do take your part in voicing out your opinion or lodge a complaint to your ISP's.

rgds