bwauths doesn't reach reliable my relay
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I do wonder why both longclaw and Faravahar seems since few days not to reach my relays 1AF72E8906E6C49481A791A6F8F84F8DFEBBB2BA and 6EABEBF38CE7E3DF672C4DB01383606FE3EB2215 respectively - resulting in a bw value of 20. B/c I switched to version 0.3.1.7 I do wonder if this could be the culprit ? - -- Toralf PGP C4EACDDE 0076E94E -----BEGIN PGP SIGNATURE----- iI0EAREIADUWIQQaN2+ZSp0CbxPiTc/E6s3eAHbpTgUCWcwE1BccdG9yYWxmLmZv ZXJzdGVyQGdteC5kZQAKCRDE6s3eAHbpTik4AP4ubRPDKm3jz73xGXmNAhupWarC 9pVPhRNqoD19jgpbGwD/QUnYKHIpbV4983kVMBjr9vbt2zwHRwmT0o+YMFJEVws= =NYwf -----END PGP SIGNATURE-----
Do you have errors in your logs? Maybe they are running a really old client version and we broke compatibility somehow. Or maybe there is a config issue. T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n ------------------------------------------------------------------------
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 09/29/2017 01:59 AM, teor wrote:
Do you have errors in your log no, except 1 or 2 few http errors for faharvar that a consensus upload failed or so.
In the mean while I got a reasonable bw back. But b/c the were 3 "outages" within a week for about 6-8 hours each I'll still take a look on this. - -- Toralf PGP C4EACDDE 0076E94E -----BEGIN PGP SIGNATURE----- iI0EAREIADUWIQQaN2+ZSp0CbxPiTc/E6s3eAHbpTgUCWc5unxccdG9yYWxmLmZv ZXJzdGVyQGdteC5kZQAKCRDE6s3eAHbpTiD2AP0fXtwnQtcH/2UDI+8bqLU2i++/ EkptSlv7oVbvkS9nEAD6Alkvx2oFPRp1oM4o0B/tirPNnLsmBU+3Uqq4ELlPXMQ= =wdKA -----END PGP SIGNATURE-----
-----BEGIN PGP MESSAGE----- Charset: utf-8 hQQOA9vCYl42+L0WEA//VFaxE6QcaoO0VzW4rkSlbceYTu7yPgBX1u80HWJwGvVB 4Wv/Wk0YpaKl2FKQvo0tU01021f8Qf9e3cHDHeu7DcxTb6TDkOGE3M6BYZndGFz+ 6d7sWe2E2kUXQQpZbjjvsjSqIE1r/OdSb2jyQnj75HkMrOsR1df0FzQ+CtnKMoyN mKijc41Mc6Bt3lvJkdBNpbOnCiuxZWQnnow5iR+dism0uW9kIqIcc38/2jG3aiIZ SXKcyP5hBBjygsO+YcUb1xcGVJsw/mpzd6KaBtFktp8e7SLtQj752m5DZ+C//GyT R9Ie3cc1TrR+1c3CUM0LqWWp5xiMsuac1iHrON3sKBchVOWcdKCk09cZZsgth5rx U8GqMrvYi7ljNMt/wcGXcLNDCFnoKrduTsZF+UjxPkpWPYhg1lBG+ehCqctEukBX MheWQOIA7j6n0lVaJhdzC3Aaxr71xKwwY0R8kPL/15KZGDZ/lpr4z2e+BWVWkfDh dHIUXRqd1yXglaF/VXkUW/jr7+M/kQtbXQz8+Gt3SJuq3tJilZE+dVBqDkazJk1q 7b+gHujt7osTnYEofjvChFYGpg0Chke5lToUfYSIXfmmeYCdvWJuAaago0XBIKB7 QYz8jxv7ZuMwsU7coM1Z7dcn/Bq+Qv8q0hLP2JCIblCZrLDlGaQJxk44Wx8UNbEQ AJdfQZShS0C4mL5pycL3Wo94EcRBw6QkEUw2hlt6MzlXlWgQzBShZSlH44/EzCyA Vxd4eZ8t4gK8j0IG1SyUDwporwR6Z176W32IemY7QewuB9wflkppBPSI7kQbkbJz norf6p1Wv8Jl3MktYndzXnA902X5nnwGMRB5GYOvWjjCqtU0gYlyaxh9d7vySiYh uNttxuxOfprHt1OKiHPfoj4XvJxE5Zqv+IiCXvWLfg+2itsPWvfHSuvwv+NPIag/ B2sSvK3Dc/BL6ZGBlTk2/I3RPcl17qZX6r2OFzBA3151G/NcJvHeU4BfJzbv/xc9 zhirrhrre2cwThUZDvytUmQsIZy5DolTwZ1oqQNyJj0dQivFsCwKRF4K2ji6bt1C R+rviPKFkWXubzK3w6F/OVF9RDdn1rXfBKuSqXRueDWXoKXypcqF7OoQlUf5XNoz I4ZkziG6SG2/eRjPSQyBQmMJgUyVbbU7IHmUmCbaNUpUdpZ+g0djzUx7qYLe2pS/ fA6niLgvLcALUtu6US6mpfkr5GJBNcoN3OfZjQJKrDZ6sjCalygSjg/ad+YmPmH0 jhvG7gBL0WQXj0Q0BYGy8FFcyvnFYT+91dHX4hPgp3UK1DXBj4YEmUr7bARvp+n0 ALXIRcwaiW7Vkq4qhZ3AyxszcjGqGL6Xo6wYbD+fQmI80sE7AZ4zfjWhNFIqjVCT tZHkqW0JS59m90bCmvdulCumHeQlHZMY2E0SdpumdwScAhsJKLudIYxbdLDFm1wZ Gpa7zXHQNfkb0bDXb+EpECkZIwiiCgSA1i/STCMM91jXMuf0b/5WYVrE8/j0jaAJ geICP5DUcqJnKSDQvSbgV9q9HKzj4ga7tsnM8xU7LiyeDVEvXqjyAbGWwoQgmIdA V6wHFmHB2Lu0x3qHcu6Vs5FmqiU3lvnr+uxqyY5fwtxr5Kwp7NXvZBDq083KUKvI 9GLU4Cr50EeDnb849Iyd8zBPdBg+XK/LGTHe6G2aMCJdDij3nb8LhH2KB+BR3q+5 IKDTuQepvtHjRrNvuwWBrY7NspZg0FhDhh/PrT+aNnFwlrQW28n+c6Hvv2YSO/Va ow1iOPir32CqBuXNVOZFBPZuwJrck8uKEpqNKbkxRd3OolTE8KHbyFh3T8UeNrBL 2Lm711n2Qfrb9HViEitb0ehTd84u9On6Qst8BuYsqTIKXW9BO/5XeHRSaSZoND1B A162abki/5KGxUIMW3SMZrwHyy2evZzHhlf9bd+G89NNiPtoaogIKjW3Pgp4/a24 x0byLjMW9ERYDDCedvCMS+xfNKEfVCOTw2ypQkRAQfcIXJWrAzYLdouCem5S/hxZ I5l3euU5m8ySSRa4EyC9 =nHmX -----END PGP MESSAGE-----
btw you just wrote sent an encrypted message to a public mailing list. i don't see the point in doing this, maybe is was an accident? On Sat, Sep 30, 2017 at 02:47:35PM +0200, Toralf Förster wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 09/30/2017 06:59 PM, dawuud wrote:
My fault, I just wanted to sign it, sry. - -- Toralf PGP C4EACDDE 0076E94E -----BEGIN PGP SIGNATURE----- iI0EAREIADUWIQQaN2+ZSp0CbxPiTc/E6s3eAHbpTgUCWc/NqBccdG9yYWxmLmZv ZXJzdGVyQGdteC5kZQAKCRDE6s3eAHbpTjl+AP40N/bMgIGexOm2eY4Hf5+O4kaS BOdPRkA39FpfH5iGagD+JOWzyU64qlKlUJvT5xGg7+2br7qGjjIHd+7ttQyG9Kc= =trx3 -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 09/29/2017 06:02 PM, Toralf Förster wrote:
In the mean while I got a reasonable bw back.
And again , one relay is at bw=20 (fropm about 60,000) whereas the other (same hardware, just different ip and port) has bw=3000. Both have nearly identical configs (in fact, parts of the config file are the same). - -- Toralf PGP C4EACDDE 0076E94E -----BEGIN PGP SIGNATURE----- iIwEAREIADUWIQQaN2+ZSp0CbxPiTc/E6s3eAHbpTgUCWc/NcxccdG9yYWxmLmZv ZXJzdGVyQGdteC5kZQAKCRDE6s3eAHbpTrooAPY3bBxXN7ljV7jmoex21TGcJdxT 6e/DRO6pP+H06BkhAP4z9VIU64xzt/bENvgeFKUUH7fk9+xtaxbQK2HROJiS0Q== =j0P7 -----END PGP SIGNATURE-----
participants (3)
-
dawuud -
teor -
Toralf Förster