gstuartj 40 Posted September 9, 2015 Posted September 9, 2015 Hi guys, I'd like to use the rate-limiting feature in the settings under Playback>Streaming, but my clients access Emby via a VPN right now and aren't being detected as remote clients. Is there an advanced setting in a config file somewhere that would let me define a custom IP range/subnet as being remote clients so the feature will work?
jody 4 Posted September 11, 2015 Posted September 11, 2015 Hi guys, I'd like to use the rate-limiting feature in the settings under Playback>Streaming, but my clients access Emby via a VPN right now and aren't being detected as remote clients. Is there an advanced setting in a config file somewhere that would let me define a custom IP range/subnet as being remote clients so the feature will work? I also have clients that connect via vpn over internet to my emby server. My clients have the option to use either emby server and it's local site running on my server or the kodi plugin, but they are all connected via vpn and the clients to show up on my server. So for me this works. I'm using openvpn (installed on a linux box). I have installed the emby server on the same box as my openvpn server. I do have linux and windows clients for my vpn server and consequently emby. The main reason for me to do this was that some of the clients I have that connect over internet (VPN) to my emby server have a slow internet connection, they can't watch any HD content and sometimes SD content was buffering, so I wanted to have transcoding activated on lowest possible setting. Also I didn't want to have any multicasting/dlna, so I accomplished it all by doing the above. Should work for you as well.
gstuartj 40 Posted September 17, 2015 Author Posted September 17, 2015 I've just confirmed the setting does not work for me over VPN. I'm using the current Docker container, my VPN IP range is different from my LAN IP range, and the remote streaming limit is set to 1.75Mbps. I'm still able to stream at 10Mbps. I wonder what the difference is...
ebr 16184 Posted September 17, 2015 Posted September 17, 2015 I've just confirmed the setting does not work for me over VPN. I'm using the current Docker container, my VPN IP range is different from my LAN IP range, and the remote streaming limit is set to 1.75Mbps. I'm still able to stream at 10Mbps. I wonder what the difference is... The difference is that a VPN looks like a local network and rate limiting is only applied to remote networks.
gstuartj 40 Posted September 17, 2015 Author Posted September 17, 2015 (edited) The difference is that a VPN looks like a local network and rate limiting is only applied to remote networks. I understand that, but @@jody reported above that the feature works for him over VPN. Either he's mistaken or we have a very different configuration. Regardless, would defining what counts as a local range be a realistic setting for a future version? Or even an open-ended rate-limiting feature that allows you to define limits for various arbitrary ranges? Edited September 17, 2015 by gstuartj
jody 4 Posted September 21, 2015 Posted September 21, 2015 I understand that, but @@jody reported above that the feature works for him over VPN. Either he's mistaken or we have a very different configuration. Regardless, would defining what counts as a local range be a realistic setting for a future version? Or even an open-ended rate-limiting feature that allows you to define limits for various arbitrary ranges? is use the beta client emby for kodi and also tried via web-browser both connected via vpn and both work for me transcoding
Scott84Z28 39 Posted September 21, 2015 Posted September 21, 2015 What defines a "local network"? Just the subnet that the Emby server is in? If so, could you not just create a different subnet for your VPN users? You (VPN) server would then act as a router between the subnets, and then they would appear as "remote", or?
gstuartj 40 Posted September 21, 2015 Author Posted September 21, 2015 What defines a "local network"? Just the subnet that the Emby server is in? If so, could you not just create a different subnet for your VPN users? You (VPN) server would then act as a router between the subnets, and then they would appear as "remote", or? Yeah, my VPN is in a different subnet already. As far as I can tell, currently any address in a private range is considered by the server to be "local", anything in a public range is remote. I'd love more power to define those rules.
jpaytoncfd 5 Posted November 16, 2015 Posted November 16, 2015 Yeah, my VPN is in a different subnet already. As far as I can tell, currently any address in a private range is considered by the server to be "local", anything in a public range is remote. I'd love more power to define those rules. I know this is a few months old but If I recall users can set their trans-code rate manually by user or even by video. That might help you.
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