FAQ  •  Register  •  Login

To solve the bound address returning problems

<<

turnig56

Streaming enthusiast

Posts: 22

Joined: Sat Sep 24, 2011 2:17 am

Post Tue Nov 01, 2011 3:19 am

To solve the bound address returning problems

Hello,
I often can't use Serviio because it is not found by a device. For example today I was testing some tvs in shop and I did not test Serviio because it was not discovered by the tvs. Foobar2000 and some other DLNA server didn't share this issue. So it looks like it is possible to solve this? (Why not listen on 0.0.0.0?)

It is a recurring problem and I think that solving this would be like getting small rock out of a shoe or similar :)
<<

zip

User avatar

Serviio developer / Site Admin

Posts: 17215

Joined: Sat Oct 24, 2009 12:24 pm

Location: London, UK

Post Tue Nov 01, 2011 9:52 am

Re: To solve the bound address returning problems

Serviio is trying to figure out what is the IP in use and binds to it. Obviously it fails sometimes. It cannot bind to 0.0.0.0 as it has to let the devices know where it lives, ie a real IP address of the box it can be reached at.

Can you post results of

  Code:
ipconfig /all
<<

turnig56

Streaming enthusiast

Posts: 22

Joined: Sat Sep 24, 2011 2:17 am

Post Tue Nov 01, 2011 10:52 pm

To solve the bound address returning problems

Ok below is the data. I think it is worth saying that in the shop I simply plugged Ethernet cable to my vaio and tv's LAN port. I did not configure anything just waited for the "Identifying.." process to end. So I am not sure if there was any real network estabbilished, but foobar and other server did handle that.


C:\Win7\system32>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : my-VAIO
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : F0-BF-97-19-C5-CA
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::65fb:d002:8d3b:eef5%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.18(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 31 October 2011 20:10:07
Lease Expires . . . . . . . . . . : 08 November 2011 18:27:24
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 293110844
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-F2-E7-1F-F0-BF-97-19-C5-CA
DNS Servers . . . . . . . . . . . : 62.179.1.63
62.179.1.62
NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) WiFi Link 1000 BGN
Physical Address. . . . . . . . . : 8C-A9-82-40-3A-00
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection 3:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter #2
Physical Address. . . . . . . . . : 8C-A9-82-40-3A-01
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
Physical Address. . . . . . . . . : 8C-A9-82-40-3A-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{A6C54CAB-C86C-4024-82F9-E7FEE81CE87D}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{62FCA43A-431D-428E-88A9-C015665AD599}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:2453:1c06:a6ba:6aa4(Preferred)
Link-local IPv6 Address . . . . . : fe80::2453:1c06:a6ba:6aa4%16(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Reusable ISATAP Interface {3E7BEBC9-053F-4022-AB28-28EC7BF8087C}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{F22BDE39-38F9-4FA7-8575-E2A71FBBF2D7}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{12DEB657-3080-4AD7-8D06-C434B2794891}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #5
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
<<

Cerberus

User avatar

DLNA master

Posts: 4114

Joined: Sun Jan 02, 2011 5:20 pm

Location: Reading, UK

Post Sat Nov 05, 2011 8:05 am

Re: To solve the bound address returning problems

might not be possible but why not instead of binding to a set IP could we not bind to the network adaptor itself like some windows sidebar gadgets do??

so the bind Ip box would then be a drop down menu with all availible adaptor list and you just select teh one you want or select Auto and serviio will do it for you.

ok i used turnig56 info as an example in this FLAT example.

  Code:
Bind Network Interface ¬
                     Realtek PCIe GBE Family Controller
                     Intel(R) WiFi Link 1000 BGN
                     Microsoft Virtual WiFi Miniport Adapter #2
                     Microsoft Virtual WiFi Miniport Adapter
                     Microsoft ISATAP Adapter
Phil Bennett
Beta Tester Group
Wiki | FAQ

Samsung LE40C750 LCD | Samsung BD-C5900 | Sony PS3 | Windows 7 |
HowTo: Provide supported formats of a device HowTo: Record a new ticket on Bitbucket
HowTo: Provide details of a video file that doesn't play HowTo: Turn on detailed logging
<<

turnig56

Streaming enthusiast

Posts: 22

Joined: Sat Sep 24, 2011 2:17 am

Post Sat Nov 12, 2011 11:27 pm

To solve the bound address returning problems

Today I reconfigured my network – added a new wifi router, changed some plugs (I have adsl modem, 1gb switch, the new wifi), disabled old wifi in adsl modem. So, basically IPs and some routes have changed, and a new network appeared (from the new router).

In effect I do not see Serviio in my DLNA clients. It would be very distress-revealing if Serviio could handle that. Think about regular, not advanced users.

I have to restart Serviio and it then should work. But I have problem with restarting service on mac. So I prefer to restart computer. But some file is currently being downloaded and I don't want to interrupt. So I must wait. As you see, distress is escalating :) Not mentioning that I am already in comfortable position watching TV and I will need to get up to computer ;/

Advanced, flexible binding feature is a very comfortable thing. It would gave Serviio a higher standard touch and feel.
<<

zip

User avatar

Serviio developer / Site Admin

Posts: 17215

Joined: Sat Oct 24, 2009 12:24 pm

Location: London, UK

Post Sun Nov 13, 2011 12:53 am

Re: To solve the bound address returning problems

I agree, but there are so many ways network can be setup that it's impossible for me to reproduce it. On my network all the devices bind properly, automatically. Obviously if you have virtual NICs etc they will get in the way. I might also be limited by Java.
<<

moltra

DLNA master

Posts: 1871

Joined: Thu Mar 24, 2011 11:00 pm

Location: Ohio USA

Post Sun Nov 13, 2011 3:11 am

Re: To solve the bound address returning problems

Would it be possible or of benefit for serviio to try each IP address and pick the one that has a DLNA Renderer respond?
Mark
Beta Tester Group
http://www.serviidb.com Online media resource repository

Netgear EVA2000 | Samsung BD-D5300 | XBOX 360 | Windows 7 | Mint Debian 12 | Raxz Maxx
HowTo: Provide supported formats of a device HowTo: Record a new ticket on Bitbucket
HowTo: Provide details of a video file that doesn't play HowTo: Turn on detailed logging
<<

zip

User avatar

Serviio developer / Site Admin

Posts: 17215

Joined: Sat Oct 24, 2009 12:24 pm

Location: London, UK

Post Sun Nov 13, 2011 12:51 pm

Re: To solve the bound address returning problems

I wrote a small program that should help me investigate it. For those who don't get automatic binding right - download the attachment and run it like:

  Code:
java ListNic


and post the result here (attachment).
Attachments
ListNic.class
(2.49 KiB) Downloaded 849 times
<<

JohninLA

Serviio lover

Posts: 64

Joined: Sun Feb 13, 2011 4:51 pm

Post Tue Nov 15, 2011 3:24 pm

Re: To solve the bound address returning problems

Sure, here's what I get:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\John>java ListNic
Exception in thread "main" java.lang.NoClassDefFoundError: ListNic
Caused by: java.lang.ClassNotFoundException: ListNic
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
Could not find the main class: ListNic. Program will exit.

I hope that helps others!
<<

zip

User avatar

Serviio developer / Site Admin

Posts: 17215

Joined: Sat Oct 24, 2009 12:24 pm

Location: London, UK

Post Tue Nov 15, 2011 3:40 pm

Re: To solve the bound address returning problems

you have to invoke it from the folder whene ListNic.class is stored
<<

JohninLA

Serviio lover

Posts: 64

Joined: Sun Feb 13, 2011 4:51 pm

Post Tue Nov 15, 2011 5:20 pm

Re: To solve the bound address returning problems

oops, sorry about that, here it is:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\John>java ListNic
ip: 127.0.0.1,
name: lo
display name: Software Loopback Interface 1
loopback: true
p2p: false
up: true
virtual: false
multicast: true
------------------------------
ip:
name: net0
display name: WAN Miniport (SSTP)
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: net1
display name: WAN Miniport (L2TP)
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: net2
display name: WAN Miniport (PPTP)
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: ppp0
display name: WAN Miniport (PPPOE)
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth0
display name: WAN Miniport (IPv6)
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth1
display name: WAN Miniport (Network Monitor)
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth2
display name: WAN Miniport (IP)
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: ppp1
display name: RAS Async Adapter
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip: 192.168.1.100,
name: eth3
display name: Realtek RTL8169/8110 Family PCI Gigabit Ethernet NIC (NDIS 6.20)
loopback: false
p2p: false
up: true
virtual: false
multicast: true
------------------------------
ip:
name: net3
display name: Microsoft ISATAP Adapter
loopback: false
p2p: true
up: false
virtual: false
multicast: false
------------------------------
ip:
name: net4
display name: Teredo Tunneling Pseudo-Interface
loopback: false
p2p: true
up: true
virtual: false
multicast: false
------------------------------
ip:
name: net5
display name: WAN Miniport (IKEv2)
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: net6
display name: Bluetooth Device (RFCOMM Protocol TDI)
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth4
display name: Bluetooth Device (Personal Area Network)
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: net7
display name: Microsoft ISATAP Adapter #2
loopback: false
p2p: true
up: false
virtual: false
multicast: false
------------------------------
ip: 192.168.50.1,
name: eth5
display name: Bluetooth PAN Network Adapter
loopback: false
p2p: false
up: true
virtual: false
multicast: true
------------------------------
ip:
name: net8
display name: Microsoft ISATAP Adapter #3
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth6
display name: Realtek RTL8169/8110 Family PCI Gigabit Ethernet NIC (NDIS 6.20)-Q
oS Packet Scheduler-0000
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth7
display name: Realtek RTL8169/8110 Family PCI Gigabit Ethernet NIC (NDIS 6.20)-W
FP LightWeight Filter-0000
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth8
display name: WAN Miniport (Network Monitor)-QoS Packet Scheduler-0000
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth9
display name: WAN Miniport (IP)-QoS Packet Scheduler-0000
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth10
display name: WAN Miniport (IPv6)-QoS Packet Scheduler-0000
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth11
display name: Bluetooth PAN Network Adapter-QoS Packet Scheduler-0000
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth12
display name: Bluetooth PAN Network Adapter-WFP LightWeight Filter-0000
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
<<

eclp

User avatar

DLNA master

Posts: 102

Joined: Thu Dec 29, 2011 5:12 am

Post Thu Dec 29, 2011 4:23 pm

Re: To solve the bound address returning problems

from: viewtopic.php?f=11&t=4520

Why are not the green button?

serviio.jpg
serviio.jpg (106.29 KiB) Viewed 20485 times


Windows-IP-Konfiguration

Hostname . . . . . . . . . . . . : PC
Primäres DNS-Suffix . . . . . . . :
Knotentyp . . . . . . . . . . . . : Hybrid
IP-Routing aktiviert . . . . . . : Nein
WINS-Proxy aktiviert . . . . . . : Nein

PPP-Adapter t-online:

Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : online
Physikalische Adresse . . . . . . :
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
IPv4-Adresse . . . . . . . . . . : 88.161.218.177(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.255.255
Standardgateway . . . . . . . . . : 0.0.0.0
DNS-Server . . . . . . . . . . . : 218.0.48.191
NetBIOS über TCP/IP . . . . . . . : Deaktiviert

Ethernet-Adapter LAN-Verbindung 3:

Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Fast-Ethernet-Netzwerkkarte für Realtek RTL8139/810x-Familie
Physikalische Adresse . . . . . . : 00-E0-7D-B9-21-F7
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
Verbindungslokale IPv6-Adresse . : fe80::479:4d20:a5cb:b6ec%16(Bevorzugt)
IPv4-Adresse (Auto. Konfiguration): 169.254.182.236(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.0.0
Standardgateway . . . . . . . . . :
DHCPv6-IAID . . . . . . . . . . . : 268492925
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-12-7A-5B-F8-00-11-D8-CE-CD-DF
DNS-Server . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS über TCP/IP . . . . . . . : Aktiviert

Ethernet-Adapter LAN-Verbindung:

Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Intel(R) PRO/1000 CT-Netzwerkverbindung
Physikalische Adresse . . . . . . : 00-11-D8-CE-CD-DF
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
IPv4-Adresse . . . . . . . . . . : 192.168.137.1(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . :
NetBIOS über TCP/IP . . . . . . . : Aktiviert

Tunneladapter isatap.{3FD972A6-EA6B-457D-96BC-FAE3A3EB3BC4}:

Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja

Tunneladapter isatap.{2670AE00-837D-4EF6-9494-FDC046071AA9}:

Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter #3
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja

Tunneladapter 6TO4 Adapter:

Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft-6zu4-Adapter
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
IPv6-Adresse. . . . . . . . . . . : 2002:57a5:d6ab::57a5:d6ab(Bevorzugt)
Standardgateway . . . . . . . . . : 2002:c058:6301::c058:6301
DNS-Server . . . . . . . . . . . : 217.0.43.193
NetBIOS über TCP/IP . . . . . . . : Deaktiviert

Tunneladapter isatap.{8C278552-7DF0-4C9A-965A-F98D70317B59}:

Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter #4
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja

eclp :)
Last edited by eclp on Thu Dec 29, 2011 4:27 pm, edited 1 time in total.
<<

moltra

DLNA master

Posts: 1871

Joined: Thu Mar 24, 2011 11:00 pm

Location: Ohio USA

Post Thu Dec 29, 2011 4:26 pm

Re: To solve the bound address returning problems

Green means that the correct profile for the renderer was automatically detected.
Mark
Beta Tester Group
http://www.serviidb.com Online media resource repository

Netgear EVA2000 | Samsung BD-D5300 | XBOX 360 | Windows 7 | Mint Debian 12 | Raxz Maxx
HowTo: Provide supported formats of a device HowTo: Record a new ticket on Bitbucket
HowTo: Provide details of a video file that doesn't play HowTo: Turn on detailed logging
<<

eclp

User avatar

DLNA master

Posts: 102

Joined: Thu Dec 29, 2011 5:12 am

Post Thu Dec 29, 2011 4:29 pm

Re: To solve the bound address returning problems

And why the correct profile is not recognized?
<<

moltra

DLNA master

Posts: 1871

Joined: Thu Mar 24, 2011 11:00 pm

Location: Ohio USA

Post Thu Dec 29, 2011 4:33 pm

Re: To solve the bound address returning problems

Can you supply the information on the renderer (see signature) in a new thread under support?

As companies make new models and more devices are used with serviio, we have to tweak the detection strings to detect them.

By supplying the renderer information it will allow us to see what needs to be added or changed in the regular expression used to properly detect each device.
Mark
Beta Tester Group
http://www.serviidb.com Online media resource repository

Netgear EVA2000 | Samsung BD-D5300 | XBOX 360 | Windows 7 | Mint Debian 12 | Raxz Maxx
HowTo: Provide supported formats of a device HowTo: Record a new ticket on Bitbucket
HowTo: Provide details of a video file that doesn't play HowTo: Turn on detailed logging
<<

Cerberus

User avatar

DLNA master

Posts: 4114

Joined: Sun Jan 02, 2011 5:20 pm

Location: Reading, UK

Post Thu Dec 29, 2011 6:27 pm

Re: To solve the bound address returning problems

eclp wrote:And why the correct profile is not recognized?


http://wiki.serviio.org/doku.php?id=ser ... _explained
Phil Bennett
Beta Tester Group
Wiki | FAQ

Samsung LE40C750 LCD | Samsung BD-C5900 | Sony PS3 | Windows 7 |
HowTo: Provide supported formats of a device HowTo: Record a new ticket on Bitbucket
HowTo: Provide details of a video file that doesn't play HowTo: Turn on detailed logging
<<

Christopher_Povey

Serviio lover

Posts: 73

Joined: Thu Feb 17, 2011 12:13 pm

Post Wed May 30, 2012 8:58 pm

Re: To solve the bound address returning problems

I am having similar issues with bound IP addresses. Every so often if I boot my PC (but do not log in), none of my devices can see the Serviio server on my Windows 7 x64 PC. However Serviidroid can see it and will allow me to refresh it and stop and start the server.

When I log in I see the following entries:

  Code:
[Device] Created UPnP Device with UUID: 86eb080b-760a-33a2-82e0-afac81c91e1a, bound address: 169.254.157.224
...
[DiscoverySSDPMessageListener] Starting DiscoverySSDPMessageListener using interface eth4 (Intel(R) Gigabit CT Desktop Adapter) and address 169.254.157.224, timeout = 0


Or:

  Code:
[DiscoverySSDPMessageListener] Starting DiscoverySSDPMessageListener using interface Unknown and address 169.254.157.224, timeout = 0
...
[DiscoverySSDPMessageListener] Starting DiscoverySSDPMessageListener using interface Unknown and address 169.254.157.224, timeout = 0


Now my Windows 7 PC is allocated a DHCP IP address by my router (BT HomeHUB2A) but it is always 192.168.1.80).

If I bound the IP address in the Serviio console I get:

  Code:
[Device] Updated bound IP address of Device with UUID: c5393d7e-c47d-385b-ab6a-ca836f6773f8, bound address: 192.168.1.80
...
[DiscoverySSDPMessageListener] Starting DiscoverySSDPMessageListener using interface Unknown and address 192.168.1.80, timeout = 0


My network card is "Intel(R) Gigabit CT Desktop Adapter". The motherboard also has an "Atheros L1 Gigabit Ethernet 10/100/1000Base-T Controller" (but it is not 100% compatible with Windows 7 x64 so it is disabled in the BIOS.

Output from ListNic.class:

  Code:
ip: 127.0.0.1,
name: lo
display name: Software Loopback Interface 1
loopback: true
p2p: false
up: true
virtual: false
multicast: true
------------------------------
ip:
name: net0
display name: WAN Miniport (SSTP)
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: net1
display name: WAN Miniport (L2TP)
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: net2
display name: WAN Miniport (PPTP)
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: ppp0
display name: WAN Miniport (PPPOE)
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth0
display name: WAN Miniport (IPv6)
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth1
display name: WAN Miniport (Network Monitor)
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth2
display name: WAN Miniport (IP)
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: ppp1
display name: RAS Async Adapter
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth3
display name: Atheros L1 Gigabit Ethernet 10/100/1000Base-T Controller
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: net3
display name: Microsoft ISATAP Adapter
loopback: false
p2p: true
up: false
virtual: false
multicast: false
------------------------------
ip:
name: net4
display name: Teredo Tunneling Pseudo-Interface
loopback: false
p2p: true
up: true
virtual: false
multicast: false
------------------------------
ip:
name: net5
display name: WAN Miniport (IKEv2)
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: net6
display name: Microsoft ISATAP Adapter #2
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip: 192.168.1.80,
name: eth4
display name: Intel(R) Gigabit CT Desktop Adapter
loopback: false
p2p: false
up: true
virtual: false
multicast: true
------------------------------
ip:
name: net7
display name: Microsoft ISATAP Adapter-McAfee NDIS Light-Weight Filter-0000
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: net8
display name: Microsoft ISATAP Adapter #2-McAfee NDIS Light-Weight Filter-0000
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: net9
display name: Teredo Tunneling Pseudo-Interface-McAfee NDIS Light-Weight Filter-
0000
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth5
display name: Intel(R) Gigabit CT Desktop Adapter-McAfee NDIS Light-Weight Filte
r-0000
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth6
display name: Intel(R) Gigabit CT Desktop Adapter-QoS Packet Scheduler-0000
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth7
display name: Intel(R) Gigabit CT Desktop Adapter-WFP LightWeight Filter-0000
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth8
display name: WAN Miniport (Network Monitor)-McAfee NDIS Light-Weight Filter-000
0
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth9
display name: WAN Miniport (Network Monitor)-QoS Packet Scheduler-0000
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth10
display name: WAN Miniport (IP)-McAfee NDIS Light-Weight Filter-0000
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth11
display name: WAN Miniport (IP)-QoS Packet Scheduler-0000
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth12
display name: WAN Miniport (IPv6)-McAfee NDIS Light-Weight Filter-0000
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------
ip:
name: eth13
display name: WAN Miniport (IPv6)-QoS Packet Scheduler-0000
loopback: false
p2p: false
up: false
virtual: false
multicast: true
------------------------------


If I log in and stop the Serviio server via the batch file and then restart it then it initialises correctly. It is as if the Serviio server is looking for a network card before Windows has acknowledged it exists...

Any thoughts?
Chris

Running Serviio on Intel Q6700 Windows 7 Ultimate x64 PC feeding a Sony BDP-S570, Pansonic TX-L37G20B, and a XBox 360.
Managed with Serviidroid via HTC One X
<<

zip

User avatar

Serviio developer / Site Admin

Posts: 17215

Joined: Sat Oct 24, 2009 12:24 pm

Location: London, UK

Post Wed May 30, 2012 9:42 pm

Re: To solve the bound address returning problems

weird, because from ListNic there is only one NIC (192.168.1.80) which is available. Not sure why it gives the other IP, unless your DHCP is not correctly setup somehow.
<<

Christopher_Povey

Serviio lover

Posts: 73

Joined: Thu Feb 17, 2011 12:13 pm

Post Wed May 30, 2012 9:50 pm

Re: To solve the bound address returning problems

zip wrote:weird, because from ListNic there is only one NIC (192.168.1.80) which is available. Not sure why it gives the other IP, unless your DHCP is not correctly setup somehow.


It only happens every now and then too. If I log into Windows 7 and restart the server it picks up the card:

  Code:
[Device] Created UPnP Device with UUID: c5393d7e-c47d-385b-ab6a-ca836f6773f8, bound address: 192.168.1.80
...
[DiscoverySSDPMessageListener] Starting DiscoverySSDPMessageListener using interface eth4 (Intel(R) Gigabit CT Desktop Adapter) and address 192.168.1.80, timeout = 0


I think it could be a delay in Windows 7 picking up the IP address from the Router and Serviio has already started and decided it is not there. Might try static IP address for my PC...

If I then log out of my User Account (so that Windows is sitting on the log in screen, this seems to cause Serviio to restart again and it can then repeat the issue.

The other odd thing is that my HTC One X running Servdriod sees the Serviio server on 192.168.1.80 and I can do stuff to it through Servdriod. However the TV', Xbox360 and Sony Blu-ray all return Server Not Found errors. :?
Last edited by Christopher_Povey on Wed May 30, 2012 9:52 pm, edited 1 time in total.
Chris

Running Serviio on Intel Q6700 Windows 7 Ultimate x64 PC feeding a Sony BDP-S570, Pansonic TX-L37G20B, and a XBox 360.
Managed with Serviidroid via HTC One X
<<

zip

User avatar

Serviio developer / Site Admin

Posts: 17215

Joined: Sat Oct 24, 2009 12:24 pm

Location: London, UK

Post Wed May 30, 2012 9:51 pm

Re: To solve the bound address returning problems

Next

Return to Feature requests

Who is online

Users browsing this forum: Google Adsense [Bot] and 19 guests

cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software for PTF.