Здравствуйте!
стоит Elastix за Mikrotik
Обнаружил что с разных белых Ip идут пакеты udp на порт 16354.
за что отвечает порт 16354?
что это за трафик?
Захватил на elastix.
1 0.000000 192.168.200.9 192.168.200.233 UDP 72 Source port: 55879 Destination port: 16354
2 0.449175 192.168.200.9 192.168.200.233 BT-uTP 109 uTorrent Transport Protocol Type: Unknown 142
3 1.759804 192.168.200.9 192.168.200.233 BT-uTP 109 uTorrent Transport Protocol Type: Unknown 165
4 11.434356 192.168.200.9 192.168.200.233 BT-uTP 109 uTorrent Transport Protocol Type: Unknown 106
5 12.863961 192.168.200.9 192.168.200.233 UDP 72 Source port: sightline Destination port: 16354
6 12.936522 192.168.200.9 192.168.200.233 UDP 72 Source port: 47538 Destination port: 16354
7 13.405999 192.168.200.9 192.168.200.233 UDP 75 Source port: 54979 Destination port: 16354
порт давно блокирован но все равно долбятся с меньше активностью
21:00:10 firewall,info forward: in:l2tp-out1 out:bridge1, proto UDP, 91.229.205.165:55561->192.168.200.233:16354, len 38
21:00:13 firewall,info forward: in:l2tp-out1 out:bridge1, proto UDP, 91.229.205.165:55561->192.168.200.233:16354, len 38
21:02:08 firewall,info forward: in:l2tp-out1 out:bridge1, proto UDP, 91.229.205.165:55561->192.168.200.233:16354, len 38
21:02:11 firewall,info forward: in:l2tp-out1 out:bridge1, proto UDP, 91.229.205.165:55561->192.168.200.233:16354, len 38
21:03:29 firewall,info forward: in:l2tp-out1 out:bridge1, proto UDP, 31.40.114.59:61069->192.168.200.233:16354, len 73
21:04:16 firewall,info forward: in:l2tp-out1 out:bridge1, proto UDP, 95.84.17.25:29840->192.168.200.233:16354, len 73
21:05:04 firewall,info forward: in:l2tp-out1 out:bridge1, proto UDP, 213.176.230.155:64456->192.168.200.233:16354, len 38
21:05:07 firewall,info forward: in:l2tp-out1 out:bridge1, proto UDP, 213.176.230.155:64456->192.168.200.233:16354, len 38
21:05:13 firewall,info forward: in:l2tp-out1 out:bridge1, proto UDP, 213.176.230.155:64456->192.168.200.233:16354, len 38
21:06:38 firewall,info forward: in:l2tp-out1 out:bridge1, proto UDP, 213.176.230.155:64456->192.168.200.233:16354, len 75
21:07:23 firewall,info forward: in:l2tp-out1 out:bridge1, proto UDP, 2.132.91.1:50178->192.168.200.233:16354, len 75
21:07:26 firewall,info forward: in:l2tp-out1 out:bridge1, proto UDP, 91.216.126.102:39822->192.168.200.233:16354, len 73
21:08:11 firewall,info forward: in:l2tp-out1 out:bridge1, proto UDP, 91.229.205.165:55561->192.168.200.233:16354, len 38
21:08:14 firewall,info forward: in:l2tp-out1 out:bridge1, proto UDP, 91.229.205.165:55561->192.168.200.233:16354, len 38
21:08:31 firewall,info forward: in:l2tp-out1 out:bridge1, proto UDP, 213.176.230.155:64456->192.168.200.233:16354, len 38
21:08:34 firewall,info forward: in:l2tp-out1 out:bridge1, proto UDP, 213.176.230.155:64456->192.168.200.233:16354, len 38
21:08:40 firewall,info forward: in:l2tp-out1 out:bridge1, proto UDP, 213.176.230.155:64456->192.168.200.233:16354, len 38
21:13:16 firewall,info forward: in:l2tp-out1 out:bridge1, proto UDP, 213.176.230.155:64456->192.168.200.233:16354, len 38
21:13:19 firewall,info forward: in:l2tp-out1 out:bridge1, proto UDP, 213.176.230.155:64456->192.168.200.233:16354, len 38
21:13:25 firewall,info forward: in:l2tp-out1 out:bridge1, proto UDP, 213.176.230.155:64456->192.168.200.233:16354, len 38