The networking behind shifting is very complex.
Let me know what problems you are having and about your firewall/network config - I would like to see how this solution works with different configurations.
Forums
A community for Skifta users to learn and share.
Tell us about your networking setup and any networking issues you're having.
-
Posted 1 year ago
lathanhaiko
MemberThis may or may not be a network issue, I'm setting up skifta for the first time.
This morning (6:30 PST) my phone was showing up correctly on my Skifta dashboard.
1. I went to work (new Wifi network)
2. Skifta updated on my phone (don't know why, but I saw the updating screen)Now (from work) my phone is grayed out on the skifta dashboard. My media server (still at home) shows up on the dashboard correctly.
When attempting to create a connection (from my phone), I can successfully create a connection from my phone to my phone, but when I try to create a connection from my home media server to my phone it sits on "creating a connection" for about 5 minutes, then goes to "waiting for connection" and sits there forever (at least > 10 minutes).
Any suggestions on how I can debug this?
I'm guessing there's a network port blocked by my work's firewall that is not blocked on my home networ, but I don't know. This evening I'll check again when I get to my home network.
Any idea which network port(s) is needed?
-
Posted 1 year ago
lathanhaiko
MemberJust a guess, but I see the following error in the android logs
E/SkiftaService-Generic( 1726): Unable to obtain device xml from: http://10.46.6.126:49152/rootdesc1.xml
E/SkiftaService-Generic( 1726): org.apache.http.conn.ConnectTimeoutException: Connect to /10.46.6.126:49152 timed outI can access this file over Ethernet, but not over WIFI.
-
Posted 1 year ago
Few points here:
* "Skifta Updated my phone" - In fact, all that's happening here is that Skifta contacts the home server to check if there are any new bundles that you need. Most of the time there will be no updates but you still see this screen.
* I was going to suggest that you check the logging - but you have done this. "Connect to /10.46.6.126:49152 timed out" is an issue, yes. It's not clear if that test was conducted on your home network on your work network. Which was it? It could be likely that this is a deliberately blocked outgoing port..
*An additional test would be to use a friends wifi network to perform the same test, and that would isolate the issue as being the network. -
Posted 1 year ago
So you need to look at the two things separately, as although they're both errors, they relate to different things.
In terms of the work network preventing the phone showing up, this is very much likely to be network conditions in some way. Commonly we find certain transparent proxies in work/corporate environments treat the traffic as web traffic and in some way prevent the phone app coming online. You may still be able to use channel content in such environments, but shifting might not work. Trying this on a different network as Conal suggests will certainly help prove this.
In terms of the second error with the rootdesc1.xml timing out - this is a local UPnP error and is usually seen when a 'duff' device is present on the network. Generally speaking these types of devices/errors can be ignored (i.e. errant router broadcasting itself as a UPnP device, but then refusing to hand out its device description,etc). As long as the devices you expect/want to see appear on the local list, ignore these. Since you're seeing this error from your phone and it only has wifi available, there appears to be a local network problem in that the phone is receiving the broadcast message letting it know that a device (10.46.6.126) is available, but it can't route back to it.
Do you have two subnets (one for wired, one for wireless)? Or does the device in question (10.46.6.126) have two network connections (for example in the case of a router itself, this may be true)? Some devices have implemented the multi-connection stack badly and they'll broadcast their availability on multiple interfaces (correctly), but incorrectly pass out the return address for one interface (i.e. broadcast on both wired and wireless, but hand out the return address as wired).
-
Posted 1 year ago
lathanhaiko
Member* The timeout to 10.46.6.126:49152 was from my work network
* * I have requested my workplace unblock this port and provided them info about what is failing. I will update you when I get a response from them.* I will test on an alternate (besides work and home) Wifi network and let you know the results.
* My work ethernet and Wifi are on different subnets, but neither is on the same subnet as 10.46.6.126.
* I downloaded the rootdesc1.xml file using ethernet, and it looks like it's describing an "Axis Q7406 Video Encoder Blade". I do not have any access or knowledge of it.
* Allan, if you're correct and this is not the actual reason my phone cannot connect while on my work network, what should be my next step in debugging this?
-
Posted 1 year ago
lathanhaiko
MemberI tried from a friends WIFI network, and I was able to establish a connection and view the music, but not play any. See this thread for a full log
http://forums.skifta.com/topic/java-error#post-1492 -
Posted 1 year ago
Ok - lets work from the thread http://forums.skifta.com/topic/java-error - and consolidate this all in one place :-)
Reply
You must log in to post.