Geo IP

[rejetto]

With 0.50 we get the possibility to see the country of origin of connections (displayed under Admin > Monitoring), but also to allow or block some countries.

[W-i-n-7]

awesome

[mcodr]

It seems like when GEO IP feature is enabled, and the "When country cannot be determined is set to: Block", you are no longer able to access the site/admin panel locally using direct local IP.

Any way, to still allow it?

[rejetto]

of course with local you don't mean localhost, but local network.
that's expected, a "local network" is not always trusted, it can be your college campus, filled with people you don't know.

but maybe it's better if the geo-firewall doesn't act on the LAN, leaving that to the general "block" feature. That sounds like more flexible.

[W-i-n-7]

first thing that came to mind was that there could be a "only allow the following local ip:s" setting
but i dont know how good that would be

[rejetto]

another option is not really needed, if can block local ips using "blocked ip" feature

[W-i-n-7]

except you wouldnt know an attacker's ip and local ips change due to dhcp

[mcodr]

in my case, I got an old netbook computer dedicated to run the HFS server at home.
I would prefer to use the local ip to check admin panel on my main computer.

Perhaps an "allowed ip" feature that can overwrite Geo IP?

[W-i-n-7]

or a toggle to affect or not local ips

[rejetto]

except you wouldnt know an attacker's ip and local ips change due to dhcp

geo is not blockin one specific ip but the whole lan, so i don't understand your point.
if you want to block the lan you block 192.168.0.* for example, and you are done, you don't need to know other's ip.

my point is that you at the moment CANNOT exclude the lan.
with the other way i described you CAN include lan if you want.
geo has very little to do with a lan.

[rejetto]

would you try it and give me a feedback?
just right click on "check for updates" and paste this link https://github.com/rejetto/hfs/files/14157522/hfs-windows.zip

[mcodr]

yes, that is exactly what i meant. thank you.
for example - http://192.168.1.10:8080/~/admin/#/ does not work on 192.168.1.11 even when on 192.168.1.10

[W-i-n-7]

i access over local ip alot too

[rejetto]

i have this configuration, and i'm correctly connecting on to 192.168.0.3, so I don't know what's going on there

@W-i-n-7 do you have the same problem as he?

[mcodr]

I got it to work now! Thank you!
I had to uncheck this settings which is funny.

[W-i-n-7]

oh that makes sense