Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
| install_22_4_coova [2024/02/08 17:55] – system | install_22_4_coova [2024/02/08 18:21] (current) – system | ||
|---|---|---|---|
| Line 153: | Line 153: | ||
| </ | </ | ||
| - | * Use the following / | + | * Use the following / |
| <code bash> | <code bash> | ||
| HS_WANIF=enp0s3 | HS_WANIF=enp0s3 | ||
| Line 188: | Line 188: | ||
| </ | </ | ||
| - | * Comment the following line out of /// | + | * Comment |
| <code bash> | <code bash> | ||
| - | # Same principal goes for HS_UAMHOMEPAGE. | + | # The same principle applies to HS_UAMHOMEPAGE. |
| # | # | ||
| </ | </ | ||
| Line 216: | Line 216: | ||
| ===== Test it out ===== | ===== Test it out ===== | ||
| - | * Restart CoovaChilli | + | * Restart CoovaChilli |
| <code bash> | <code bash> | ||
| sudo systemctl stop chilli | sudo systemctl stop chilli | ||
| Line 223: | Line 223: | ||
| </ | </ | ||
| - | * Confirm it started | + | * Confirm |
| <code bash> | <code bash> | ||
| sudo systemctl status chilli | sudo systemctl status chilli | ||
| Line 250: | Line 250: | ||
| </ | </ | ||
| - | * Reboot the system and make sure CoovaChilli started | + | * Reboot the system and make sure that CoovaChilli |
| ===== Troubleshooting tips ===== | ===== Troubleshooting tips ===== | ||
| - | * When things does not work is can be a bit tricky | + | * If something |
| - | * It might help if you see the captive portal | + | * It might help if you think of the Captive Portal |
| - | * So then there are a couple of important things to check. | + | * So there are a few important things to check. |
| ==== Are you getting an IP address ==== | ==== Are you getting an IP address ==== | ||
| - | * The captive portal | + | * The Captive Portal |
| * You can check both sides (server and client) | * You can check both sides (server and client) | ||
| - | * To check on the server | + | * To check the server, enter the following command. |
| <code bash> | <code bash> | ||
| sudo chilli_query list | sudo chilli_query list | ||
| Line 267: | Line 267: | ||
| </ | </ | ||
| * You can read more about the **chilli_query** command here: [[https:// | * You can read more about the **chilli_query** command here: [[https:// | ||
| - | * After consulting | + | * After reading |
| * This means that they ' | * This means that they ' | ||
| - | * If you are not redirected to a login page we can try the following procedure which basically comes down to two things | + | * If you are not redirected to a login page, we can try the following procedure, which essentially boils down to two things not working as intended. |
| - | * The routing between the LAN and WAN is not working | + | * The routing between the LAN and the WAN is not working |
| - | * The DNS on the setup is not working | + | * The DNS on the setup is not working |
| - | ==== Forcing the login page to display | + | ==== Forcing the login page to be displayed |
| - | * CoovaChilli has a special URL which will log you out and redirect | + | * CoovaChilli has a special URL that logs you out and redirects |
| * The URL is http:// | * The URL is http:// | ||
| - | * If you do get a login page you can next try to test the routing and the DNS. | + | * If you get a login page, the next thing you can try is to test the routing and DNS. |
| ==== Test the routing | ==== Test the routing | ||
| Line 292: | Line 292: | ||
| 08-00-27-8C-D3-32 10.1.0.2 dnat 157706713900000001 0 08-00-27-8C-D3-32 0/0 0/0 0/0 0/0 0 0 0/0 0/0 - | 08-00-27-8C-D3-32 10.1.0.2 dnat 157706713900000001 0 08-00-27-8C-D3-32 0/0 0/0 0/0 0/0 0 0 0/0 0/0 - | ||
| </ | </ | ||
| - | * On the client you can now try to go to an IP Address | + | * On the client, you can now try to get to an IP address |
| - | * I can now again log this client | + | * I can now log off this client |
| <code bash> | <code bash> | ||
| sudo chilli_query logoff ip 10.1.0.3 | sudo chilli_query logoff ip 10.1.0.3 | ||
| Line 304: | Line 304: | ||
| ==== Test the DNS ==== | ==== Test the DNS ==== | ||
| - | * DNS traffic | + | * DNS traffic |
| - | * In order for the client to magically | + | * In order for the client to magically |
| - | * A common problem is that sometimes the client has their own DNS servers | + | * A common problem is that sometimes the client has specified its own DNS servers and then (depending on the configuration settings of CoovaChilli) |
| - | * After you confirmed that the client does not have any hard defined | + | * Once you have confirmed that the client does not have any fixed DNS servers, you can perform |
| - | * With a ping test you just want to test and confirm that the DNS is working | + | * With a ping test, you only want to test and confirm that the DNS is working |
| - | * You can try and ping any known FQDN and see if the system | + | * You can try to ping any known FQDN and see if the system |
| - | * Here I try to ping www.radiusdesk.com. As you can see the name resolution worked | + | * Here I am trying |
| <code bash> | <code bash> | ||
| ping www.radiusdesk.com | ping www.radiusdesk.com | ||
| Line 320: | Line 320: | ||
| ==== Conclusion | ==== Conclusion | ||
| - | * By using these check points on the captive portal setup, you can now point to a component | + | * Using these checkpoints for the captive portal setup, you can now point to a component |
| * Be it the login page. | * Be it the login page. | ||
| * The routing between WAN and LAN. | * The routing between WAN and LAN. | ||
| * The DNS service. | * The DNS service. | ||