2016-09-16 - Re: Ip address configuration

Header Data

From: Rachitta A Dua <ra***a@gmail.com>
Message Hash: a10e90fb12cdf27b1af9a09ec223b50a9fa6c67e771d23e0d706d397a0a32d6d
Message ID: <42da4f8d-a571-4fe4-bbb5-d1b07fd38688@grasehotspot.org>
Reply To: <8070344e-1d8d-4120-a790-77a10651dd64@grasehotspot.org>
UTC Datetime: 2016-09-16 01:13:43 UTC
Raw Date: Fri, 16 Sep 2016 01:13:43 -0700

Raw message 



<https://lh3.googleusercontent.com/-vCMIGD_9mCQ/V9upk-zjATI/AAAAAAAAATM/r-nPArSh1twok_u90ZJ9orRWbIpm2dwEACLcB/s1600/2016-09-16-130308.jpg>
So I tried installing ubuntu trusty Rpi img on Rpi 2. I was able to install 
grase without any glitches. However, when I try to connect a device to the 
access point, the system stops responding. There is no internet access. And 
the whole thing just stops responding. Even the keyboard doesn't function. 
PFA image of the screen.



On Thursday, September 15, 2016 at 11:25:23 AM UTC+5:30, Rachitta A Dua 
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.
>

Thread