2016-09-15 - Re: [GRASE-Hotspot] Ip address configuration

Header Data

From: emre erdoğan <po***e@gmail.com>
Message Hash: a9b484476cd2c72aacf2d3ea7d8e04531817b35c388d7644b4d933269d3f0a3a
Message ID: <CADDedMEcqw311N40LhfTvZ4qwiqpFkttsZ25qBXY4n=d=K_mAA@mail.gmail.com>
Reply To: <8f4b0392-8a6b-4e53-a990-f8659269beff@grasehotspot.org>
UTC Datetime: 2016-09-15 04:37:30 UTC
Raw Date: Thu, 15 Sep 2016 14:37:30 +0300

Raw message 

If you are facing the same problem like me, you shouldn't do anything with
the dhcp.

Raspberry Pi's onboard ethernet should be used as WAN, it must be connected
to modem. It is input. Static or dynamic IP addressescan be used, no matter.

USB external ethernet adapter should be used for LAN, it must be connected
to the access point. It is output. Hotspot users are using USB ethernet to
connect the Internet. You shouldn't give any ip address or change
anysetting for this device. It is managed by Grase automatically.

Another subject is using correct USB device for raspberry. Cheap devices
are not accepted and there is a list of devices :
http://elinux.org/RPi_USB_Ethernet_adapters
I am using TP-Link UE300 and there is no speed / performance problem with
it.

The only problem for raspberry is to redirect to the login page. I made a
cron job to restart dnsmasq service for every 10 minutes.

Have a nice try..


2016-09-15 14:23 GMT+03:00 Rishabbh A Dua <du***h@gmail.com>:

> sure will check it over internet and get back with results
>
> On Thursday, 15 September 2016 16:52:10 UTC+5:30, timwhite88 wrote:
>>
>> You shouldn't need to disable dhcpcd on the WAN, only on the LAN. There
>> is a config option for that, to enable it only on certain interfaces, I
>> just don't know it off the top of my head.
>>
>> Tim
>>
>> On Thu, Sep 15, 2016 at 9:19 PM, Rishabbh A Dua <du***.@gmail.com>
>> wrote:
>>
>>> ok i will assign static ip address on wan (internet) interface and will
>>> disable dhcpcd and will get back with the results.
>>>
>>> Regards
>>>
>>> Rishabbh
>>>
>>> On Thursday, 15 September 2016 16:46:48 UTC+5:30, timwhite88 wrote:
>>>>
>>>> You'll need to make sure that dhcpcd is doing nothing on that
>>>> interface. It's possible it's doing IPv6 for the clients, which will
>>>> confuse them.
>>>>
>>>> Tim
>>>>
>>>> On Thu, Sep 15, 2016 at 9:04 PM, Rishabbh A Dua <du***.@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi Tim, Emre
>>>>>
>>>>> My perception was since dhcpcd is running on eth1 ( usb ethernet port
>>>>> which is connected to access point), it was getting ipv4ll address.
>>>>> So in order to disable ipv4ll address on this interface, i modified
>>>>> /etc/dhcpcd.conf file and added noipv4ll at the end of file and it worked
>>>>> (ie no ipv4ll address on eth1 in case dhcp server is not found).
>>>>>
>>>>> However, when i connect some device with access point, it is still
>>>>> stuck at obtaining IP address.
>>>>>
>>>>> Any thoughts/ pointers on this?
>>>>>
>>>>> Thanks
>>>>> Rishabbh
>>>>>
>>>>>
>>>>> On Thursday, 15 September 2016 12:50:01 UTC+5:30, timwhite88 wrote:
>>>>>>
>>>>>> Please collect support information as described at
>>>>>> https://grasehotspot.org/support/collecting-support-information/
>>>>>>
>>>>>> It's hard to know what your setup is from that information, what is
>>>>>> WAN and LAN. You also don't appear to have a network interface set to
>>>>>> manual (see https://grasehotspot.org/documentation/hardware-setup/)
>>>>>> for Coova Chilli to use.
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> Tim
>>>>>>
>>>>>>
>>>>>> On Thu, Sep 15, 2016 at 3:55 PM, Rachitta A Dua <ra***.@gmail.com
>>>>>> > wrote:
>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> I have installed grase on a Raspberry Pi. The moment I installed it,
>>>>>>> it worked fine. Even worked properly after an immediate reboot. However,
>>>>>>> when I started the device the following day, it wasn't working. The issue
>>>>>>> is that I cannot connect to the access point. If i try to connect my mobile
>>>>>>> to the access point, it just shows connecting but never connects.
>>>>>>>
>>>>>>>
>>>>>>> This is the result of ifconfig
>>>>>>>
>>>>>>> eth0      Link encap:Ethernet  HWaddr b8:27:eb:38:08:33
>>>>>>>           inet addr:192.168.1.8  Bcast:192.168.1.255
>>>>>>>  Mask:255.255.255.0
>>>>>>>           inet6 addr: fe80::a362:20f7:2ad9:ced1/64 Scope:Link
>>>>>>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>>>>>           RX packets:917 errors:0 dropped:0 overruns:0 frame:0
>>>>>>>           TX packets:519 errors:0 dropped:0 overruns:0 carrier:0
>>>>>>>           collisions:0 txqueuelen:1000
>>>>>>>           RX bytes:82599 (80.6 KiB)  TX bytes:86937 (84.8 KiB)
>>>>>>>
>>>>>>> eth1      Link encap:Ethernet  HWaddr 00:e0:4c:53:44:58
>>>>>>>           inet addr:169.254.161.241  Bcast:169.254.255.255
>>>>>>>  Mask:255.255.0.0
>>>>>>>           inet6 addr: fe80::26a5:b629:f948:92c3/64 Scope:Link
>>>>>>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>>>>>           RX packets:11 errors:2 dropped:1 overruns:0 frame:0
>>>>>>>           TX packets:78 errors:0 dropped:0 overruns:0 carrier:0
>>>>>>>           collisions:0 txqueuelen:1000
>>>>>>>           RX bytes:3350 (3.2 KiB)  TX bytes:16024 (15.6 KiB)
>>>>>>> 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:196 errors:0 dropped:0 overruns:0 frame:0
>>>>>>>           TX packets:196 errors:0 dropped:0 overruns:0 carrier:0
>>>>>>>           collisions:0 txqueuelen:1
>>>>>>>           RX bytes:25419 (24.8 KiB)  TX bytes:25419 (24.8 KiB)
>>>>>>>
>>>>>>> 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)
>>>>>>>
>>>>>>> wlan0     Link encap:Ethernet  HWaddr b8:27:eb:6d:5d:66
>>>>>>>           UP BROADCAST PROMISC  MTU:1500  Metric:1
>>>>>>>           RX packets:1 errors:0 dropped:1 overruns:0 frame:0
>>>>>>>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>>>>>>           collisions:0 txqueuelen:1000
>>>>>>>           RX bytes:60 (60.0 B)  TX bytes:0 (0.0 B)
>>>>>>>
>>>>>>> I believe it's the ip address of eth1 that is creating the issue.
>>>>>>> Please help me out.
>>>>>>>
>>>>>>> --
>>>>>>> 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 https://groups.google.com/a/gr
>>>>>>> asehotspot.org/group/grase-hotspot/.
>>>>>>> To view this discussion on the web visit
>>>>>>> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-
>>>>>>> hotspot/8070344e-1d8d-4120-a790-77a10651dd64%40grasehotspot.org
>>>>>>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/8070344e-1d8d-4120-a790-77a10651dd64%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 https://groups.google.com/a/gr
>>>>> asehotspot.org/group/grase-hotspot/.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-
>>>>> hotspot/a39b6967-7450-4ae5-8fd7-44e72d7c7c2c%40grasehotspot.org
>>>>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/a39b6967-7450-4ae5-8fd7-44e72d7c7c2c%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 https://groups.google.com/a/gr
>>> asehotspot.org/group/grase-hotspot/.
>>> To view this discussion on the web visit https://groups.google.com/a/gr
>>> asehotspot.org/d/msgid/grase-hotspot/37257a25-ff07-481d-
>>> a341-7bf5cc2cb817%40grasehotspot.org
>>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/37257a25-ff07-481d-a341-7bf5cc2cb817%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***e@grasehotspot.org.
> To post to this group, send email to gr***t@grasehotspot.org.
> Visit this group at https://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/8f4b0392-8a6b-
> 4e53-a990-f8659269beff%40grasehotspot.org
> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/8f4b0392-8a6b-4e53-a990-f8659269beff%40grasehotspot.org?utm_medium=email&utm_source=footer>
> .
>

Thread