Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 1
    this is an important rule in business: if you are spending a million dollars, the manufacturer can afford to have a meeting with you and then manufacture precisely what you need, and that is better for both you and them. Conversely, if you are only spending $10 then the meeting literally isn't worth the time for you or for them. Commented Apr 21, 2023 at 15:06
  • I've accepted your answer, because of the NAT. But ICMP is also supported by NAT. So there may be more of them. Commented Apr 21, 2023 at 15:53
  • @user1576055 the point stands: it has to be something the NAT supports. And the NAT decodes ICMP packets by looking at the embedded UDP or TCP packet, anyway. (When a packet causes a problem and an ICMP packet is sent out, that ICMP packet includes the headers of the packet that caused the problem) Commented Apr 21, 2023 at 17:57
  • Well for ICMP ping there is no UDP or TCP packet. I will quote from another thread "For ICMP query/reply type messages like Echoes (pings), NAPT uses the ICMP Query ID (sometimes just called the ICMP ID) the same way it would use a TCP or UDP port number." Commented Apr 21, 2023 at 21:50