troyhough 57 Posted February 27, 2019 Share Posted February 27, 2019 Yes, that's just the web app. You can access the dashboard there too. Thanks @@ebr. I found it. Do you have any idea why watching via the Web app circumvents throttling from the ISP's versus the native Android app? Does the data flow over port 80 instead of some other port maybe? Link to comment Share on other sites More sharing options...
Carlo 4331 Posted February 27, 2019 Share Posted February 27, 2019 Is your server setup for encrypted communication? What ports are open for remote use? Link to comment Share on other sites More sharing options...
lightsout 144 Posted February 27, 2019 Author Share Posted February 27, 2019 Is your server setup for encrypted communication? What ports are open for remote use? No, just the standard port. Link to comment Share on other sites More sharing options...
Carlo 4331 Posted February 27, 2019 Share Posted February 27, 2019 It would make no sense why one would be faster then the other because it's the same port. I would check your client options to make sure they aren't restrictive in some way. Link to comment Share on other sites More sharing options...
troyhough 57 Posted February 27, 2019 Share Posted February 27, 2019 (edited) I can assure you that with Sprint, the Android app is throttled. @@lightsout says it's the same way with his testing and Verizon. Edited February 27, 2019 by troyhough Link to comment Share on other sites More sharing options...
lightsout 144 Posted February 27, 2019 Author Share Posted February 27, 2019 I can assure you that with Sprint, the Android app is throttled. @@lightsout says it's the same way with his testing and Verizon. I still have to do further testing. Link to comment Share on other sites More sharing options...
troyhough 57 Posted October 4, 2020 Share Posted October 4, 2020 (edited) Ok so I just noticed that Sprint is not throttling the Emby app any longer. I haven't changed my plan so not sure if this is a Sprint change or a change that Emby has made recently in sending out the data??? Edit: After further testing, the Emby app is still throttled exactly as it was before. Sorry for the misinformation. Edited October 5, 2020 by troyhough Link to comment Share on other sites More sharing options...
Luke 37193 Posted October 4, 2020 Share Posted October 4, 2020 That's great to know, thanks ! Link to comment Share on other sites More sharing options...
troyhough 57 Posted October 5, 2020 Share Posted October 5, 2020 18 hours ago, Luke said: That's great to know, thanks ! After further testing, the Emby app is still throttled exactly as it was before. The Web app/player is not throttled. Sorry for the misinformation. Link to comment Share on other sites More sharing options...
rbjtech 4315 Posted October 6, 2020 Share Posted October 6, 2020 (edited) At the network layer - there is no difference between the web app and any other app. The only possibility is they are analysing the way the traffic is read (not the actual content, impossible if SSL) and then throttling it. As an EXAMPLE (don't know if this is true) - Web server data is read in bursts of X, connection then closed. Connection then re-opended, next batch read, then connection closed. ie typical Web 'browser' based traffic. Emby App is different - it opens the connection and leaves it open, streaming data until you press stop, then the connection is closed. The traffic analysis picks up on these 'differences' and then throttles the traffic connection for the App. Even SSL can be interrogated in this way (without needing decryption) to produce a lot of 'usage' data. To add - it's also possible they are using DNS as the identifier (which will be transmitted in plain text) - so also probably worth trying DNS over SSL - or IP only only to see if that makes any difference. Edited October 6, 2020 by rbjtech Link to comment Share on other sites More sharing options...
troyhough 57 Posted October 6, 2020 Share Posted October 6, 2020 3 hours ago, rbjtech said: At the network layer - there is no difference between the web app and any other app. The only possibility is they are analysing the way the traffic is read (not the actual content, impossible if SSL) and then throttling it. As an EXAMPLE (don't know if this is true) - Web server data is read in bursts of X, connection then closed. Connection then re-opended, next batch read, then connection closed. ie typical Web 'browser' based traffic. Emby App is different - it opens the connection and leaves it open, streaming data until you press stop, then the connection is closed. The traffic analysis picks up on these 'differences' and then throttles the traffic connection for the App. Even SSL can be interrogated in this way (without needing decryption) to produce a lot of 'usage' data. To add - it's also possible they are using DNS as the identifier (which will be transmitted in plain text) - so also probably worth trying DNS over SSL - or IP only only to see if that makes any difference. This is probably correct. When using the Emby Android app, with network monitor enabled, I can see that as soon as I start to watch something, the data rate is high for the first second or so, then immediately is throttled to around 1.5Mb. With the Web app/player, there doesn't appear to be any throttle (Sprint). 1 Link to comment Share on other sites More sharing options...
Carlo 4331 Posted October 7, 2020 Share Posted October 7, 2020 Try it over a VPN connection which should make the whole tunnel unavailable to the ISP to look at. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now