Why TCP Packets leaving the host is not MASQUERADED in Red Hat Enterprise Linux ?

Solution Verified - Updated -

Issue

  • Why TCP Packets leaving the host is not MASQUERADED in Red Hat Enterprise Linux ?
  • Why are packets with container IP address seen on the firewall ?
IP 172.17.0.4.55954 > 192.168.10.1.webcache: Flags [F.], seq 3728907624, ack 2096635523, win 288, options [nop,nop,TS val 38062125 ecr 1408832848], length 0
IP 172.17.0.4.55954 > 192.168.10.1.webcache: Flags [F.], seq 0, ack 1, win 288, options [nop,nop,TS val 38062326 ecr 1408832848], length 0
IP 172.17.0.4.55954 > 192.168.10.1.webcache: Flags [F.], seq 0, ack 1, win 288, options [nop,nop,TS val 38062527 ecr 1408832848], length 0

Environment

  • Red Hat Enterprise Linux 7/8
  • httpd container configured as reverse proxy with mod_jk
  • Container engine docker or podman

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content