[Question]Edge pod connectivity test failed

[nelzhang02184516]

What happened:

I conducted connectivity testing on the busy-box pod on node fj-xamen-4.10.0.0.12 (Raven gateway node) and found that the data disappeared after passing through node fj-quanzhou-8.10.0.0.12 (Raven gateway node) and reaching node fj-quanzhou-8.10.0.0.14.

The same operation is performed on the busy-box pod (non Raven gateway) of fj-xamen-4.10.0.0.11, ping 172.16.0.72. There is data on fj-xamen-4.10.0.0.11 and fj-xamen-4.10.0.0.12, but no data on fj-quanzhou-8.10.0.0.12.

On fj-quanzhou-8.10.0.0.12, the bus pod IP of fj-xamen-4.10.0.0.12 can be tested to be normal

What you expected to happen:
cloud-edge communication
How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• OpenYurt version:v1.4.4
• Kubernetes version (use kubectl version):v1.25.6
• OS (e.g: cat /etc/os-release):Linux
• Kernel (e.g. uname -a):3.10.0-1160.119.1.el7.x86_64
• Install tools:
• Others:

others
/kind question

[YTGhost]

This issue appears to be one that was fixed last year. Could you please provide the Raven version deployed in your cluster, the configured Gateway resource objects, and the iptables NAT table information on gateway node(if you use flannel, just like iptables -t nat -vnL FLANNEL-POSTRTG)?

[nelzhang02184516]

This issue appears to be one that was fixed last year. Could you please provide the Raven version deployed in your cluster, the configured Gateway resource objects, and the iptables NAT table information on gateway node(if you use flannel, just like iptables -t nat -vnL FLANNEL-POSTRTG)?

raven-agent:0.4.2

cloud gateway
`[root@fj-quanzhou-8 /]# kubectl get gw gw-cloud -oyaml
apiVersion: raven.openyurt.io/v1beta1
kind: Gateway
metadata:
generation: 1
name: gw-cloud
resourceVersion: "38575"
uid: d8b4ce77-bf6a-45fe-8941-e2e003d4a681
spec:
endpoints:

• nodeName: fj-quanzhou-8.10.0.0.12
  port: 10262
  publicIP: 120.xx.xx.xx
  type: proxy
• nodeName: fj-quanzhou-8.10.0.0.12
  port: 4500
  publicIP: 120.xx.xx.xx
  type: tunnel
  exposeType: PublicIP
  nodeSelector:
  matchLabels:
  raven.openyurt.io/gateway: gw-cloud
  proxyConfig:
  Replicas: 1
  proxyHTTPPort: 10255,9445
  proxyHTTPSPort: 10250,9100
  tunnelConfig:
  Replicas: 1
  status:
  activeEndpoints:
• config:
  enable-l7-proxy: "true"
  nodeName: fj-quanzhou-8.10.0.0.12
  port: 10262
  publicIP: 120.xx.xx.xx
  type: proxy
• config:
  enable-l3-tunnel: "true"
  nodeName: fj-quanzhou-8.10.0.0.12
  port: 4500
  publicIP: 120.xx.xx.xx
  type: tunnel
  nodes:
• nodeName: fj-quanzhou-8.10.0.0.12
  privateIP: 10.0.0.12
  subnets:
  • 172.16.0.0/26
• nodeName: fj-quanzhou-8.10.0.0.13
  privateIP: 10.0.0.13
  subnets:
  • 172.16.0.128/26
• nodeName: fj-quanzhou-8.10.0.0.14
  privateIP: 10.0.0.14
  subnets:
  • 172.16.0.64/26`

edge gateway
`[root@fj-quanzhou-8 /]# kubectl get gw gw-fj-xiamen-4 -oyaml
apiVersion: raven.openyurt.io/v1beta1
kind: Gateway
metadata:
generation: 1
name: gw-fj-xiamen-4
resourceVersion: "36329"
uid: 0cebcba1-6a1a-45c8-a9e2-632ca7fee94d
spec:
endpoints:

• nodeName: fj-xiamen-4.10.0.0.12
  port: 10262
  publicIP: 120.xx.xx.xx
  type: proxy
  underNAT: true
• nodeName: fj-xiamen-4.10.0.0.12
  port: 4500
  publicIP: 120.xx.xx.xx
  type: tunnel
  underNAT: true
  nodeSelector:
  matchLabels:
  raven.openyurt.io/gateway: gw-fj-xiamen-4
  proxyConfig:
  Replicas: 1
  tunnelConfig:
  Replicas: 1
  status:
  activeEndpoints:
• config:
  enable-l7-proxy: "true"
  nodeName: fj-xiamen-4.10.0.0.12
  port: 10262
  publicIP: 120.xx.xx.xx
  type: proxy
  underNAT: true
• config:
  enable-l3-tunnel: "true"
  nodeName: fj-xiamen-4.10.0.0.12
  port: 4500
  publicIP: 120.xx.xx.xx
  type: tunnel
  underNAT: true
  nodes:
• nodeName: fj-xiamen-4.10.0.0.11
  privateIP: 10.0.0.11
  subnets:
  • 172.16.0.192/26
• nodeName: fj-xiamen-4.10.0.0.12
  privateIP: 10.0.0.12
  subnets:
  • 172.16.1.0/26`

cloud gateway node

edge gateway node