Thank you very much, Databeestje; that did the trick. I have a Verizon FiOS connection that terminates by PPPoE with an MTU less than 1500, so that was definitely my problem. I am now happily exploring and learning about the IPv6 realm.

Thanks again,
Rain

Thanks all for the help.

Just a status update.  I've been working with my ISP, who's never really done this before for anybody yet.  They've made a number of changes and assigned me two /64 blocks.

After I assigned the 64 addresses to the two interfaces, added the default route, and configured rtadvd, everything worked fine.  I'm now able to ipv6.

Thanks again for the help.  I think the problem was part with me and part with my ISP.

That's not the case for me. Check the attachments showing version number, the unticked boxes and the IPv6 packets in the logs. This happens on both my work setup and my home setup.

version.png
version.png_thumb

@Cino:

@wallabybob:

Why not allocate more addresses to your subnets? There are over 65000 address in 192,168.0.0/16 and over 16 million in 10.0.0.0/8.

Why not (for example) use 192.168.0.0/18, 192.168.64.0/18, 192.168.128.0/18 (over 16,000 addresses each) 192.168.192.0/18 for further subdivision and future expansion (e.g 192.168.192.0/24 for servers, 192.168.193.0/24 for teachers's and admin PCs etc).

I can't speak for brcisna but most school network environments use Public IP Subnets instead of Private IP Subnets. So I'm thinking that is why they are running out of IPs.

The company I work for, we used to use Public IPs for our internal servers but over the last 3 years we have moved them to 10.x.x.x and re-use the public ip for any internet facing servers.. Then again Public IP space for my company isnt running low yet

Many higher ed institutions already have IPv6 allocations, it's simply a matter of architecting and deploying.  Generally most have been too apathetic about IPv6 and now everyone is behind and scrambling to figure it out and port their old tools to support it and begging for money to upgrade infrastructure to do IPv6.  It's really not that hard, especially for anyone that has done another protocol in addition to IPv4.  For a long time our IPv6 path wasn't the same as v4, nor does it need to be, as its a totally different protocol.   
Internet2 has a workshop that they put on (that I have been an instructor for in the past) that teaches v6 deployment / theory, etc. to networking folks.

This is interesting too. http://bgpmon.net/blog/?p=340

thank you very much :)

The link local addressing (fe80::) will have something to do with that, so that won't work.

I'll add bridging to the Todo