Remove testnet-seed.bitcoin.schildbach.de. #6446

pull schildbach wants to merge 1 commits into bitcoin:master from schildbach:remove-seed-schildbach changing 1 files +0 −1
  1. schildbach commented at 8:33 AM on July 16, 2015: contributor

    My provider was constantly complaining about unroutable traffic to port 18333 and finally taking down my server. I was running sipa's crawler, modified to add zonefile support.

    Can this PR be considered for the next 0.11 release as well?

  2. Remove testnet-seed.bitcoin.schildbach.de.
    My provider was constantly complaining about unroutable traffic to port 18333 and finally taking down my server. I was running sipa's crawler, modified to add zonefile support.
    6bd98b4644
  3. luke-jr commented at 8:36 AM on July 16, 2015: member

    Eh, ACK, but .. how is unrouteable traffic supposed to be grounds to terminate/shutdown your server??

  4. schildbach commented at 8:39 AM on July 16, 2015: contributor

    This is all I got from them.

    ##########################################################################
#               Netscan detected from host   78.46.152.204               #
##########################################################################

time                protocol src_ip src_port          dest_ip dest_port
---------------------------------------------------------------------------
Wed Jul 15 12:16:27 2015 TCP   78.46.152.204 41074 =>      252.0.25.3 18333
Wed Jul 15 12:16:28 2015 TCP   78.46.152.204 41074 =>      252.0.25.3 18333
Wed Jul 15 12:16:30 2015 TCP   78.46.152.204 41074 =>      252.0.25.3 18333
Wed Jul 15 12:16:02 2015 TCP   78.46.152.204 35411 =>     252.1.40.14 18333
Wed Jul 15 12:16:03 2015 TCP   78.46.152.204 35411 =>     252.1.40.14 18333
Wed Jul 15 12:16:05 2015 TCP   78.46.152.204 35411 =>     252.1.40.14 18333
Wed Jul 15 12:17:28 2015 TCP   78.46.152.204 42500 =>     252.2.11.28 18333
Wed Jul 15 12:17:29 2015 TCP   78.46.152.204 42500 =>     252.2.11.28 18333
Wed Jul 15 12:16:26 2015 TCP   78.46.152.204 40066 =>    252.2.39.106 18333
Wed Jul 15 12:16:29 2015 TCP   78.46.152.204 40066 =>    252.2.39.106 18333
Wed Jul 15 12:17:13 2015 TCP   78.46.152.204 36340 =>       252.3.4.9 18333
Wed Jul 15 12:17:14 2015 TCP   78.46.152.204 36340 =>       252.3.4.9 18333
Wed Jul 15 12:17:16 2015 TCP   78.46.152.204 36340 =>       252.3.4.9 18333
Wed Jul 15 12:17:22 2015 TCP   78.46.152.204 60238 =>      252.4.7.68 18333
Wed Jul 15 12:17:23 2015 TCP   78.46.152.204 60238 =>      252.4.7.68 18333
Wed Jul 15 12:17:25 2015 TCP   78.46.152.204 60238 =>      252.4.7.68 18333
Wed Jul 15 12:17:58 2015 TCP   78.46.152.204 38986 =>     252.5.25.66 18333
Wed Jul 15 12:17:59 2015 TCP   78.46.152.204 38986 =>     252.5.25.66 18333
Wed Jul 15 12:16:23 2015 TCP   78.46.152.204 33233 =>     252.5.54.35 18333
Wed Jul 15 12:16:24 2015 TCP   78.46.152.204 33233 =>     252.5.54.35 18333
Wed Jul 15 12:17:58 2015 TCP   78.46.152.204 45141 =>     252.5.60.70 18333
Wed Jul 15 12:17:59 2015 TCP   78.46.152.204 45141 =>     252.5.60.70 18333
Wed Jul 15 12:18:01 2015 TCP   78.46.152.204 45141 =>     252.5.60.70 18333
Wed Jul 15 12:17:28 2015 TCP   78.46.152.204 43785 =>     252.7.38.36 18333
Wed Jul 15 12:17:01 2015 TCP   78.46.152.204 51397 =>     252.7.42.18 18333
Wed Jul 15 12:16:36 2015 TCP   78.46.152.204 60582 =>      252.8.3.57 18333
Wed Jul 15 12:16:37 2015 TCP   78.46.152.204 60582 =>      252.8.3.57 18333
Wed Jul 15 12:16:39 2015 TCP   78.46.152.204 60582 =>      252.8.3.57 18333
Wed Jul 15 12:16:48 2015 TCP   78.46.152.204 60506 =>     252.8.34.56 18333
Wed Jul 15 12:16:49 2015 TCP   78.46.152.204 60506 =>     252.8.34.56 18333
Wed Jul 15 12:16:51 2015 TCP   78.46.152.204 60506 =>     252.8.34.56 18333
Wed Jul 15 12:16:16 2015 TCP   78.46.152.204 58103 =>     252.9.16.27 18333
Wed Jul 15 12:16:19 2015 TCP   78.46.152.204 58103 =>     252.9.16.27 18333
Wed Jul 15 12:16:44 2015 TCP   78.46.152.204 42632 =>    252.9.27.117 18333
Wed Jul 15 12:16:45 2015 TCP   78.46.152.204 42632 =>    252.9.27.117 18333
Wed Jul 15 12:16:47 2015 TCP   78.46.152.204 42632 =>    252.9.27.117 18333
Wed Jul 15 12:17:46 2015 TCP   78.46.152.204 59083 =>     252.9.28.27 18333
Wed Jul 15 12:17:47 2015 TCP   78.46.152.204 59083 =>     252.9.28.27 18333
Wed Jul 15 12:18:16 2015 TCP   78.46.152.204 54011 =>     252.9.31.35 18333
Wed Jul 15 12:18:17 2015 TCP   78.46.152.204 54011 =>     252.9.31.35 18333
Wed Jul 15 12:18:19 2015 TCP   78.46.152.204 54011 =>     252.9.31.35 18333
Wed Jul 15 12:16:44 2015 TCP   78.46.152.204 48681 =>    252.10.46.54 18333
Wed Jul 15 12:16:45 2015 TCP   78.46.152.204 48681 =>    252.10.46.54 18333
Wed Jul 15 12:16:47 2015 TCP   78.46.152.204 48681 =>    252.10.46.54 18333
Wed Jul 15 12:18:23 2015 TCP   78.46.152.204 56820 =>    252.12.13.12 18333
Wed Jul 15 12:18:24 2015 TCP   78.46.152.204 56820 =>    252.12.13.12 18333
Wed Jul 15 12:18:26 2015 TCP   78.46.152.204 56820 =>    252.12.13.12 18333
Wed Jul 15 12:17:21 2015 TCP   78.46.152.204 44134 =>     252.12.15.2 18333
Wed Jul 15 12:17:22 2015 TCP   78.46.152.204 44134 =>     252.12.15.2 18333
Wed Jul 15 12:17:24 2015 TCP   78.46.152.204 44134 =>     252.12.15.2 18333
Wed Jul 15 12:17:06 2015 TCP   78.46.152.204 47109 =>   252.12.19.104 18333
Wed Jul 15 12:17:09 2015 TCP   78.46.152.204 47109 =>   252.12.19.104 18333
Wed Jul 15 12:18:14 2015 TCP   78.46.152.204 48967 =>    252.12.60.42 18333
Wed Jul 15 12:18:15 2015 TCP   78.46.152.204 48967 =>    252.12.60.42 18333
Wed Jul 15 12:16:20 2015 TCP   78.46.152.204 54934 =>      252.13.3.9 18333
Wed Jul 15 12:16:22 2015 TCP   78.46.152.204 54934 =>      252.13.3.9 18333
Wed Jul 15 12:18:19 2015 TCP   78.46.152.204 57016 =>    252.13.37.51 18333
Wed Jul 15 12:18:20 2015 TCP   78.46.152.204 57016 =>    252.13.37.51 18333
Wed Jul 15 12:18:22 2015 TCP   78.46.152.204 57016 =>    252.13.37.51 18333
Wed Jul 15 12:18:08 2015 TCP   78.46.152.204 51734 =>    252.13.37.84 18333
Wed Jul 15 12:18:11 2015 TCP   78.46.152.204 51734 =>    252.13.37.84 18333
Wed Jul 15 12:16:31 2015 TCP   78.46.152.204 34633 =>    252.13.45.13 18333
Wed Jul 15 12:16:34 2015 TCP   78.46.152.204 34633 =>    252.13.45.13 18333
Wed Jul 15 12:16:43 2015 TCP   78.46.152.204 59950 =>    252.14.13.35 18333
Wed Jul 15 12:16:44 2015 TCP   78.46.152.204 59950 =>    252.14.13.35 18333
Wed Jul 15 12:16:46 2015 TCP   78.46.152.204 59950 =>    252.14.13.35 18333
Wed Jul 15 12:16:12 2015 TCP   78.46.152.204 49251 =>    252.14.32.29 18333
Wed Jul 15 12:17:26 2015 TCP   78.46.152.204 34681 =>    252.14.58.11 18333
Wed Jul 15 12:17:27 2015 TCP   78.46.152.204 34681 =>    252.14.58.11 18333
Wed Jul 15 12:17:29 2015 TCP   78.46.152.204 34681 =>    252.14.58.11 18333
Wed Jul 15 12:17:51 2015 TCP   78.46.152.204 37949 =>     252.15.3.15 18333
Wed Jul 15 12:17:54 2015 TCP   78.46.152.204 37949 =>     252.15.3.15 18333
Wed Jul 15 12:16:53 2015 TCP   78.46.152.204 42424 =>    252.15.51.15 18333
Wed Jul 15 12:16:55 2015 TCP   78.46.152.204 42424 =>    252.15.51.15 18333
Wed Jul 15 12:17:56 2015 TCP   78.46.152.204 47727 =>    252.15.52.47 18333
Wed Jul 15 12:17:57 2015 TCP   78.46.152.204 47727 =>    252.15.52.47 18333
Wed Jul 15 12:16:10 2015 TCP   78.46.152.204 40538 =>     252.16.7.38 18333
Wed Jul 15 12:16:11 2015 TCP   78.46.152.204 40538 =>     252.16.7.38 18333
Wed Jul 15 12:16:13 2015 TCP   78.46.152.204 40538 =>     252.16.7.38 18333
Wed Jul 15 12:16:41 2015 TCP   78.46.152.204 59147 =>    252.16.20.59 18333
Wed Jul 15 12:16:42 2015 TCP   78.46.152.204 59147 =>    252.16.20.59 18333
Wed Jul 15 12:16:44 2015 TCP   78.46.152.204 59147 =>    252.16.20.59 18333
Wed Jul 15 12:18:11 2015 TCP   78.46.152.204 58225 =>     252.16.34.8 18333
Wed Jul 15 12:18:14 2015 TCP   78.46.152.204 58225 =>     252.16.34.8 18333
Wed Jul 15 12:16:31 2015 TCP   78.46.152.204 46315 =>     252.16.53.4 18333
Wed Jul 15 12:16:32 2015 TCP   78.46.152.204 46315 =>     252.16.53.4 18333
Wed Jul 15 12:16:34 2015 TCP   78.46.152.204 46315 =>     252.16.53.4 18333
Wed Jul 15 12:17:28 2015 TCP   78.46.152.204 39640 =>     252.17.0.42 18333
Wed Jul 15 12:17:29 2015 TCP   78.46.152.204 39640 =>     252.17.0.42 18333
Wed Jul 15 12:17:31 2015 TCP   78.46.152.204 39640 =>     252.17.0.42 18333
Wed Jul 15 12:16:56 2015 TCP   78.46.152.204 55752 =>     252.17.1.88 18333
Wed Jul 15 12:16:57 2015 TCP   78.46.152.204 55752 =>     252.17.1.88 18333
Wed Jul 15 12:16:59 2015 TCP   78.46.152.204 55752 =>     252.17.1.88 18333
Wed Jul 15 12:16:46 2015 TCP   78.46.152.204 51442 =>    252.17.16.21 18333
Wed Jul 15 12:16:47 2015 TCP   78.46.152.204 51442 =>    252.17.16.21 18333
Wed Jul 15 12:16:49 2015 TCP   78.46.152.204 51442 =>    252.17.16.21 18333
Wed Jul 15 12:16:13 2015 TCP   78.46.152.204 57218 =>     252.17.28.4 18333
Wed Jul 15 12:16:14 2015 TCP   78.46.152.204 57218 =>     252.17.28.4 18333
Wed Jul 15 12:16:16 2015 TCP   78.46.152.204 57218 =>     252.17.28.4 18333
Wed Jul 15 12:16:31 2015 TCP   78.46.152.204 60797 =>    252.17.28.73 18333
Wed Jul 15 12:16:32 2015 TCP   78.46.152.204 60797 =>    252.17.28.73 18333
Wed Jul 15 12:16:34 2015 TCP   78.46.152.204 60797 =>    252.17.28.73 18333
Wed Jul 15 12:17:39 2015 TCP   78.46.152.204 44913 =>   252.17.59.120 18333
Wed Jul 15 12:17:41 2015 TCP   78.46.152.204 44913 =>   252.17.59.120 18333
Wed Jul 15 12:17:23 2015 TCP   78.46.152.204 37136 =>    252.18.15.76 18333
Wed Jul 15 12:17:24 2015 TCP   78.46.152.204 37136 =>    252.18.15.76 18333
Wed Jul 15 12:17:26 2015 TCP   78.46.152.204 37136 =>    252.18.15.76 18333
Wed Jul 15 12:18:18 2015 TCP   78.46.152.204 50652 =>    252.18.57.10 18333
Wed Jul 15 12:18:21 2015 TCP   78.46.152.204 50652 =>    252.18.57.10 18333
Wed Jul 15 12:17:33 2015 TCP   78.46.152.204 33153 =>    252.19.54.83 18333
Wed Jul 15 12:17:34 2015 TCP   78.46.152.204 33153 =>    252.19.54.83 18333
Wed Jul 15 12:17:36 2015 TCP   78.46.152.204 33153 =>    252.19.54.83 18333
Wed Jul 15 12:16:21 2015 TCP   78.46.152.204 54172 =>     252.20.53.1 18333
Wed Jul 15 12:16:22 2015 TCP   78.46.152.204 54172 =>     252.20.53.1 18333
Wed Jul 15 12:16:24 2015 TCP   78.46.152.204 54172 =>     252.20.53.1 18333
Wed Jul 15 12:16:27 2015 TCP   78.46.152.204 39428 =>    252.20.54.37 18333
Wed Jul 15 12:16:07 2015 TCP   78.46.152.204 46868 =>    252.20.59.55 18333
Wed Jul 15 12:16:08 2015 TCP   78.46.152.204 46868 =>    252.20.59.55 18333
Wed Jul 15 12:16:38 2015 TCP   78.46.152.204 34084 =>     252.21.35.6 18333
Wed Jul 15 12:16:39 2015 TCP   78.46.152.204 34084 =>     252.21.35.6 18333
Wed Jul 15 12:16:41 2015 TCP   78.46.152.204 34084 =>     252.21.35.6 18333
Wed Jul 15 12:16:53 2015 TCP   78.46.152.204 34348 =>    252.21.51.22 18333
Wed Jul 15 12:16:56 2015 TCP   78.46.152.204 34348 =>    252.21.51.22 18333
Wed Jul 15 12:16:33 2015 TCP   78.46.152.204 39130 =>    252.21.53.64 18333
Wed Jul 15 12:16:34 2015 TCP   78.46.152.204 39130 =>    252.21.53.64 18333
Wed Jul 15 12:16:36 2015 TCP   78.46.152.204 39130 =>    252.21.53.64 18333
Wed Jul 15 12:18:15 2015 TCP   78.46.152.204 34630 =>      252.22.4.5 18333
Wed Jul 15 12:18:16 2015 TCP   78.46.152.204 34630 =>      252.22.4.5 18333
Wed Jul 15 12:18:18 2015 TCP   78.46.152.204 34630 =>      252.22.4.5 18333
Wed Jul 15 12:16:41 2015 TCP   78.46.152.204 57477 =>    252.22.15.47 18333
Wed Jul 15 12:16:44 2015 TCP   78.46.152.204 57477 =>    252.22.15.47 18333
Wed Jul 15 12:16:58 2015 TCP   78.46.152.204 47328 =>     252.23.35.8 18333
Wed Jul 15 12:17:02 2015 TCP   78.46.152.204 55135 =>    252.23.35.21 18333
Wed Jul 15 12:17:05 2015 TCP   78.46.152.204 55135 =>    252.23.35.21 18333
Wed Jul 15 12:17:31 2015 TCP   78.46.152.204 53226 =>    252.23.35.45 18333
Wed Jul 15 12:18:24 2015 TCP   78.46.152.204 38130 =>    252.23.38.80 18333
Wed Jul 15 12:18:25 2015 TCP   78.46.152.204 38130 =>    252.23.38.80 18333
Wed Jul 15 12:18:27 2015 TCP   78.46.152.204 38130 =>    252.23.38.80 18333
Wed Jul 15 12:16:39 2015 TCP   78.46.152.204 55887 =>    252.24.10.14 18333
Wed Jul 15 12:16:40 2015 TCP   78.46.152.204 55887 =>    252.24.10.14 18333
Wed Jul 15 12:16:42 2015 TCP   78.46.152.204 55887 =>    252.24.10.14 18333
Wed Jul 15 12:17:41 2015 TCP   78.46.152.204 37445 =>     252.24.12.2 18333
Wed Jul 15 12:17:44 2015 TCP   78.46.152.204 37445 =>     252.24.12.2 18333
Wed Jul 15 12:16:37 2015 TCP   78.46.152.204 36244 =>    252.25.37.29 18333
Wed Jul 15 12:16:08 2015 TCP   78.46.152.204 48319 =>    252.25.38.14 18333
Wed Jul 15 12:16:09 2015 TCP   78.46.152.204 48319 =>    252.25.38.14 18333
Wed Jul 15 12:16:11 2015 TCP   78.46.152.204 48319 =>    252.25.38.14 18333
Wed Jul 15 12:17:34 2015 TCP   78.46.152.204 43146 =>    252.25.50.73 18333
Wed Jul 15 12:17:36 2015 TCP   78.46.152.204 43146 =>    252.25.50.73 18333
Wed Jul 15 12:17:46 2015 TCP   78.46.152.204 42448 =>    252.26.17.24 18333
Wed Jul 15 12:17:47 2015 TCP   78.46.152.204 42448 =>    252.26.17.24 18333
Wed Jul 15 12:17:49 2015 TCP   78.46.152.204 42448 =>    252.26.17.24 18333
Wed Jul 15 12:17:01 2015 TCP   78.46.152.204 53942 =>    252.26.42.28 18333
Wed Jul 15 12:17:02 2015 TCP   78.46.152.204 53942 =>    252.26.42.28 18333
Wed Jul 15 12:17:04 2015 TCP   78.46.152.204 53942 =>    252.26.42.28 18333
Wed Jul 15 12:17:34 2015 TCP   78.46.152.204 54464 =>    252.26.58.29 18333
Wed Jul 15 12:16:34 2015 TCP   78.46.152.204 53436 =>   252.26.63.101 18333
Wed Jul 15 12:16:35 2015 TCP   78.46.152.204 53436 =>   252.26.63.101 18333
Wed Jul 15 12:16:37 2015 TCP   78.46.152.204 53436 =>   252.26.63.101 18333
Wed Jul 15 12:18:27 2015 TCP   78.46.152.204 58896 =>     252.27.8.66 18333
Wed Jul 15 12:18:03 2015 TCP   78.46.152.204 60298 =>   252.27.44.114 18333
Wed Jul 15 12:18:04 2015 TCP   78.46.152.204 60298 =>   252.27.44.114 18333
Wed Jul 15 12:16:18 2015 TCP   78.46.152.204 57203 =>    252.28.19.26 18333
Wed Jul 15 12:16:19 2015 TCP   78.46.152.204 57203 =>    252.28.19.26 18333
Wed Jul 15 12:16:21 2015 TCP   78.46.152.204 57203 =>    252.28.19.26 18333
Wed Jul 15 12:17:44 2015 TCP   78.46.152.204 35995 =>    252.28.19.68 18333
Wed Jul 15 12:18:04 2015 TCP   78.46.152.204 38428 =>    252.28.50.89 18333
Wed Jul 15 12:18:06 2015 TCP   78.46.152.204 38428 =>    252.28.50.89 18333
Wed Jul 15 12:17:18 2015 TCP   78.46.152.204 41098 =>    252.29.25.25 18333
Wed Jul 15 12:17:47 2015 TCP   78.46.152.204 41010 =>    252.29.45.32 18333
Wed Jul 15 12:18:06 2015 TCP   78.46.152.204 56881 =>     252.30.3.68 18333
Wed Jul 15 12:18:07 2015 TCP   78.46.152.204 56881 =>     252.30.3.68 18333
Wed Jul 15 12:18:09 2015 TCP   78.46.152.204 56881 =>     252.30.3.68 18333
Wed Jul 15 12:17:07 2015 TCP   78.46.152.204 48377 =>    252.30.19.62 18333
Wed Jul 15 12:17:08 2015 TCP   78.46.152.204 48377 =>    252.30.19.62 18333
Wed Jul 15 12:17:10 2015 TCP   78.46.152.204 48377 =>    252.30.19.62 18333
Wed Jul 15 12:17:03 2015 TCP   78.46.152.204 34366 =>    252.30.25.70 18333
Wed Jul 15 12:17:04 2015 TCP   78.46.152.204 34366 =>    252.30.25.70 18333
Wed Jul 15 12:17:06 2015 TCP   78.46.152.204 34366 =>    252.30.25.70 18333
Wed Jul 15 12:17:53 2015 TCP   78.46.152.204 43601 =>    252.30.28.26 18333
Wed Jul 15 12:17:54 2015 TCP   78.46.152.204 43601 =>    252.30.28.26 18333
Wed Jul 15 12:17:56 2015 TCP   78.46.152.204 43601 =>    252.30.28.26 18333
Wed Jul 15 12:16:21 2015 TCP   78.46.152.204 35414 =>    252.30.47.42 18333
Wed Jul 15 12:16:23 2015 TCP   78.46.152.204 35414 =>    252.30.47.42 18333
Wed Jul 15 12:18:24 2015 TCP   78.46.152.204 46802 =>     252.30.50.5 18333
Wed Jul 15 12:18:25 2015 TCP   78.46.152.204 46802 =>     252.30.50.5 18333
Wed Jul 15 12:18:06 2015 TCP   78.46.152.204 48850 =>   252.30.50.119 18333
Wed Jul 15 12:18:07 2015 TCP   78.46.152.204 48850 =>   252.30.50.119 18333
Wed Jul 15 12:18:09 2015 TCP   78.46.152.204 48850 =>   252.30.50.119 18333
Wed Jul 15 12:18:08 2015 TCP   78.46.152.204 36973 =>    252.31.50.39 18333
Wed Jul 15 12:18:09 2015 TCP   78.46.152.204 36973 =>    252.31.50.39 18333
Wed Jul 15 12:18:11 2015 TCP   78.46.152.204 36973 =>    252.31.50.39 18333
Wed Jul 15 12:18:20 2015 TCP   78.46.152.204 58651 =>    252.32.13.22 18333
Wed Jul 15 12:18:23 2015 TCP   78.46.152.204 58651 =>    252.32.13.22 18333
Wed Jul 15 12:16:20 2015 TCP   78.46.152.204 60975 =>    252.33.21.84 18333
Wed Jul 15 12:16:21 2015 TCP   78.46.152.204 60975 =>    252.33.21.84 18333
Wed Jul 15 12:16:23 2015 TCP   78.46.152.204 60975 =>    252.33.21.84 18333
Wed Jul 15 12:17:48 2015 TCP   78.46.152.204 59104 =>    252.33.45.95 18333
Wed Jul 15 12:17:49 2015 TCP   78.46.152.204 59104 =>    252.33.45.95 18333
Wed Jul 15 12:17:19 2015 TCP   78.46.152.204 56485 =>    252.35.14.43 18333
Wed Jul 15 12:17:21 2015 TCP   78.46.152.204 56485 =>    252.35.14.43 18333
Wed Jul 15 12:16:55 2015 TCP   78.46.152.204 41585 =>     252.35.28.5 18333
Wed Jul 15 12:16:57 2015 TCP   78.46.152.204 41585 =>     252.35.28.5 18333
Wed Jul 15 12:18:01 2015 TCP   78.46.152.204 33894 =>    252.35.49.32 18333
Wed Jul 15 12:18:04 2015 TCP   78.46.152.204 33894 =>    252.35.49.32 18333
Wed Jul 15 12:17:36 2015 TCP   78.46.152.204 40628 =>     252.36.37.5 18333
Wed Jul 15 12:17:37 2015 TCP   78.46.152.204 40628 =>     252.36.37.5 18333
Wed Jul 15 12:17:39 2015 TCP   78.46.152.204 40628 =>     252.36.37.5 18333
Wed Jul 15 12:16:15 2015 TCP   78.46.152.204 56838 =>   252.36.38.117 18333
Wed Jul 15 12:16:16 2015 TCP   78.46.152.204 56838 =>   252.36.38.117 18333
Wed Jul 15 12:16:18 2015 TCP   78.46.152.204 56838 =>   252.36.38.117 18333
Wed Jul 15 12:17:11 2015 TCP   78.46.152.204 44695 =>     252.36.46.3 18333
Wed Jul 15 12:17:12 2015 TCP   78.46.152.204 44695 =>     252.36.46.3 18333
Wed Jul 15 12:17:14 2015 TCP   78.46.152.204 44695 =>     252.36.46.3 18333
Wed Jul 15 12:16:24 2015 TCP   78.46.152.204 58828 =>    252.37.40.89 18333
Wed Jul 15 12:16:27 2015 TCP   78.46.152.204 58828 =>    252.37.40.89 18333
Wed Jul 15 12:17:08 2015 TCP   78.46.152.204 37109 =>     252.38.4.32 18333
Wed Jul 15 12:17:09 2015 TCP   78.46.152.204 37109 =>     252.38.4.32 18333
Wed Jul 15 12:17:11 2015 TCP   78.46.152.204 37109 =>     252.38.4.32 18333
Wed Jul 15 12:17:12 2015 TCP   78.46.152.204 36916 =>    252.38.12.15 18333
Wed Jul 15 12:17:13 2015 TCP   78.46.152.204 36916 =>    252.38.12.15 18333
Wed Jul 15 12:17:15 2015 TCP   78.46.152.204 36916 =>    252.38.12.15 18333
Wed Jul 15 12:16:49 2015 TCP   78.46.152.204 58965 =>    252.38.12.23 18333
Wed Jul 15 12:16:50 2015 TCP   78.46.152.204 58965 =>    252.38.12.23 18333
Wed Jul 15 12:16:41 2015 TCP   78.46.152.204 60385 =>    252.38.12.27 18333
Wed Jul 15 12:16:42 2015 TCP   78.46.152.204 60385 =>    252.38.12.27 18333
Wed Jul 15 12:16:29 2015 TCP   78.46.152.204 56434 =>    252.38.45.30 18333
Wed Jul 15 12:18:13 2015 TCP   78.46.152.204 46804 =>    252.38.45.88 18333
Wed Jul 15 12:18:14 2015 TCP   78.46.152.204 46804 =>    252.38.45.88 18333
Wed Jul 15 12:18:16 2015 TCP   78.46.152.204 46804 =>    252.38.45.88 18333
Wed Jul 15 12:17:04 2015 TCP   78.46.152.204 56820 =>    252.38.48.56 18333
Wed Jul 15 12:17:05 2015 TCP   78.46.152.204 56820 =>    252.38.48.56 18333
Wed Jul 15 12:17:07 2015 TCP   78.46.152.204 56820 =>    252.38.48.56 18333
Wed Jul 15 12:17:38 2015 TCP   78.46.152.204 36475 =>     252.39.0.34 18333
Wed Jul 15 12:17:39 2015 TCP   78.46.152.204 36475 =>     252.39.0.34 18333
Wed Jul 15 12:17:41 2015 TCP   78.46.152.204 36475 =>     252.39.0.34 18333
Wed Jul 15 12:18:06 2015 TCP   78.46.152.204 40528 =>   252.39.19.116 18333
Wed Jul 15 12:18:07 2015 TCP   78.46.152.204 40528 =>   252.39.19.116 18333
Wed Jul 15 12:18:09 2015 TCP   78.46.152.204 40528 =>   252.39.19.116 18333
  5. paveljanik commented at 8:43 AM on July 16, 2015: contributor

    Why do you want to communicate with such addresses?

    NetRange: 240.0.0.0 - 255.255.255.255 CIDR: 240.0.0.0/4 NetName: SPECIAL-IPV4-FUTURE-USE-IANA-RESERVED NetHandle: NET-240-0-0-0-0 Parent: () NetType: IANA Special Use OriginAS:
    Organization: Internet Assigned Numbers Authority (IANA) RegDate:
    Updated: 2013-08-30 Comment: Addresses starting with 240 or a higher number have not been allocated and should not be used, apart from 255.255.255.255, which is used for "limited broadcast" on a local network. Comment:
    Comment: This block was reserved by the IETF, the organization that develops Internet protocols, in the Standard document and in RFC 1112. The documents can be found at: Comment: http://datatracker.ietf.org/doc/rfc1112 Ref: http://whois.arin.net/rest/net/NET-240-0-0-0-0

  6. paveljanik commented at 8:44 AM on July 16, 2015: contributor

    ACK

  7. schildbach commented at 8:47 AM on July 16, 2015: contributor

    @paveljanik As I said, I just used sipa's crawler. Maybe it can be extended to exclude certain problematic address ranges, or addresses that throw up with certain kinds of TCP errors. I told my provider that the same can happen with lots of other protocols, for example I could try to write an email to user@252.0.25.3 and I think common MTAs will try to connect to 252.0.25.3.

  8. jonasschnelli commented at 8:54 AM on July 16, 2015: contributor

    @schildbach a quick and dirty solution to make your server center happy would be this commit https://github.com/jonasschnelli/bitcoin-seeder/commit/4abf94b12baa62b1da60c0129c754f3f20171268

    I had the same problem and hacked it down successfully with the patch above.

  9. laanwj added the label P2P on Jul 17, 2015
  10. sipa commented at 6:30 PM on July 17, 2015: member

    @jonasschnelli Please PR that?

  11. laanwj commented at 8:10 AM on July 18, 2015: member

    I'd strongly prefer the DNS seed to be fixed instead of removed. Though if you insist I'll merge this.

  12. schildbach commented at 8:31 AM on July 18, 2015: contributor

    Well the thing is Hetzner does not say in advance which IP addresses or ranges violate their policy. And they seemingly require a response time of just several hours (shorter than the average amount of sleep per night for sure). So I will not run the seeder again on this server.

  13. jonasschnelli commented at 8:50 AM on July 18, 2015: contributor

    @sipa: I'll try to open a PR (need to complete it with more invalid IP ranges). @schildbach: I can assure you with the patch above you want run into trouble with hetzner anymore. But yeah, if you have decided to stop the testnet seeder I'm can understand that.

    If there is need for more DNS seeders on testnet I can try to run another seeder on a different server.

  14. schildbach commented at 9:12 AM on July 18, 2015: contributor

    @jonasschnelli I have more reports from Hetzner. Shall I all send them to you?

  15. jonasschnelli commented at 11:31 AM on July 18, 2015: contributor

    @schildbach: Yes. Please. Let's sort this out. Please forward the mails to dev@jonasschnelli.ch

  16. schildbach commented at 12:06 PM on July 18, 2015: contributor

    @jonasschnelli I forwarded you all 4 reports I got.

  17. jonasschnelli commented at 6:47 PM on July 18, 2015: contributor

    I have updated the patch to avoid connecting to everything which is between 240.x.x.x and 255.255.255.255 in ipv4 space. This is now running on seed.bitcoin.jonasschnelli.ch. Let's see if Hetzner (datacenter provider) is happy with this. Will report back in some days (maybe @schildbach can do the same?).

  18. schildbach commented at 6:57 PM on July 18, 2015: contributor

    @jonasschnelli I'll wait on your report (-:

  19. jonasschnelli commented at 7:48 AM on July 19, 2015: contributor

    Blocking >= 240.x.x.x wasn't sufficient (got a abuse report this night). Reverted back to the original hack PLUS block above >= 240.x.x.x.

  20. schildbach commented at 7:54 AM on July 19, 2015: contributor

    I wonder if any of the IP addresses/ranges appear in some RFC document or specification as not to be used.

  21. jonasschnelli commented at 7:56 AM on July 19, 2015: contributor

    There is a paper: http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml. But following the ALLOCATED and LEGACY ranges will still end up in calling IP's which have no route.

  22. schildbach commented at 7:57 AM on July 19, 2015: contributor

    Ah, @paveljanik already linked it above: http://whois.arin.net/rest/net/NET-240-0-0-0-0 Is this block excluded from bitcoind as well?

  23. jonasschnelli commented at 7:59 AM on July 19, 2015: contributor

    As example, the IP 1.0.1.4 was in the abuse report. But the seeder fond some valid bitcoin clients at 1.9.178.82:8333, 1.23.96.69:8333, etc. (many more). Now how should we detect valid routes in 1.x.x.x range? Maybe just block 1.0.x.x but is there a definition what in the 1.x range is routable and what not?

  24. schildbach commented at 8:38 AM on July 19, 2015: contributor

    The approach of hardcoding single IP addresses is not scalable. I tried to explain that to Hetzner as well, but I don't think the support guy understood.

    I think we should identify blocks of IPs that are to be excluded by some form of specification (e.g. the 240.x.x.x block). These rules should then go into the seeder and bitcoind, because they are useful to anyone.

    Any other IPs reported by Hetzner we should ask them how we should know we should not connect them without trying in the first place. (I did that but didn't get a reply – maybe we need to be more people.)

  25. jonasschnelli commented at 9:07 AM on July 20, 2015: contributor

    Hmm... they just shut down my server (where the dns seed was running). Portscans are forbidden by the TOC. And i have to admit bitcoin-seeders ip collecting can be seen as a portscan. Any good ideas how to prevent/patch the seeder so that it won't be interpreted as portscan?

    1. Would it be possible over TOR?
    2. Maybe crawl in local home/office connection (no portscan rules) and upload the database to the seed server?
  26. jonasschnelli commented at 12:19 PM on July 20, 2015: contributor

    @schildbach: I'm now testing https://github.com/sipa/bitcoin-seeder/pull/29 (Tor ipv4 proxy). Ipv6 still connectes direct but i couldn't find any ipv6 addresses in the abuse report. Will report back in about 1-2day if this solution works.

  27. ajweiss commented at 6:48 PM on July 20, 2015: contributor

    At the very least, these netblocks should be filtered:

    https://en.wikipedia.org/wiki/Reserved_IP_addresses

    As for other bogon ranges that are just merely unassigned, not currently routable, etc, it would be more complicated as those lists change frequently:

    http://www.team-cymru.org/bogon-reference.html

    These could, however, be queried daily by an updated seeder that downloads and respects these lists. (This, of course, does introduce a single point of censor though...)

  28. jgarzik commented at 7:05 PM on July 23, 2015: contributor

    ACK

  29. jonasschnelli commented at 7:07 PM on July 23, 2015: contributor

    Running the seeder with a tor ipv4 proxy (https://github.com/sipa/bitcoin-seeder/pull/29) for about 3 days now. No abuse reports since then. I can recommend this setup for @schildbach if he likes to keep the testnet seeder. Setup is done within 5mins.

  30. schildbach commented at 7:33 PM on July 23, 2015: contributor

    Hm, apart from the fact that this is "just" testnet, does this still count as an independant seeder? I mean with this setup basically the Tor exit nodes control the seeder, right?

  31. jonasschnelli commented at 7:40 PM on July 23, 2015: contributor

    Right. Either you trust your Tor exit nodes OR your ISP/Datacenter provider because the P2P crawling goes obviously over unencrypted port ~8333. It's your choice. :)

  32. laanwj commented at 12:38 PM on July 27, 2015: member

    Hm, apart from the fact that this is "just" testnet, does this still count as an independant seeder? I mean with this setup basically the Tor exit nodes control the seeder, right?

    I do think this is a good point. If a seeder 'scans' over Tor, the exit nodes decide the view of the network. If multiple seeders switch to Tor, they would be pretty much equivalent.

    Even then, for redundancy reasons it can still make sense to have them available though!

    Also at least in the case of Tor there is no single entity that decides the network connectivity. One malicious exit node will only cause intermittent issues.

  33. schildbach commented at 2:00 PM on July 29, 2015: contributor

    I'm going to give it another try with the new seeder version. @jonasschnelli Can you give an example for Tor usage? I've never used Tor and have no idea what would be a valid proxy address.

    In any case, thanks for help!

  34. schildbach closed this on Jul 29, 2015
  35. jonasschnelli commented at 2:04 PM on July 29, 2015: contributor 
    sudo aptitude install tor
sudo /etc/init.d/tor status
./dnsseed -p 5353 -t 10 -i 127.0.0.1:9050 -h seed.bitcoin.jonasschnelli.ch -n bitcoin.jonasschnelli.ch

    You maybe wan't to play with the -t arg (parallel threads).

    check the tor log (should report error or successful connections): sudo tail /var/log/tor/log

  36. jonasschnelli commented at 2:06 PM on July 29, 2015: contributor

    After building first make sure your seeder supports the -i arg by ./dnsseed -?.

  37. schildbach deleted the branch on Aug 31, 2015
  38. MarcoFalke locked this on Sep 8, 2021
Contributors
schildbachluke-jrpaveljanikjonasschnellisipalaanwjajweissjgarzik
Labels
P2P
github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-22 21:15 UTC
This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me