redirect page for login

[momothecat]

Hi,
I was searching simple and good solution for internet access parental control for home user, and I found this product.

Configuration a little bit confusing because using two ip address on the same NIC, but I managed it.

I setup the box only for DNS only, and I already setup a client using DNS from keexybox, but it looks like it missing dns redirection for initial connection, or am i missing something in the configuration?

Thanks
Momo

[momothecat]

Hi,
I was searching simple and good solution for internet access parental control for home user, and I found this product.

Configuration a little bit confusing because using two ip address on the same NIC, but I managed it.

I setup the box only for DNS only, and I already setup a client using DNS from keexybox, but it looks like it missing dns redirection for initial connection, or am i missing something in the configuration?

Thanks
Momo

[benoit]

Hi,
By default, the use of KeexyBox's DNS is blocked. The user must enter his credentials in the login page to use KeexyBox's DNS. If you want users to not have to enter their credentials, you must declare their devices to KeexyBox and connect them.

The steps to check to have a working DNS with KeexyBox are:
1/ Under "System Setting -> Network" make sure that "DNS 1" and optionnally "DNS 2" are valid DNS servers. These DNS are use to relay DNS queries to the internet. You can use the DNS of your router or a public DNS like 8.8.8.8.
2/ Under "System Setting -> Misc..." Check the box "Use defined DNS as redirectors".
3/ Setup KeexyBox's DNS on the client computer.
4/ Open a browser on the client computer, enter the KeexyBox address and then enter the user credential to connect it to the internet (you have to create users before).

If want to prevent users from doing step 4:
1/ You can declare user's device as explain at: https://wiki.keexybox.org/doku.php/devices_manage
2/ And then connect declared devices as explain at: https://wiki.keexybox.org/doku.php/using...ct_devices
3/ Setup KeexyBox's DNS on the client device.

[benoit]

Hi,
By default, the use of KeexyBox's DNS is blocked. The user must enter his credentials in the login page to use KeexyBox's DNS. If you want users to not have to enter their credentials, you must declare their devices to KeexyBox and connect them.

The steps to check to have a working DNS with KeexyBox are:
1/ Under "System Setting -> Network" make sure that "DNS 1" and optionnally "DNS 2" are valid DNS servers. These DNS are use to relay DNS queries to the internet. You can use the DNS of your router or a public DNS like 8.8.8.8.
2/ Under "System Setting -> Misc..." Check the box "Use defined DNS as redirectors".
3/ Setup KeexyBox's DNS on the client computer.
4/ Open a browser on the client computer, enter the KeexyBox address and then enter the user credential to connect it to the internet (you have to create users before).

If want to prevent users from doing step 4:
1/ You can declare user's device as explain at: https://wiki.keexybox.org/doku.php/devices_manage
2/ And then connect declared devices as explain at: https://wiki.keexybox.org/doku.php/using...ct_devices
3/ Setup KeexyBox's DNS on the client device.

[momothecat]

Hi Benoit,

Thanks for your response. So, for initial connection, user "must" access to KeexyBox IP address manually from their browser and there's no redirection mechanism.

What I mean in redirection is, for example; a user just enter any url in their browser and then the request redirected to the KeexyBox captive portal for authentication. After he/she authenticated, they can continue to access the internet.

If that function not in current version, maybe the developer can be so kind to add it in the future version.

Thanks

[momothecat]

Hi Benoit,

Thanks for your response. So, for initial connection, user "must" access to KeexyBox IP address manually from their browser and there's no redirection mechanism.

What I mean in redirection is, for example; a user just enter any url in their browser and then the request redirected to the KeexyBox captive portal for authentication. After he/she authenticated, they can continue to access the internet.

If that function not in current version, maybe the developer can be so kind to add it in the future version.

Thanks

[benoit]

Hi Benoit,

Thanks for your response. So, for initial connection, user "must" access to KeexyBox IP address manually from their browser and there's no redirection mechanism.

What I mean in redirection is, for example; a user just enter any url in their browser and then the request redirected to the KeexyBox captive portal for authentication. After he/she authenticated, they can continue to access the internet.

If that function not in current version, maybe the developer can be so kind to add it in the future version.

Thanks

You should have a redirection. But maybe you had to disconnect from network and reconnect at client side to get it working.


Devices are redirected to KeexyBox Captive Portal if the client tries to reach one of these domains after accessing the local network:



connectivitycheck.gstatic.com

clients1.google.com

clients3.google.com

connect.rom.miui.com

captive.apple.com

airport.us

thinkdifferent.us

msftconnecttest.com

www.msftconnecttest.com



So it should works for Windows, Apple devices and Android.



What are your clients OS ?



For example we find out that XIAOMI phones do not use standard android URL (they use connect.rom.miui.com) to check if there is a Captive Portal on the network.

[benoit]

Hi Benoit,

Thanks for your response. So, for initial connection, user "must" access to KeexyBox IP address manually from their browser and there's no redirection mechanism.

What I mean in redirection is, for example; a user just enter any url in their browser and then the request redirected to the KeexyBox captive portal for authentication. After he/she authenticated, they can continue to access the internet.

If that function not in current version, maybe the developer can be so kind to add it in the future version.

Thanks

You should have a redirection. But maybe you had to disconnect from network and reconnect at client side to get it working.


Devices are redirected to KeexyBox Captive Portal if the client tries to reach one of these domains after accessing the local network:



connectivitycheck.gstatic.com

clients1.google.com

clients3.google.com

connect.rom.miui.com

captive.apple.com

airport.us

thinkdifferent.us

msftconnecttest.com

www.msftconnecttest.com



So it should works for Windows, Apple devices and Android.



What are your clients OS ?



For example we find out that XIAOMI phones do not use standard android URL (they use connect.rom.miui.com) to check if there is a Captive Portal on the network.

[momothecat]

Hi Benoit,

Thanks for your response. So, for initial connection, user "must" access to KeexyBox IP address manually from their browser and there's no redirection mechanism.

What I mean in redirection is, for example; a user just enter any url in their browser and then the request redirected to the KeexyBox captive portal for authentication. After he/she authenticated, they can continue to access the internet.

If that function not in current version, maybe the developer can be so kind to add it in the future version.

Thanks

You should have a redirection. But maybe you had to disconnect from network and reconnect at client side to get it working.


Devices are redirected to KeexyBox Captive Portal if the client tries to reach one of these domains after accessing the local network:



connectivitycheck.gstatic.com

clients1.google.com

clients3.google.com

connect.rom.miui.com

captive.apple.com

airport.us

thinkdifferent.us

msftconnecttest.com

www.msftconnecttest.com



So it should works for Windows, Apple devices and Android.



What are your clients OS ?



For example we find out that XIAOMI phones do not use standard android URL (they use connect.rom.miui.com) to check if there is a Captive Portal on the network.

I'm sorry, it's look like I came to a conclusion too soon and not testing with other operating system. Earlier I was using CentOS 8.

After done some testing, here are the result with all the devices that I have in my home.

1. Windows 10
Initial connection: redirected to captive portal
Without authentication: not able to browse
Connection duration time out: not able to browse

2. iPad OS 13.7
Initial connection: redirected to captive portal
Without authentication: not able to browse
Connection duration time out: not able to browse

3. CentOS 8
Initial connection: not redirected, manual
Without authentication: not able to browse
Connection duration time out: not able to browse

4. Mi 11.0.6/Android 9 & Realme ColorOS 7/Android 10 & Vivo Funtouch OS_3.1/Android 7.1.2
Initial connection: redirected to captive portal
Without authentication: still able to browse
Connection duration timeout: still able to browse

[momothecat]

Hi Benoit,

Thanks for your response. So, for initial connection, user "must" access to KeexyBox IP address manually from their browser and there's no redirection mechanism.

What I mean in redirection is, for example; a user just enter any url in their browser and then the request redirected to the KeexyBox captive portal for authentication. After he/she authenticated, they can continue to access the internet.

If that function not in current version, maybe the developer can be so kind to add it in the future version.

Thanks

You should have a redirection. But maybe you had to disconnect from network and reconnect at client side to get it working.


Devices are redirected to KeexyBox Captive Portal if the client tries to reach one of these domains after accessing the local network:



connectivitycheck.gstatic.com

clients1.google.com

clients3.google.com

connect.rom.miui.com

captive.apple.com

airport.us

thinkdifferent.us

msftconnecttest.com

www.msftconnecttest.com



So it should works for Windows, Apple devices and Android.



What are your clients OS ?



For example we find out that XIAOMI phones do not use standard android URL (they use connect.rom.miui.com) to check if there is a Captive Portal on the network.

I'm sorry, it's look like I came to a conclusion too soon and not testing with other operating system. Earlier I was using CentOS 8.

After done some testing, here are the result with all the devices that I have in my home.

1. Windows 10
Initial connection: redirected to captive portal
Without authentication: not able to browse
Connection duration time out: not able to browse

2. iPad OS 13.7
Initial connection: redirected to captive portal
Without authentication: not able to browse
Connection duration time out: not able to browse

3. CentOS 8
Initial connection: not redirected, manual
Without authentication: not able to browse
Connection duration time out: not able to browse

4. Mi 11.0.6/Android 9 & Realme ColorOS 7/Android 10 & Vivo Funtouch OS_3.1/Android 7.1.2
Initial connection: redirected to captive portal
Without authentication: still able to browse
Connection duration timeout: still able to browse

[benoit]

Hi Benoit,

Thanks for your response. So, for initial connection, user "must" access to KeexyBox IP address manually from their browser and there's no redirection mechanism.

What I mean in redirection is, for example; a user just enter any url in their browser and then the request redirected to the KeexyBox captive portal for authentication. After he/she authenticated, they can continue to access the internet.

If that function not in current version, maybe the developer can be so kind to add it in the future version.

Thanks

You should have a redirection. But maybe you had to disconnect from network and reconnect at client side to get it working.


Devices are redirected to KeexyBox Captive Portal if the client tries to reach one of these domains after accessing the local network:



connectivitycheck.gstatic.com

clients1.google.com

clients3.google.com

connect.rom.miui.com

captive.apple.com

airport.us

thinkdifferent.us

msftconnecttest.com

www.msftconnecttest.com



So it should works for Windows, Apple devices and Android.



What are your clients OS ?



For example we find out that XIAOMI phones do not use standard android URL (they use connect.rom.miui.com) to check if there is a Captive Portal on the network.

I'm sorry, it's look like I came to a conclusion too soon and not testing with other operating system. Earlier I was using CentOS 8.

After done some testing, here are the result with all the devices that I have in my home.

1. Windows 10
Initial connection: redirected to captive portal
Without authentication: not able to browse
Connection duration time out: not able to browse

2. iPad OS 13.7
Initial connection: redirected to captive portal
Without authentication: not able to browse
Connection duration time out: not able to browse

3. CentOS 8
Initial connection: not redirected, manual
Without authentication: not able to browse
Connection duration time out: not able to browse

4. Mi 11.0.6/Android 9 & Realme ColorOS 7/Android 10 & Vivo Funtouch OS_3.1/Android 7.1.2
Initial connection: redirected to captive portal
Without authentication: still able to browse
Connection duration timeout: still able to browse

For CentOS we need to find the address used to detect the captive portal. Once known, it is possible (since version 20.10.1 of KeexyBox) to modify the list of URLs by editing the "cportal_test_domains" param at http://keexybox:8001/config/advanced

It's strange for result 4, without authentication, you should not be able to use KeexyBox DNS...

[benoit]

Hi Benoit,

Thanks for your response. So, for initial connection, user "must" access to KeexyBox IP address manually from their browser and there's no redirection mechanism.

What I mean in redirection is, for example; a user just enter any url in their browser and then the request redirected to the KeexyBox captive portal for authentication. After he/she authenticated, they can continue to access the internet.

If that function not in current version, maybe the developer can be so kind to add it in the future version.

Thanks

You should have a redirection. But maybe you had to disconnect from network and reconnect at client side to get it working.


Devices are redirected to KeexyBox Captive Portal if the client tries to reach one of these domains after accessing the local network:



connectivitycheck.gstatic.com

clients1.google.com

clients3.google.com

connect.rom.miui.com

captive.apple.com

airport.us

thinkdifferent.us

msftconnecttest.com

www.msftconnecttest.com



So it should works for Windows, Apple devices and Android.



What are your clients OS ?



For example we find out that XIAOMI phones do not use standard android URL (they use connect.rom.miui.com) to check if there is a Captive Portal on the network.

I'm sorry, it's look like I came to a conclusion too soon and not testing with other operating system. Earlier I was using CentOS 8.

After done some testing, here are the result with all the devices that I have in my home.

1. Windows 10
Initial connection: redirected to captive portal
Without authentication: not able to browse
Connection duration time out: not able to browse

2. iPad OS 13.7
Initial connection: redirected to captive portal
Without authentication: not able to browse
Connection duration time out: not able to browse

3. CentOS 8
Initial connection: not redirected, manual
Without authentication: not able to browse
Connection duration time out: not able to browse

4. Mi 11.0.6/Android 9 & Realme ColorOS 7/Android 10 & Vivo Funtouch OS_3.1/Android 7.1.2
Initial connection: redirected to captive portal
Without authentication: still able to browse
Connection duration timeout: still able to browse

For CentOS we need to find the address used to detect the captive portal. Once known, it is possible (since version 20.10.1 of KeexyBox) to modify the list of URLs by editing the "cportal_test_domains" param at http://keexybox:8001/config/advanced

It's strange for result 4, without authentication, you should not be able to use KeexyBox DNS...

[momothecat]

Hi Benoit,

Thanks for your response. So, for initial connection, user "must" access to KeexyBox IP address manually from their browser and there's no redirection mechanism.

What I mean in redirection is, for example; a user just enter any url in their browser and then the request redirected to the KeexyBox captive portal for authentication. After he/she authenticated, they can continue to access the internet.

If that function not in current version, maybe the developer can be so kind to add it in the future version.

Thanks

You should have a redirection. But maybe you had to disconnect from network and reconnect at client side to get it working.


Devices are redirected to KeexyBox Captive Portal if the client tries to reach one of these domains after accessing the local network:



connectivitycheck.gstatic.com

clients1.google.com

clients3.google.com

connect.rom.miui.com

captive.apple.com

airport.us

thinkdifferent.us

msftconnecttest.com

www.msftconnecttest.com



So it should works for Windows, Apple devices and Android.



What are your clients OS ?



For example we find out that XIAOMI phones do not use standard android URL (they use connect.rom.miui.com) to check if there is a Captive Portal on the network.

I'm sorry, it's look like I came to a conclusion too soon and not testing with other operating system. Earlier I was using CentOS 8.

After done some testing, here are the result with all the devices that I have in my home.

1. Windows 10
Initial connection: redirected to captive portal
Without authentication: not able to browse
Connection duration time out: not able to browse

2. iPad OS 13.7
Initial connection: redirected to captive portal
Without authentication: not able to browse
Connection duration time out: not able to browse

3. CentOS 8
Initial connection: not redirected, manual
Without authentication: not able to browse
Connection duration time out: not able to browse

4. Mi 11.0.6/Android 9 & Realme ColorOS 7/Android 10 & Vivo Funtouch OS_3.1/Android 7.1.2
Initial connection: redirected to captive portal
Without authentication: still able to browse
Connection duration timeout: still able to browse

For CentOS we need to find the address used to detect the captive portal. Once known, it is possible (since version 20.10.1 of KeexyBox) to modify the list of URLs by editing the "cportal_test_domains" param at http://keexybox:8001/config/advanced

It's strange for result 4, without authentication, you should not be able to use KeexyBox DNS...

I'll try to modify the captive portal config later for CentOS (other Linux OS).

In mean time, I reinstall the keexybox with the version 20.10.1 on the new sdcard and hope if the android devices redirection is fixed, but it's look like still the same. They still able to bypass access without authentication (DNS only mode).

[momothecat]

Hi Benoit,

Thanks for your response. So, for initial connection, user "must" access to KeexyBox IP address manually from their browser and there's no redirection mechanism.

What I mean in redirection is, for example; a user just enter any url in their browser and then the request redirected to the KeexyBox captive portal for authentication. After he/she authenticated, they can continue to access the internet.

If that function not in current version, maybe the developer can be so kind to add it in the future version.

Thanks

You should have a redirection. But maybe you had to disconnect from network and reconnect at client side to get it working.


Devices are redirected to KeexyBox Captive Portal if the client tries to reach one of these domains after accessing the local network:



connectivitycheck.gstatic.com

clients1.google.com

clients3.google.com

connect.rom.miui.com

captive.apple.com

airport.us

thinkdifferent.us

msftconnecttest.com

www.msftconnecttest.com



So it should works for Windows, Apple devices and Android.



What are your clients OS ?



For example we find out that XIAOMI phones do not use standard android URL (they use connect.rom.miui.com) to check if there is a Captive Portal on the network.

I'm sorry, it's look like I came to a conclusion too soon and not testing with other operating system. Earlier I was using CentOS 8.

After done some testing, here are the result with all the devices that I have in my home.

1. Windows 10
Initial connection: redirected to captive portal
Without authentication: not able to browse
Connection duration time out: not able to browse

2. iPad OS 13.7
Initial connection: redirected to captive portal
Without authentication: not able to browse
Connection duration time out: not able to browse

3. CentOS 8
Initial connection: not redirected, manual
Without authentication: not able to browse
Connection duration time out: not able to browse

4. Mi 11.0.6/Android 9 & Realme ColorOS 7/Android 10 & Vivo Funtouch OS_3.1/Android 7.1.2
Initial connection: redirected to captive portal
Without authentication: still able to browse
Connection duration timeout: still able to browse

For CentOS we need to find the address used to detect the captive portal. Once known, it is possible (since version 20.10.1 of KeexyBox) to modify the list of URLs by editing the "cportal_test_domains" param at http://keexybox:8001/config/advanced

It's strange for result 4, without authentication, you should not be able to use KeexyBox DNS...

I'll try to modify the captive portal config later for CentOS (other Linux OS).

In mean time, I reinstall the keexybox with the version 20.10.1 on the new sdcard and hope if the android devices redirection is fixed, but it's look like still the same. They still able to bypass access without authentication (DNS only mode).

[benoit]

Hi Benoit,

Thanks for your response. So, for initial connection, user "must" access to KeexyBox IP address manually from their browser and there's no redirection mechanism.

What I mean in redirection is, for example; a user just enter any url in their browser and then the request redirected to the KeexyBox captive portal for authentication. After he/she authenticated, they can continue to access the internet.

If that function not in current version, maybe the developer can be so kind to add it in the future version.

Thanks

You should have a redirection. But maybe you had to disconnect from network and reconnect at client side to get it working.


Devices are redirected to KeexyBox Captive Portal if the client tries to reach one of these domains after accessing the local network:



connectivitycheck.gstatic.com

clients1.google.com

clients3.google.com

connect.rom.miui.com

captive.apple.com

airport.us

thinkdifferent.us

msftconnecttest.com

www.msftconnecttest.com



So it should works for Windows, Apple devices and Android.



What are your clients OS ?



For example we find out that XIAOMI phones do not use standard android URL (they use connect.rom.miui.com) to check if there is a Captive Portal on the network.

I'm sorry, it's look like I came to a conclusion too soon and not testing with other operating system. Earlier I was using CentOS 8.

After done some testing, here are the result with all the devices that I have in my home.

1. Windows 10
Initial connection: redirected to captive portal
Without authentication: not able to browse
Connection duration time out: not able to browse

2. iPad OS 13.7
Initial connection: redirected to captive portal
Without authentication: not able to browse
Connection duration time out: not able to browse

3. CentOS 8
Initial connection: not redirected, manual
Without authentication: not able to browse
Connection duration time out: not able to browse

4. Mi 11.0.6/Android 9 & Realme ColorOS 7/Android 10 & Vivo Funtouch OS_3.1/Android 7.1.2
Initial connection: redirected to captive portal
Without authentication: still able to browse
Connection duration timeout: still able to browse

For CentOS we need to find the address used to detect the captive portal. Once known, it is possible (since version 20.10.1 of KeexyBox) to modify the list of URLs by editing the "cportal_test_domains" param at http://keexybox:8001/config/advanced

It's strange for result 4, without authentication, you should not be able to use KeexyBox DNS...

I'll try to modify the captive portal config later for CentOS (other Linux OS).

In mean time, I reinstall the keexybox with the version 20.10.1 on the new sdcard and hope if the android devices redirection is fixed, but it's look like still the same. They still able to bypass access without authentication (DNS only mode).

I am able to reproduce the issue on my Android device. It looks to be a DNS over HTTPS (DoH) mechanism (called sometimes Private DNS or Secure DNS) that is implemented by default when DNS queries failed.
On my android I could resolve domain names and browse while KeexyBox was blocking DNS queries and private DNS was off on my device.
For a test, on my Android (Xiaomi) in "Settings -> Connection & share -> Private DNS" I had to set a fake hostname as the private DNS provider to really block DoH feature but by this way it make your device to never use DNS protocol even if DNS queries are allowed by KeexyBox or any available DNS on the network and you are not able to browse. So it is not a solution.
The problem is that the "off" option in "Settings -> Connection & share -> Private DNS" on the Android looks to have no effect to disable DoH.

https://support.google.com/android/answer/9654714

The only workaround I see is to use KeexyBox as gateway and DNS for Android devices, so it can also block HTTPS if user is not authenticated.

[benoit]

Hi Benoit,

Thanks for your response. So, for initial connection, user "must" access to KeexyBox IP address manually from their browser and there's no redirection mechanism.

What I mean in redirection is, for example; a user just enter any url in their browser and then the request redirected to the KeexyBox captive portal for authentication. After he/she authenticated, they can continue to access the internet.

If that function not in current version, maybe the developer can be so kind to add it in the future version.

Thanks

You should have a redirection. But maybe you had to disconnect from network and reconnect at client side to get it working.


Devices are redirected to KeexyBox Captive Portal if the client tries to reach one of these domains after accessing the local network:



connectivitycheck.gstatic.com

clients1.google.com

clients3.google.com

connect.rom.miui.com

captive.apple.com

airport.us

thinkdifferent.us

msftconnecttest.com

www.msftconnecttest.com



So it should works for Windows, Apple devices and Android.



What are your clients OS ?



For example we find out that XIAOMI phones do not use standard android URL (they use connect.rom.miui.com) to check if there is a Captive Portal on the network.

I'm sorry, it's look like I came to a conclusion too soon and not testing with other operating system. Earlier I was using CentOS 8.

After done some testing, here are the result with all the devices that I have in my home.

1. Windows 10
Initial connection: redirected to captive portal
Without authentication: not able to browse
Connection duration time out: not able to browse

2. iPad OS 13.7
Initial connection: redirected to captive portal
Without authentication: not able to browse
Connection duration time out: not able to browse

3. CentOS 8
Initial connection: not redirected, manual
Without authentication: not able to browse
Connection duration time out: not able to browse

4. Mi 11.0.6/Android 9 & Realme ColorOS 7/Android 10 & Vivo Funtouch OS_3.1/Android 7.1.2
Initial connection: redirected to captive portal
Without authentication: still able to browse
Connection duration timeout: still able to browse

For CentOS we need to find the address used to detect the captive portal. Once known, it is possible (since version 20.10.1 of KeexyBox) to modify the list of URLs by editing the "cportal_test_domains" param at http://keexybox:8001/config/advanced

It's strange for result 4, without authentication, you should not be able to use KeexyBox DNS...

I'll try to modify the captive portal config later for CentOS (other Linux OS).

In mean time, I reinstall the keexybox with the version 20.10.1 on the new sdcard and hope if the android devices redirection is fixed, but it's look like still the same. They still able to bypass access without authentication (DNS only mode).

I am able to reproduce the issue on my Android device. It looks to be a DNS over HTTPS (DoH) mechanism (called sometimes Private DNS or Secure DNS) that is implemented by default when DNS queries failed.
On my android I could resolve domain names and browse while KeexyBox was blocking DNS queries and private DNS was off on my device.
For a test, on my Android (Xiaomi) in "Settings -> Connection & share -> Private DNS" I had to set a fake hostname as the private DNS provider to really block DoH feature but by this way it make your device to never use DNS protocol even if DNS queries are allowed by KeexyBox or any available DNS on the network and you are not able to browse. So it is not a solution.
The problem is that the "off" option in "Settings -> Connection & share -> Private DNS" on the Android looks to have no effect to disable DoH.

https://support.google.com/android/answer/9654714

The only workaround I see is to use KeexyBox as gateway and DNS for Android devices, so it can also block HTTPS if user is not authenticated.