مشکل نت اسکن در سرور مجازی

سلام خدمت دوستان
بنده یه سرور مجازی دارم که روش وی پی ان cisco و CWP نصبه و وبسایتم 1 گیگ دیتابیس داره که خیلی مصرف cpu بالاست و الان دوبارپس از عوض کردن سرور ابیوز نت اسکن برام اومده و سرورم رو هم عوض کردم ولی رفع نشد . از زمانی که دیتایسم حجیم شده این مشکلات پیشاومده .
دوستان راه حلی دارین؟

نقل قول:

---

################################################## ######################### Netscan detected from host 188.40.164.221 #
################################################## ########################


time protocol src_ip src_port dest_ip dest_port
---------------------------------------------------------------------------
Thu May 10 06:17:35 2018 TCP 188.40.164.221 34647 => 192.168.1.2 7
Thu May 10 06:17:35 2018 TCP 188.40.164.221 33525 => 192.168.1.3 7
Thu May 10 06:17:35 2018 TCP 188.40.164.221 50470 => 192.168.1.4 7
Thu May 10 06:17:35 2018 TCP 188.40.164.221 57225 => 192.168.1.5 7
Thu May 10 06:17:35 2018 TCP 188.40.164.221 60956 => 192.168.1.6 7
Thu May 10 06:17:35 2018 TCP 188.40.164.221 57395 => 192.168.1.7 7
Thu May 10 06:17:35 2018 TCP 188.40.164.221 48058 => 192.168.1.8 7
Thu May 10 06:17:35 2018 TCP 188.40.164.221 45033 => 192.168.1.9 7
Thu May 10 06:17:35 2018 TCP 188.40.164.221 39218 => 192.168.1.10 7
Thu May 10 06:17:35 2018 TCP 188.40.164.221 60144 => 192.168.1.11 7
Thu May 10 06:17:36 2018 TCP 188.40.164.221 43665 => 192.168.1.12 7
Thu May 10 06:17:36 2018 TCP 188.40.164.221 34644 => 192.168.1.13 7
Thu May 10 06:17:36 2018 TCP 188.40.164.221 59630 => 192.168.1.14 7
Thu May 10 06:17:36 2018 TCP 188.40.164.221 54768 => 192.168.1.15 7
Thu May 10 06:17:36 2018 TCP 188.40.164.221 60775 => 192.168.1.16 7
Thu May 10 06:17:36 2018 TCP 188.40.164.221 53326 => 192.168.1.17 7
Thu May 10 06:17:36 2018 TCP 188.40.164.221 46675 => 192.168.1.18 7
Thu May 10 06:17:36 2018 TCP 188.40.164.221 52998 => 192.168.1.19 7
Thu May 10 06:17:36 2018 TCP 188.40.164.221 40987 => 192.168.1.20 7
Thu May 10 06:17:36 2018 TCP 188.40.164.221 53949 => 192.168.1.21 7
Thu May 10 06:17:36 2018 TCP 188.40.164.221 60305 => 192.168.1.22 7
Thu May 10 06:17:36 2018 TCP 188.40.164.221 39878 => 192.168.1.23 7
Thu May 10 06:17:36 2018 TCP 188.40.164.221 56589 => 192.168.1.24 7
Thu May 10 06:17:37 2018 TCP 188.40.164.221 33987 => 192.168.1.25 7
Thu May 10 06:17:37 2018 TCP 188.40.164.221 40860 => 192.168.1.26 7
Thu May 10 06:17:37 2018 TCP 188.40.164.221 39924 => 192.168.1.27 7
Thu May 10 06:17:37 2018 TCP 188.40.164.221 39463 => 192.168.1.28 7
Thu May 10 06:17:37 2018 TCP 188.40.164.221 49577 => 192.168.1.29 7
Thu May 10 06:17:37 2018 TCP 188.40.164.221 43411 => 192.168.1.30 7
Thu May 10 06:17:37 2018 TCP 188.40.164.221 41756 => 192.168.1.31 7
Thu May 10 06:17:37 2018 TCP 188.40.164.221 34792 => 192.168.1.32 7
Thu May 10 06:17:37 2018 TCP 188.40.164.221 41328 => 192.168.1.33 7
Thu May 10 06:17:37 2018 TCP 188.40.164.221 39968 => 192.168.1.34 7
Thu May 10 06:17:37 2018 TCP 188.40.164.221 59191 => 192.168.1.35 7
Thu May 10 06:17:37 2018 TCP 188.40.164.221 36344 => 192.168.1.37 7
Thu May 10 06:17:37 2018 TCP 188.40.164.221 56107 => 192.168.1.38 7
Thu May 10 06:17:37 2018 TCP 188.40.164.221 53080 => 192.168.1.39 7
Thu May 10 06:17:37 2018 TCP 188.40.164.221 39056 => 192.168.1.40 7
Thu May 10 06:17:37 2018 TCP 188.40.164.221 49942 => 192.168.1.41 7
Thu May 10 06:17:38 2018 TCP 188.40.164.221 53285 => 192.168.1.42 7
Thu May 10 06:17:38 2018 TCP 188.40.164.221 45723 => 192.168.1.43 7
Thu May 10 06:17:38 2018 TCP 188.40.164.221 41018 => 192.168.1.44 7
Thu May 10 06:17:38 2018 TCP 188.40.164.221 51238 => 192.168.1.45 7
Thu May 10 06:17:38 2018 TCP 188.40.164.221 33615 => 192.168.1.46 7
Thu May 10 06:17:38 2018 TCP 188.40.164.221 52963 => 192.168.1.47 7
Thu May 10 06:17:38 2018 TCP 188.40.164.221 54910 => 192.168.1.48 7
Thu May 10 06:17:38 2018 TCP 188.40.164.221 43330 => 192.168.1.49 7
Thu May 10 06:17:38 2018 TCP 188.40.164.221 47495 => 192.168.1.50 7
Thu May 10 06:17:38 2018 TCP 188.40.164.221 42665 => 192.168.1.51 7
Thu May 10 06:17:38 2018 TCP 188.40.164.221 51145 => 192.168.1.52 7
Thu May 10 06:17:38 2018 TCP 188.40.164.221 58907 => 192.168.1.53 7
Thu May 10 06:17:38 2018 TCP 188.40.164.221 47501 => 192.168.1.54 7
Thu May 10 06:17:38 2018 TCP 188.40.164.221 33772 => 192.168.1.55 7
Thu May 10 06:17:38 2018 TCP 188.40.164.221 59096 => 192.168.1.56 7
Thu May 10 06:17:38 2018 TCP 188.40.164.221 40726 => 192.168.1.57 7
Thu May 10 06:17:38 2018 TCP 188.40.164.221 45757 => 192.168.1.58 7
Thu May 10 06:17:38 2018 TCP 188.40.164.221 48736 => 192.168.1.59 7
Thu May 10 06:17:39 2018 TCP 188.40.164.221 52760 => 192.168.1.60 7
Thu May 10 06:17:39 2018 TCP 188.40.164.221 55887 => 192.168.1.61 7
Thu May 10 06:17:39 2018 TCP 188.40.164.221 41248 => 192.168.1.62 7
Thu May 10 06:17:43 2018 TCP 188.40.164.221 47715 => 192.168.1.63 7
Thu May 10 06:17:43 2018 TCP 188.40.164.221 41975 => 192.168.1.64 7
Thu May 10 06:17:43 2018 TCP 188.40.164.221 58226 => 192.168.1.65 7
Thu May 10 06:17:43 2018 TCP 188.40.164.221 58276 => 192.168.1.66 7
Thu May 10 06:17:43 2018 TCP 188.40.164.221 58474 => 192.168.1.67 7
Thu May 10 06:17:43 2018 TCP 188.40.164.221 35946 => 192.168.1.68 7
Thu May 10 06:17:43 2018 TCP 188.40.164.221 40755 => 192.168.1.69 7
Thu May 10 06:17:43 2018 TCP 188.40.164.221 36760 => 192.168.1.70 7
Thu May 10 06:17:43 2018 TCP 188.40.164.221 37093 => 192.168.1.71 7
Thu May 10 06:17:43 2018 TCP 188.40.164.221 58266 => 192.168.1.72 7
Thu May 10 06:17:44 2018 TCP 188.40.164.221 50795 => 192.168.1.73 7
Thu May 10 06:17:44 2018 TCP 188.40.164.221 57847 => 192.168.1.74 7
Thu May 10 06:17:44 2018 TCP 188.40.164.221 52370 => 192.168.1.75 7
Thu May 10 06:17:44 2018 TCP 188.40.164.221 53710 => 192.168.1.76 7
Thu May 10 06:17:44 2018 TCP 188.40.164.221 35308 => 192.168.1.77 7
Thu May 10 06:17:44 2018 TCP 188.40.164.221 59954 => 192.168.1.78 7
Thu May 10 06:17:44 2018 TCP 188.40.164.221 57128 => 192.168.1.79 7
Thu May 10 06:17:44 2018 TCP 188.40.164.221 41628 => 192.168.1.80 7
Thu May 10 06:17:44 2018 TCP 188.40.164.221 59060 => 192.168.1.81 7
Thu May 10 06:17:44 2018 TCP 188.40.164.221 38251 => 192.168.1.82 7
Thu May 10 06:17:44 2018 TCP 188.40.164.221 54721 => 192.168.1.83 7
Thu May 10 06:17:44 2018 TCP 188.40.164.221 34023 => 192.168.1.84 7
Thu May 10 06:17:44 2018 TCP 188.40.164.221 36758 => 192.168.1.85 7
Thu May 10 06:17:44 2018 TCP 188.40.164.221 35548 => 192.168.1.86 7
Thu May 10 06:17:44 2018 TCP 188.40.164.221 45664 => 192.168.1.87 7
Thu May 10 06:17:44 2018 TCP 188.40.164.221 58083 => 192.168.1.88 7
Thu May 10 06:17:44 2018 TCP 188.40.164.221 42510 => 192.168.1.89 7
Thu May 10 06:17:44 2018 TCP 188.40.164.221 59313 => 192.168.1.90 7
Thu May 10 06:17:44 2018 TCP 188.40.164.221 57425 => 192.168.1.91 7
Thu May 10 06:17:44 2018 TCP 188.40.164.221 38252 => 192.168.1.92 7
Thu May 10 06:17:45 2018 TCP 188.40.164.221 47571 => 192.168.1.93 7
Thu May 10 06:17:45 2018 TCP 188.40.164.221 35060 => 192.168.1.94 7
Thu May 10 06:17:45 2018 TCP 188.40.164.221 54990 => 192.168.1.95 7
Thu May 10 06:17:45 2018 TCP 188.40.164.221 53298 => 192.168.1.96 7
Thu May 10 06:17:45 2018 TCP 188.40.164.221 57762 => 192.168.1.97 7
Thu May 10 06:17:45 2018 TCP 188.40.164.221 49425 => 192.168.1.98 7
Thu May 10 06:17:45 2018 TCP 188.40.164.221 33470 => 192.168.1.99 7
Thu May 10 06:17:45 2018 TCP 188.40.164.221 46708 => 192.168.1.100 7
Thu May 10 06:17:45 2018 TCP 188.40.164.221 55733 => 192.168.1.101 7
Thu May 10 06:17:45 2018 TCP 188.40.164.221 52422 => 192.168.1.102 7
Thu May 10 06:17:39 2018 TCP 188.40.164.221 46980 => 10.10.34.35 443
Thu May 10 06:17:39 2018 TCP 188.40.164.221 46981 => 10.10.34.35 443
Thu May 10 06:17:39 2018 TCP 188.40.164.221 46982 => 10.10.34.35 443
Thu May 10 06:17:40 2018 TCP 188.40.164.221 46980 => 10.10.34.35 443
Thu May 10 06:17:40 2018 TCP 188.40.164.221 46981 => 10.10.34.35 443
Thu May 10 06:17:40 2018 TCP 188.40.164.221 46982 => 10.10.34.35 443
Thu May 10 06:17:42 2018 TCP 188.40.164.221 46980 => 10.10.34.35 443
Thu May 10 06:17:42 2018 TCP 188.40.164.221 46981 => 10.10.34.35 443
Thu May 10 06:17:42 2018 TCP 188.40.164.221 46982 => 10.10.34.35 443
Thu May 10 06:17:37 2018 UDP 188.40.164.221 36912 => 192.168.1.36 137
Thu May 10 06:17:40 2018 UDP 188.40.164.221 36912 => 192.168.1.36 137

---

نقل قول:

---

################################################## ######################### Netscan detected from host 88.99.150.58 #
################################################## ########################


time protocol src_ip src_port dest_ip dest_port
---------------------------------------------------------------------------
Mon May 7 23:34:35 2018 TCP 88.99.150.58 58309 => 192.168.1.2 7
Mon May 7 23:34:35 2018 TCP 88.99.150.58 57189 => 192.168.1.3 7
Mon May 7 23:34:35 2018 TCP 88.99.150.58 45903 => 192.168.1.4 7
Mon May 7 23:34:35 2018 TCP 88.99.150.58 52656 => 192.168.1.5 7
Mon May 7 23:34:35 2018 TCP 88.99.150.58 56387 => 192.168.1.6 7
Mon May 7 23:34:35 2018 TCP 88.99.150.58 52829 => 192.168.1.7 7
Mon May 7 23:34:35 2018 TCP 88.99.150.58 43489 => 192.168.1.8 7
Mon May 7 23:34:35 2018 TCP 88.99.150.58 40465 => 192.168.1.9 7
Mon May 7 23:34:35 2018 TCP 88.99.150.58 34649 => 192.168.1.10 7
Mon May 7 23:34:35 2018 TCP 88.99.150.58 55571 => 192.168.1.11 7
Mon May 7 23:34:35 2018 TCP 88.99.150.58 39095 => 192.168.1.12 7
Mon May 7 23:34:35 2018 TCP 88.99.150.58 58307 => 192.168.1.13 7
Mon May 7 23:34:35 2018 TCP 88.99.150.58 55065 => 192.168.1.14 7
Mon May 7 23:34:35 2018 TCP 88.99.150.58 50198 => 192.168.1.15 7
Mon May 7 23:34:35 2018 TCP 88.99.150.58 56205 => 192.168.1.16 7
Mon May 7 23:34:35 2018 TCP 88.99.150.58 48758 => 192.168.1.17 7
Mon May 7 23:34:35 2018 TCP 88.99.150.58 42106 => 192.168.1.18 7
Mon May 7 23:34:35 2018 TCP 88.99.150.58 48430 => 192.168.1.19 7
Mon May 7 23:34:35 2018 TCP 88.99.150.58 36417 => 192.168.1.20 7
Mon May 7 23:34:35 2018 TCP 88.99.150.58 49376 => 192.168.1.21 7
Mon May 7 23:34:36 2018 TCP 88.99.150.58 55736 => 192.168.1.22 7
Mon May 7 23:34:36 2018 TCP 88.99.150.58 35307 => 192.168.1.23 7
Mon May 7 23:34:36 2018 TCP 88.99.150.58 52019 => 192.168.1.24 7
Mon May 7 23:34:36 2018 TCP 88.99.150.58 57649 => 192.168.1.25 7
Mon May 7 23:34:36 2018 TCP 88.99.150.58 36287 => 192.168.1.26 7
Mon May 7 23:34:36 2018 TCP 88.99.150.58 35356 => 192.168.1.27 7
Mon May 7 23:34:36 2018 TCP 88.99.150.58 34894 => 192.168.1.28 7
Mon May 7 23:34:36 2018 TCP 88.99.150.58 45008 => 192.168.1.29 7
Mon May 7 23:34:36 2018 TCP 88.99.150.58 38842 => 192.168.1.30 7
Mon May 7 23:34:36 2018 TCP 88.99.150.58 37185 => 192.168.1.31 7
Mon May 7 23:34:37 2018 TCP 88.99.150.58 58452 => 192.168.1.32 7
Mon May 7 23:34:37 2018 TCP 88.99.150.58 36764 => 192.168.1.33 7
Mon May 7 23:34:37 2018 TCP 88.99.150.58 35402 => 192.168.1.34 7
Mon May 7 23:34:37 2018 TCP 88.99.150.58 54624 => 192.168.1.35 7
Mon May 7 23:34:37 2018 TCP 88.99.150.58 46216 => 192.168.1.36 7
Mon May 7 23:34:37 2018 TCP 88.99.150.58 60004 => 192.168.1.37 7
Mon May 7 23:34:37 2018 TCP 88.99.150.58 51545 => 192.168.1.38 7
Mon May 7 23:34:37 2018 TCP 88.99.150.58 48509 => 192.168.1.39 7
Mon May 7 23:34:37 2018 TCP 88.99.150.58 34482 => 192.168.1.40 7
Mon May 7 23:34:37 2018 TCP 88.99.150.58 45366 => 192.168.1.41 7
Mon May 7 23:34:37 2018 TCP 88.99.150.58 48715 => 192.168.1.42 7
Mon May 7 23:34:37 2018 TCP 88.99.150.58 41152 => 192.168.1.43 7
Mon May 7 23:34:37 2018 TCP 88.99.150.58 36449 => 192.168.1.44 7
Mon May 7 23:34:37 2018 TCP 88.99.150.58 46676 => 192.168.1.45 7
Mon May 7 23:34:37 2018 TCP 88.99.150.58 57279 => 192.168.1.46 7
Mon May 7 23:34:37 2018 TCP 88.99.150.58 48387 => 192.168.1.47 7
Mon May 7 23:34:37 2018 TCP 88.99.150.58 50339 => 192.168.1.48 7
Mon May 7 23:34:37 2018 TCP 88.99.150.58 38764 => 192.168.1.49 7
Mon May 7 23:34:37 2018 TCP 88.99.150.58 42920 => 192.168.1.50 7
Mon May 7 23:34:37 2018 TCP 88.99.150.58 38094 => 192.168.1.51 7
Mon May 7 23:34:38 2018 TCP 88.99.150.58 46580 => 192.168.1.52 7
Mon May 7 23:34:38 2018 TCP 88.99.150.58 54337 => 192.168.1.53 7
Mon May 7 23:34:38 2018 TCP 88.99.150.58 42931 => 192.168.1.54 7
Mon May 7 23:34:38 2018 TCP 88.99.150.58 57438 => 192.168.1.55 7
Mon May 7 23:34:38 2018 TCP 88.99.150.58 54530 => 192.168.1.56 7
Mon May 7 23:34:38 2018 TCP 88.99.150.58 36154 => 192.168.1.57 7
Mon May 7 23:34:38 2018 TCP 88.99.150.58 41188 => 192.168.1.58 7
Mon May 7 23:34:38 2018 TCP 88.99.150.58 44161 => 192.168.1.59 7
Mon May 7 23:34:38 2018 TCP 88.99.150.58 48188 => 192.168.1.60 7
Mon May 7 23:34:38 2018 TCP 88.99.150.58 51311 => 192.168.1.61 7
Mon May 7 23:34:38 2018 TCP 88.99.150.58 36680 => 192.168.1.62 7
Mon May 7 23:34:57 2018 TCP 88.99.150.58 43130 => 192.168.1.63 7
Mon May 7 23:34:57 2018 TCP 88.99.150.58 37398 => 192.168.1.64 7
Mon May 7 23:34:57 2018 TCP 88.99.150.58 53644 => 192.168.1.65 7
Mon May 7 23:34:57 2018 TCP 88.99.150.58 53688 => 192.168.1.66 7
Mon May 7 23:34:57 2018 TCP 88.99.150.58 53889 => 192.168.1.67 7
Mon May 7 23:34:57 2018 TCP 88.99.150.58 59602 => 192.168.1.68 7
Mon May 7 23:34:57 2018 TCP 88.99.150.58 36170 => 192.168.1.69 7
Mon May 7 23:34:57 2018 TCP 88.99.150.58 60403 => 192.168.1.70 7
Mon May 7 23:34:57 2018 TCP 88.99.150.58 60741 => 192.168.1.71 7
Mon May 7 23:34:57 2018 TCP 88.99.150.58 53680 => 192.168.1.72 7
Mon May 7 23:35:08 2018 TCP 88.99.150.58 46220 => 192.168.1.73 7
Mon May 7 23:35:08 2018 TCP 88.99.150.58 53267 => 192.168.1.74 7
Mon May 7 23:35:08 2018 TCP 88.99.150.58 47793 => 192.168.1.75 7
Mon May 7 23:35:08 2018 TCP 88.99.150.58 49127 => 192.168.1.76 7
Mon May 7 23:35:08 2018 TCP 88.99.150.58 58955 => 192.168.1.77 7
Mon May 7 23:35:08 2018 TCP 88.99.150.58 55361 => 192.168.1.78 7
Mon May 7 23:35:08 2018 TCP 88.99.150.58 52541 => 192.168.1.79 7
Mon May 7 23:35:08 2018 TCP 88.99.150.58 37046 => 192.168.1.80 7
Mon May 7 23:35:08 2018 TCP 88.99.150.58 54471 => 192.168.1.81 7
Mon May 7 23:35:08 2018 TCP 88.99.150.58 33663 => 192.168.1.82 7
Mon May 7 23:35:09 2018 TCP 88.99.150.58 50137 => 192.168.1.83 7
Mon May 7 23:35:37 2018 TCP 88.99.150.58 50137 => 192.168.1.83 7
Mon May 7 23:35:09 2018 TCP 88.99.150.58 57670 => 192.168.1.84 7
Mon May 7 23:35:37 2018 TCP 88.99.150.58 57670 => 192.168.1.84 7
Mon May 7 23:35:09 2018 TCP 88.99.150.58 60403 => 192.168.1.85 7
Mon May 7 23:35:09 2018 TCP 88.99.150.58 59200 => 192.168.1.86 7
Mon May 7 23:35:09 2018 TCP 88.99.150.58 41081 => 192.168.1.87 7
Mon May 7 23:35:09 2018 TCP 88.99.150.58 53494 => 192.168.1.88 7
Mon May 7 23:35:09 2018 TCP 88.99.150.58 37933 => 192.168.1.89 7
Mon May 7 23:35:37 2018 TCP 88.99.150.58 37933 => 192.168.1.89 7
Mon May 7 23:35:09 2018 TCP 88.99.150.58 54725 => 192.168.1.90 7
Mon May 7 23:35:37 2018 TCP 88.99.150.58 54725 => 192.168.1.90 7
Mon May 7 23:35:09 2018 TCP 88.99.150.58 52844 => 192.168.1.91 7
Mon May 7 23:35:09 2018 TCP 88.99.150.58 33669 => 192.168.1.92 7
Mon May 7 23:35:37 2018 TCP 88.99.150.58 33669 => 192.168.1.92 7
Mon May 7 23:35:37 2018 TCP 88.99.150.58 42983 => 192.168.1.93 7
Mon May 7 23:35:37 2018 TCP 88.99.150.58 58704 => 192.168.1.94 7
Mon May 7 23:35:37 2018 TCP 88.99.150.58 50409 => 192.168.1.95 7
Mon May 7 23:35:37 2018 TCP 88.99.150.58 48720 => 192.168.1.96 7
Mon May 7 23:35:37 2018 TCP 88.99.150.58 53173 => 192.168.1.97 7
Mon May 7 23:35:37 2018 TCP 88.99.150.58 44841 => 192.168.1.98 7
Mon May 7 23:35:37 2018 TCP 88.99.150.58 57125 => 192.168.1.99 7
Mon May 7 23:35:37 2018 TCP 88.99.150.58 42124 => 192.168.1.100 7
Mon May 7 23:35:37 2018 TCP 88.99.150.58 51146 => 192.168.1.101 7

---

سیسکو رو غیرفعال کنید ویا سرور از دیتاسنتر غیر هتزنر تهیه کنید

راه حل دیگه ای هست که بشه سیسکو هم روش باشه چون نیاز دارم بهش؟

باسلام .

روي بلاك آي پي هست يا تك آِي پي ؟

این ابیوز ها اتوماتیک ارسال میشه و به این رنج آیپی ها bogon IP میگن که شامل
192.168.0.0/16
10.0.0.0/8
100.64.0.0/10
127.0.0.0/8
169.254.0.0/16
172.16.0.0/12
192.0.0.0/24
192.0.2.0/24
198.18.0.0/15
198.51.100.0/24
203.0.113.0/24
224.0.0.0/3


بر اساس پروتکل های شبکه و قوانین شبکه این آیپی ها داخل اینترنت غیر قابل دسترس هستند و عملا روتی براشون وجود نداره

این ابیوز بخاطر این هست که کلاینت شما خواسته به آیپی های داخل شبکه خودش وصل بشه
188.40.164.221 46980 => 10.10.34.35 443
مثلا این 10.10.34.36 آدرس معروفی هست

کافیه ایمیل بدید که چرا این ابیوز الکی برای شما اومده
اگر هم فایروال دارید این رنج آیپی هارو ببندید

نقل قول:

---

نوشته اصلی توسط mizbanwebhost

باسلام . روي بلاك آي پي هست يا تك آِي پي ؟

---

سلام روی تک ایپیهست

- - - Updated - - -

نقل قول:

---

نوشته اصلی توسط NetworkFA

این ابیوز ها اتوماتیک ارسال میشه و به این رنج آیپی ها bogon IP میگن که شامل
192.168.0.0/16
10.0.0.0/8
100.64.0.0/10
127.0.0.0/8
169.254.0.0/16
172.16.0.0/12
192.0.0.0/24
192.0.2.0/24
198.18.0.0/15
198.51.100.0/24
203.0.113.0/24
224.0.0.0/3


بر اساس پروتکل های شبکه و قوانین شبکه این آیپی ها داخل اینترنت غیر قابل دسترس هستند و عملا روتی براشون وجود نداره

این ابیوز بخاطر این هست که کلاینت شما خواسته به آیپی های داخل شبکه خودش وصل بشه
188.40.164.221 46980 => 10.10.34.35 443
مثلا این 10.10.34.36 آدرس معروفی هست

کافیه ایمیل بدید که چرا این ابیوز الکی برای شما اومده
اگر هم فایروال دارید این رنج آیپی هارو ببندید

---

اگر ببندم مشکلی برای بازدید کاربران از سایت یا وی پی ان پیش نمیاد؟

چند وقت پیش برای بنده هم اومد و من جواب زیر رو دادم خودشون تیکت برو بستن

these are Bogon IPs which are not accessible from Internet network
Why we receive abuse for these IPs?

سلام . میتونید از فایروال میکروتیک جهت هندل این مدل ابیوز ها استفاده کنید .