2015-06-08 - Re: [GRASE-Hotspot] Re: Grase nightlyBuilds connection problem

Header Data

From: Sheena Arora <sh***2@gmail.com>
Message Hash: 11c73dc3e1f2bbcc6ada87a6a12c5b9bfda6239249d67d6e06de4ebd39c51b96
Message ID: <ead85fbe-381c-4809-92f0-0b2aa28b23b2@grasehotspot.org>
Reply To: <CAESLx0LbavLLvYM9hgBr_hhXAFFaPP0QDXMA2ES1zdN-TsBfLw@mail.gmail.com>
UTC Datetime: 2015-06-08 22:40:34 UTC
Raw Date: Mon, 08 Jun 2015 22:40:34 -0700

Raw message 

Hey Tim,

I've attached the requested files.

CLIENT MACHINES
=================================
*grase_client_ubuntu1_host.txt* : These logs are collected from an ubuntu  
grase-client machine running on ubuntu desktop 14.04.1 LTS and  this is 
directly running on hardware (i.e. no VM is involved). This is a different 
client from the earlier one.

*grase_ubuntu_client_vm.txt :* These logs are collected from a vm running 
ubuntu desktop on host machine operating system windows 8. 

===================================

Thanks,
Sheena



On Tuesday, June 9, 2015 at 2:15:29 AM UTC+5:30, timwhite88 wrote:
>
> Hmmm. The Grase server is running Systemd. That's not something I've had 
> time to test yet. I'll try and do some tests later this week.
>
> On the clients, can you do cat /etc/dnsmasq.d/network-manager, and cat 
> /etc/resolv.conf before and after it's working?
> Also try "dig @10.1.0.1 google.com" when it's not working on a client, 
> and show me the results.
>
> Regards
>
> Tim
>
>
>
> On Sat, Jun 6, 2015 at 10:55 PM, Sheena Arora <sh***.@gmail.com 
> <javascript:>> wrote:
>
>> Hi Tim,
>>
>> Thanks for looking into it even on weekend. Really appreciate it.
>>
>> PFA 3 files.
>>
>> CLIENT  MACHINE LOGS
>> =========================
>> *grase_client_ubuntu1_host.txt* : These logs are collected from an 
>> ubuntu  grase-client machine running on ubuntu desktop 14.04.1 LTS and  
>> this directly running on hardware (i.e. no VM is involved).
>>
>> *grase_ubuntu_client_vm.txt :* These logs are collected from a vm 
>> running ubuntu desktop on host machine operating system windows 8. 
>> ===============================
>>
>> GRASE SERVER LOGS
>> ====================
>>
>> *logs_grase_bfr_after_dns_change.docx* : these logs are collected from 
>> grase server . Again no virtual machine is involved here.
>>
>> Just to summarize another observation(in case I have failed to mention it 
>> before) 
>> 1.After changing dns servers 
>> 2. Restarting chilli
>> 3. Restarting dnsmasq 
>>
>> tunn0 disappears and it only reappears when ADMIN PANEL -> NETWORK 
>> SETTINGS shows an alert "settings match running config" 
>> (Once we have restarted the services from console, this alert comes up 
>> after about 5 minutes).
>>
>> Regards
>> Sheena
>>
>>
>> On Saturday, June 6, 2015 at 4:00:31 PM UTC+5:30, timwhite88 wrote:
>>>
>>> Hi Sheena
>>>
>>> Interesting. Do you have linux clients you can do some tests with?
>>>
>>> Can you check what the DNS is that the clients receive via DHCP when 
>>> things aren't working? They should all be pointing at the Grase server 
>>> (10.1.0.1).
>>> If you run "dig google.com" on the client, what is the result (full 
>>> result, as it shows which server it talked to etc)
>>> What is the contents of /etc/dnsmasq.d/01-grasehotspot before and after 
>>> things work.
>>> While things aren't working, is dnsmasq running (do pgrep dnsmasq)
>>>
>>> While it's not working, instead of changing DNS settings, try running 
>>> (as root) /usr/share/grase/scripts/update_grase_networksettings.sh and see 
>>> if it starts working.
>>>
>>> Regards
>>>
>>> Tim
>>>
>>> On Sat, Jun 6, 2015 at 5:27 PM, Sheena Arora <sh***.@gmail.com> 
>>> wrote:
>>>
>>>>
>>>> Hi Tim,
>>>>
>>>> Thanks for your support.
>>>> I followed the link that you have given in previous post and made 
>>>> changes accordingly. Below is the output of my* 
>>>> /etc/network/interfaces* file :
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *auto loiface lo inet loopback#iface eth0 inet manualauto eth1iface 
>>>> eth1 inet static    address 192.168.1.75    netmask 255.255.255.0    
>>>> gateway 192.168.1.1auto eth0iface eth0 inet manual*
>>>>
>>>> Here , eth0 is LAN interface and eth1 is WAN interface.I have set eth1 
>>>> as static and assign *192.168.1.75* to it.
>>>>
>>>> I have also attached the result of *ifconfig* and running services 
>>>> status page.
>>>>
>>>> The current grase status is as
>>>> ===============================
>>>> *Status* *Device Information* *Model Name**GRASE* *Host Name**logitech* *HTTP 
>>>> Server**Apache/2.4.10 (Ubuntu) via apache2handler* *System Up-Time**0 
>>>> days, 0 hours, 13 minutes * *Current Server Time**Sat, 06 Jun 2015 
>>>> 12:48:15 +0530*
>>>> *Hardware Version**Intel(R) Pentium(R) CPU G2020 @ 2.90GHz 
>>>> @2891.957MHz* *Software Version**3.7.7.11.403.g6a46f86* *Home URL**GRASE 
>>>> (Purewhite) <http://grasehotspot.org>* *LAN* *IP Address*
>>>>  *Subnet Mask*
>>>>  *MAC Address*
>>>>  *Network Interface*
>>>>  *WAN* *IP Address**192.168.1.75 * *Subnet Mask**255.255.255.0* 
>>>> *Gateway**192.168.1.1* *DNS 1**127.0.0.1* *DNS 2*
>>>>  *MAC Address**00:E0:4C:53:44:58 * *Network Interface**eth1*
>>>> =================================================
>>>>
>>>> The behaviour is still same. If I click on "save settings" in *network 
>>>> settings* section without changing anything and immediately after this 
>>>> , I restart the chilli and dnsmasq services, then It starts working after 
>>>> 5-7 mins.
>>>>
>>>> It keeps on working fine that is no login issues , no internet 
>>>> disconnectivity and all built-in features are working as 
>>>> expected(correctly) once we have brought it up by changing the dns servers 
>>>> and restrating chilli and dnsmasq services.
>>>> However , if *I reboot the system* , grase loads, chilli and dnsmasq 
>>>> is active, tunnels are  created(in due time ranging from 2-6 minutes), the 
>>>> network from AP is available on mobile devices but *it never asks for 
>>>> login credentials i.e. it dosen't loads the hotspot client login page*.
>>>>
>>>> Please advise.
>>>>
>>>>
>>>> On Saturday, June 6, 2015 at 6:26:02 AM UTC+5:30, timwhite88 wrote:
>>>>>
>>>>> Looking at what you have sent, I wonder if Network Manager is at 
>>>>> fault, as you haven't disabled it.
>>>>>
>>>>> Have a look at 
>>>>> https://github.com/GraseHotspot/grase-www-portal/wiki/Network-Interfaces 
>>>>> for some new instructions on setting up in a way that prevents Network 
>>>>> Manager causing problems.
>>>>>
>>>>> Regards
>>>>>
>>>>> Tim
>>>>>
>>>>> On Fri, Jun 5, 2015 at 5:19 PM, Sheena Arora <sh***.@gmail.com> 
>>>>> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> This is the issue I'm currently facing-
>>>>>>
>>>>>>
>>>>>>    - When I turn on my system, there is just one tunnel present but 
>>>>>>    after some 2-3 minutes, the second tunnel comes up
>>>>>>    - Then, I try to connect my phone to the network, the phone 
>>>>>>    network shows that it is connected to the grase network but the "*Sign 
>>>>>>    in to the WiFi-Network*" does not show up even after 10 mins. At 
>>>>>>    this point, the DNS Servers are 208.67.220.123 and 208.67.222.123
>>>>>>    - I then change the DNS server values to 8.8.4.4 and 8.8.8.8. 
>>>>>>    Upon restarting the services chilli and dnsmaq: *sudo service 
>>>>>>    chilli restart**           sudo service dnsmasq retsart*
>>>>>>    - At this point, the tunnel with IP address 10.1.0.1 disappears 
>>>>>>    and reappears after 5 mins (probably when the cron runs)
>>>>>>    - Now when I try to connect my phone to this network the "*Sign 
>>>>>>    in to the WiFi-Network*" shows and sometimes I am able to log 
>>>>>>    into the network and at other times, it shows a server error (PFA image).
>>>>>>    - Now if I reboot my system, the DNS server values are 8.8.4.4 
>>>>>>    and 8.8.8.8 and my phone connects to the network but "*Sign in to 
>>>>>>    the WiFi-Network*" does not come up. If I try accessing 
>>>>>>    www.google.com in the browser the page never loads.
>>>>>>    - At this time, if I change the DNS server values to 
>>>>>>    208.67.220.123 and 208.67.222.123, after restarting chilli and dnsmasq, 
>>>>>>    after 5 mins, I am able to access the network.
>>>>>>
>>>>>> I have to change the DNS server values after every reboot to get it 
>>>>>> working....where am I going wrong?
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wednesday, June 3, 2015 at 12:57:17 PM UTC+5:30, shaveta puri 
>>>>>> wrote:
>>>>>>
>>>>>>> Hi 
>>>>>>>  
>>>>>>> I have been testing Grase NightlyBuilds 1.5 for the past few days on 
>>>>>>> ubuntu 15.04 (desktop version) .
>>>>>>>
>>>>>>> Initially , it works like a charm. But suddenly after some time 
>>>>>>> nobody is able to access the internet through it.It shows full hotspot 
>>>>>>> connection and allows users to connect to it.
>>>>>>> It starts and stops randomly, at its own will. I have also tried its 
>>>>>>> installation using virtualbox(ubuntu server 14.04), but the behavior 
>>>>>>> remains the same.
>>>>>>>
>>>>>>> Could you please help me with this. Where am I going wrong?
>>>>>>>
>>>>>>>  -- 
>>>>>> This mailing list is for the Grase Hotspot Project 
>>>>>> http://grasehotspot.org
>>>>>> --- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "Grase Hotspot" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>> send an email to gr***.@grasehotspot.org.
>>>>>> To post to this group, send email to gr***.@grasehotspot.org.
>>>>>> Visit this group at 
>>>>>> http://groups.google.com/a/grasehotspot.org/group/grase-hotspot/.
>>>>>> To view this discussion on the web visit 
>>>>>> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/9d536ba9-304b-46d8-acfe-1c5a855ac221%40grasehotspot.org 
>>>>>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/9d536ba9-304b-46d8-acfe-1c5a855ac221%40grasehotspot.org?utm_medium=email&utm_source=footer>
>>>>>> .
>>>>>>
>>>>>
>>>>>  -- 
>>>> This mailing list is for the Grase Hotspot Project 
>>>> http://grasehotspot.org
>>>> --- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "Grase Hotspot" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to gr***.@grasehotspot.org.
>>>> To post to this group, send email to gr***.@grasehotspot.org.
>>>> Visit this group at 
>>>> http://groups.google.com/a/grasehotspot.org/group/grase-hotspot/.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/4aac2ee3-9fab-4594-88d3-1fcf1987ee4a%40grasehotspot.org 
>>>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/4aac2ee3-9fab-4594-88d3-1fcf1987ee4a%40grasehotspot.org?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>
>>>  -- 
>> This mailing list is for the Grase Hotspot Project 
>> http://grasehotspot.org
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Grase Hotspot" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to gr***.@grasehotspot.org <javascript:>.
>> To post to this group, send email to gr***.@grasehotspot.org 
>> <javascript:>.
>> Visit this group at 
>> http://groups.google.com/a/grasehotspot.org/group/grase-hotspot/.
>> To view this discussion on the web visit 
>> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/68fd5429-41bf-4f0d-9db8-45646a053e54%40grasehotspot.org 
>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/68fd5429-41bf-4f0d-9db8-45646a053e54%40grasehotspot.org?utm_medium=email&utm_source=footer>
>> .
>>
>
>

Thread