2016-05-12 - Re: UAM redirection

Header Data

From: José Borges <jo***s@algardata.pt>
Message Hash: 094ab1e835db998c9a08bc502d8d88f562925d1c6a4ea2aaadf68fbbad86ebc4
Message ID: <1f09a37e-45b1-47e4-a3dc-69dbcb114d2b@grasehotspot.org>
Reply To: <64944ebe-b61b-4930-8d2e-fbdf7b7ee8a3@grasehotspot.org>
UTC Datetime: 2016-05-12 07:14:42 UTC
Raw Date: Thu, 12 May 2016 07:14:42 -0700

Raw message 

Unfortunately this does bother me and i have been searching for an answer 
for months... because mobile clients fire up they wifi, connect to the open 
wifi hotspot and launch facebook... and they dont understand they have to 
go to http://10.1.0.1 and do a login... i keep getting asked why doesnt it 
show the UAM login when i connect to the wifi as other solutions do. I did 
a fresh install of grase hotspot and it happens the same thing, so it isn't 
anything i changed by myself. 

Everyone has this behaviour or could it be a hardware (hotspot server) 
issue?

quinta-feira, 12 de Maio de 2016 às 12:30:05 UTC+1, Emmanuel Nyachoke 
escreveu:
>
> I think I noticed this even with windows clients but it seemed irregular 
> in my case the very first time I connected the client I got the message 
> 'additional login my be required' but did not see the message subsequently. 
> This does not bother me  much but other hotspot management systems do this 
> consistently. 
>
> On Wednesday, 11 May 2016 19:38:40 UTC+3, José Borges wrote:
>>
>>
>> How on earth i make the browser open the UAM upon the user connecting to 
>> the wireless network?
>>
>>    1. User turns on WIFI on the smartphone (android/ios)
>>    2. User selects correct WIFI SSID
>>    3. User taps LOGIN to connect to WIFI
>>    4. ... Chilli/FreeRadius/Chilli do their stuff ...
>>    5. Browser open with the UAM url in it
>>    6. User can then type his username/password to access internet.
>>
>> I'm only missing step 5... The browser wont open... :(
>>
>>
>> I use this HS_REDIRDNSREQ=on on /etc/chilli/config, but sometimes it 
>> works sometimes it doesnt.
>>
>>
>> Any advise?
>>
>>
>>
>>
>> Here's my /etc/chilli/config
>>
>> GRASE_VARS=$(cat /etc/dnsmasq.d/01-grasehotspot | grep #)
>> HS_NETWORK=$(echo "$GRASE_VARS" |grep chilli_network|awk '{print $2}');
>> HS_NETMASK=$(echo "$GRASE_VARS" |grep chilli_netmask|awk '{print $2}');
>> HS_UAMLISTEN=$(echo "$GRASE_VARS" |grep chilli_lanip|awk '{print $2}');
>> HS_WANIF=$(echo "$GRASE_VARS" |grep chilli_wanif|awk '{print $2}');
>> HS_LANIF=$(echo "$GRASE_VARS" |grep chilli_lanif|awk '{print $2}');
>> HS_REDIRDNSREQ=on
>> HS_WANIF=${HS_WANIF:-eth0}
>> HS_LANIF=${HS_LANIF:-eth1}
>> HS_NETWORK=${HS_NETWORK:-10.1.0.0}
>> HS_NETMASK=${HS_NETMASK:-255.255.255.0}
>> HS_UAMLISTEN=${HS_UAMLISTEN:-10.1.0.1}
>> HS_UAMPORT=3990
>> HS_UAMUIPORT=4990
>> HS_DNS_DOMAIN=hotspot.lan
>> HS_DNS1=$HS_UAMLISTEN
>> HS_DNS2=$HS_UAMLISTEN
>> HS_MAXCLIENTS=65000
>> HS_NASID=nas01
>> HS_RADIUS=localhost
>> HS_RADIUS2=localhost
>> HS_UAMALLOW=$HS_UAMLISTEN
>> HS_RADSECRET=SuperSpecialSecret 
>> HS_UAMALIASNAME=grase
>> HS_UAMDOMAINS=".google-analytics.com,.googletagmanager.com,.gstatic.com,.
>> googleapis.com"
>> HS_UAMSERVER=$HS_UAMLISTEN
>> HS_UAMFORMAT=http://\$HS_UAMSERVER/grase/uam/hotspot
>> HS_UAMHOMEPAGE=http://\$HS_UAMSERVER/grase/uam/hotspot
>> HS_MACAUTH=on
>>
>> HS_TCP_PORTS="80 443 22 2812 53 3990 3128"
>> HS_MODE=hotspot
>> HS_TYPE=chillispot
>> HS_ADMUSR=CoovaChilli
>> HS_ADMPWD=radmin
>> HS_DEFINTERIMINTERVAL=150
>> HS_WWWDIR=/etc/chilli/www
>> HS_WWWBIN=/etc/chilli/wwwsh
>> HS_PROVIDER=Grase
>> HS_PROVIDER_LINK=http://hotspot.purewhite.id.au/
>> HS_LOC_NAME="GRASE HotSpot"
>>
>

Thread