11:37:04.282223 IP windows_server > linux_host: ip-proto-17 11:37:04.282227 IP windows_server > linux_host: ip-proto-17 CLDAP Sample of Printable Response Text Packet 1 2[`0vdm0e0¤tTime120170213163705.0Z0WsubschemaSubentry1> Mar 18, 2019 · policy: type: ACL criteria:-name: block_tcp classifier: network_src_port_id: 640dfd77-c92b-45a3-b8fc-22712de480e1 destination_port_range: 80-1024 ip_proto: 6 ip_dst_prefix: 192.168.1.2/24-name: block_udp classifier: network_src_port_id: 640dfd77-c92b-45a3-b8fc-22712de480eda destination_port_range: 80-1024 ip_proto: 17 ip_dst_prefix: 192.168.2.2/24 If you want to filter out the IP fragments associated with the TCP, UDP or ICMP packets as well, then a better filter is: ip and !(ip.proto == 1 or ip.proto == 6 or ip.proto == 17). edit flag offensive delete link more Okay, I get all that. What I do not get is why I cannot specify the protocol in a normal webconfigurator firewall rule? Code: [Select] proto Looking for information on Protocol UDP 17?This page will attempt to provide you with as much port information as possible on UDP Port 17. UDP Port 17 may use a defined protocol to communicate depending on the application. A protocol is a set of formalized rules 11:37:04.282223 IP windows_server > linux_host: ip-proto-17 11:37:04.282227 IP windows_server > linux_host: ip-proto-17 CLDAP Sample of Printable Response Text Packet 1 2[`0vdm0e0¤tTime120170213163705.0Z0WsubschemaSubentry1>Jul 21, 2016 · Hi All,I've got a weird issue that I've been banging my head on a break wall over for the past few weeks. Bit of background first:We have 2 sites, 1 in UK, 1 in US.Each site has a 500Mbps leased line Internet connection.Sites are connected via IPSEC VPN using Fortigate 800D A/P clusters running 5.4.
Documentation for socket() on Linux is split between various manpages including ip(7) that specifies that you have to use 0 or IPPROTO_UDP for UDP and 0 or IPPROTO_TCP for TCP.