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: 9d2d630853b0c10290a165adb4ec3a9f500ef4cf0d6f9ad018504e6792e42960
Message ID: <6fd134b9-1aa6-4cb5-8894-2d9440893786@grasehotspot.org>
Reply To: <8de9e32a-4c03-4fef-a1da-dd8067b708f3@grasehotspot.org>
UTC Datetime: 2014-10-04 09:03:40 UTC
Raw Date: Sat, 04 Oct 2014 09:03:40 -0700

Raw message 

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/
>>>>> grasehotspot.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>
>>> .
>>>
>>
>>

Thread