Is it possible ?, I have a client with Tivo Roamio and a few minis who wants to stream recorded content between two remote locations. I know i could do it via sling box and airplay in remote location, but the overall user experience is just not the same.
As always TIA

Tivo Stream is built into the Plus and Pro Roamios. If not, the Tivo Stream may be your best option.

Missed the point there....I believe the question was with that hardware would the Roamio stream out over a VPN to remote location the same way it would over a LAN (or MOCA network)....love to see someone try this.

That's correct , I have done some digging and tried (failed) it over openVPN - dedicated server, I have plenty of bandwidth at both locations (125M down and 52M up), broadcasting is all set, all units are on the same VLAN and still "no-go ". It almost seems like there is some kind of "stream protection" on Tivo units that will automatically disable the stream when packets latency exceeds certain threshold.

Are you using the same subnet on both sides? Some services require layer 2 adjacency (ie, have to be on the same subnet).

You may also be dealing with fragmentation. VPN encapsulation has overhead and increases the size of the packet. If the packets are large enough, they will be fragmented and have to be reassembled on the other side. Even with a fast connections on either side, if your packets exceed the egress MTU (eg, 1492 on DSL), they will be fragmented. This can add 2-5ms of latency to each side.

Yes, all TiVo's are on the same subnet ( both sides ). One thing I have not tried is to use a full Tivo in remote location ( not mini ) and check if " transfer " works ( instead of stream ) .
Anyway, I am about to give up on this project , the only thing that worked was this :
- (location A) Tivo -> slingbox -> (location B) iPad with slingplayer app->airplay-> Apple TV ->TV , or it works the same way with Roku instead of Apple TV
Tivo app does not support airplay/screen mirroring or direct connection via VGA or HDMI cable from ipad or android devices . There used to be a hardware based slingplayer that disappeared from the market as quickly as it showed up, that could probably work in this case but I don't think I would be willing to waste any more time then I already did on this project....

You need ports and ips available through your vpn. Some could be blocked by your provider or your router.

Do a trace route on some of the IPs and see where the bottle neck is. Open command prompt by Run and CMD. tracert 204.176.49.127. That is one of their IPs.

[Link: support.tivo.com]

The TiVo Mini is very sensitive and you'd stand no chance at accomplishing this task unless you got them up and running on the same network and likely both plugged into the router for the initial setup. Once that initial setup is complete if you're crafty enough with your networking skills I don't see why it wouldn't work. I would never try this for a project, I deal with enough mysterious TiVo Mini issues inside of the same location.

Figured I'd post here since I have just made this work (Mini interoperating with a mother-DVR located at a remote site):

First, you need Layer2 transparancy between the two units. They need to experience the same connectivity as if they were on the same Ethernet segment, so when they use broadcast and other Layer2 shenanigans (probably Bonjour, but I haven't done any analysis on how they talk) to find each other; it all works.

Second, you need a decent amount of capacity between the two sites. I have 100Mbit or so. Monitoring traffic with the Mini streaming, I see it using between 10-20Mbit/s. I don't know how much headroom you need above this base in order to keep it happy. 100Mbit is definitely enough :)

Third, perhaps you need low latency. I'm not sure. People have speculated that Tivo may have some "tunnel detector" that measures latency. I have typically less than 10ms RTT btween my two locations. Not exactly LAN speed, but perhaps less than you'd see transiting between two ISPs in the same city. Two sites both on the same CableCo in the same city I would imagine would have similar latency.

Some details about my setup, for the curious:

The network between the two sites is run by me (private microwave) and provides IPv4 connectivity through several routers (it is not bridged, not MPLS, just IP). Connecting via the public Internet should work just as well, provided the QoS is good enough. The DVR (Bolt, in my case) sits on a regular residential-type network, nothing special. The router there is configured to bridge the local LAN via a EoIP tunnel to the second site. I use Mikrotik routers which support EoIP. Typical consumer routers won't do this but you cold also use Cisco or Linux boxes. At the other site (which has its own distinct subnet, firewall, etc for regular Internet connectivity) its router is configured to feed the bridged traffic onto a VLAN that is distinct from the main LAN. Then, I used cheap VLAN-capable switches (TP-Link) to feed the Minis. These are configured to un-tag the special VLAN traffic on a per-port basis. The result is that regular devices work as before, on the local subnet, but any device plugged into one of the magic switch ports believes it is on the LAN at the other site. I experienced no problems getting the Mini to see and associate with the remote Bolt, once the network was working properly. This Mini had not previously been used with the Bolt.

Viola.