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

Header Data

From: Rishabbh A Dua <du***h@gmail.com>
Message Hash: 019f9ecc8da4a45e7d35c886dff2c7215d3e19eec5d80247c11ac4fcc7f8f61d
Message ID: <f3abbe5f-c719-46e6-8f54-ce0d2030d3ea@grasehotspot.org>
Reply To: <CADDedMFN7t–LrFGhNTaztV4Z1gr7m0KZQ0sb5g60hSMJzUb-w@mail.gmail.com>
UTC Datetime: 2016-09-15 03:24:47 UTC
Raw Date: Thu, 15 Sep 2016 03:24:47 -0700

Raw message 

Thanks for your reply Emre.
just to be clear you mean, usb nic should be connected to internet where as 
in on-board interface should be connected to access point?

Regards
Rishabbh

On Thursday, 15 September 2016 15:31:34 UTC+5:30, postaemre wrote:
>
> Hi.
>
> I also tried to setup grase on Raspberry Pi 2 and 3. Now it works like a 
> charm.
>
> Internal nic should be eth0 and USB nic should be eth1. These settings 
> must be checked after the setup , because wifi adaptor also tries to be 
> eth1. Radmin can configure it at the network settings page.
>
> Many times i faced the same problem like you. At the end, my solution was 
> to install raspbian with graphical interface. Network manager is helping us 
> to maintain the settings for the network adaptors, however server edition 
> is changing the usb bus and devices's addresses after reboot and interface 
> setups are changing.
>
> You may want to try https://downloads.raspberrypi.org/raspbian_latest
>
> Happy days for everyone and thanks Tim for everyting :)
>
> Emre Erdogan
>   
>
> 2016-09-15 8:55 GMT+03:00 Rachitta A Dua <ra***.@gmail.com 
> <javascript:>>:
>
>> 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