[Mythtv-soc] MythTV Autoconfiguration Status

[David Blain]

The uPnP Spec uses standard Multicast support.  The TTL (Time To Live) is a
configuration value ("upnpTTL" - currently defaulted to 4) that can be
changed to tell routers how many hops to forward the packet to.  However, it
requires that all routers support multicast.

It sounds like the problem is simply that your router is not Multicast
aware.  I'm not sure how mDNS will do any better.

David.
 

-----Original Message-----
From: mythtv-soc-bounces at mythtv.org [mailto:mythtv-soc-bounces at mythtv.org]
On Behalf Of Kenny Root
Sent: Monday, July 24, 2006 3:49 PM
To: mythtv-soc at mythtv.org
Subject: Re: [Mythtv-soc] MythTV Autoconfiguration Status

I have a router in the core of the network that routes between the two
subnets. The test MythTV master backend is on a segment that supports jumbo
frames (10.100.9.x). The test MythTV client is on my notebook that is
connecting to the segment that doesn't support jumbo frames (10.100.10.x).

Basically I ran into the issue of not having a multicast router between the
two subnets. I tried downloading mrouted, pim-dense, and xoops, but they
were either not updated to work with the Linux 2.6 kernel or way overkill.

I saw your code for utilizing multiple interfaces on the backend, but right
now my setup doesn't utilize that.

Is there anything in the UPnP spec that parallels what it's suggested to do
with multicast DNS? That is, if you can't find the service you're looking
for with a link-local multicast, go to the DNS server via unicast and search
for the appropriate SRV record?

On Mon, 24 Jul 2006 15:34:03 -0400
  "David Blain" <mythtv-soc at TheBlains.net> wrote:
> 
> The UPnP code should work with multi-homed backends... 
>Can you give more
> details about your network setup?  It may be that there is a bug in my 
>code  that could be easily fixed.
> 
> David Blain.
> 
> -----Original Message-----
>From: mythtv-soc-bounces at mythtv.org
>[mailto:mythtv-soc-bounces at mythtv.org]
> On Behalf Of Kenny Root
> Sent: Monday, July 24, 2006 11:36 AM
> To: mythtv-soc at mythtv.org
> Subject: [Mythtv-soc] MythTV Autoconfiguration Status
> 
> I have been working on the automatic backend discovery mechanism using 
>UPnP  which seems to work. However, I ran into a snag in my own setup 
>since I have  multiple subnets in my house. The test MythTV master 
>backend supports jumbo  frames and is on a different segment than my 
>test MythTV clients, so UPnP  doesn't work very well. I'm investigating 
>ways to get around this. Multicast  DNS is well-established in that it 
>has servers that help you bridge subnets.
> I'm looking at writing my own implementation of mDNS for MythTV so I 
>can get  support for multiple subnets while leveraging existing
>(well-known) packages
> on the router.
> _______________________________________________
> mythtv-soc mailing list
> mythtv-soc at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-soc
> 
> _______________________________________________
> mythtv-soc mailing list
> mythtv-soc at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-soc

_______________________________________________
mythtv-soc mailing list
mythtv-soc at mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-soc