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

Header Data

From: Rishabbh A Dua <du***h@gmail.com>
Message Hash: 5d81691574ead53fe4b2e0a687106f1d3c35cab740502f0ddb91517230737122
Message ID: <0d9c0beb-bcf2-460f-9563-aa4d53207cc8@grasehotspot.org>
Reply To: <CAESLx0+YRb1ot1owcn_SmL3p8=NO_QF-KaQr_F41-01P-gGYxw@mail.gmail.com>
UTC Datetime: 2016-09-15 02:32:20 UTC
Raw Date: Thu, 15 Sep 2016 02:32:20 -0700

Raw message 

Also from /var/log/syslog, we found that when system is booting, even 
though eth1 is manual, it tries to get dhcp address


pi@raspberrypi:~ $ cat /var/log/syslog | grep eth
Sep 15 09:24:41 raspberrypi dhclient: Listening on 
LPF/eth0/b8:27:eb:38:08:33
Sep 15 09:24:41 raspberrypi dhclient: Sending on   
LPF/eth0/b8:27:eb:38:08:33
Sep 15 09:24:41 raspberrypi dhclient: DHCPDISCOVER on eth0 to 
255.255.255.255 port 67 interval 8
Sep 15 09:24:41 raspberrypi networking[251]: Listening on 
LPF/eth0/b8:27:eb:38:08:33
Sep 15 09:24:41 raspberrypi networking[251]: Sending on   
LPF/eth0/b8:27:eb:38:08:33
Sep 15 09:24:41 raspberrypi networking[251]: DHCPDISCOVER on eth0 to 
255.255.255.255 port 67 interval 8
Sep 15 09:24:41 raspberrypi dhclient: DHCPDISCOVER on eth0 to 
255.255.255.255 port 67 interval 12
Sep 15 09:24:41 raspberrypi dhclient: DHCPREQUEST on eth0 to 
255.255.255.255 port 67
Sep 15 09:24:41 raspberrypi networking[251]: DHCPDISCOVER on eth0 to 
255.255.255.255 port 67 interval 12
Sep 15 09:24:41 raspberrypi networking[251]: DHCPREQUEST on eth0 to 
255.255.255.255 port 67
Sep 15 09:24:41 raspberrypi kernel: [    2.705233] smsc95xx 1-1.1:1.0 eth0: 
register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, 
b8:27:eb:38:08:33
Sep 15 09:24:41 raspberrypi dhcpcd[615]: eth1: adding address 
fe80::26a5:b629:f948:92c3
Sep 15 09:24:41 raspberrypi kernel: [    3.668945] dm9601 1-1.4:1.0 eth1: 
register 'dm9601' at usb-3f980000.usb-1.4, Davicom DM96xx USB 10/100 
Ethernet, 00:e0:4c:53:44:58
Sep 15 09:24:41 raspberrypi kernel: [    5.220319] smsc95xx 1-1.1:1.0 eth0: 
hardware isn't capable of remote wakeup
Sep 15 09:24:41 raspberrypi kernel: [    5.220417] IPv6: 
ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 15 09:24:41 raspberrypi kernel: [    6.822852] IPv6: 
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sep 15 09:24:41 raspberrypi kernel: [    6.823345] smsc95xx 1-1.1:1.0 eth0: 
link up, 100Mbps, full-duplex, lpa 0xC5E1
Sep 15 09:24:41 raspberrypi kernel: [   15.533907] dm9601 1-1.4:1.0 eth1: 
link up, 100Mbps, full-duplex, lpa 0xFFFF
Sep 15 09:24:41 raspberrypi kernel: [   15.601406] dm9601 1-1.4:1.0 eth1: 
kevent 4 may have been dropped
Sep 15 09:24:41 raspberrypi kernel: [   15.603405] dm9601 1-1.4:1.0 eth1: 
kevent 4 may have been dropped
Sep 15 09:24:41 raspberrypi avahi-daemon[624]: Joining mDNS multicast group 
on interface eth0.IPv6 with address fe80::ba27:ebff:fe38:833.
Sep 15 09:24:41 raspberrypi avahi-daemon[624]: New relevant interface 
eth0.IPv6 for mDNS.
Sep 15 09:24:41 raspberrypi avahi-daemon[624]: Joining mDNS multicast group 
on interface eth0.IPv4 with address 192.168.1.8.
Sep 15 09:24:41 raspberrypi avahi-daemon[624]: New relevant interface 
eth0.IPv4 for mDNS.
Sep 15 09:24:41 raspberrypi avahi-daemon[624]: Registering new address 
record for fe80::ba27:ebff:fe38:833 on eth0.*.
Sep 15 09:24:41 raspberrypi avahi-daemon[624]: Registering new address 
record for 192.168.1.8 on eth0.IPv4.
Sep 15 09:24:41 raspberrypi dhcpcd[615]: eth0: IAID eb:38:08:33
Sep 15 09:24:41 raspberrypi avahi-daemon[624]: Joining mDNS multicast group 
on interface eth1.IPv6 with address fe80::26a5:b629:f948:92c3.
Sep 15 09:24:41 raspberrypi avahi-daemon[624]: New relevant interface 
eth1.IPv6 for mDNS.
Sep 15 09:24:41 raspberrypi avahi-daemon[624]: Registering new address 
record for fe80::26a5:b629:f948:92c3 on eth1.*.
Sep 15 09:24:41 raspberrypi dhcpcd[615]: eth1: waiting for carrier
Sep 15 09:24:41 raspberrypi kernel: [   15.605407] dm9601 1-1.4:1.0 eth1: 
kevent 4 may have been dropped
Sep 15 09:24:41 raspberrypi dhcpcd[615]: eth1: carrier acquired
Sep 15 09:24:41 raspberrypi kernel: [   15.640694] dm9601 1-1.4:1.0 eth1: 
link up, 100Mbps, full-duplex, lpa 0xFFFF
Sep 15 09:24:41 raspberrypi dhcpcd[615]: eth1: IAID 4c:53:44:58
Sep 15 09:24:41 raspberrypi kernel: [   15.743937] dm9601 1-1.4:1.0 eth1: 
link up, 100Mbps, full-duplex, lpa 0xFFFF
Sep 15 09:24:42 raspberrypi dhcpcd[615]: eth0: rebinding lease of 
192.168.1.8
Sep 15 09:24:42 raspberrypi dhcpcd[615]: eth0: changing route to 
192.168.1.0/24
Sep 15 09:24:42 raspberrypi dhcpcd[615]: eth0: changing default route via 
192.168.1.1
Sep 15 09:24:42 raspberrypi dhcpcd[860]: eth0: soliciting an IPv6 router
Sep 15 09:24:42 raspberrypi dhcpcd[860]: eth0: Router Advertisement from 
fe80::ed2:b5ff:fe26:35c
Sep 15 09:24:42 raspberrypi dhcpcd[860]: eth0: adding default route via 
fe80::ed2:b5ff:fe26:35c
Sep 15 09:24:42 raspberrypi dhcpcd[860]: eth0: soliciting a DHCPv6 lease




*Sep 15 09:24:42 raspberrypi dhcpcd[860]: eth1: soliciting an IPv6 
routerSep 15 09:24:42 raspberrypi dhcpcd[860]: eth1: soliciting a DHCP 
leaseSep 15 09:24:52 raspberrypi dhcpcd[860]: eth1: using IPv4LL address 
169.254.161.241Sep 15 09:24:52 raspberrypi dhcpcd[860]: eth1: adding route 
to 169.254.0.0/16*Sep 15 09:24:52 raspberrypi avahi-daemon[624]: Joining 
mDNS multicast group on interface eth1.IPv4 with address 169.254.161.241.
Sep 15 09:24:52 raspberrypi avahi-daemon[624]: New relevant interface 
eth1.IPv4 for mDNS.
Sep 15 09:24:52 raspberrypi avahi-daemon[624]: Registering new address 
record for 169.254.161.241 on eth1.IPv4.
Sep 15 09:24:55 raspberrypi dhcpcd[860]: eth1: no IPv6 Routers available
Sep 15 09:25:50 raspberrypi ntpd[1951]: Listen normally on 3 eth0 
192.168.1.8 UDP 123
Sep 15 09:25:50 raspberrypi ntpd[1951]: Listen normally on 4 eth1 
169.254.161.241 UDP 123
Sep 15 09:25:50 raspberrypi ntpd[1951]: Listen normally on 8 eth1 
fe80::26a5:b629:f948:92c3 UDP 123
Sep 15 09:25:50 raspberrypi ntpd[1951]: Listen normally on 9 eth0 
fe80::ba27:ebff:fe38:833 UDP 123

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