Не вижу лог от iptables что меня пинганули

[_art_]

Привет.

IP динамический, попросил товарища пингануть себя. Пинг прошёл, однако логов в /var/log/syslog не увидел.

Правила только такие, других не писал ввиду непонятности ситуации:
# Log any incoming ping
iptables -A INPUT -p icmp --icmp-type 8 -j LOG --log-prefix "Iptables: Ping detected: "
iptables -A INPUT -p icmp --icmp-type 8 -j ACCEPT

Вопрос: почему нету в логах данных о пинге ? ISP режет это ?

[fisher74]

а tcpdump что на это говорит?

... и было бы неплохо всю цепочку INPUT показать... да и PREROUTING...
короче sudo iptables-save в студию

[_art_]

tcpdump:

(Нажмите, чтобы показать/скрыть)

14:54:59.260516 IP msnbot-65-52-108-74.search.msn.com.https > 192.168.0.102.55798: Flags [P.], seq 24443718:24444203, ack 4058097780, win 8192, options [nop,nop,TS val 115949882 ecr 953273], length 485
14:54:59.260604 IP 192.168.0.102.55798 > msnbot-65-52-108-74.search.msn.com.https: Flags [.], ack 485, win 1441, options [nop,nop,TS val 954730 ecr 115949882], length 0
14:54:59.808922 IP 192.168.0.102.61042 > 85.116.126.126.domain: 18358+ PTR? 102.0.168.192.in-addr.arpa. (44)
14:54:59.819512 IP 85.116.126.126.domain > 192.168.0.102.61042: 18358 NXDomain* 0/1/0 (93)
14:54:59.820139 IP 192.168.0.102.21040 > 85.116.126.126.domain: 28662+ PTR? 74.108.52.65.in-addr.arpa. (43)
14:54:59.832305 IP 85.116.126.126.domain > 192.168.0.102.21040: 28662 1/0/0 PTR msnbot-65-52-108-74.search.msn.com. (91)
14:55:00.515957 IP 192.168.0.102.51971 > la-in-f101.1e100.net.http: Flags [.], ack 3591219139, win 264, options [nop,nop,TS val 955044 ecr 4157311790], length 0
14:55:00.563741 IP la-in-f101.1e100.net.http > 192.168.0.102.51971: Flags [.], ack 1, win 358, options [nop,nop,TS val 4157321854 ecr 942482], length 0
14:55:00.807838 IP 192.168.0.102.46953 > 85.116.126.126.domain: 10109+ PTR? 126.126.116.85.in-addr.arpa. (45)
14:55:00.817909 IP 85.116.126.126.domain > 192.168.0.102.46953: 10109 NXDomain 0/1/0 (105)
14:55:00.818237 IP 192.168.0.102.47450 > 85.116.126.126.domain: 39681+ PTR? 101.143.125.74.in-addr.arpa. (45)
14:55:00.828021 IP 85.116.126.126.domain > 192.168.0.102.47450: 39681 1/0/0 PTR la-in-f101.1e100.net. (79)
14:55:00.861997 IP ec2-52-11-218-52.us-west-2.compute.amazonaws.com.https > 192.168.0.102.40380: Flags [P.], seq 3000220601:3000220632, ack 2594705233, win 80, options [nop,nop,TS val 665615641 ecr 939929], length 31
14:55:00.862233 IP 192.168.0.102.40380 > ec2-52-11-218-52.us-west-2.compute.amazonaws.com.https: Flags [F.], seq 1, ack 31, win 319, options [nop,nop,TS val 955130 ecr 665615641], length 0
14:55:01.086213 IP ec2-52-11-218-52.us-west-2.compute.amazonaws.com.https > 192.168.0.102.40380: Flags [F.], seq 31, ack 2, win 80, options [nop,nop,TS val 665615697 ecr 955130], length 0
14:55:01.086294 IP 192.168.0.102.40380 > ec2-52-11-218-52.us-west-2.compute.amazonaws.com.https: Flags [.], ack 32, win 319, options [nop,nop,TS val 955186 ecr 665615697], length 0
14:55:01.808331 IP 192.168.0.102.16384 > 85.116.126.126.domain: 14766+ PTR? 52.218.11.52.in-addr.arpa. (43)
14:55:01.893271 IP 85.116.126.126.domain > 192.168.0.102.16384: 14766 1/0/0 PTR ec2-52-11-218-52.us-west-2.compute.amazonaws.com. (105)
14:55:02.560906 IP 5.141.89.191.46334 > 192.168.0.102.6584: UDP, length 111
14:55:02.561876 IP 192.168.0.102.6584 > 5.141.89.191.46334: UDP, length 50
14:55:02.562428 IP 5.141.89.191.46238 > 192.168.0.102.8464: UDP, length 111
14:55:02.562479 IP 192.168.0.102 > 5.141.89.191: ICMP 192.168.0.102 udp port 8464 unreachable, length 147
14:55:02.808197 IP 192.168.0.102.10168 > 85.116.126.126.domain: 4460+ PTR? 191.89.141.5.in-addr.arpa. (43)
14:55:02.861973 IP 85.116.126.126.domain > 192.168.0.102.10168: 4460 NXDomain 0/1/0 (103)
14:55:03.507950 IP 192.168.0.102.52020 > mc.yandex.ru.https: Flags [.], ack 574914372, win 263, options [nop,nop,TS val 955792 ecr 1373201134], length 0
14:55:03.552931 IP mc.yandex.ru.https > 192.168.0.102.52020: Flags [.], ack 1, win 115, options [nop,nop,TS val 1373203646 ecr 948264], length 0
14:55:03.807895 IP 192.168.0.102.50215 > 85.116.126.126.domain: 1193+ PTR? 119.251.250.87.in-addr.arpa. (45)
14:55:03.817728 IP 85.116.126.126.domain > 192.168.0.102.50215: 1193 1/0/0 PTR mc.yandex.ru. (71)
14:55:03.987627 IP 192.168.0.102.52019 > mc.yandex.ru.https: Flags [.], ack 1469054803, win 280, options [nop,nop,TS val 955912 ecr 1373200536], length 0
14:55:04.032021 IP mc.yandex.ru.https > 192.168.0.102.52019: Flags [.], ack 1, win 170, options [nop,nop,TS val 1373203048 ecr 948387], length 0
14:55:04.066184 IP 192.168.0.102.55798 > msnbot-65-52-108-74.search.msn.com.https: Flags [P.], seq 1:630, ack 485, win 1444, options [nop,nop,TS val 955931 ecr 115949882], length 629
14:55:04.279979 IP msnbot-65-52-108-74.search.msn.com.https > 192.168.0.102.55798: Flags [P.], seq 485:1210, ack 630, win 7563, options [nop,nop,TS val 115950384 ecr 955931], length 725
14:55:04.280063 IP 192.168.0.102.55798 > msnbot-65-52-108-74.search.msn.com.https: Flags [.], ack 1210, win 1439, options [nop,nop,TS val 955985 ecr 115950384], length 0
14:55:04.286032 IP msnbot-65-52-108-74.search.msn.com.https > 192.168.0.102.55798: Flags [P.], seq 1210:1311, ack 630, win 7563, options [nop,nop,TS val 115950386 ecr 955931], length 101
14:55:04.286081 IP 192.168.0.102.55798 > msnbot-65-52-108-74.search.msn.com.https: Flags [.], ack 1311, win 1444, options [nop,nop,TS val 955986 ecr 115950386], length 0
14:55:05.304317 IP 192.168.0.102.52921 > lb-in-f157.1e100.net.https: Flags [P.], seq 1405933992:1405934038, ack 4234220368, win 317, options [nop,nop,TS val 956241 ecr 3140351476], length 46
14:55:05.304484 IP 192.168.0.102.60741 > lo-in-f154.1e100.net.https: Flags [P.], seq 322792717:322792763, ack 2907040268, win 339, options [nop,nop,TS val 956241 ecr 192653008], length 46
14:55:05.356305 IP lo-in-f154.1e100.net.https > 192.168.0.102.60741: Flags [P.], seq 1:61, ack 46, win 358, options [nop,nop,TS val 192711439 ecr 956241], length 60
14:55:05.356558 IP 192.168.0.102.60741 > lo-in-f154.1e100.net.https: Flags [P.], seq 46:92, ack 61, win 339, options [nop,nop,TS val 956254 ecr 192711439], length 46
14:55:05.356781 IP 192.168.0.102.60741 > lo-in-f154.1e100.net.https: Flags [FP.], seq 92:123, ack 61, win 339, options [nop,nop,TS val 956254 ecr 192711439], length 31
14:55:05.356924 IP lo-in-f154.1e100.net.https > 192.168.0.102.60741: Flags [F.], seq 61, ack 46, win 358, options [nop,nop,TS val 192711439 ecr 956241], length 0
14:55:05.356953 IP 192.168.0.102.60741 > lo-in-f154.1e100.net.https: Flags [.], ack 62, win 339, options [nop,nop,TS val 956254 ecr 192711439], length 0
14:55:05.363345 IP lb-in-f157.1e100.net.https > 192.168.0.102.52921: Flags [P.], seq 1:61, ack 46, win 350, options [nop,nop,TS val 3140409552 ecr 956241], length 60
14:55:05.363400 IP 192.168.0.102.52921 > lb-in-f157.1e100.net.https: Flags [.], ack 61, win 317, options [nop,nop,TS val 956255 ecr 3140409552], length 0
14:55:05.363491 IP lb-in-f157.1e100.net.https > 192.168.0.102.52921: Flags [F.], seq 61, ack 46, win 350, options [nop,nop,TS val 3140409552 ecr 956241], length 0
14:55:05.370012 IP 192.168.0.102.52921 > lb-in-f157.1e100.net.https: Flags [P.], seq 46:92, ack 62, win 317, options [nop,nop,TS val 956257 ecr 3140409552], length 46
14:55:05.370184 IP 192.168.0.102.52921 > lb-in-f157.1e100.net.https: Flags [FP.], seq 92:123, ack 62, win 317, options [nop,nop,TS val 956257 ecr 3140409552], length 31
14:55:05.406519 IP lo-in-f154.1e100.net.https > 192.168.0.102.60741: Flags [R], seq 2907040328, win 0, length 0
14:55:05.408700 IP lo-in-f154.1e100.net.https > 192.168.0.102.60741: Flags [R], seq 2907040328, win 0, length 0
14:55:05.410086 IP lo-in-f154.1e100.net.https > 192.168.0.102.60741: Flags [R], seq 2907040329, win 0, length 0
14:55:05.426456 IP lb-in-f157.1e100.net.https > 192.168.0.102.52921: Flags [R], seq 4234220429, win 0, length 0
14:55:05.428398 IP lb-in-f157.1e100.net.https > 192.168.0.102.52921: Flags [R], seq 4234220429, win 0, length 0
14:55:05.808390 IP 192.168.0.102.27675 > 85.116.126.126.domain: 56371+ PTR? 157.71.194.173.in-addr.arpa. (45)
14:55:05.818965 IP 85.116.126.126.domain > 192.168.0.102.27675: 56371 1/0/0 PTR lb-in-f157.1e100.net. (79)
14:55:05.819785 IP 192.168.0.102.35006 > 85.116.126.126.domain: 14063+ PTR? 154.222.194.173.in-addr.arpa. (46)
14:55:05.830247 IP 85.116.126.126.domain > 192.168.0.102.35006: 14063 1/0/0 PTR lo-in-f154.1e100.net. (80)
14:55:06.305335 IP 192.168.0.102.52516 > lb-in-f155.1e100.net.https: Flags [P.], seq 3880901362:3880901408, ack 1197550972, win 605, options [nop,nop,TS val 956491 ecr 2175182886], length 46
14:55:06.354807 IP lb-in-f155.1e100.net.https > 192.168.0.102.52516: Flags [.], ack 46, win 377, options [nop,nop,TS val 2175240589 ecr 956491], length 0
14:55:06.356045 IP lb-in-f155.1e100.net.https > 192.168.0.102.52516: Flags [P.], seq 1:61, ack 46, win 377, options [nop,nop,TS val 2175240589 ecr 956491], length 60
14:55:06.356110 IP 192.168.0.102.52516 > lb-in-f155.1e100.net.https: Flags [.], ack 61, win 605, options [nop,nop,TS val 956504 ecr 2175240589], length 0
14:55:06.356389 IP 192.168.0.102.52516 > lb-in-f155.1e100.net.https: Flags [P.], seq 46:92, ack 61, win 605, options [nop,nop,TS val 956504 ecr 2175240589], length 46
14:55:06.356698 IP 192.168.0.102.52516 > lb-in-f155.1e100.net.https: Flags [FP.], seq 92:123, ack 61, win 605, options [nop,nop,TS val 956504 ecr 2175240589], length 31
14:55:06.356767 IP lb-in-f155.1e100.net.https > 192.168.0.102.52516: Flags [F.], seq 61, ack 46, win 377, options [nop,nop,TS val 2175240589 ecr 956491], length 0
14:55:06.356827 IP 192.168.0.102.52516 > lb-in-f155.1e100.net.https: Flags [.], ack 62, win 605, options [nop,nop,TS val 956504 ecr 2175240589], length 0
14:55:06.407967 IP lb-in-f155.1e100.net.https > 192.168.0.102.52516: Flags [R], seq 1197551032, win 0, length 0
14:55:06.409984 IP lb-in-f155.1e100.net.https > 192.168.0.102.52516: Flags [R], seq 1197551032, win 0, length 0
14:55:06.411738 IP lb-in-f155.1e100.net.https > 192.168.0.102.52516: Flags [R], seq 1197551033, win 0, length 0
14:55:06.808070 IP 192.168.0.102.29319 > 85.116.126.126.domain: 40057+ PTR? 155.71.194.173.in-addr.arpa. (45)
14:55:06.819635 IP 85.116.126.126.domain > 192.168.0.102.29319: 40057 1/0/0 PTR lb-in-f155.1e100.net. (79)
14:55:07.383037 IP 5.141.89.191.46334 > 192.168.0.102.6584: UDP, length 111
14:55:07.383277 IP 192.168.0.102.6584 > 5.141.89.191.46334: UDP, length 50
14:55:07.384633 IP 5.141.89.191.46238 > 192.168.0.102.8464: UDP, length 111
14:55:07.384694 IP 192.168.0.102 > 5.141.89.191: ICMP 192.168.0.102 udp port 8464 unreachable, length 147
14:55:07.933136 IP pool-5-79-255-159.is74.ru.29651 > 192.168.0.102.46141: Flags [P.], seq 1525733574:1525733704, ack 854409320, win 610, options [nop,nop,TS val 496816 ecr 953236], length 130
14:55:07.933197 IP 192.168.0.102.46141 > pool-5-79-255-159.is74.ru.29651: Flags [.], ack 130, win 1406, options [nop,nop,TS val 956898 ecr 496816], length 0
14:55:07.933462 IP 192.168.0.102.46141 > pool-5-79-255-159.is74.ru.29651: Flags [P.], seq 1:22, ack 130, win 1406, options [nop,nop,TS val 956898 ecr 496816], length 21
14:55:07.935581 IP 192.168.0.102.46141 > pool-5-79-255-159.is74.ru.29651: Flags [P.], seq 22:69, ack 130, win 1406, options [nop,nop,TS val 956899 ecr 496816], length 47
14:55:07.949649 IP pool-5-79-255-159.is74.ru.29651 > 192.168.0.102.46141: Flags [.], ack 69, win 610, options [nop,nop,TS val 496820 ecr 956898], length 0
14:55:07.949821 IP pool-5-79-255-159.is74.ru.29651 > 192.168.0.102.46141: Flags [P.], seq 130:158, ack 69, win 610, options [nop,nop,TS val 496820 ecr 956898], length 28
14:55:07.987939 IP 192.168.0.102.46141 > pool-5-79-255-159.is74.ru.29651: Flags [.], ack 158, win 1406, options [nop,nop,TS val 956912 ecr 496820], length 0
14:55:08.110016 IP msnbot-65-52-108-74.search.msn.com.https > 192.168.0.102.55798: Flags [P.], seq 1311:1796, ack 630, win 7563, options [nop,nop,TS val 115950768 ecr 955986], length 485
14:55:08.110094 IP 192.168.0.102.55798 > msnbot-65-52-108-74.search.msn.com.https: Flags [.], ack 1796, win 1441, options [nop,nop,TS val 956942 ecr 115950768], length 0
14:55:08.307835 IP 192.168.0.102.53998 > srv118-131-240-87.vk.com.https: Flags [P.], seq 1657825302:1657825343, ack 1655022022, win 454, options [nop,nop,TS val 956992 ecr 529784631], length 41
14:55:08.364882 IP srv118-131-240-87.vk.com.https > 192.168.0.102.53998: Flags [P.], seq 1:42, ack 41, win 3620, options [nop,nop,TS val 529799175 ecr 956992], length 41
14:55:08.364945 IP 192.168.0.102.53998 > srv118-131-240-87.vk.com.https: Flags [.], ack 42, win 454, options [nop,nop,TS val 957006 ecr 529799175], length 0
14:55:08.808362 IP 192.168.0.102.58561 > 85.116.126.126.domain: 7704+ PTR? 159.255.79.5.in-addr.arpa. (43)
14:55:08.819054 IP 85.116.126.126.domain > 192.168.0.102.58561: 7704 1/0/0 PTR pool-5-79-255-159.is74.ru. (82)
14:55:08.819843 IP 192.168.0.102.42014 > 85.116.126.126.domain: 6349+ PTR? 118.131.240.87.in-addr.arpa. (45)
14:55:08.830498 IP 85.116.126.126.domain > 192.168.0.102.42014: 6349 1/0/0 PTR srv118-131-240-87.vk.com. (83)
14:55:08.922627 IP pool-5-79-255-159.is74.ru.29651 > 192.168.0.102.46141: Flags [P.], seq 395:532, ack 69, win 610, options [nop,nop,TS val 497064 ecr 956912], length 137
14:55:08.922700 IP 192.168.0.102.46141 > pool-5-79-255-159.is74.ru.29651: Flags [.], ack 158, win 1428, options [nop,nop,TS val 957145 ecr 496820,nop,nop,sack 1 {395:532}], length 0
14:55:08.925029 IP pool-5-79-255-159.is74.ru.29651 > 192.168.0.102.46141: Flags [P.], seq 158:395, ack 69, win 610, options [nop,nop,TS val 497064 ecr 956912], length 237
14:55:08.925099 IP 192.168.0.102.46141 > pool-5-79-255-159.is74.ru.29651: Flags [.], ack 532, win 1436, options [nop,nop,TS val 957146 ecr 497064], length 0
14:55:08.925562 IP 192.168.0.102.46141 > pool-5-79-255-159.is74.ru.29651: Flags [P.], seq 69:96, ack 532, win 1444, options [nop,nop,TS val 957146 ecr 497064], length 27
14:55:08.927423 IP 192.168.0.102.46141 > pool-5-79-255-159.is74.ru.29651: Flags [P.], seq 96:212, ack 532, win 1444, options [nop,nop,TS val 957146 ecr 497064], length 116
14:55:08.941699 IP pool-5-79-255-159.is74.ru.29651 > 192.168.0.102.46141: Flags [.], ack 212, win 610, options [nop,nop,TS val 497069 ecr 957146], length 0
14:55:08.942579 IP pool-5-79-255-159.is74.ru.29651 > 192.168.0.102.46141: Flags [P.], seq 532:560, ack 212, win 610, options [nop,nop,TS val 497069 ecr 957146], length 28
14:55:08.943648 IP pool-5-79-255-159.is74.ru.29651 > 192.168.0.102.46141: Flags [P.], seq 560:581, ack 212, win 610, options [nop,nop,TS val 497069 ecr 957146], length 21
14:55:08.943689 IP 192.168.0.102.46141 > pool-5-79-255-159.is74.ru.29651: Flags [.], ack 581, win 1444, options [nop,nop,TS val 957151 ecr 497069], length 0
14:55:09.093431 IP msnbot-65-52-108-74.search.msn.com.https > 192.168.0.102.55798: Flags [P.], seq 1796:2345, ack 630, win 7563, options [nop,nop,TS val 115950866 ecr 956942], length 549
14:55:09.093501 IP 192.168.0.102.55798 > msnbot-65-52-108-74.search.msn.com.https: Flags [.], ack 2345, win 1437, options [nop,nop,TS val 957188 ecr 115950866], length 0
14:55:09.093857 IP 192.168.0.102.55798 > msnbot-65-52-108-74.search.msn.com.https: Flags [P.], seq 630:1115, ack 2345, win 1444, options [nop,nop,TS val 957188 ecr 115950866], length 485
14:55:09.309220 IP 192.168.0.102.43824 > 95.213.4.201.https: Flags [P.], seq 4013864551:4013864592, ack 932005180, win 499, options [nop,nop,TS val 957242 ecr 854806665], length 41
14:55:09.309333 IP 192.168.0.102.49770 > lb-in-f156.1e100.net.https: Flags [P.], seq 609560773:609560819, ack 3153302063, win 1270, options [nop,nop,TS val 957242 ecr 3098140234], length 46
14:55:09.309527 IP 192.168.0.102.39086 > lb-in-f97.1e100.net.https: Flags [P.], seq 1175304163:1175304209, ack 794358845, win 362, options [nop,nop,TS val 957242 ecr 2056813163], length 46
14:55:09.309585 IP 192.168.0.102.39084 > lb-in-f97.1e100.net.https: Flags [P.], seq 4088447596:4088447642, ack 132972870, win 237, options [nop,nop,TS val 957242 ecr 3442863088], length 46
14:55:09.309652 IP 192.168.0.102.44749 > le-in-f132.1e100.net.https: Flags [P.], seq 491053496:491053542, ack 1675731543, win 694, options [nop,nop,TS val 957242 ecr 1934957484], length 46
14:55:09.330812 IP msnbot-65-52-108-74.search.msn.com.https > 192.168.0.102.55798: Flags [.], ack 1115, win 7078, options [nop,nop,TS val 115950891 ecr 957188], length 0
14:55:09.362212 IP lb-in-f156.1e100.net.https > 192.168.0.102.49770: Flags [P.], seq 1:61, ack 46, win 381, options [nop,nop,TS val 3098198450 ecr 957242], length 60
14:55:09.362543 IP 192.168.0.102.49770 > lb-in-f156.1e100.net.https: Flags [P.], seq 46:92, ack 61, win 1270, options [nop,nop,TS val 957255 ecr 3098198450], length 46
14:55:09.363174 IP lb-in-f156.1e100.net.https > 192.168.0.102.49770: Flags [F.], seq 61, ack 46, win 381, options [nop,nop,TS val 3098198450 ecr 957242], length 0
14:55:09.363276 IP 192.168.0.102.49770 > lb-in-f156.1e100.net.https: Flags [P.], seq 92:123, ack 62, win 1270, options [nop,nop,TS val 957255 ecr 3098198450], length 31
14:55:09.363327 IP 192.168.0.102.49770 > lb-in-f156.1e100.net.https: Flags [F.], seq 123, ack 62, win 1270, options [nop,nop,TS val 957255 ecr 3098198450], length 0
14:55:09.364660 IP lb-in-f97.1e100.net.https > 192.168.0.102.39086: Flags [.], ack 46, win 366, options [nop,nop,TS val 2056871781 ecr 957242], length 0
14:55:09.366467 IP lb-in-f97.1e100.net.https > 192.168.0.102.39086: Flags [P.], seq 1:61, ack 46, win 366, options [nop,nop,TS val 2056871781 ecr 957242], length 60
14:55:09.367446 IP lb-in-f97.1e100.net.https > 192.168.0.102.39086: Flags [F.], seq 61, ack 46, win 366, options [nop,nop,TS val 2056871781 ecr 957242], length 0
14:55:09.369106 IP 95.213.4.201.https > 192.168.0.102.43824: Flags [P.], seq 1:42, ack 41, win 2534, options [nop,nop,TS val 854821220 ecr 957242], length 41
14:55:09.369159 IP 192.168.0.102.43824 > 95.213.4.201.https: Flags [.], ack 42, win 499, options [nop,nop,TS val 957257 ecr 854821220], length 0
14:55:09.369525 IP lb-in-f97.1e100.net.https > 192.168.0.102.39084: Flags [.], ack 46, win 350, options [nop,nop,TS val 3442921658 ecr 957242], length 0
14:55:09.369649 IP lb-in-f97.1e100.net.https > 192.168.0.102.39084: Flags [P.], seq 1:61, ack 46, win 350, options [nop,nop,TS val 3442921658 ecr 957242], length 60
14:55:09.369666 IP 192.168.0.102.39084 > lb-in-f97.1e100.net.https: Flags [.], ack 61, win 237, options [nop,nop,TS val 957257 ecr 3442921658], length 0
14:55:09.371764 IP lb-in-f97.1e100.net.https > 192.168.0.102.39084: Flags [F.], seq 61, ack 46, win 350, options [nop,nop,TS val 3442921658 ecr 957242], length 0
14:55:09.375376 IP 192.168.0.102.39086 > lb-in-f97.1e100.net.https: Flags [P.], seq 46:92, ack 62, win 362, options [nop,nop,TS val 957258 ecr 2056871781], length 46
14:55:09.375777 IP 192.168.0.102.39086 > lb-in-f97.1e100.net.https: Flags [FP.], seq 92:123, ack 62, win 362, options [nop,nop,TS val 957259 ecr 2056871781], length 31
14:55:09.379282 IP le-in-f132.1e100.net.https > 192.168.0.102.44749: Flags [.], ack 46, win 362, options [nop,nop,TS val 1935015403 ecr 957242], length 0
14:55:09.379406 IP le-in-f132.1e100.net.https > 192.168.0.102.44749: Flags [P.], seq 1:61, ack 46, win 362, options [nop,nop,TS val 1935015403 ecr 957242], length 60
14:55:09.379515 IP le-in-f132.1e100.net.https > 192.168.0.102.44749: Flags [F.], seq 61, ack 46, win 362, options [nop,nop,TS val 1935015403 ecr 957242], length 0
14:55:09.382811 IP 192.168.0.102.44749 > le-in-f132.1e100.net.https: Flags [P.], seq 46:92, ack 62, win 694, options [nop,nop,TS val 957260 ecr 1935015403], length 46
14:55:09.382990 IP 192.168.0.102.39084 > lb-in-f97.1e100.net.https: Flags [P.], seq 46:92, ack 62, win 237, options [nop,nop,TS val 957260 ecr 3442921658], length 46
14:55:09.383596 IP 192.168.0.102.39084 > lb-in-f97.1e100.net.https: Flags [FP.], seq 92:123, ack 62, win 237, options [nop,nop,TS val 957261 ecr 3442921658], length 31
14:55:09.383789 IP 192.168.0.102.44749 > le-in-f132.1e100.net.https: Flags [FP.], seq 92:123, ack 62, win 694, options [nop,nop,TS val 957261 ecr 1935015403], length 31
14:55:09.412984 IP lb-in-f156.1e100.net.https > 192.168.0.102.49770: Flags [R], seq 3153302123, win 0, length 0
14:55:09.415580 IP lb-in-f156.1e100.net.https > 192.168.0.102.49770: Flags [R], seq 3153302124, win 0, length 0
14:55:09.417187 IP lb-in-f156.1e100.net.https > 192.168.0.102.49770: Flags [R], seq 3153302124, win 0, length 0
14:55:09.424266 IP lb-in-f97.1e100.net.https > 192.168.0.102.39086: Flags [R], seq 794358906, win 0, length 0
14:55:09.427111 IP lb-in-f97.1e100.net.https > 192.168.0.102.39086: Flags [R], seq 794358906, win 0, length 0
14:55:09.434521 IP lb-in-f97.1e100.net.https > 192.168.0.102.39084: Flags [R], seq 132972931, win 0, length 0
14:55:09.437161 IP lb-in-f97.1e100.net.https > 192.168.0.102.39084: Flags [R], seq 132972931, win 0, length 0
14:55:09.440029 IP le-in-f132.1e100.net.https > 192.168.0.102.44749: Flags [R], seq 1675731604, win 0, length 0
14:55:09.447935 IP le-in-f132.1e100.net.https > 192.168.0.102.44749: Flags [R], seq 1675731604, win 0, length 0

sudo iptables-save:

(Нажмите, чтобы показать/скрыть)

# Generated by iptables-save v1.4.21 on Thu Oct 15 14:57:20 2015
*filter
:INPUT ACCEPT [2625:692682]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [2860:811593]
-A INPUT -p icmp -m icmp --icmp-type 8 -j LOG --log-prefix "Iptables: Ping detected: "
-A INPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
COMMIT
# Completed on Thu Oct 15 14:57:20 2015

Внешний IP был на момент тестирования: 31.162.213.36

[fisher74]

И зачем Вы это сюда вывалили? Сами не могли фильтрануть по известным IP-ам?
Но по простынке видно, что Вы за роутером, потому пинговают не Вас, а роутер, так что ничего Вы в логах не увидите.

[_art_]

Хмм..

А как сделать чтобы именно меня можно было, а не роутер ?

[fisher74]

отказаться от роутера...

Но перед этимо нужно решить другую проблему.
А точнее ответить на вопрос:"А нафига зачем это нужно?"

[_art_]

Как-то "пробросить порты" ?
Этож icmp - он низкоуровневый напрямую к сетевой карте обращается.
Я просто хочу логировать любые попытки пинга моего web сервера.

[fisher74]

Я просто хочу логировать любые попытки пинга моего web сервера.

Вопрос тот же: ЗАЧЕМ?

[_art_]

Ну как, интересно же, кто к тебе ломится...

Хочу.

Как один из элементов построение безопасности

Не знаю, что еще можно написать...

И даже, просто ради эксперимента.

[AnrDaemon]

Безопасность у вас уже обеспечивается маршрутизатором.
В текущей ситуации вы можете только снизить безопасность системы.

[Scorry]

Ну как, интересно же, кто к тебе ломится...

Хочу.

Как один из элементов построение безопасности

Не знаю, что еще можно написать...

И даже, просто ради эксперимента.

Для укрепления безопасности надо сначала знать, что укреплять, где слабые места у сервера, вектор атаки, вот это всё (с).
Ну будете вы логировать пинги — дальше-то что? :-)

[symon2014]

  А мне вот интересно , кого это пингуют при динамическом IP? 

[_art_]

Безопасность у вас уже обеспечивается маршрутизатором.
В текущей ситуации вы можете только снизить безопасность системы.

Почему ?

[fisher74]

Тема уходит в оффтоп. На Ваш вопрос я ответил.
Вопросы хотелок и безопасности обсуждаются в других ветках

[_art_]

Тема уходит в оффтоп. На Ваш вопрос я ответил.
Вопросы хотелок и безопасности обсуждаются в других ветках

Вопросом на вопрос ?