Question About My Lan Networks

[justinrh 260]

I have the option checked for "Hide this user from login screens when connected remotely" for the admin user, but the user still shows on the login page when I connect from the Internet.  Why for?

[Happy2Play 9782]

Only way for that to happen is if your remote connection is not considered remote and is considered local.

[justinrh 260]

Righto, that is what I thought, and in trying to prove that out I was being deceived by my test.  I was using my guest WiFi (on a diff subnet with intranet access disabled) on my tablet to simulate the external connection, and even had to use my domain to access Emby.  But, Emby still saw it as a local connection because the tablet's IP address was still coming thru as a common private IP subnet!  I didn't know this was happening until I dug into the logs.

If I restrict the local address to only the server subnet, the tablet can't connect at all.

[Carlo 4561]

Yea, that probably won't work.  Try a browser on your cell phone connected to WIFI vs cell network.  You should see the difference easily that way.

[MBSki 1114]

This was fixed for me in a recent update. I think it's still in beta though. 

Here's the thread that was tracking the change: WAN IP (172.58) tagged as Local IP by Emby - General/Windows - Emby Community. 

Is your WAN IP in the 172.58 range?

[Happy2Play 9782]

So you are trying to get your LAN WIFI guest network to appear as a remote connections?

10 minutes ago, justinrh said:

If I restrict the local address to only the server subnet, the tablet can't connect at all.

What exactly are you applying and to what Network field?

[justinrh 260]

2 minutes ago, Happy2Play said:

So you are trying to get your LAN WIFI guest network to appear as a remote connections?

What exactly are you applying and to what Network field?

I put the server's subnet 192.168.1.0/24 in the "LAN networks" field.  The tablet is on 192.168.101.0.  The tablet's browser showed 'forbidden'.

[Carlo 4561]

What do you mean forbidden?

If you have a cell phone that can use wifi or cell you can just put the network back the way it was and use the phone to test both local and remote.
That could save a lot of hassle of trying to reconfigure the network and Emby.

[Happy2Play 9782]

2 minutes ago, cayars said:

What do you mean forbidden?

Easily reproducible by limiting your LAN Network address info.

13 minutes ago, justinrh said:

I put the server's subnet 192.168.1.0/24 in the "LAN networks" field.  The tablet is on 192.168.101.0.  The tablet's browser showed 'forbidden'.

Do have anything white/black listed in Remote IP address filter mode:?

[justinrh 260]

12 minutes ago, Happy2Play said:

Do have anything white/black listed in Remote IP address filter mode:?

No.

[Happy2Play 9782]

Example if I limit my LAN network to say my Server IP address, no other LAN device can connect since I have applied Regional GEO IP addresses in Remote IP address filter mode as a Whitelist.  Since the list does not contain any 192.168.x.x/xx network, I get FORBIDDEN when trying to connect any other LAN device.

But I do not have a multi-subnet setup to test on.

1 minute ago, justinrh said:

14 minutes ago, Happy2Play said:

Do have anything white/black listed in Remote IP address filter mode:?

No.

Something is blocking the subnet for access completely.

[justinrh 260]

@Happy2Play  What I experienced with the tablet not being able to connect is expected, right?  If I don't allow 192.168.101.x, then I should get forbidden, right?  I'm not sure what issue you are chasing.

[Happy2Play 9782]

9 minutes ago, justinrh said:

@Happy2Play  What I experienced with the tablet not being able to connect is expected, right?  If I don't allow 192.168.101.x, then I should get forbidden, right?  I'm not sure what issue you are chasing.

You are telling Emby that only 192.168.1.0/24 is a local network, other networks should be considered and treated as Remote connections.  But don't have the network to test the this.

You can test adding 192.168.101.0/24 to Remote IP address filter mode: as a whitelist.  But note populating this field will only allow addresses set in that field, so I would only test this from within your local environment.

[justinrh 260]

Well, I tried it again and the tablet can connect and Emby treats it as remote.  (Yeah!)  I don't know what is different this time.  Thanks for the help.

It looks like Emby still sees 127.0.0.1 as local even if when you specify the LAN subnet.  Darn it.

[Happy2Play 9782]

32 minutes ago, justinrh said:

It looks like Emby still sees 127.0.0.1 as local even if when you specify the LAN subnet.

I don't believe you can make the loopback 127.0.0.1/localhost address remote, but why would you?

[Carlo 4561]

The IP address 127.0.0.1 is a special-purpose IPv4 address and is called the localhost or loopback address. All computers use this address as their own, but it doesn't let computers communicate with other devices as a real IP address does.  So you can think of it as a special purpose, non-routable IP address.

 

[justinrh 260]

18 hours ago, Happy2Play said:

I don't believe you can make the loopback 127.0.0.1/localhost address remote, but why would you?

That would solve my my Stunnel problem 

[Happy2Play 9782]

2 minutes ago, justinrh said:

That would solve my my Stunnel problem 

But as Cayars mentioned it would cause more problems as your local system hosting Emby would no longer be local.  So local LAN connection would not exist.

[Luke 42080]

6 minutes ago, Happy2Play said:

But as Cayars mentioned it would cause more problems as your local system hosting Emby would no longer be local.  So local LAN connection would not exist.

Exactly. The server has a lot of options and in many cases we allow you to make your own mess, but that would just be taking it a bit too far.

[justinrh 260]

I'd think it could work in theory (excluding the localhost restrictions, of course).  (Not to make an issue of this, but just to give my thought process; I consider the issue done.)  If you exclude everything except your server's subnet, then local connections would still work because that traffic would be on the subnet and not localhost.