2 independent issues with pms-current

For help and support with issues specific to Linux/Unix
Forum rules
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply.

2 independent issues with pms-current

Postby arabek » Wed May 06, 2009 10:25 pm

O hai! :) My first post here.

1st issue:

This is not directly related to pms, but tsMuxer fails on 64bit only userland, as it's an 32bit app. I've already contacted the creators about a 64bit version, but got no response at all. Maybe someone could persuade them to do a 64bit build of it.

2nd issue:

pms fails to properly use a given network interface, even if you explictly set it.

My config:
Code: Select all
network_interface = eth0
hostname = 192.168.0.1
port = 5001


PS3 is on 192.168.0.2

debug shows:
Code: Select all
[Thread-1] TRACE 21:35:48.832 Receiving a request from: 192.168.0.2
[main] TRACE 21:35:49.998 It's ready! You should see the server appears on XMB


but the ps3 does not see the media server.

Tested also without explictly setting the interface (i've expected it'll listen and respond properly on all interfaces - unfortunatelly i've been wrong).

Output of ifconfig (cropped):
Code: Select all
eth0      Link encap:Ethernet  HWaddr 00:1f:d0:(hidden)
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
(...)
wlan0     Link encap:Ethernet  HWaddr 00:fd:07:(hidden)
          inet addr:192.168.145.13  Bcast:192.168.145.255  Mask:255.255.255.0


It seems (sniffed trough wireshark), as pms is getting the request on eth0, but responds on wlan0, wich is wrong. If i disable wlan0 completly, it works as expected.

I've had doubts, so i've tested, if mediatomb will work properly in such environment. I had no problems getting the ps3 and pc working toegether with mediatomb on the same setup.
arabek
 
Posts: 2
Joined: Wed May 06, 2009 10:15 pm

Re: 2 independent issues with pms-current

Postby shagrath » Wed May 06, 2009 11:16 pm

interesting, would be glad if you could post the debug.log output of the non working case

you can also try to comment the hostname property, and only keep the network_interface one
shagrath
Project Lead
 
Posts: 2667
Joined: Wed Jan 14, 2009 1:39 pm

Re: 2 independent issues with pms-current

Postby arabek » Tue May 12, 2009 11:12 am

Ok, i managed to trace the bug, unfortunatelly in my computers config.

PMS could not resolve eth0 assigned ip (own) hostname (i always tend to _not set_ it properly for hand-managed [ifconfig eth0 192.168.0.1] network interfaces).

After fixing this (setting proper hostname on both ip addressess, for the eth0 and wlan0 interfaces) it started working.

Nevertheless, if one sets a net interface in the config forcibly, pms should (in case it could not resolve it's own hostname) fallback to something like "pms.unknown" and serve everything on that interface.
arabek
 
Posts: 2
Joined: Wed May 06, 2009 10:15 pm

Re: 2 independent issues with pms-current

Postby groff » Sun May 17, 2009 12:43 am

arabek wrote:O hai! :) My first post here.

1st issue:

This is not directly related to pms, but tsMuxer fails on 64bit only userland, as it's an 32bit app. I've already contacted the creators about a 64bit version, but got no response at all. Maybe someone could persuade them to do a 64bit build of it.


The 32bit version runs on 64bit linux but needs 32bit libraries (and you should download the static version from SmartLabs). Run the binary and install the 32bit archives that are reported missing and it should work. Mine does (Gentoo 64bit).
groff
 
Posts: 17
Joined: Sun Apr 05, 2009 2:21 pm


Return to Linux/Unix Support

Who is online

Users browsing this forum: No registered users and 1 guest