Does anyone know if the transport mechanism for homegroup network sharing is routable at all?
The backstory:
Comcast cable modem in bridge mode running DOCsis 2 - can't do IPv6. That's OK
I have a Linux 3.2 kernel based router/firewall package that has three interfaces.
WAN, Internal, and WiFi. each of the internal interfaces have their own subnets.
The saga started last year, I have a Win8.1 desktop and a Win 7 laptop, and I wanted to backup a file from quicken onto the other machine. I understand all of my options. You would think I might know better, but nooo...
At the time, the Linux router running on a machine with 2 NICs, and the WiFi AP was plugged into the switch on the inside. I researched and discovered that MSWin homegroup requires ipv6, and my trusty AP was too 'long in the tooth' for that.
So, I bought a fancy new faster AP and the problem was solved. Homegroup worked!
Then, I re-arranged everything, moved it to the basement, and fired up a noisy, ancient server that had more NICs and started to have fun. Until it was time to backup Quicken. Couldn't find the homegroup. where did it go? IPv6 wasn't being routed. The WiFi is on a separate interface with it's own subnet now. So I set the router up to do something with IPv6, but no joy. I can ping (most of the time).
If I plug the laptop 100baseT into the switch with the desktop, homegroup works fine, so there are no configuration issues on the windows boxes, AFAIK.
I suspect that Homegroup uses the link-local addresses, and cannot be routed at all. Does anyone know if that is true?
↧