How to treat ip in 172.24.0.0/18 as public network

[Guest]

So I would say it needs to be properly checked when your local IP IS NOT automatically detected as 172.16.. for local.. 

EDIT: Note when I put mine in for the range I can no longer connect with my phone... If I remove the ip address range, I can again connect.. otherwise I get a white screen with 'cidr' at the top in my browser.

This is on a Wireless 5GHz connection with 172.16.0.9 as an address.. Using Edge on a Microsoft Lumia 950XL using Edge as a browser.

Emby on Windows 10.. with a local detected ( and indicated at one point/try 172.16.0.x address )

Edited March 31, 2021 by Guest

[maplefeng 3]

16 minutes ago, Hxemby001 said:

So I would say it needs to be properly checked when your local IP IS NOT automatically detected as 172.16.. for local.. 

EDIT: Note when I put mine in for the range I can no longer connect with my phone... If I remove the ip address range, I can again connect.. otherwise I get a white screen with 'cidr' at the top in my browser.

This is on a Wireless 5GHz connection with 172.16.0.9 as an address.. Using Edge on a Microsoft Lumia 950XL using Edge as a browser.

Emby on Windows 10.. with a local detected ( and indicated at one point/try 172.16.0.x address )

The problem is, the 172 address is ALWAYS treated as an local ip, even though I've set the local network as 192.168.1.0/24

[Guest]

Right.. and mine will not allow me to connect when I set the range... If I leave it out, everything is fine..( I do not allow remote connections )

Edited March 31, 2021 by Guest

[Luke 42078]

21 minutes ago, maplefeng said:

The problem is, the 172 address is ALWAYS treated as an local ip, even though I've set the local network as 192.168.1.0/24

Correct, that's what I mentioned earlier.

[maplefeng 3]

3 minutes ago, Luke said:

Correct, that's what I mentioned earlier.

But I believe that the better idea is when the LAN ip range is set to be 192.168.1.0/24,  only 192.168.1.X is treated as the local ip, especially for users who relies on VPN connection to access local Emby server, due to speed (VPN is way slower than LAN, music transcode is required) and security (username is displayed on the login screen)

[rbjtech 5284]

May we ask why 172.16.0.0/12 (aka 172.16.0.0 – 172.31.255.255) is being treated differently ?

They are all RFC 1918 private IP addresses .. 

 

 

Edited March 31, 2021 by rbjtech

[Carlo 4561]

1 hour ago, rbjtech said:

May we ask why 172.16.0.0/12 (aka 172.16.0.0 – 172.31.255.255) is being treated differently ?

They are all RFC 1918 private IP addresses .. 

 

 

Correct and since there are 2 different ways these reserved addresses are being used I'd suggest that we take this time to fix and make it the most flexible.
In other words treat all 3 spaces as local UNLESS the network field is filled in THEN ONLY use that field.

That would all a user to have 10.x as local by default but by configuring only a 192.x space the 10 would become a remote address.  This is perfect for those who run VPNs or proxies as it gives them total control in Emby how the IP space should be used and how bitrates and other Emby features get applied.

[Happy2Play 9780]

1 hour ago, Luke said:

2 hours ago, maplefeng said:

The problem is, the 172 address is ALWAYS treated as an local ip, even though I've set the local network as 192.168.1.0/24

Correct, that's what I mentioned earlier.

So the note is incorrect.  As this is not true.

Quote

Comma separated list of IP addresses or IP/netmask entries for networks that will be considered on local network when enforcing bandwidth restrictions. If set, all other IP addresses will be considered to be on the external network and will be subject to the external bandwidth restrictions.

 

[maplefeng 3]

Hi @Luck. Will this feature be further improved in the future please

[Luke 42078]

Yes it will. Thanks for the feedback.

[jimbobjonesbob 7]

Has anything changed in relation to the 172. addresses?

I have this in network:

but get this when connecting remotely via vpn

RemoteIp: 172.26.0.1, IsInLocalNetwork: True

[Happy2Play 9780]

2 hours ago, jimbobjonesbob said:

Has anything changed in relation to the 172. addresses?

I have this in network:

but get this when connecting remotely via vpn

RemoteIp: 172.26.0.1, IsInLocalNetwork: True

Can you post a server log after restarting the server to show network detection.

[rbjtech 5284]

I personally think this needs a re-think.

The RFC1918 addresses are private and technically you are going to have issues routing them across the internet - they should not work beyond your own gateway - routers should drop connections that try and use them.

Therefore trying to 'accommodate' them is futile - it is the wrong thing to do.  They are an RFC standard for a reason !

I believe emby should just change the 'LAN Networks' to be an 'Exception/VPN' range (within RFC1918) where emby simply changes the status from 'Local' to 'Remote' - purely for transcoding policy reasons and nothing more.    Change the wording to reflect this - and I think the issue/confusion will be resolved ?

[Carlo 4561]

Yes, totally agree with rbjtech. All RFC1918 addresses should not be treated as remote but instead as local addresses.

You can fully route these addresses on networks you control including their use with privately VPN, but all RFC1918 addresses are always considered unrouteable outside the local network.

[justinrh 260]

 .

Edited February 10, 2023 by justinrh

[luser 37]

Quote

...purely for transcoding policy reasons and nothing more

Yes. Managing networking in the application layer is always confusing and a headache. Stay in the app layer. Just create a socket on the address of choice and you're done. Anything more just causes confusion. Emby's "Local" and "Remote" concepts have always been a frustration for me.

[justinrh 260]

But there does need to be a distinction, because the login screen and access changes based on local/remote context.  I wouldn't want to lose that.

[Luke 42078]

Hi, this is resolved in the upcoming 4.8 server release. Thanks.