Issue 1391

[Abscissa]

Very nice FAQ, but the answer for "PMS is bound to the wrong network interface" needs an addendum like this:

"Also, make sure you're using version 1.50.1 or BELOW. Versions after 1.50.1 contain a bug which causes the network interface setting to be ignored. (The status of this bug can be tracked at: http://code.google.com/p/ps3mediaserver ... il?id=1391 )"

(Unfortunately, that problem causes anything above 1.50.1 to be completely unusable by anyone who has VirtualBox installed on their computer, among other people as well. So it really should be mentioned in the FAQ.)

[meskibob]

This is my first time hearing of this issue.
Provide a trace log (viewtopic.php?f=6&t=3507&start=30#p38484) and a copy of the PMS.conf file (viewtopic.php?f=6&t=3507&start=20#p32731) showing the forced NIC not being applied in version 1.72.0.

Side request: Please do not post in the FAQ unless actually providing a new help point. Use the FAQ discussion thread (viewtopic.php?f=6&t=13353) if you wish to comment on the FAQ.

[meskibob]

Anyone having this issue want to provide the requested information? I have a live VMware network and can correctly switch PMS between my NICs using the force NIC setting.

[heavydawson]

Attaching the requested files.
I'm not running VMWare, but I'm running VirtualBox.

[meskibob]

You need to provide a trace log, not just the standard debug.log. Check the first FAQ post I linked for how to modify the logback.xml to provide a trace log.
However, looking at the PMS.conf and taking a guess, is "net6" the correct instance of the actual NIC you're trying to use? Sometimes NICs get enumerated multiple times for sub-interfaces on the same NIC. If it's not the correct one, I could see PMS not finding a valid IP on that forced incorrect NIC and defaulting instead to the VM NIC (a dev can confirm that this is the expected behavior for an invalid IP on a NIC)...

[heavydawson]

You need to provide a trace log, not just the standard debug.log. Check the first FAQ post I linked for how to modify the logback.xml to provide a trace log.
However, looking at the PMS.conf and taking a guess, is "net6" the correct instance of the actual NIC you're trying to use? Sometimes NICs get enumerated multiple times for sub-interfaces on the same NIC. If it's not the correct one, I could see PMS not finding a valid IP on that forced incorrect NIC and defaulting instead to the VM NIC (a dev can confirm that this is the expected behavior for an invalid IP on a NIC)...

Attaching trace log as requested.
net6 is the desired connection, but there's some suspicious references to it in the trace log:

Code: Select all

TRACE 2013-05-21 11:41:55.952 [main] checking net6, display name: Intel(R) Centrino(R) Advanced-N 6200 AGN
TRACE 2013-05-21 11:41:55.952 [main] available addresses for net6 is: [/10.53.153.108]
TRACE 2013-05-21 11:41:55.952 [main] non loopback/ipv4 addresses: []
TRACE 2013-05-21 11:41:55.952 [main] checkNetworkInterface(parent = net6, child interfaces = java.net.NetworkInterface$1subIFs@4adf2940)
TRACE 2013-05-21 11:41:55.952 [main] checkNetworkInterface(parent = net6) finished
TRACE 2013-05-21 11:41:55.952 [main] sub address for net6 is []
TRACE 2013-05-21 11:41:55.952 [main] found net6, without valid address


It looks like it finds a valid IP (10.53....) but then finishes up by saying no valid address....

[meskibob]

Can you post the output of a "ipconfig /all" command from the command prompt?
Side note: You actually configured a 10.53.153.x IP address? That seems like a weird IP for a local subnet.

[heavydawson]

Output of ipconfig /all

[meskibob]

To test, can you disable any IPv6 addressing/configuration on that NIC?

[meskibob]

Update: it looks like a change was made elsewhere in the NetworkConfiguration.java file that could also be applicable here. Not sure if it will necessarily solve your issue, but it might.