swampdog
Posts: 221
Joined: Fri Dec 04, 2015 11:22 am

Re: Loosing IP - no way to connect

Thu Sep 15, 2016 11:00 am

This is probably useless but back when I was building iscsi into the rpi kernel I noticed the pi was getting two leases (this with dhcpcd). I am running an old DNS/DHCP under FreeBSD 8.2 so fortunately I could see this happening. The iscsi thing wasn't worth the hassle. However, later on when I went with an nfs network boot the same issue cropped up.

pi$ ip addr show

If the above shows more than one ip bound to the same device it could be the same issue. If not then this post is useless!

Just in case.. what appeared to be happening was my old BSD dhcpd wasn't handling "clientid" correctly. The pi wasn't passing clientid on boot (1st ip assigned) but once it got booting off the network the pi dhcpcd sent another better formed (with clientid) request (2nd ip assigned). BSD saw both were the same mac address but treated them as distinct. After some time the 1st ip lease expired and there was nothing on the pi that knew to refresh it and BSD might reassign it elsewhere at any time.

An effective (but irritating) way of bypassing the problem was to stop the pi passing "clientid" at all..

Code: Select all

pi$ diff -u /etc/dhcpcd.conf.ORIGINAL /etc/dhcpcd.conf
--- /etc/dhcpcd.conf.ORIGINAL	2016-06-15 05:30:26.000000000 +0100
+++ /etc/dhcpcd.conf	2016-06-15 05:30:38.000000000 +0100
@@ -8,7 +8,7 @@
 hostname
 
 # Use the hardware address of the interface for the Client ID.
-clientid
+##clientid
 # or
 # Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
 #duid

User avatar
pi-anazazi
Posts: 516
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: Loosing IP - no way to connect

Thu Sep 15, 2016 12:22 pm

Hi!

Thanks, for the info! My router (based on freeBSD) has reserved IPs for every device based on MAC, all other requests are discarded. So I can exclude this, I guess...

I see from my DHCP logs that the raspi suddenly stops to refresh the IP, but the rest of the machine appears to be doing fine.

Waiting for the next event to plug in serial and see if I can find something strange.
Kind regards

anazazi

vsgregg
Posts: 1
Joined: Fri Sep 16, 2016 12:30 pm

Re: Loosing IP - no way to connect

Fri Sep 16, 2016 12:39 pm

pi-anazazi,

you seem to be an active participant here, and maybe I can ask you to help me debug a VNC issue with my new RPI.

I won't post the details here for obvious reasons, but if you e-mail me at [email protected], we can chat.

Maybe I can return the favor as I learn more about Raspberry Pi.

Thanks,

Victor


pi-anazazi wrote:Hi again!

Have here 6 raspi 1B, 2B with identical raspian jessie installations (cloned cards with Windiskimager) normally doing fine, but after some weeks 2 of these might loose there IP (DHCP IPv4 from router with static ARP entries for these MAC adresses). If this happens I loose contact, no VNC no SSH possible (all raspis running headless, so no way at all to enter, I have to pull the power plug to access them again).

Unplugging the ethernet cable does not result in the request of an IP, I checked that in the protocol of the DHCPD running on the router.

Any ideas how to debug this? Any log files in jessie to check?

Maybe the easiest was will be to prepare a new SD-card?

Many thanks in advance!

anazazi

User avatar
pi-anazazi
Posts: 516
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: Loosing IP - no way to connect

Wed Nov 16, 2016 8:36 am

Here we go!

@vsgregg, sorry found your post this morning, issue resolved?

Have now the raspi in vegetative state after doing fine for weeks now, no networking possible,

Code: Select all

ifdown eth0  && ifup eth0
gives
ifdown: interface eth0 not configured
with wicd I get "Not connected" after trying to connect.

Ifconfig gives no IP for eth0.

I saved /var/log/syslog. Anything else I should store before rebooting to get network back?
Kind regards

anazazi

User avatar
pi-anazazi
Posts: 516
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: Loosing IP - no way to connect

Wed Nov 16, 2016 8:07 pm

Nobody interested? :geek:
Kind regards

anazazi

User avatar
pi-anazazi
Posts: 516
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: Loosing IP - no way to connect

Thu Nov 17, 2016 7:56 am

OK, I made another try on the same raspi (NO reboot in the menatime) to get back an IP, via wicd and with the ifdown&ifup command given above. Interestingly the router even sees the IP request and hands out the correct IP, but is never used, connection not succesful gives wicd and ifconfig or related does not show any IP

Code: Select all

Nov 17 08:49:02 	dhcpd 		DHCPREQUEST for 10.x.x.y (10.x.x.a) from b8:27:eb:xx:xx:xx via em1
Nov 17 08:49:02 	dhcpd 		DHCPOFFER on 10.x.x.y to b8:27:eb:xx:xx:xx via em1
Nov 17 08:49:02 	dhcpd 		DHCPDISCOVER from b8:27:eb:xx:xx:xx via em1 
Really strange.
Kind regards

anazazi

User avatar
pi-anazazi
Posts: 516
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: Loosing IP - no way to connect

Thu Nov 17, 2016 10:12 am

- Hostname on raspi was not the same as in the router, now harmonized (didn't make any difference, though)

- Rebooting the router did not change anything

- Updated and rebooted the raspi, now

Code: Select all

uname -a
Linux raspXCVBCXCBXC 4.4.26+ #915 Thu Oct 20 17:02:14 BST 2016 armv6l GNU/Linux
...wait and see what will happen.
Kind regards

anazazi

User avatar
pi-anazazi
Posts: 516
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: Loosing IP - no way to connect

Thu Nov 17, 2016 12:47 pm

As this here is apparently my private thread, I will bring in some pictures, furniture and a little red carpet, to make it a little more cosy ;)
Kind regards

anazazi

User avatar
pi-anazazi
Posts: 516
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: Loosing IP - no way to connect

Fri Nov 18, 2016 9:04 am

I cannot reach this forum from my usual IP range. Getting blocked? Strange...
Kind regards

anazazi

User avatar
pi-anazazi
Posts: 516
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: Loosing IP - no way to connect

Fri Nov 18, 2016 9:39 am

Found out that I can trigger the "no LAN"-state of the raspi by unplugging the RJ45 cable. Afterwards no reconnection to network possible, although the correct IP is handed out by the router.

Changed the RJ45 cable, didn't buy me anything...
Kind regards

anazazi

User avatar
pi-anazazi
Posts: 516
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: Loosing IP - no way to connect

Fri Nov 18, 2016 3:08 pm

Info

Code: Select all

uname -a
Linux raspxxxx 4.4.26+ #915 Thu Oct 20 17:02:14 BST 2016 armv6l GNU/Linux

Code: Select all

 $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
Kind regards

anazazi

User avatar
pi-anazazi
Posts: 516
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: Loosing IP - no way to connect

Sat Nov 19, 2016 11:54 am

OK, what happend in the meantime:

- Changed hardware (different Raspi 1) -> same result, no network after unplugging RJ45

- disabled IPv6 according to this:

https://www.leowkahman.com/2016/03/19/d ... -raspbian/

to avoid IPv6 noise in Wireshark (lots of!) -> same result,...

- the "ifdown+ifup" command sometimes (but not always) results in

Code: Select all

interface eth0 not configured
- Wireshark shows on re-inserting the RJ45

Code: Select all

28	2016-11-19 11:36:15.811382696	Raspberr_xx:yy:zz	Broadcast	ARP	60	Who has 10.aa.bb.cc? Tell 0.0.0.0
...but no reply, while the router log shows:

Code: Select all

Nov 19 12:44:34 	dhcpd 		DHCPACK on 10.aa.bb.cc to b8:27:eb:xx:yy:zz via em1
Nov 19 12:44:34 	dhcpd 		DHCPREQUEST for 10.aa.bb.cc (10.aa.bb.oo) from b8:27:eb:xx:yy:zz via em1
Nov 19 12:44:34 	dhcpd 		DHCPOFFER on 10.aa.bb.cc to b8:27:eb:xx:yy:zz via em1
Nov 19 12:44:34 	dhcpd 		DHCPDISCOVER from b8:27:eb:xx:yy:zz via em1 
Which indicates successful handout of IP via DHCP, or?

What is going wrong here? I'm running out of ideas where to look...
Kind regards

anazazi

User avatar
pi-anazazi
Posts: 516
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: Loosing IP - no way to connect

Sat Nov 19, 2016 12:24 pm

Log of wicd after try to reconnect (RJ45 out - RJ45 in - press "Connect " in wicd widget from task bar)

Code: Select all

2016/11/19 12:59:02 :: Putting interface down
2016/11/19 12:59:02 :: Releasing DHCP leases...
2016/11/19 12:59:02 :: Setting false IP...
2016/11/19 12:59:03 :: Stopping wpa_supplicant
2016/11/19 12:59:03 :: Flushing the routing table...
2016/11/19 12:59:03 :: Putting interface up...
2016/11/19 12:59:05 :: Running DHCP with hostname "HOSTNAME"
2016/11/19 12:59:05 :: dhcpcd[3326]: sending commands to master dhcpcd process
2016/11/19 12:59:05 :: 
2016/11/19 12:59:05 :: 
2016/11/19 12:59:05 :: DHCP connection successful
2016/11/19 12:59:06 :: Connecting thread exiting.
2016/11/19 12:59:06 :: Sending connection attempt result success
Looks successful, but always says

"Not connected" in the wicd GUI in the end...

syslog looks like this for the same operation:

Code: Select all

Nov 19 12:59:01 HOSTNAME dhcpcd[3301]: sending commands to master dhcpcd process
Nov 19 12:59:01 HOSTNAME dhcpcd[518]: control command: /sbin/dhcpcd -k eth0
Nov 19 12:59:01 HOSTNAME kernel: [ 2352.546851] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Nov 19 12:59:01 HOSTNAME kernel: [ 2352.694290] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Nov 19 12:59:02 HOSTNAME kernel: [ 2353.687772] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Nov 19 12:59:02 HOSTNAME dhcpcd[3321]: sending commands to master dhcpcd process
Nov 19 12:59:02 HOSTNAME dhcpcd[518]: control command: /sbin/dhcpcd -k eth0
Nov 19 12:59:03 HOSTNAME kernel: [ 2353.999116] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Nov 19 12:59:04 HOSTNAME kernel: [ 2355.436918] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Nov 19 12:59:05 HOSTNAME dhcpcd[3326]: sending commands to master dhcpcd process
Nov 19 12:59:05 HOSTNAME dhcpcd[518]: control command: /sbin/dhcpcd -h HOSTNAME --noipv4ll eth0
Nov 19 12:59:05 HOSTNAME dhcpcd[518]: eth0: adding address fe80::6e20:aaa:bbbb:cccc
Nov 19 12:59:05 HOSTNAME dhcpcd[518]: if_addaddress6: Permission denied
Nov 19 12:59:05 HOSTNAME dhcpcd[518]: eth0: IAID eb:xx:yy:zz
Nov 19 12:59:06 HOSTNAME dhcpcd[518]: eth0: soliciting a DHCP lease
Nov 19 12:59:06 HOSTNAME dhcpcd[518]: eth0: offered 10.aa.bb.cc from 10.aa.bb.oo
Nov 19 12:59:06 HOSTNAME dhcpcd[518]: eth0: soliciting an IPv6 router
Nov 19 12:59:07 HOSTNAME dhcpcd[3376]: sending commands to master dhcpcd process
Nov 19 12:59:07 HOSTNAME dhcpcd[518]: control command: /sbin/dhcpcd -k eth0
Nov 19 12:59:07 HOSTNAME dhcpcd[518]: eth0: removing interface
Nov 19 12:59:07 HOSTNAME kernel: [ 2358.825432] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Nov 19 12:59:08 HOSTNAME kernel: [ 2358.961305] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Nov 19 12:59:09 HOSTNAME kernel: [ 2360.503308] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Kind regards

anazazi

User avatar
pi-anazazi
Posts: 516
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: Loosing IP - no way to connect

Sat Nov 19, 2016 12:55 pm

This is syslog when unplugging RJ45 and reconnecting the RJ45 cable

Code: Select all

Nov 19 13:44:27 HOSTNAME kernel: [ 1660.966367] smsc95xx 1-1.1:1.0 eth0: link down
Nov 19 13:44:27 HOSTNAME dhcpcd[519]: eth0: carrier lost
Nov 19 13:44:27 HOSTNAME rsyslogd-2007: action 'action 17' suspended, next retry is Sat Nov 19 13:44:57 2016 [try http://www.rsyslog.com/e/2007 ]
Nov 19 13:44:28 HOSTNAME avahi-daemon[356]: Withdrawing address record for 10.aa.bb.cc. on eth0.
Nov 19 13:44:28 HOSTNAME avahi-daemon[356]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.aa.bb.cc..
Nov 19 13:44:28 HOSTNAME avahi-daemon[356]: Interface eth0.IPv4 no longer relevant for mDNS.
Nov 19 13:44:28 HOSTNAME dhcpcd[519]: eth0: deleting route to 10.aa.bb.0/26
Nov 19 13:44:28 HOSTNAME dhcpcd[519]: eth0: deleting default route via 10.aa.bb.oo
Nov 19 13:44:29 HOSTNAME dhcpcd[1706]: sending commands to master dhcpcd process
Nov 19 13:44:30 HOSTNAME dhcpcd[519]: control command: /sbin/dhcpcd -k eth0
Nov 19 13:44:30 HOSTNAME dhcpcd[519]: eth0: removing interface
Nov 19 13:44:30 HOSTNAME kernel: [ 1663.507311] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Nov 19 13:44:30 HOSTNAME kernel: [ 1663.646348] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Nov 19 13:44:32 HOSTNAME ntpd[542]: Deleting interface #3 eth0, 10.aa.bb.cc.#123, interface stats: received=32, sent=32, dropped=0, active_time=1635 secs
Nov 19 13:44:32 HOSTNAME ntpd[542]: 100.10.00.00 interface 10.aa.bb.cc. -> (none)
Nov 19 13:44:32 HOSTNAME ntpd[542]: peers refreshed
Nov 19 13:44:34 HOSTNAME kernel: [ 1667.338433] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Nov 19 13:44:34 HOSTNAME dhcpcd[1816]: sending commands to master dhcpcd process
Nov 19 13:44:34 HOSTNAME dhcpcd[519]: control command: /sbin/dhcpcd -k eth0
Nov 19 13:44:34 HOSTNAME kernel: [ 1668.190207] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Nov 19 13:44:35 HOSTNAME kernel: [ 1668.294317] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Nov 19 13:44:36 HOSTNAME kernel: [ 1669.251518] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Nov 19 13:44:36 HOSTNAME dhcpcd[1837]: sending commands to master dhcpcd process
Nov 19 13:44:36 HOSTNAME dhcpcd[519]: control command: /sbin/dhcpcd -k eth0
Nov 19 13:44:36 HOSTNAME kernel: [ 1669.424012] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Nov 19 13:44:37 HOSTNAME kernel: [ 1670.949723] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Nov 19 13:44:38 HOSTNAME dhcpcd[1842]: sending commands to master dhcpcd process
Nov 19 13:44:38 HOSTNAME dhcpcd[519]: control command: /sbin/dhcpcd -h HOSTNAME --noipv4ll eth0
Nov 19 13:44:38 HOSTNAME dhcpcd[519]: eth0: adding address fe80::6e20:ddd.ffff.gggg
Nov 19 13:44:38 HOSTNAME dhcpcd[519]: if_addaddress6: Permission denied
Nov 19 13:44:38 HOSTNAME dhcpcd[519]: eth0: IAID eb:xx:yy:zz
Nov 19 13:44:38 HOSTNAME dhcpcd[519]: eth0: soliciting an IPv6 router
Nov 19 13:44:39 HOSTNAME dhcpcd[519]: eth0: soliciting a DHCP lease
Nov 19 13:44:39 HOSTNAME dhcpcd[519]: eth0: offered 10.aa.bb.cc. from 10.aa.bb.oo
Nov 19 13:44:43 HOSTNAME dhcpcd[519]: eth0: leased 10.aa.bb.cc. for 7200 seconds
Nov 19 13:44:43 HOSTNAME avahi-daemon[356]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.aa.bb.cc..
Nov 19 13:44:43 HOSTNAME avahi-daemon[356]: New relevant interface eth0.IPv4 for mDNS.
Nov 19 13:44:43 HOSTNAME avahi-daemon[356]: Registering new address record for 10.aa.bb.cc. on eth0.IPv4.
Nov 19 13:44:43 HOSTNAME dhcpcd[519]: eth0: adding route to 10.aa.bb.0/26
Nov 19 13:44:43 HOSTNAME dhcpcd[519]: eth0: adding default route via 10.aa.bb.oo
Nov 19 13:44:45 HOSTNAME dhcpcd[1936]: sending commands to master dhcpcd process
Nov 19 13:44:45 HOSTNAME ntpd[542]: Listen normally on 4 eth0 10.aa.bb.cc. UDP 123
Nov 19 13:44:45 HOSTNAME ntpd[542]: peers refreshed
Nov 19 13:44:45 HOSTNAME avahi-daemon[356]: Withdrawing address record for 10.aa.bb.cc. on eth0.
Nov 19 13:44:45 HOSTNAME avahi-daemon[356]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.aa.bb.cc..
Nov 19 13:44:45 HOSTNAME avahi-daemon[356]: Interface eth0.IPv4 no longer relevant for mDNS.
Nov 19 13:44:45 HOSTNAME kernel: [ 1678.912489] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Nov 19 13:44:45 HOSTNAME kernel: [ 1679.144821] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Nov 19 13:44:47 HOSTNAME dhcpcd[519]: send_arp: Network is down
Nov 19 13:44:47 HOSTNAME dhcpcd[519]: eth0: removing IP address 10.aa.bb.cc./26
Nov 19 13:44:47 HOSTNAME dhcpcd[519]: eth0: deleting route to 10.aa.bb.0/26
Nov 19 13:44:47 HOSTNAME dhcpcd[519]: eth0: deleting default route via 10.aa.bb.oo
Nov 19 13:44:47 HOSTNAME ntpd[542]: Deleting interface #4 eth0, 10.aa.bb.cc.#123, interface stats: received=0, sent=0, dropped=1, active_time=2 secs
Nov 19 13:44:47 HOSTNAME ntpd[542]: 100.10.00.00 interface 10.aa.bb.cc. -> (none)
Nov 19 13:44:47 HOSTNAME ntpd[542]: peers refreshed
Nov 19 13:44:47 HOSTNAME kernel: [ 1680.670173] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Nov 19 13:44:49 HOSTNAME dhcpcd[519]: eth0: carrier lost
Nov 19 13:44:50 HOSTNAME dhcpcd[519]: eth0: carrier acquired
Nov 19 13:44:50 HOSTNAME dhcpcd[519]: eth0: IAID eb:xx:yy:zz
Nov 19 13:44:50 HOSTNAME dhcpcd[519]: control command: /sbin/dhcpcd -k eth0
Nov 19 13:44:50 HOSTNAME dhcpcd[519]: eth0: removing interface
Kind regards

anazazi

User avatar
pi-anazazi
Posts: 516
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: Loosing IP - no way to connect

Sat Nov 19, 2016 1:13 pm

from 13:44:37 there is the reconnect, look good first, but in the end avahi kicks in

Code: Select all

Nov 19 13:44:45 HOSTNAME avahi-daemon[356]: Withdrawing address record for 10.aa.bb.cc. on eth0.
Nov 19 13:44:45 HOSTNAME avahi-daemon[356]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.aa.bb.cc..
Nov 19 13:44:45 HOSTNAME avahi-daemon[356]: Interface eth0.IPv4 no longer relevant for mDNS.
...without any good reason, in my opinion. WHY?
Kind regards

anazazi

User avatar
pi-anazazi
Posts: 516
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: Loosing IP - no way to connect

Sat Nov 19, 2016 7:47 pm

Meanwhile:

- Avahi is not the culprit (and no local domain in the DHCP server...), disabling helps nothing.

- Found the "missing" DHCP packages in wireshark, the DHCP process is complete, but raspian cuts the connection directly after initiating the interface, including the correct IP

- changeing /etc/network/interfaces from dhcp to manual for eth0 and return helps nothing, also allowing "hotplug" for eth0 changes nothing.

Where is the fine log for dhcpd, can't find it anywhere and nothing from dhcpd in syslog either.

Great community here, btw. Keep up with the great support! :mrgreen:
Last edited by pi-anazazi on Sat Nov 19, 2016 8:09 pm, edited 1 time in total.
Kind regards

anazazi

User avatar
DougieLawson
Posts: 35537
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: Loosing IP - no way to connect

Sat Nov 19, 2016 7:51 pm

Try building a brand new fresh SDCard with a newly downloaded copy of NOBS/Raspbian or plain Raspbian. That's the usual solution for this problem when it's been reported by other punters.

BTW, please edit your post above to remove the profanity, this is a family friendly forum and you don't want to incur the wrath of the moderation team.
Note: Having anything remotely humorous in your signature is completely banned on this forum. Wear a tinfoil hat and you'll get a ban.

Any DMs sent on Twitter will be answered next month.

This is a doctor free zone.

User avatar
pi-anazazi
Posts: 516
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: Loosing IP - no way to connect

Sat Nov 19, 2016 8:08 pm

Ok, DHCP daemon logs to system log, but as "dhcpcd"...

Apparently it messes around with some IPv6 address, which is disabled, I don't want to have anything to do with IPv6. In the end it kills the interface, according to the log.

Why?
Kind regards

anazazi

User avatar
pi-anazazi
Posts: 516
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: Loosing IP - no way to connect

Sat Nov 19, 2016 8:14 pm

Hi DougieLawson!

After our political sidekick last week we are apparently dead here. :-D
Could start our own forums somewhere, huh?

Fresh card... hmm, as the cards running on at least 6 raspis are burned as identical copies of one initial installation I can't believe that this is the solution. Changed raspi, SD-card, cloned SD-card, all to no avail. So apparently there must be something wrong with IPv6 handling somewhere, although disabled completely on boot. I don't see the logics behind all that!

Dunno where to look further....
Kind regards

anazazi

User avatar
DougieLawson
Posts: 35537
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: Loosing IP - no way to connect

Sat Nov 19, 2016 8:52 pm

It's the solution for everyone else, because the network management stuff is so very badly borken in Raspbian. It's a flaming mess of brown steaming stuff.
Note: Having anything remotely humorous in your signature is completely banned on this forum. Wear a tinfoil hat and you'll get a ban.

Any DMs sent on Twitter will be answered next month.

This is a doctor free zone.

User avatar
paulwratt
Posts: 83
Joined: Fri Jun 12, 2015 12:15 am

Re: Loosing IP - no way to connect

Wed Dec 07, 2016 9:06 am

@pi-anazazi I not follow this originally, but read entire thread, please keep posting results of ur quest, even tho no-one can help atm.

I have vague memory of there being "linux bind" issues a few years ago. what you describe, sounds like some process maxing out on memory or disk space. If you were talking about WiFi I would say swap hardware with another pi, but you are not, but then it not make sense why you also getting "hardware isn't capable of remote wakeup", this is completely wrong for eth0, so check module firmware for "smsc95xx"

you talk about multiple "different" pi's, it is the 1B or 2B that has problem. If pi1, try using Raspbian Wheezy image with your software on that, it may make difference.

also, when pi goes down, if you restart network related processes in order (there is couple of files outline boot process, should give you indication). If that no work, stop networking (all) remove modules (un-modprob) for networking, re-install them (re-modprob) restart services.

if either of those work, you have "kinda" iscolated the problem, so set up cron to test ping ip, if above services, stop and restart all needed, if module as well, run shell script to stop services, pull module, put module, restart services.

if you are thorough in your tests above to manually restart hardware, interface, services, you should be able to pinpoint the offending item.

one last question, how old is the pi that looses ip. how many total hours has it run. does it have heat sink on memory and usb controller (not just CPU)

K, hope the is a solution somewhere in all of that, or at least a feeling of getting closer.

NOTE: if you test for IP failure, and cant figure failure item, get cron job to start pi (you say this works fine)

Cheers
Paul

User avatar
pi-anazazi
Posts: 516
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: Loosing IP - no way to connect

Sun Dec 11, 2016 11:12 pm

Hi paulwratt!

Busy these days :-)

Just some infos:

- Currently there is 1 raspi 1B and 1 raspi 2B with this phenomenon. Switching hardware (raspi 1) does not change anything. Cloning the SD card does not help either.

- The problem started after switching from wheezy to jessy earlier this year. Installation based on jessy light with GUI installed. The raspi 1B running phyton scripts, the raspi 2 running motion and pilight. Other raspis with identical cloned SD cards doing fine.

- The raspis don't have a high cpu load, cpu temp around 40 to 44°C. Always.

I will have a look at the other raspis doing fine, what the logs look like for a successful IP refresh after RJ45 re-connect. Maybe
Kind regards

anazazi

User avatar
pi-anazazi
Posts: 516
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: Loosing IP - no way to connect

Wed May 31, 2017 7:30 am

covfefe...
Kind regards

anazazi

Return to “Troubleshooting”