Ah, all easily solved. Just hardcode the TTL internally on the ip rebroadcast server to a value range of 2-4. That will get it out of the local server (1), and through the WiFi broadcasting router/box (2) to the home receivers -- and subsequently be dropped at the WAN port of the home firewall (3), or alternatively the internet host's router point (4). Any value <= 4 should pretty much take care of redistribution over the internet. Yes there are exceptions to the rule, but these will 99% of the time be at the home user's cheapo firewall/router/switch that ignores the TTL. However, the provider is not going to be using a $49 router, and it will do the job as required. Cheers Kon > This is all fine and good in a glossy viewgraph presentation, but > how does a router vendor implement this? How does the vendor know > when Port X in his router will be connecting to the Internet vs. > connected to an in-house multimedia LAN? How does the router at > one end of you in-house LAN know that there might not be another > router connecting to the Internet at the other end? > > How will the FCC decree that all routers in the US suddenly become > BF-aware? > > Of course, if this BF were merely a legal tool, you would say > it's up to the user to set up his equipment correctly, or face > possible legal consequences. But supposedly, this system is to be > almost fool proof. To the extent that they want this stuff > encased in epoxy or whatever. ---------------------------------------------------------------------- You can UNSUBSCRIBE from the OpenDTV list in two ways: - Using the UNSUBSCRIBE command in your user configuration settings at FreeLists.org - By sending a message to: opendtv-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.