[mythtv-users] Updated MiniMyth2 Rpi edition
Mike Bibbings
mike.bibbings at gmail.com
Tue Nov 28 18:39:06 UTC 2017
On 28/11/17 17:41, Piotr Oniszczuk wrote:
>
>> Wiadomość napisana przez Mike Bibbings <mike.bibbings at gmail.com> w dniu 25.11.2017, o godz. 17:12:
>>
>> Hi Piotr,
>>
>> Tried again same problems.
>> I increased logging in /usr/bin/mythfrontend.sh to:
>> /usr/bin/mythfrontend -p -v upnp,system,socket --loglevel debug > mythfrontend.log
>>
>>
>> Attached is the result, I am suspicious about the use of IP V6 addresses, my backend is IP v4 on 192.168.1.22, but I could be totally wrong, my knowledge of upnp is zero.
> Mike,
>
> I’m scratching my head how it is possible that Your system has IPv6 interface?
> Looking on /boot/cmdline.txt in vanilla image:
>
> root=/dev/mmcblk0p2 rw rootwait console=ttyAMA0,115200 console=tty1 selinux=0 plymouth.enable=0 smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 kgdboc=ttyAMA0,115200 elevator=noop ipv6.disable=1
>
> look at end of line: how You can have IPv6 interface with ipv6.disable=1?
>
> vanilla image has following interfaces in my case:
>
> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> inet 192.168.1.159 netmask 255.255.255.0 broadcast 192.168.1.255
> ether b8:27:eb:2f:4b:fc txqueuelen 1000 (Ethernet)
> RX packets 16225404 bytes 1678337378 (1.5 GiB)
> RX errors 0 dropped 214 overruns 0 frame 0
> TX packets 4102218 bytes 424668576 (404.9 MiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
> inet 127.0.0.1 netmask 255.0.0.0
> loop txqueuelen 1 (Local Loopback)
> RX packets 37 bytes 15267 (14.9 KiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 37 bytes 15267 (14.9 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> as You see there is no IPv6.
>
> how You then are getting IPv6 interface on my SD image?
>
>
> Nevertheless issue with Your setup where You have: FE IPv6/IPv4 + BE only IPv4 shouldn’t break BE discovery.
> This IMHO should be investigated (and probably reported as myth bug)
>
> I think it will be good to do some tests in Your case:
> 1.disable IPv6 on FE and see how discovery goes
> 2.enable IPv6 on BE see how discovery goes
>
Piotr,
I have ipv6.disable=1 in /boot/cmdline.txt and it always hangs even if
a mythbackend is occasionally found.
On the off chance I checked the archlinux wiki on IP v6, the part about
Disable IPv6 see https://wiki.archlinux.org/index.php/IPv6
So I changed ipv6.disable=1 to ipv6.disable_ipv6=1 deleted
/home/mythtv/.mythtv/config.xml rebooted and it all worked mythbackend
was found.
I switched the rpi2 to my other subnet which has another mythbackend,
deleted thre config.xml file, rebooted, again everything worked.
Here is an example of the config.xml file created after I changed to
ipv6.disable_ipv6=1 (which leaves the IP V6 stack active, but not using
IP v6).
<Configuration>
<UPnP>
<MythFrontend>
<DefaultBackend>
<USN>uuid:3bcb5dd0-ec7b-44bc-a4d0-617706d4d83f::urn:schemas-mythtv-org:device:MasterMediaServer:1</USN>
</DefaultBackend>
</MythFrontend>
<UDN>
<MediaRenderer>b7f0b838-2cb1-48dd-9321-85aa9de89a5e</MediaRenderer>
</UDN>
</UPnP>
<LocalHostName>my-unique-identifier-goes-here</LocalHostName>
<Database>
<PingHost>1</PingHost>
<Host>192.168.1.22</Host>
<UserName>mythtv</UserName>
<Password>Jz3jRYsl</Password>
<DatabaseName>mythconverg</DatabaseName>
<Port>3306</Port>
</Database>
<WakeOnLAN>
<Enabled>0</Enabled>
<SQLReconnectWaitTime>0</SQLReconnectWaitTime>
<SQLConnectRetry>5</SQLConnectRetry>
<Command>echo 'WOLsqlServerCommand not set'</Command>
</WakeOnLAN>
</Configuration>
Just to make sure I changed the hostname to one that did not exist on
mythbackend, deleted /home/mythtv.mythtv/ rebooted was greeted with
Country/Language screen selected UK, selected the found mythbackend, all
works (after changing to OpenMAX:hdmi etc).
Mike
I
More information about the mythtv-users
mailing list