Re: [tor-relays] Pi3 mid relay dropping lil bit of packets
Hmm I just noticed that systemd HUPs tor exactly every 24h and now I have 16 packets lost with 30gb relayed. Can this be the cause? Is there a way to log these drops without putting too much load on ram/cpu? Just to have a timestamp?___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Pi3 mid relay dropping lil bit of packets
Ok thank you for replies, will keep an eye on this. On Tue, Aug 16, 2016 at 6:11 AM, Green Dream greendream...@gmail.com wrote: Counter-point... transmission errors are not a certainty: RX packets:323526978271 errors:0 dropped:0 overruns:0 frame:0 TX packets:249565709357 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:285274358053849 (285.2 TB) TX bytes:287754558279252 (287.7 TB) Ideally there should be no errors. :) 11 dropped packets isn't a big deal, but I wouldn't be quick to dismiss these errors by default. In certain cases things might be improved with driver updates, or sysctl tweaks, or a new ethernet cable, etc. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Pi3 mid relay dropping lil bit of packets
Counter-point... transmission errors are not a certainty: RX packets:323526978271 errors:0 dropped:0 overruns:0 frame:0 TX packets:249565709357 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:285274358053849 (285.2 TB) TX bytes:287754558279252 (287.7 TB) Ideally there should be no errors. :) 11 dropped packets isn't a big deal, but I wouldn't be quick to dismiss these errors by default. In certain cases things might be improved with driver updates, or sysctl tweaks, or a new ethernet cable, etc. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Pi3 mid relay dropping lil bit of packets
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1053088862188 errors:0 dropped:0 overruns:511390 frame:0 TX packets:306784541602 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1413645618747401 (1.2 PiB) TX bytes:317045507788162 (288.3 TiB) Memory:8000-8001 Over half a million packets lost. Nothing to worry at all. Even good packets get sometimes hurt. I would not worry about your 11 packets :) Markus 2016-08-15 21:50 GMT+02:00 Roman Mamedov: > On Mon, 15 Aug 2016 20:08:31 +0200 > Pi3 wrote: > >> Hello, >> I just started running my little 5 mbits mid relay on Pi3 on raspbian and >> all seems to be dandy, >> it picked traffic nicely, hovering around 700-800 total connections, >> its not unusual to see it pushing full advertised bandwidth during peak >> hours (with ~20-25% load on 1 core, multithread pls come already), tldr so >> far nice. >> Except with 3days uptime and 20 gigs of data relayed ifconfig shows 11 >> (eleven) packets dropped on eth0. >> Google says it can be ring buffer on NIC getting full, but >> ethtool -g eth0 says >> Ring parameters for eth0: Cannot get device ring settings: Operation not >> supported >> ethtool -S eth0 = no stats available >> Htop avg load is 0.30, tor uses 121/950mb of ram. Im running standard >> conntrack cstate established related iptable rule with default drop. >> Pi3 is in LAN behind modem nat. >> It worries me because if I get more consensus, drops will probably go up. >> I didnt apply any sysctl tweaks. Using official deb >> NIC is Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter and >> its internally connected to usb2 by design - it shows under lsusb. >> ethtool says 100Mb/s full duplex. >> Tor log is clean with only heartbeat in it, syslog seemed ok also if I didnt >> miss anything. >> Or is it so marginal I should forget about it? >> Im not sure what should I do about it, any suggestions are welcomed. >> Thanks > ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Pi3 mid relay dropping lil bit of packets
On Mon, 15 Aug 2016 20:08:31 +0200 Pi3wrote: > Hello, > I just started running my little 5 mbits mid relay on Pi3 on raspbian and all > seems to be dandy, > it picked traffic nicely, hovering around 700-800 total connections, > its not unusual to see it pushing full advertised bandwidth during peak hours > (with ~20-25% load on 1 core, multithread pls come already), tldr so far nice. > Except with 3days uptime and 20 gigs of data relayed ifconfig shows 11 > (eleven) packets dropped on eth0. > Google says it can be ring buffer on NIC getting full, but > ethtool -g eth0 says > Ring parameters for eth0: Cannot get device ring settings: Operation not > supported > ethtool -S eth0 = no stats available > Htop avg load is 0.30, tor uses 121/950mb of ram. Im running standard > conntrack cstate established related iptable rule with default drop. > Pi3 is in LAN behind modem nat. > It worries me because if I get more consensus, drops will probably go up. > I didnt apply any sysctl tweaks. Using official deb > NIC is Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter and > its internally connected to usb2 by design - it shows under lsusb. > ethtool says 100Mb/s full duplex. > Tor log is clean with only heartbeat in it, syslog seemed ok also if I didnt > miss anything. > Or is it so marginal I should forget about it? > Im not sure what should I do about it, any suggestions are welcomed. > Thanks Like others explained, just 11 frames (at maximum, around 15 KB or so in 20GB!) is practically nothing, so there is no reason to worry. Also keep in mind that frames can be dropped for legitimate reasons, e.g. if for some reason the board sees packets on the wire which are not addressed to it, or oversized, or generally malformed in some way by the other side. In any case, thanks to TCP any dropped frame (=lost packet) gets rapidly retransmitted with no significant impact on throughput or connection stability. That said, I remember from reading various Raspberry Pi forums that the smsc95xx device doesn't exactly have the reputation of the most reliable or well designed piece of hardware in the world (mostly related to attempts to make various 'unusual' USB devices such as some audio interfaces to work with it, or using a number of USB devices concurrently), so considering your results it's actually working amazingly well for you so far. :) -- With respect, Roman pgpp6r5cC2MTO.pgp Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Pi3 mid relay dropping lil bit of packets
>> Hello, >> I just started running my little 5 mbits mid relay on Pi3 on raspbian and >> all seems to be dandy, >> it picked traffic nicely, hovering around 700-800 total connections, >> its not unusual to see it pushing full advertised bandwidth during peak >> hours (with ~20-25% load on 1 core, multithread pls come already), tldr so >> far nice. >> Except with 3days uptime and 20 gigs of data relayed ifconfig shows 11 >> (eleven) packets dropped on eth0. > Personal opinion here: > > 11 packets dropped on 20GB of data sounds pretty small, and these packets > might not even be from Tor. Literally any network service could have > dropped those packets (ntp, ssh, updates, etc.) I wouldn't worry about it > unless it starts to dramatically increase. I agree. 11 packets dropped is literally nothing. I just pulled up some stats from one of my webservers: > packets:5436637 errors:0 dropped:4287 overruns:0 carrier:0 Server is performing fine, and the packet loss percentage calculated from those numbers is 0.07%. Yours would be even smaller. Don't worry about it. --Sean ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Pi3 mid relay dropping lil bit of packets
Personal opinion here: 11 packets dropped on 20GB of data sounds pretty small, and these packets might not even be from Tor. Literally any network service could have dropped those packets (ntp, ssh, updates, etc.) I wouldn't worry about it unless it starts to dramatically increase. On Aug 15, 2016 1:08 PM, "Pi3"wrote: Hello, I just started running my little 5 mbits mid relay on Pi3 on raspbian and all seems to be dandy, it picked traffic nicely, hovering around 700-800 total connections, its not unusual to see it pushing full advertised bandwidth during peak hours (with ~20-25% load on 1 core, multithread pls come already), tldr so far nice. Except with 3days uptime and 20 gigs of data relayed ifconfig shows 11 (eleven) packets dropped on eth0. Google says it can be ring buffer on NIC getting full, but ethtool -g eth0 says Ring parameters for eth0: Cannot get device ring settings: Operation not supported ethtool -S eth0 = no stats available Htop avg load is 0.30, tor uses 121/950mb of ram. Im running standard conntrack cstate established related iptable rule with default drop. Pi3 is in LAN behind modem nat. It worries me because if I get more consensus, drops will probably go up. I didnt apply any sysctl tweaks. Using official deb NIC is Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter and its internally connected to usb2 by design - it shows under lsusb. ethtool says 100Mb/s full duplex. Tor log is clean with only heartbeat in it, syslog seemed ok also if I didnt miss anything. Or is it so marginal I should forget about it? Im not sure what should I do about it, any suggestions are welcomed. Thanks ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Pi3 mid relay dropping lil bit of packets
Hello, I just started running my little 5 mbits mid relay on Pi3 on raspbian and all seems to be dandy, it picked traffic nicely, hovering around 700-800 total connections, its not unusual to see it pushing full advertised bandwidth during peak hours (with ~20-25% load on 1 core, multithread pls come already), tldr so far nice. Except with 3days uptime and 20 gigs of data relayed ifconfig shows 11 (eleven) packets dropped on eth0. Google says it can be ring buffer on NIC getting full, but ethtool -g eth0 says Ring parameters for eth0: Cannot get device ring settings: Operation not supported ethtool -S eth0 = no stats available Htop avg load is 0.30, tor uses 121/950mb of ram. Im running standard conntrack cstate established related iptable rule with default drop. Pi3 is in LAN behind modem nat. It worries me because if I get more consensus, drops will probably go up. I didnt apply any sysctl tweaks. Using official deb NIC is Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter and its internally connected to usb2 by design - it shows under lsusb. ethtool says 100Mb/s full duplex. Tor log is clean with only heartbeat in it, syslog seemed ok also if I didnt miss anything. Or is it so marginal I should forget about it? Im not sure what should I do about it, any suggestions are welcomed. Thanks___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays