new VPS bridge bandwidth under-reported
Hello, Just setup a new bridge running 0.2.6.1-alpha and it's working fine. The bridge is running in a Linux container VPS and appears to have an iptables traffic-shaped bandwidth limit of 400KB. Can browse and download files through it with decent performance using obfs4. However self-measurement of bandwidth, after starting at around 200Kbytes has steadily declined until now its showing 8KB and has lost the "fast" flag. At this point the bridge has yet to attract any traffic other then my testing usage--but it works just fine nevertheless. I suspect that latency for small transfers is fairly bad (in the sense of milliseconds, rather than seconds) and that this may be distorting bandwidth metrics. Also the number of bytes transferred is close to zero, which does not seem likely to help the situation. Should I be concerned about it? Anything anyone can recommend to correct it aside from looking another VPS provider? Does the advertised bandwidth have much effect on whether the bridge will be disseminated by the bridge database system? No "stable" flag yet, but not enough time has passed for this to happen. Thanks
Oops. The "rate limit" I quoted is actually the limit on the DOCSIS modem here, not on the VPS. Probably not 'iptables' traffic shaping after all. Using 'speedtest_cli.py' the max rate has been showing 100 Mbits/sec, but I discount that because the speedtest node appears to reside in the same data center as the VPS and is probably on the same LAN. Nonetheless, the Tor bridge is showing a ridiculous low bandwidth value and it seems reasonable to figure out why.
What's the fingerprint of your bridge or what's the uptime? When I setup my relay the shown bandwidth was first low and increased since then to full declared speed. ~Josef Am 05.01.2015 um 11:39 schrieb starlight.2015q1@binnacle.cx:
Oops. The "rate limit" I quoted is actually the limit on the DOCSIS modem here, not on the VPS. Probably not 'iptables' traffic shaping after all.
Using 'speedtest_cli.py' the max rate has been showing 100 Mbits/sec, but I discount that because the speedtest node appears to reside in the same data center as the VPS and is probably on the same LAN.
Nonetheless, the Tor bridge is showing a ridiculous low bandwidth value and it seems reasonable to figure out why.
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
At 11:49 1/5/2015 +0100, Josef 'veloc1ty' Stautner wrote:
What's the fingerprint of your bridge or what's the uptime? When I setup my relay the shown bandwidth was first low and increased since then to full declared speed.
Bridge is A411C021A7B95F340485A9CCE34187025193DEF6 Uptime is two+ days. Did your relay start out with a reasonable bandwidth (e.g. 200MBytes/sec) and then drop like a stone to nothing before recovering?
Hello list, I'm new to this but got my node up and running on a MK802 arm device. However, tor-arm keep complaining about missing history. The exact message is: "Read the last day of bandwidth history from the state file (9 minutes is missing)" Does anyone know why this is but more important, how to solve? Greets, FreedomBitcoin 2015-01-05 11:49 GMT+01:00 Josef 'veloc1ty' Stautner <hello@veloc1ty.de>:
What's the fingerprint of your bridge or what's the uptime? When I setup my relay the shown bandwidth was first low and increased since then to full declared speed.
~Josef
Am 05.01.2015 um 11:39 schrieb starlight.2015q1@binnacle.cx:
Oops. The "rate limit" I quoted is actually the limit on the DOCSIS modem here, not on the VPS. Probably not 'iptables' traffic shaping after all.
Using 'speedtest_cli.py' the max rate has been showing 100 Mbits/sec, but I discount that because the speedtest node appears to reside in the same data center as the VPS and is probably on the same LAN.
Nonetheless, the Tor bridge is showing a ridiculous low bandwidth value and it seems reasonable to figure out why.
_______________________________________________ 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
participants (3)
-
Josef 'veloc1ty' Stautner -
Michiel Bruijn -
starlight.2015q1＠binnacle.cx