UMS 2.6.5 not working in Aptosid amd64
Forum rules
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
UMS 2.6.5 not working in Aptosid amd64
Hi,
I'm trying to set up UMS 2.6.5 in Aptosid amd64 latest version which is not working over wifi. The controller can be detected by Android renderer when I use Android USB tethering. UMS for windows works fine in wifi mode - ruling out any issues with router configuration. Can somebody please help?
Thanks,
Anand
I'm trying to set up UMS 2.6.5 in Aptosid amd64 latest version which is not working over wifi. The controller can be detected by Android renderer when I use Android USB tethering. UMS for windows works fine in wifi mode - ruling out any issues with router configuration. Can somebody please help?
Thanks,
Anand
Re: UMS 2.6.5 not working in Aptosid amd64
Some possibly useful log.
Code: Select all
TRACE 2013-08-10 22:29:23.827 [main] checkNetworkInterface(parent = null, child interfaces = java.net.NetworkInterface$1@1b1325d3)
TRACE 2013-08-10 22:29:23.827 [main] checking eth0, display name: eth0
TRACE 2013-08-10 22:29:23.828 [main] available addresses for eth0 is: [/192.168.1.6]
TRACE 2013-08-10 22:29:23.828 [main] non loopback/ipv4 addresses: [/192.168.1.6]
TRACE 2013-08-10 22:29:23.828 [main] checkNetworkInterface(parent = eth0, child interfaces = java.net.NetworkInterface$1subIFs@4792ba63)
TRACE 2013-08-10 22:29:23.828 [main] checkNetworkInterface(parent = eth0) finished
TRACE 2013-08-10 22:29:23.828 [main] sub address for eth0 is []
TRACE 2013-08-10 22:29:23.828 [main] checking /192.168.1.6 on eth0
TRACE 2013-08-10 22:29:23.828 [main] found eth0 -> 192.168.1.6
TRACE 2013-08-10 22:29:23.829 [main] checking lo, display name: lo
TRACE 2013-08-10 22:29:23.829 [main] available addresses for lo is: [/127.0.0.1]
TRACE 2013-08-10 22:29:23.829 [main] non loopback/ipv4 addresses: []
TRACE 2013-08-10 22:29:23.829 [main] checkNetworkInterface(parent = lo, child interfaces = java.net.NetworkInterface$1subIFs@407d29df)
TRACE 2013-08-10 22:29:23.829 [main] checkNetworkInterface(parent = lo) finished
TRACE 2013-08-10 22:29:23.829 [main] sub address for lo is []
TRACE 2013-08-10 22:29:23.829 [main] checking /127.0.0.1 on lo
TRACE 2013-08-10 22:29:23.830 [main] has /127.0.0.1, which is skipped, because loopback=true, ipv6=false
TRACE 2013-08-10 22:29:23.830 [main] found lo, without valid address
TRACE 2013-08-10 22:29:23.830 [main] checkNetworkInterface(parent = null) finished
TRACE 2013-08-10 22:29:23.830 [main] default network interface address from [InterfaceAssociation(addr=/192.168.1.6, iface=name:eth0 (eth0), parent=null), InterfaceAssociation(addr=null, iface=name:lo (lo), parent=null)]
TRACE 2013-08-10 22:29:23.830 [main] first network interface: InterfaceAssociation(addr=/192.168.1.6, iface=name:eth0 (eth0), parent=null)
INFO 2013-08-10 22:29:23.830 [main] Using address /192.168.1.6 found on network interface: name:eth0 (eth0)
INFO 2013-08-10 22:29:23.831 [main] Created socket: /192.168.1.6:5001
DEBUG 2013-08-10 22:29:23.918 [main] Sending ALIVE...
TRACE 2013-08-10 22:29:23.919 [main] Sending message from multicast socket on network interface: name:null
TRACE 2013-08-10 22:29:23.919 [main] Multicast socket is on interface: /0.0.0.0
TRACE 2013-08-10 22:29:23.920 [main] Socket Timeout: 0
TRACE 2013-08-10 22:29:23.920 [main] Socket TTL: 32
INFO 2013-08-10 22:29:23.920 [main] Using the following UUID configured in UMS.conf: d2851958-33ca-47cf-a533-ea55570d602a
TRACE 2013-08-10 22:29:23.921 [main] Waiting 250 milliseconds...
INFO 2013-08-10 22:29:24.175 [main] The server is now available for renderers to find
TRACE 2013-08-10 22:29:24.176 [UPNPHelper] Setting multicast network interface: name:eth0 (eth0)
DEBUG 2013-08-10 22:29:34.173 [UPNP-AliveMessageSender] Sending ALIVE...
TRACE 2013-08-10 22:29:34.175 [UPNP-AliveMessageSender] Sending message from multicast socket on network interface: name:null
TRACE 2013-08-10 22:29:34.175 [UPNP-AliveMessageSender] Multicast socket is on interface: /0.0.0.0
TRACE 2013-08-10 22:29:34.175 [UPNP-AliveMessageSender] Socket Timeout: 0
TRACE 2013-08-10 22:29:34.176 [UPNP-AliveMessageSender] Socket TTL: 32
TRACE 2013-08-10 22:29:34.177 [UPNPHelper] Receiving a NOTIFY from [192.168.1.6:54655]
Re: UMS 2.6.5 not working in Aptosid amd64
Seems like WLAN and LAN are not bridged on my router. Guess I've to admit defeat 
http://forums.whirlpool.net.au/archive/1269103

http://forums.whirlpool.net.au/archive/1269103
- Optimus_prime
- Posts: 678
- Joined: Fri Jun 01, 2012 6:39 pm
- Location: Sydney, Australia
Re: UMS 2.6.5 not working in Aptosid amd64
Maybe you might have to get a new router. Sounds like your issue is very much related to your Netgear
How Ask For Support
Remember, Debug Log's Can/Will Help and Explain your issues, we're not mind reader's but here to help
OS's I Use And Can Assist With: Windows 7/8, Mac OS-X 10.8 & 10.9
Mac OS-X Java 7 Builds Mac OS-X Java 7 Forum
Remember, Debug Log's Can/Will Help and Explain your issues, we're not mind reader's but here to help
OS's I Use And Can Assist With: Windows 7/8, Mac OS-X 10.8 & 10.9
Mac OS-X Java 7 Builds Mac OS-X Java 7 Forum