[mythtv-users] MythTV on Win 7 conflicts with ip tunnel software

[Orange Pants]

Thanks for the comments. See below.

On Sat, Dec 1, 2012 at 10:07 PM, Raymond Wagner <raymond at wagnerrp.com>wrote:

> On 12/1/2012 21:20, Orange Pants wrote:
>
>> On Sat, Dec 1, 2012 at 8:35 PM, Raymond Wagner wrote:
>>
>>> MythTV will not operate without access to tuner hardware, and use of
>>> the backend on Windows is untested and likely non-functional.
>>>
>> Was it something in the logs that made you believe i have no tuner
>> software??
>>
>
>
Nothing in the logs indicated you have any tuner, because the backend
> terminated before it got to that point.
>
> in other words the tuner is irrelevant to my problem


>  My network has HDHomeRun. Setup was able to see it and successfully
>> scanned the channels.
>> Also wiki page confirms HDHomeRun works in windows builds.
>>
>
> The wiki says a lot of things, but with all freely editable things, it may
> not be true, or may be outdated. I do not believe there has ever been any
> confirmation as to whether the master backend will actually run properly on
> Windows, even when using a networked tuner that requires no direct hardware
> support.
>

The binary i downloaded from sourceforge page linked from the wiki is
referred to as "stable build". I don't suppose anyone would call it stable
if it didn't work at all. Then again - anyone can say anything, but i hope
it does actually work at least for the basic things.


 the code puzzles me a little -  why does serverpool.cpp need to throw
>> away a perfectly good ip address that i provide in the configuration and
>> start searching through interfaces?
>>
>
> The code searches through all available network interfaces to make sure
> those perfectly good IP addresses you provided are actually available for
> use. If they did not exist, then client's would be told to contact the
> backend at the wrong address, and there would be no point to running an
> inaccessible frontend. Your logs do indeed show your defined addresses are
> found and used.
>
> Um... i dont' see that in my logs. my ip in configuration was 127.0.0.1.
I hope there is a good reason for mythtv to try to bind to address that was
not specified in the server configuration as it may create all kinds of
security hazards i presume.


 2012-12-01 11:03:52.005177 D [7936] CoreContext serverpool.cpp:209
>>
> (SelectDefaultListen) - Adding BackendServerIP6 to address list.
>
>> 2012-12-01 11:03:52.005177 D [7936] CoreContext serverpool.cpp:129
>> (SelectDefaultListen) - Adding BackendServerIP to address list.
>>
>
> The code also grabs any link-local addresses as those are often used for
> autodetection mechanisms. Those are the fe80:: and 169.xxx addresses. For
> whatever reason, Windows does not actually want to allow you to use this
> 169.254.62.238 address, and so when MythTV tries to listen on it, it fails.
> There is an option in mythtv-setup, where you configured the IP addresses,
> to select whether or not you want to listen on these additional addresses.
> Uncheck it.
>
> That address is for VPN which is not active at the time when the server
ran.
What page in configuration setup is this flag on? My version is 0.25.3 and
i don't see it in neither network setup nor in the source code.

See also...
> http://code.mythtv.org/trac/**ticket/11030<http://code.mythtv.org/trac/ticket/11030>
>

>>> In recent versions of 0.25 and 0.26 where MythTV listens to all
link-local addresses by default

Really?? That explains i guess. I wonder if that flag you mentioned above
disables this behavior. so, is it possible to connect to MythTV from
outside when the tunnel is running?

Thanks for the reference.

______________________________**_________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/**listinfo/mythtv-users<http://www.mythtv.org/mailman/listinfo/mythtv-users>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20121201/2b88dad5/attachment.html>