PMS on Debian sqeeze not found by PS3 - (OpenVZ container)

[gladiator]

Hello,

I would kindly ask your help on troubleshooting my issue. I've read several posts, and I will include as much information I have.
Unfortunately for some reason my PS3 cannot find PMS on my Debian [in an OpenVZ container].
Debug-root_log.zip file attached.

Details:
PS3
System Software: 3.56
192.168.1.25 [Manual]
uPnP enabled
Media Server Connection enabled

PMS-linux
Install went fine
PS3 Media Server v1.20.412
on Debian sqeeze 32bit
192.168.1.101 - venet0
Seems all good starting PMS.. (full log attached)

Code: Select all

[main] DEBUG 17:34:14.564 Setting DLNA id 0$4$6 to Save configuration
[main] DEBUG 17:34:14.564 Setting DLNA id 0$4$7 to Restart HTTP server
[main] TRACE 17:34:14.568 Scanning network interface venet0 / venet0
[main] TRACE 17:34:14.570 Using address /192.168.1.101 found on network interfac
[main] TRACE 17:34:14.571 Created socket: /192.168.1.101:5001
[main] INFO  17:34:14.699 Sending ALIVE...
[main] DEBUG 17:34:14.701 Setting multicast network interface: name:venet0 (vene
/192.168.1.101;
/127.0.0.1;


Network
LAN 100Mbit
Asus wl-500g Premium on 192.168.1.1
Everything is wired.

PING ok from Debian to PS3.

Code: Select all

debian:/usr/src# ping 192.168.1.25
PING 192.168.1.25 (192.168.1.25) 56(84) bytes of data.
64 bytes from 192.168.1.25: icmp_req=1 ttl=254 time=0.491 ms
64 bytes from 192.168.1.25: icmp_req=2 ttl=254 time=0.209 ms

Port 5001 is open

Code: Select all

debian:/usr/src# netstat -ant |grep 5001
tcp        0      0 192.168.1.101:5001      0.0.0.0:*               LISTEN


Please assist me on this. Why my PS3 does not sees the PMS?.
Thank you.

[meskibob]

viewtopic.php?f=6&t=3507&start=80#p34933

[gladiator]

I went through all the points presented in that post. Not identifying any issues. My PS3 still unable to find PMS.
I do not have any Firewall.

Code: Select all

debian:/l# iptables -nL
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Please advice,
I would really appreciate it.

Thank you.

[WorldOfHurt]

Your router is probably blocking UDP multicast packets. Try checking the router configuration: switch off UPnP configuration on the router if it supports it, and if there are any settings to do with multicast, check what happens when they are tweaked.

[gladiator]

Thank you!
I've checked further - seems the router is not blocks the udp packets; but id does my hardware node.
As it can be seen in my debug log, i'm running pms-linux in an OpenVZ container (vps).

What i have found out is the following in my hardware node:

Code: Select all

server:~# tcpdump host 192.168.1.25
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
17:55:03.621596 arp who-has 192.168.1.1 tell 192.168.1.25
17:55:20.392039 IP 192.168.1.25.54924 > 239.255.255.250.1900: UDP, length 223
17:55:20.492220 IP 192.168.1.25.54924 > 239.255.255.250.1900: UDP, length 223
17:55:20.592425 IP 192.168.1.25.54924 > 239.255.255.250.1900: UDP, length 223


Again
192.168.1.1 [router/gateway]
192.168.1.25 [ps3]
192.168.1.100 [hardware node]
192.168.1.101 [container - pms-linux]

I have packets forwarding activated.
My iptables rules in the hardware node:

Code: Select all

iptables -A INPUT -i venet0 -j ACCEPT
iptables -A OUTPUT -o venet0 -j ACCEPT
iptables -A FORWARD -j ACCEPT -p all -s 0/0 -i venet0
iptables -A FORWARD -j ACCEPT -p all -s 0/0 -o venet0


Any further assistance or hint would be appreciated.
Thank your for your cooperation.

[Topguy]

Its tempting to blame your OpenVZ environment.

Can you run tcpdump from inside the container ?
Can you test PMS in your Hardware node ?

[gladiator]

Hello,

I can run tcpdump in the container but nothing is captured [# tcpdump -p udp ]
I have added the following iptables rules on the main node, but i think still not forwarding properly:

Code: Select all

iptables -t nat -A PREROUTING -p udp -i venet0 -d 192.168.1.101  --dport 1900 --sport 1024:65535 -j DNAT --to 192.168.1.101:1900
iptables -A FORWARD -p udp -i venet0 -o venet0 -d 192.168.1.101 --dport 1900 --sport 1024:65535 -m state --state NEW -j ACCEPT

Any thoughts?
Thank you.

[nisse]

First, it was a while since I tangoed with iptables but doesn't your first rule forward from 192.168.1.101:1900 to 192.168.1.101:1900?
IE shouldn't you have "iptables -t nat -A PREROUTING -p udp -i venet0 -d 192.168.1.100 --dport 1900 --sport 1024:65535 -j DNAT --to 192.168.1.101:1900"

If that's not the case a good way to debug would be to:
1. Run "nc -l -p 1900 -u 192.168.1.100" on the "hardware node"
2. Run "nc -l -p 1900 -u 192.168.1.101" in debian
3. Run "nc -u 192.168.1.100 1900" and "nc -u 192.168.1.101 1900" and type things there (preferably on a third computer)

If you don't see anything on the 101 you're obviously not forwarding the traffic. You can also combine this with "snort -vd -i your_nic proto udp and port 1900" (or tcpdump) to see things. If you don't see traffic in snort it's the firewall blocking/dropping/not forwarding things before the traffic has a chance to reach you. Try running snort/tcpdump on both the container and hw node to see where it ends up.

[gladiator]

I haven't quite had any time from that time, now I'm trying again to make this work-- no luck so far with the iptables rules.
My OpenVZ container still can't be found by the PMS, on the same LAN - but other OS, that is directly connected to the router is visible. As such, the thing here is the firewall rules in my main node.

I would appreciate any hints with this.

The current rules, that I've tried so far:

Code: Select all

iptables -A INPUT -i venet0 -j ACCEPT
iptables -A OUTPUT -o venet0 -j ACCEPT
iptables -A FORWARD -j ACCEPT -p all -s 0/0 -i venet0
iptables -A FORWARD -j ACCEPT -p all -s 0/0 -o venet0
#iptables -A FORWARD -s 192.168.1.225 -d 192.168.1.101 -j ACCEPT
#iptables -t nat -A PREROUTING -p udp -i venet0 -d 192.168.1.100  --dport 1900 --sport 1024:65535 -j DNAT --to 192.168.1.101:1900
#iptables -A FORWARD -p udp -i venet0 -o venet0 -d 192.168.1.101 --dport 1900 --sport 1024:65535 -m state --state NEW -j ACCEPT
iptables -t nat -A PREROUTING -s 192.168.1.225 -p udp --dport 1900 -j DNAT --to-destination 192.168.1.101:1900


Again, I have the following scenario:
192.168.1.1 [router/gateway]
192.168.1.25 [ps3]
192.168.1.100 [hardware node]
192.168.1.101 [container - pms-linux]

Thanks,