pi network going to sleep? - Raspberry Pi Forums
all,
have strange networking issue 1 of raspberry pis.
running program takes images camera , uploads them each night nas.
upload fails due networking issues. once issue (whatever is) occurs, way connectivity pi (pardon pun) ping death.
see below file ping log showing took 40 icmp requests before reply sent. investigating whether somehow related router and/or wireless connections - given other devices in house don't suffer issue i'm inclined think there rpi networking may cause go sleep after long periods of inactivity. aware of?
if has theories on may causing this, please share them. should state @ point no other changes or network traffic taking place throughout duration of ping test , hence not being caused network congestion/contention etc.
regards,
michael
couldn't have .txt attachment ping output below:
have strange networking issue 1 of raspberry pis.
running program takes images camera , uploads them each night nas.
upload fails due networking issues. once issue (whatever is) occurs, way connectivity pi (pardon pun) ping death.
see below file ping log showing took 40 icmp requests before reply sent. investigating whether somehow related router and/or wireless connections - given other devices in house don't suffer issue i'm inclined think there rpi networking may cause go sleep after long periods of inactivity. aware of?
if has theories on may causing this, please share them. should state @ point no other changes or network traffic taking place throughout duration of ping test , hence not being caused network congestion/contention etc.
regards,
michael
couldn't have .txt attachment ping output below:
code: select all
user@client ~ $ ping pi ping pi (192.168.5.2) 56(84) bytes of data. client (192.168.1.3) icmp_seq=1 destination host unreachable client (192.168.1.3) icmp_seq=2 destination host unreachable client (192.168.1.3) icmp_seq=3 destination host unreachable client (192.168.1.3) icmp_seq=4 destination host unreachable client (192.168.1.3) icmp_seq=5 destination host unreachable client (192.168.1.3) icmp_seq=6 destination host unreachable client (192.168.1.3) icmp_seq=7 destination host unreachable client (192.168.1.3) icmp_seq=8 destination host unreachable client (192.168.1.3) icmp_seq=9 destination host unreachable client (192.168.1.3) icmp_seq=10 destination host unreachable client (192.168.1.3) icmp_seq=11 destination host unreachable client (192.168.1.3) icmp_seq=12 destination host unreachable client (192.168.1.3) icmp_seq=13 destination host unreachable client (192.168.1.3) icmp_seq=14 destination host unreachable client (192.168.1.3) icmp_seq=15 destination host unreachable client (192.168.1.3) icmp_seq=16 destination host unreachable client (192.168.1.3) icmp_seq=17 destination host unreachable client (192.168.1.3) icmp_seq=18 destination host unreachable client (192.168.1.3) icmp_seq=19 destination host unreachable client (192.168.1.3) icmp_seq=20 destination host unreachable client (192.168.1.3) icmp_seq=21 destination host unreachable client (192.168.1.3) icmp_seq=22 destination host unreachable client (192.168.1.3) icmp_seq=23 destination host unreachable client (192.168.1.3) icmp_seq=24 destination host unreachable client (192.168.1.3) icmp_seq=25 destination host unreachable client (192.168.1.3) icmp_seq=26 destination host unreachable client (192.168.1.3) icmp_seq=27 destination host unreachable client (192.168.1.3) icmp_seq=28 destination host unreachable client (192.168.1.3) icmp_seq=29 destination host unreachable client (192.168.1.3) icmp_seq=30 destination host unreachable client (192.168.1.3) icmp_seq=31 destination host unreachable client (192.168.1.3) icmp_seq=32 destination host unreachable client (192.168.1.3) icmp_seq=33 destination host unreachable client (192.168.1.3) icmp_seq=34 destination host unreachable client (192.168.1.3) icmp_seq=35 destination host unreachable client (192.168.1.3) icmp_seq=36 destination host unreachable client (192.168.1.3) icmp_seq=37 destination host unreachable client (192.168.1.3) icmp_seq=38 destination host unreachable client (192.168.1.3) icmp_seq=39 destination host unreachable 64 bytes client (192.168.1.3): icmp_seq=40 ttl=64 time=2250 ms 64 bytes client (192.168.1.3): icmp_seq=41 ttl=64 time=1251 ms 64 bytes client (192.168.1.3): icmp_seq=42 ttl=64 time=252 ms 64 bytes client (192.168.1.3): icmp_seq=43 ttl=64 time=7.27 ms 64 bytes client (192.168.1.3): icmp_seq=44 ttl=64 time=7.59 ms 64 bytes client (192.168.1.3): icmp_seq=45 ttl=64 time=6.86 ms 64 bytes client (192.168.1.3): icmp_seq=46 ttl=64 time=26.8 ms 64 bytes client (192.168.1.3): icmp_seq=47 ttl=64 time=48.8 ms 64 bytes client (192.168.1.3): icmp_seq=48 ttl=64 time=8.09 ms 64 bytes client (192.168.1.3): icmp_seq=49 ttl=64 time=7.61 ms 64 bytes client (192.168.1.3): icmp_seq=50 ttl=64 time=115 ms 64 bytes client (192.168.1.3): icmp_seq=51 ttl=64 time=34.5 ms ^c --- pi ping statistics --- 51 packets transmitted, 12 received, +39 errors, 76% packet loss, time 50154ms rtt min/avg/max/mdev = 6.867/334.846/2250.868/668.934 ms, pipe 4
is wireless connection? if wireless adapter may powering down , "sleeping" if it's using power management.
raspberrypi
Comments
Post a Comment