2014-10-04 - Re: [GRASE-Hotspot] 12.04 LTS and 14.04 LTS (nightly) DHCP doesn’t work

Header Data

From: bartosz <ba***z@miklaszewski.com>
Message Hash: 76040986dbe898b24a54c402a6d3a749d1b3c0205c2555e0f1703a0b997baee3
Message ID: <a3e0cccf-0755-4a7d-b2c9-3b2a4ec0e4c3@grasehotspot.org>
Reply To: <CAESLx0JQerX=ne7cPOBKfoqmQX7VuPm71NDr+MYw5DD1K9x8iw@mail.gmail.com>
UTC Datetime: 2014-10-04 13:40:53 UTC
Raw Date: Sat, 04 Oct 2014 13:40:53 -0700

Raw message 

Hi Tim, 

i dont think its driver issue, as it works perfectly fine with grase 12.04, 
and 14.04 (as a network card)

let me do some backups, i just setup 12.04 grase, and already modify some 
files css and html so i will copy all, install 14.04 again and get back to 
you




On Saturday, 4 October 2014 21:27:04 UTC+1, timwhite88 wrote:
>
> Hi Bart
>
> I'd love to try and help you get the nightly working. While it's a 
> "nightly" it's actually pretty stable. The reason it's not the latest 
> stable release yet is partially the lack of an upgrade path.
>
> It sounds like you keep reinstalling. This actually makes it hard to work 
> out what your issue is as we can't get you to run much diagnostics. It 
> sounds like you get it all setup but dhcp doesn't work for long? This could 
> be a driver issue with your USB network card. Maybe provide some more 
> details of the hardware.
>
> Tim
> On Oct 5, 2014 2:03 AM, "bartosz" <ba***.@miklaszewski.com <javascript:>> 
> wrote:
>
>> Hi, try again but no joy, i just moving back to 12.04, will try again 
>> when nightly became stable
>>
>> many thanks for all help
>>
>>
>>  
>>
>> On Friday, 3 October 2014 18:25:15 UTC+1, bartosz wrote:
>>>
>>> ok, will try to reinstall it from beginning, as i was messing around, 
>>> and it worked for a moment and after reboot stopped... will get back to you 
>>> tonight 
>>>
>>>
>>>
>>> many thanks for support.
>>>
>>>
>>>
>>> On Thursday, 2 October 2014 01:24:32 UTC+1, timwhite88 wrote:
>>>>
>>>> Hi Bart
>>>>
>>>> This is correct. 10.1.0.1 should be on one of the tun interfaces, not 
>>>> eth1. eth1 is put into a special mode that Coova Chilli handles, and so you 
>>>> only see the other side, tun0.
>>>>
>>>> This should be working with LAN connections on eth1 (via Coova Chilli)
>>>>
>>>> Tim
>>>>
>>>> On Thu, Oct 2, 2014 at 2:50 AM, bartosz <ba***.@miklaszewski.com> 
>>>> wrote:
>>>>
>>>>> Hi Tim, so I reinstalled 14.04, then changed apt to nightly, change 
>>>>> settings in interfaces to eth1 manual
>>>>> even changed interface, as my wan is em1 and lan is eth0, ive changed 
>>>>> it to eth1, but this does not make any difference
>>>>>
>>>>> so logged in to /grase/radmin/ from wan side interfaces and in network 
>>>>> setting section looks good em1=wan and eth1=LAN, but ive saved them 
>>>>> anyway... as you said
>>>>>
>>>>> what ive noticed is, when run ifconfig... it assign 10.1.0.1 to  tun0 
>>>>> instead of eth1
>>>>>
>>>>> any idea how to force grase to use LAN eth1 ?
>>>>>
>>>>> bart@harrys:~$ ifconfig 
>>>>> em1       Link encap:Ethernet  HWaddr c0:3f:d5:6a:09:1e  
>>>>>           inet addr:192.168.7.13  Bcast:192.168.7.255 
>>>>>  Mask:255.255.255.0
>>>>>           inet6 addr: fe80::c23f:d5ff:fe6a:91e/64 Scope:Link
>>>>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>>>           RX packets:308 errors:0 dropped:0 overruns:0 frame:0
>>>>>           TX packets:315 errors:0 dropped:0 overruns:0 carrier:0
>>>>>           collisions:0 txqueuelen:1000 
>>>>>           RX bytes:37517 (37.5 KB)  TX bytes:33434 (33.4 KB)
>>>>>           Interrupt:20 Memory:f7c00000-f7c20000 
>>>>>
>>>>> eth1      Link encap:Ethernet  HWaddr 00:e0:4c:36:00:8c  
>>>>>           inet6 addr: fe80::2e0:4cff:fe36:8c/64 Scope:Link
>>>>>           UP BROADCAST RUNNING PROMISC  MTU:1500  Metric:1
>>>>>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>>>>           TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
>>>>>           collisions:0 txqueuelen:1000 
>>>>>           RX bytes:0 (0.0 B)  TX bytes:648 (648.0 B)
>>>>>
>>>>> lo        Link encap:Local Loopback  
>>>>>           inet addr:127.0.0.1  Mask:255.0.0.0
>>>>>           inet6 addr: ::1/128 Scope:Host
>>>>>           UP LOOPBACK RUNNING  MTU:65536  Metric:1
>>>>>           RX packets:121 errors:0 dropped:0 overruns:0 frame:0
>>>>>           TX packets:121 errors:0 dropped:0 overruns:0 carrier:0
>>>>>           collisions:0 txqueuelen:0 
>>>>>           RX bytes:26613 (26.6 KB)  TX bytes:26613 (26.6 KB)
>>>>>
>>>>> tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 
>>>>>  
>>>>>           inet addr:10.1.0.1  P-t-P:10.1.0.1  Mask:255.255.255.0
>>>>>           UP POINTOPOINT RUNNING  MTU:1500  Metric:1
>>>>>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>>>>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>>>>           collisions:0 txqueuelen:100 
>>>>>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>>>>>
>>>>> tun1      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 
>>>>>  
>>>>>           inet addr:10.64.63.178  P-t-P:10.64.62.1 
>>>>>  Mask:255.255.255.255
>>>>>           UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
>>>>>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>>>>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>>>>           collisions:0 txqueuelen:100 
>>>>>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>>>>>
>>>>> bart@harrys:~$ 
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Saturday, 27 September 2014 07:07:43 UTC+1, timwhite88 wrote:
>>>>>>
>>>>>> Hi Bartosz
>>>>>>
>>>>>> Firstly, changing things in /etc/chilli/config will break things. It 
>>>>>> sounds like your interface name is different to the interface names Grase 
>>>>>> is expecting, so it doesn't default to it. Once you have the web interface 
>>>>>> accessible, please go to the network settings page, and select the correct 
>>>>>> interfaces and hit save. There may be a slight bug, so even if it appears 
>>>>>> correct initially, please hit save anyway.
>>>>>>
>>>>>> What changes did you make to /etc/freeradius/radiusd.conf?? Nothing 
>>>>>> in there should have affected DHCP.
>>>>>>
>>>>>> Tim
>>>>>>
>>>>>> On Sat, Sep 27, 2014 at 6:14 AM, bartosz <ba***.@miklaszewski.com> 
>>>>>> wrote:
>>>>>>
>>>>>>> Hi, I am having this problem with DHCP, basically, when installed 
>>>>>>> grase, for some reason chilli couldn't find my LAN card, so i had to change 
>>>>>>> settings manually in /etc/chilli/config, and then it worked, i could login 
>>>>>>> to localhost/grase/radmin
>>>>>>>
>>>>>>> problem i have now, (both 12.04 LTS and 14.04 LTS nightly - sounds 
>>>>>>> that its related to hardware) that DHCP is not assigning ips's from LAN 
>>>>>>> side, can someone help me with settings?, where can i find settings for 
>>>>>>> grase DHCP? i believe grase, choose wrong interface (like with chilli), so 
>>>>>>> I hope if I set it up manually it will work.
>>>>>>>
>>>>>>> many thanks
>>>>>>>
>>>>>>> Bartosz
>>>>>>>
>>>>>>> -- 
>>>>>>> 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/gra
>>>>>>> sehotspot.org/group/grase-hotspot/.
>>>>>>> To view this discussion on the web visit 
>>>>>>> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-
>>>>>>> hotspot/b4a89e4b-44d3-461c-8e5c-d205e4e99af6%40grasehotspot.org 
>>>>>>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/b4a89e4b-44d3-461c-8e5c-d205e4e99af6%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/978edc39-769a-
>>>>> 4941-97e4-0a0565f814ed%40grasehotspot.org 
>>>>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/978edc39-769a-4941-97e4-0a0565f814ed%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/6fd134b9-1aa6-4cb5-8894-2d9440893786%40grasehotspot.org 
>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/6fd134b9-1aa6-4cb5-8894-2d9440893786%40grasehotspot.org?utm_medium=email&utm_source=footer>
>> .
>>
>

Thread