Raspberry Pi network dies

Please explain what you mean the "network dies" Does the Pi2 lose the network? If so, Issue a command "ifconfig" before and after the problem. Paste he results here. Also you can try "ifup eth0" or "ifup wlan0" depending if wired or wireless.

Clem

When this happens Ssh and telnet dies as well.

The PI is on but no network tools can connect to it.

Are you using wireless?  Have you checked out the syslog?

Wired connection and this is what SYSLOG had

Mar 23 10:17:09 raspberrypi kernel: [ 13.724325] Adding 102396k swap on /var/swap. Priority:-1 extents:2 across:2134012k SSFSMar 23 10:17:09 raspberrypi /usr/sbin/cron[1960]: (CRON) INFO (Running @reboot jobs)Mar 23 10:17:09 raspberrypi ntpd[1948]: ntpd 4.2.6p5@1.2349-o Mon Feb 9 03:34:42 UTC 2015 (1)Mar 23 10:17:09 raspberrypi ntpd[1979]: proto: precision = 1.250 usecMar 23 10:17:09 raspberrypi ntpd[1979]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123Mar 23 10:17:09 raspberrypi ntpd[1979]: Listen normally on 1 lo 127.0.0.1 UDP 123Mar 23 10:17:09 raspberrypi ntpd[1979]: peers refreshedMar 23 10:17:09 raspberrypi ntpd[1979]: Listening on routing socket on fd #18 for interface updatesMar 23 10:17:09 raspberrypi ntpd[1979]: restrict: error in address '::' on line 38. Ignoring...Mar 23 10:17:09 raspberrypi ntpd[1979]: restrict: error in address '::1' on line 42. Ignoring...Mar 23 10:17:09 raspberrypi ntpd[1979]: Deferring DNS for 0.debian.pool.ntp.org 1Mar 23 10:17:09 raspberrypi ntpd[1979]: Deferring DNS for 1.debian.pool.ntp.org 1Mar 23 10:17:09 raspberrypi ntpd[1979]: Deferring DNS for 2.debian.pool.ntp.org 1Mar 23 10:17:09 raspberrypi ntpd[1979]: Deferring DNS for 3.debian.pool.ntp.org 1Mar 23 10:17:09 raspberrypi ntpd[2001]: signal_no_reset: signal 17 had flags 4000000Mar 23 10:17:09 raspberrypi ifplugd(eth0)[1597]: Link beat detected.Mar 23 10:17:09 raspberrypi ifplugd(eth0)[1597]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.Mar 23 10:17:09 raspberrypi dhclient: Internet Systems Consortium DHCP Client 4.2.2Mar 23 10:17:09 raspberrypi dhclient: Copyright 2004-2011 Internet Systems Consortium.Mar 23 10:17:09 raspberrypi dhclient: All rights reserved.Mar 23 10:17:09 raspberrypi dhclient: For info, please visithttps://www.isc.org/software/dhcp/Mar 23 10:17:09 raspberrypi dhclient: Mar 23 10:17:09 raspberrypi ifplugd(eth0)[1597]: client: Internet Systems Consortium DHCP Client 4.2.2Mar 23 10:17:09 raspberrypi ifplugd(eth0)[1597]: client: Copyright 2004-2011 Internet Systems Consortium.Mar 23 10:17:09 raspberrypi ifplugd(eth0)[1597]: client: All rights reserved.Mar 23 10:17:09 raspberrypi ifplugd(eth0)[1597]: client: For info, please visithttps://www.isc.org/software/dhcp/Mar 23 10:17:10 raspberrypi dhclient: Listening on LPF/eth0/b8:27:eb:ca:f4:47Mar 23 10:17:10 raspberrypi ifplugd(eth0)[1597]: client: Listening on LPF/eth0/b8:27:eb:ca:f4:47Mar 23 10:17:10 raspberrypi dhclient: Sending on LPF/eth0/b8:27:eb:ca:f4:47Mar 23 10:17:10 raspberrypi ifplugd(eth0)[1597]: client: Sending on LPF/eth0/b8:27:eb:ca:f4:47Mar 23 10:17:10 raspberrypi dhclient: Sending on Socket/fallbackMar 23 10:17:10 raspberrypi ifplugd(eth0)[1597]: client: Sending on Socket/fallbackMar 23 10:17:10 raspberrypi dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67Mar 23 10:17:10 raspberrypi ifplugd(eth0)[1597]: client: DHCPREQUEST on eth0 to 255.255.255.255 port 67Mar 23 10:17:17 raspberrypi dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67Mar 23 10:17:17 raspberrypi ifplugd(eth0)[1597]: client: DHCPREQUEST on eth0 to 255.255.255.255 port 67Mar 23 10:17:17 raspberrypi dhclient: DHCPACK from 192.168.0.1Mar 23 10:17:17 raspberrypi ifplugd(eth0)[1597]: client: DHCPACK from 192.168.0.1Mar 23 10:17:17 raspberrypi dhclient: bound to 192.168.0.15 -- renewal in 41528 seconds.Mar 23 10:17:17 raspberrypi ifplugd(eth0)[1597]: client: bound to 192.168.0.15 -- renewal in 41528 seconds.Mar 23 10:17:18 raspberrypi ifplugd(eth0)[1597]: Program executed successfully.Mar 23 10:17:19 raspberrypi ntpd[1979]: Listen normally on 2 eth0 192.168.0.15 UDP 123Mar 23 10:17:19 raspberrypi ntpd[1979]: peers refreshedMar 23 10:17:21 raspberrypi ntpd_intres[2001]: DNS 0.debian.pool.ntp.org -> 129.70.132.36Mar 23 10:17:21 raspberrypi ntpd_intres[2001]: DNS 1.debian.pool.ntp.org -> 144.76.117.245Mar 23 10:17:21 raspberrypi ntpd_intres[2001]: DNS 2.debian.pool.ntp.org -> 193.140.100.41Mar 23 10:17:21 raspberrypi ntpd_intres[2001]: DNS 3.debian.pool.ntp.org -> 178.17.160.12

oh post your auth.log too I am curious about something.

SYSLOG seems all normal here and is from March 23 at 10:17... Have you tried "ifup eth0" after losing the network? This should work on an auto network

Clem

Not been around to capture the latest time it has frozen.

Will try and get it again and also the auth.log.

A friend made this change to th NTP conf file and what it has done is reduced the volume of entries in SYS.log

restrict -6 ::1

I have a lot of these entries

Apr 12 18:35:35 raspberrypi sshd[13688]: Received disconnect from 43.255.190.122: 11:  [preauth]

Apr 12 18:35:35 raspberrypi sshd[13688]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.255.190.122  user=root

Apr 12 18:35:37 raspberrypi sshd[13739]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.255.190.122  user=root

Apr 12 18:35:39 raspberrypi sshd[13739]: Failed password for root from 43.255.190.122 port 36200 ssh2

Apr 12 18:35:41 raspberrypi sshd[13739]: Failed password for root from 43.255.190.122 port 36200 ssh2

Apr 12 18:35:43 raspberrypi sshd[13739]: Failed password for root from 43.255.190.122 port 36200 ssh2

Apr 12 18:35:44 raspberrypi sshd[13739]: Received disconnect from 43.255.190.122: 11:  [preauth]

Apr 12 18:35:44 raspberrypi sshd[13739]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.255.190.122  user=root

Apr 12 18:35:46 raspberrypi sshd[13765]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.255.190.122  user=root

Apr 12 18:35:48 raspberrypi sshd[13765]: Failed password for root from 43.255.190.122 port 55395 ssh2

Apr 12 18:35:50 raspberrypi sshd[13765]: Failed password for root from 43.255.190.122 port 55395 ssh2

Apr 12 18:35:53 raspberrypi sshd[13765]: Failed password for root from 43.255.190.122 port 55395 ssh2

Apr 12 18:35:53 raspberrypi sshd[13765]: Received disconnect from 43.255.190.122: 11:  [preauth]

Apr 12 18:35:53 raspberrypi sshd[13765]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.255.190.122  user=root

Apr 12 18:35:55 raspberrypi sshd[13792]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.255.190.122  user=root

Apr 12 18:35:57 raspberrypi sshd[13792]: Failed password for root from 43.255.190.122 port 51241 ssh2

Apr 12 18:35:59 raspberrypi sshd[13792]: Failed password for root from 43.255.190.122 port 51241 ssh2

Apr 12 18:36:02 raspberrypi sshd[13792]: Failed password for root from 43.255.190.122 port 51241 ssh2

Apr 12 18:36:02 raspberrypi sshd[13792]: Received disconnect from 43.255.190.122: 11:  [preauth]

Apr 12 18:36:02 raspberrypi sshd[13792]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.255.190.122  user=root

Apr 12 18:36:04 raspberrypi sshd[13823]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.255.190.122  user=root

Apr 12 18:36:06 raspberrypi sshd[13823]: Failed password for root from 43.255.190.122 port 44557 ssh2

Apr 12 18:36:09 raspberrypi sshd[13823]: Failed password for root from 43.255.190.122 port 44557 ssh2

Apr 12 18:36:11 raspberrypi sshd[13823]: Failed password for root from 43.255.190.122 port 44557 ssh2

I thought it was my mate but not

and whosip shows these people

% [whois.apnic.net]

% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

% Information related to '43.255.190.0 - 43.255.190.255'

inetnum: 43.255.190.0 - 43.255.190.255

netname: RUNIDC

descr: HongKong Runidc Technology Co Limited

country: HK

admin-c: BDIC1-AP

tech-c: BDIC1-AP

status: ASSIGNED NON-PORTABLE

notify: 217118@qq.com

mnt-by: MAINT-BIG-HK

mnt-lower: MAINT-BIG-HK

mnt-routes: MAINT-BIG-HK

mnt-irt: IRT-BIG-HK

changed: 217118@qq.com 20130819

source: APNIC

irt: IRT-BIG-HK

address: UNIT17 9/F TOWER, A NEW MANDARIN PLAZA, NO 14 SCIENCE MUSEUM RD TST, HONGKONG HONGKONG

e-mail: abuse@0451dns.com

abuse-mailbox: abuse@0451dns.com

admin-c: BDIC1-AP

tech-c: BDIC1-AP

auth: Filtered

mnt-by: MAINT-BIG-HK

changed: hm-changed@apnic.net 20130909

source: APNIC

role: Big Dipper international company limited administr

address: UNIT17 9/F TOWER, A NEW MANDARIN PLAZA, NO 14 SCIENCE MUSEUM RD TST, HONGKONG HONGKONG

country: HK

phone: +86018676767557

fax-no: +86018676767557

e-mail: abuse@0451dns.com

admin-c: BDIC1-AP

tech-c: BDIC1-AP

nic-hdl: BDIC1-AP

mnt-by: MAINT-BIG-HK

changed: hm-changed@apnic.net 20130909

source: APNIC

% Information related to '43.255.188.0/22AS134121'

route: 43.255.188.0/22

descr: RUNIDC BGP

origin: AS134121

country: HK

notify: 217118@qq.com

mnt-lower: MAINT-BIG-HK

mnt-routes: MAINT-BIG-HK

mnt-by: MAINT-BIG-HK

changed: 217118@qq.com 20150401

source: APNIC

% This query was served by the APNIC Whois Service version 1.69.1-APNICv1r0 (UNDEFINED)

That could be it right there,  You are getting hit by script kiddies and that can cause the firewall to shut you down.  Check out my blog here.  You can also setup key authentication as well to fix this, both have worked well for me.

http://www.element14.com/community/people/screamingtiger/blog/2015/04/13/raspberry-pi-tips-and-tricks

Not good. I did not realize you had this on the internet. You may want to look at VPN tunnelling instead to allow only a few people in....

Clem