search

pihomeserver / Kupiki-Hotspot-Script

Create automatically a full Wifi Hotspot on Raspberry Pi including a Captive Portal
Other
300 stars 119 forks source link

How can I allow domains for unauthenticated users? #62

Open andreaskasper opened 7 years ago

andreaskasper commented 7 years ago

Hi, I wanna set my domain example.com to be accessible without having a user/password-Account. Is it possible to whitelist some IPs/Domains in freeradius? Or allow some external URLs on the login-splash-screen like

<img src="//otherdomain/importantimage.jpg"/>

Thanks for your answer :-) andreas

pihomeserver commented 7 years ago

not sure how to do that. may e by adding a dedicated rule in the up script of the interface to always allow the destination without a credentials check before establishing the connexio

takatar commented 6 years ago

Bonsoir, Voilà ce qui a fonctionné pour moi:

Teko4444 commented 5 years ago

Hi, I wanna set my domain example.com to be accessible without having a user/password-Account. Is it possible to whitelist some IPs/Domains in freeradius? Or allow some external URLs on the login-splash-screen like

<img src="//otherdomain/importantimage.jpg"/>

Thanks for your answer :-) andreas

same problem here and when i try @takatar solution some website like google work but others not working !! any ideas ??

pihomeserver commented 5 years ago

@Teko4444 are you sure that you added all domains and there is no redirection ? Not an issue HTTP vs HTTPS ?

Teko4444 commented 5 years ago

@pihomeserver it's not about the redirection , i want user to access my website firstly without authentication , if he want to use internet freely he should authenticate, i add .google.com to HS_UAMDOMAINS on /chilli/default its works fine but if i add my domain like .mydomain.com its not working i trying both http://mydomain.com and https://mydomain.com but its not show me my domain home page ! can you tell me what is the problem ?

pihomeserver commented 5 years ago

Your domain is available from the Pi, did you look at logs, starting coova in debug mode and look at the trace. Also you can analyse the traffic on tun0 to see if request are rejected or are dropped

Teko4444 commented 5 years ago

ther is no directory /var/log/pihotspot.log !! but every things works fine ! :D oky i will try coova in debug mode

Teko4444 commented 5 years ago

@pihomeserver the request are DROP any suggestion ?

pihomeserver commented 5 years ago

Can you try to change the order in the parameter to see if it's not related to the parsing or something else ? I'm testing a new release and will check that after

Teko4444 commented 5 years ago

@pihomeserver i have delete all allowed domains except my domain then google by order but it still not working !! can i do any thing till yr new release ?

thanks for help man

pihomeserver commented 5 years ago

Do you stop start the service each time ? I don't know how coova manage the domains but maybe some iptables rules ? Then you need to stop start to update them

Teko4444 commented 5 years ago

@pihomeserver i have made it just i put the domain without the . at first of it on /etc/chilli/default so it will be like (.google.com , mydomain.com) that's all !!

pihomeserver commented 5 years ago

So now it works without the dot ?

Teko4444 commented 5 years ago

@pihomeserver yes without the dot its works for the domain only not for subdomains but it's fine for me.

pihomeserver commented 5 years ago

Also :

All of those domains appear to be HTTPS domains with no HTTP counterparts. CoovaChilli can't inspect the packet headers to determine the end destination and determine if the packets should be forwarded because the packets are encrypted, so they're dropped. Redirection / captive portal will never work with HTTPS-secured traffic - not being able to figure out where the packets are going is kind of the point of this protocol.

Source : https://www.brightonchilli.org.uk/pipermail/coovachilli/2017-June/000233.html