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

Header Data

From: Erik Andre Aabrekk <er***e@oneway.no>
Message Hash: 8647a6695246c7cb27d85957b1d936fb651a1c506dea59098da7efa50325be1c
Message ID: <CAJgHx0kCtm4ozdjCf-3F7LitozbNxKAh-286iodrKF1Q+4aB-g@mail.gmail.com>
Reply To: <29cb8a8e-094f-4455-b55c-d2962f046e86@grasehotspot.org>
UTC Datetime: 2016-09-16 01:56:21 UTC
Raw Date: Fri, 16 Sep 2016 10:56:21 +0200

Raw message 

Its allways a nice thing to help out. so Where i can come in handy, I
SHOUt. hehe

Found you on social media if you like help there.., so we might be
able to help each other out and solve the problem.

To be honest i gonna check in my config file how it was setup, and let you know.

Erik

2016-09-16 10:43 GMT+02.00, Rachitta A Dua <ra***a@gmail.com>:
> Hi Erik
>
> Thanks for your response.
>
> Could you please guide me as to how can I do that? I tried editing
> /etc/network/interfaces by adding the line iface eth1 inet manual but that
> didn't work either.
>
> On Friday, September 16, 2016 at 1:55:26 PM UTC+5:30, erikandre wrote:
>>
>> Hi!
>>
>> The network interface of eth1 is supposed to be blank (no IP)
>>
>> So you need to setup the eth1 to not have a ip to get the grase
>> hotspot portal to work as you expect.
>>
>> Erik
>>
>> 2016-09-15 7:55 GMT+02.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.
>>
>>
>> >
>>
>
> --
> 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/29cb8a8e-094f-4455-b55c-d2962f046e86%40grasehotspot.org.
>

Thread