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

Header Data

From: Rishabbh A Dua <du***h@gmail.com>
Message Hash: 0e200e1375dc8d643ae7d234cf969fdf50a9b78e94b4a4a8071178a30307efab
Message ID: <201d1bc0-0a33-4bc4-b7fc-4a4463f9bdb1@grasehotspot.org>
Reply To: <2dbe25f4-8b1d-10fd-5cd1-b9f947c855f7@radez.hr>
UTC Datetime: 2016-09-16 06:38:38 UTC
Raw Date: Fri, 16 Sep 2016 06:38:38 -0700

Raw message 

Hi Drazen 
worked like a charm!!!

Thanks for your support.

I am facing another problem now, dns-nameservers only 1 is coming and 
coming as 127.0.0.1.
Not taking the values i am providing in network settings. 

Any pointers?

Thanks
Rishabbh

On Friday, 16 September 2016 16:39:25 UTC+5:30, drazen.zuvela wrote:
>
> So, that is the answer. 
> Only two adapters should be present before starting linux installation 
> and all should work fine. 
>
> Drazen 
>
> 16.9.2016. u 12:24, Erik Andre Aabrekk je napisao/la: 
> > Hi! 
> > 
> > Raspberry got 1 wireless and 1 ethernet. 
> > 
> > So if you use Wireless to connect to Inet (WAN) and ethernet to 
> > connect with devices. It should work just like a dream. 
> > 
> > What Image is been used to install ubuntu on raspberry 3? 
> > 
> > 
> > 
> > 2016-09-16 11:04 GMT+02.00, Dražen Žuvela <dr***.@radez.hr 
> <javascript:>>: 
> >> I agree with Erik, 
> >> but i prefer to let grase-setup did the work as per design. In order to 
> >> achieve that you need to have board with 2 network interfaces. 
> >> Seems that rPi board has *3 physical interfaces*: eth0, eth1 and wlan0 
> !!! 
> >> 
> >> eth0 and wlan0 both start with mac B8:27:EB which belonging to 
> Raspberry 
> >> Pi Foundation , 
> >> and eth1 starts with 00:e0:4c which is REALTEK (probably your 
> usb-to-eth 
> >> adapter) . 
> >> You should read your raspbery documentation carefully and see where 
> that 
> >> wlan0 comes from. Maybe you need to disable that in bios, or you may 
> >> need not your realtek adapter at all. 
> >> 
> >> Drazen 
> >> 
> >> 16.9.2016. u 10:43, Rachitta A Dua je napisao/la: 
> >>> 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/ 
> >>>      <
> 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>. 
>
> >>> 
> >>>      > 
> >>> 
> >>> -- 
> >>> 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:> 
> >>> <mailto:gr***e@grasehotspot.org <javascript:>>. 
> >>> To post to this group, send email to gr***.@grasehotspot.org 
> <javascript:> 
> >>> <mailto: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/29cb8a8e-094f-4455-b55c-d2962f046e86%40grasehotspot.org 
> >>> 
> >>> <
> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/29cb8a8e-094f-4455-b55c-d2962f046e86%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 <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/d167ef47-3445-d508-2166-bcf3545e9f07%40radez.hr. 
>
> >> 
>
>

Thread