Linksys is part of CISCO

Not so simple. If someone uploads an app, and it turns out to be missing the source, or the .tar.gz is garbage or unrelated to the app, Microsoft is still liable. Legal issues are nasty for this.

No. You can distribute BSD apps without source, and no requirement to make the app you build "licensed for the purpose of derivitive works"

Because Microsoft, as the distributor, would need to make the source code available, and they have no ability to insure this.

yes. BSD allows relicensing, even making the app closed source if that's what is desired. And it has no reuirement that source be available.

No, this doesn't work, at least with normal routing gear.

IPv6 subnets are ALWAYS exactly 64-bits, and the routers know it (actually, the IP stack in the OS usually knows this). Sure, with some linux routers you can hack things up and sort of get that to work, but it really screws up more things than it can help.

I'm not really sure why I would need multiple subnets in my home, and go through the expense of having routers to separate them and separate WiFi APs for each.

If you just want "logical separation", or something to ease your firewall rules, you don't really need a separate subnets.

Native IPv6 should work fine if you have a DD-WRT build that supports IPv6. Sure, you need to configure RADVD, but the GUI has a place to do that. 6to4 and 6RD work, I've tested them.

You are right about DD-WRT and 6to4 or 6RD: You need to write a config script that connects. It's ugly. But most Linux's are pretty ugly about IPv6. I would be nice if they make the GUI handle this. But you can get it to work.

You can reach any site connected to your ISP via 6to4, and can connect to any site that is IPv4 capable. But if the site is IPv6 only, and not on your ISP, there is no route known to the internet routers to send packets to your 6to4 address. 6RD fixes this issue.

The normal prefixes are assigned to RIRs, who assign them to ISPs. But every 6to4 address has the same prefix, so you can;t tell which ISP you need to route to.

There is nothing in a 6to4 prefix that says which ISP you are using, or even which country you are in. So routing becomes a problem for sites that are IPv6 only and are not connected to the same ISP as you are.

Why would I want to have a router between the garage and the kitchen? Makes no sense to me.

Not necessary. IPv6 has "privacy enhanced IP addresses". A random IP is used each time you connect outbound, and so anyone that records your IP will find it useless. And guessing IP addresses when even a home user has multiple quintillion doesn't work at all.

You are very confused. A /64 is enough space for every network device ever built or will be built in our lifetime to be part of one home network. And you think that is too small? That you will run out in a jiffy?

IPv6 works. Subnets cannot run out of addresses in any foreseeable future. Business will get a /48 or at least a /56. They won't have a problem.

All of the IPv6 problems are in the transition.

Home users don't need a /48 (which is 1024x bigger than a /64). It would be nice if they did allow for subnets , and gave home users at least a /62 (room for 4 subnets). But very few home users would use such a feature.

A /64 allows for more devices connected to your home subnet than all the network interfaces ever built, or will be built in our lifetimes. There isn't any worry about it being "too small".

It is looking more and more like Comcast waited too long to do this, and will run out of IPv4 addresss before people can make the transition. Dual-stack still requires you to have an IPv4 address.

So they are also testing DsLite, a system where the home user only gets an IPv6 prefix, and no IPv4 address. This connects to a NAT64 router that allows you to get at IPv4 sites, by translating your IPv6 address into an IPv4 address.

NAT64 is an ugly solution, but ARIN will run out of IPv4 blocks to give Comcast and other ISPs by the end of the year.