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

Header Data

From: Rishabbh A Dua <du***h@gmail.com>
Message Hash: 5845b70922a166e98355532bdf6455260e915dea53d0e79674ee65a34b776ff3
Message ID: <cb8bb577-99f1-4a08-9bf4-9782b874b08e@grasehotspot.org>
Reply To: <CAESLx0+YRb1ot1owcn_SmL3p8=NO_QF-KaQr_F41-01P-gGYxw@mail.gmail.com>
UTC Datetime: 2016-09-15 00:37:19 UTC
Raw Date: Thu, 15 Sep 2016 00:37:19 -0700

Raw message 

 

Hi Timothy

 

Thanks for your reponse.

Rachitta’s configuration is https://paste.grasehotspot.org/view/0af24677

 
Please find attached the hardware setup.


Also eth0 is connected to internet and is acting as wan port.
eth1 is usb to ethernet port connected to access point.


pi@raspberrypi:~ $ cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)

# Please note that this file is written to be used with dhcpcd
# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'

# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual

auto eth1
iface eth1 inet manual

allow-hotplug wlan0
iface wlan0 inet manual
    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

allow-hotplug wlan1
iface wlan1 inet manual
    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

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 
> <javascript:>> 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 <javascript:>.
>> To post to this group, send email to gr***.@grasehotspot.org 
>> <javascript:>.
>> 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/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>
>> .
>>
>
>

Thread