This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| getting_started:18_install_ubuntu_coovachilli [2019/12/23 05:05] – [Test the routing] admin | getting_started:18_install_ubuntu_coovachilli [2019/12/23 12:27] (current) – [Installing CoovaChilli] admin | ||
|---|---|---|---|
| Line 25: | Line 25: | ||
| <code bash> | <code bash> | ||
| + | # If you downloaded with wget | ||
| tar -xzvf 1.5.tar.gz | tar -xzvf 1.5.tar.gz | ||
| + | # If you downloaded with the browser | ||
| + | tar -xzvf coova-chilli-1.5.tar.gz | ||
| cd coova-chilli-1.5/ | cd coova-chilli-1.5/ | ||
| Line 302: | Line 305: | ||
| * DNS traffic has to flow regardless of a client being authurised (pass) or not (dnat). | * DNS traffic has to flow regardless of a client being authurised (pass) or not (dnat). | ||
| * In order for the client to magically pop up the login page, DNS has also to work correct. | * In order for the client to magically pop up the login page, DNS has also to work correct. | ||
| - | * A common problem is that sometimes the client has their own DNS servers specified and then (depending on the configuration settings of CoovaChilli it might not allow the DNS traffic to those server through. (Leaving things broken). | + | * A common problem is that sometimes the client has their own DNS servers specified and then (depending on the configuration settings of CoovaChilli) it might not allow the DNS traffic to those server through. (Leaving things broken). |
| * After you confirmed that the client does not have any hard defined DNS servers you can try a ping test. | * After you confirmed that the client does not have any hard defined DNS servers you can try a ping test. | ||
| * With a ping test you just want to test and confirm that the DNS is working correct on the client. | * With a ping test you just want to test and confirm that the DNS is working correct on the client. | ||