Networking MetalLB将IP分配给nginx,但无法访问目标主机

Networking MetalLB将IP分配给nginx,但无法访问目标主机,networking,kubernetes,k3s,Networking,Kubernetes,K3s,我无法从群集外部访问分配的IP地址(192.168.0.240) ❯ kubectl get services -n kube-system -l app=nginx-ingress -o wide NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR nginx-ingress-controller Loa

我无法从群集外部访问分配的IP地址(
192.168.0.240

❯ kubectl get services  -n kube-system -l app=nginx-ingress -o wide
NAME                       TYPE           CLUSTER-IP      EXTERNAL-IP     PORT(S)                      AGE    SELECTOR
nginx-ingress-controller   LoadBalancer   10.43.225.204   192.168.0.240   80:31012/TCP,443:32713/TCP   2d2h   app=nginx-ingress,component=controller,release=nginx-ingress
从群集节点:

[sseneca@alarm-master ~]$ curl http://192.168.0.240/
<html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>nginx/1.17.8</center>
</body>
</html>
并使用
ping

❯ ping 192.168.0.240
PING 192.168.0.240 (192.168.0.240) 56(84) bytes of data.
From 192.168.0.21 icmp_seq=1 Destination Host Unreachable
From 192.168.0.21 icmp_seq=2 Destination Host Unreachable
From 192.168.0.21 icmp_seq=3 Destination Host Unreachable
^C
--- 192.168.0.240 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3095ms
pipe 3

我不知道如何调试这个问题,任何帮助感谢。有人在另一个论坛上发了一条消息,但我不明白他们想让我做什么。

试试
iptables-p FORWARD ACCEPT
@cru该命令做什么?
-p
代表
策略
FORWARD
是指既不由主机发送也不直接发送给主机的数据包。它们是主机仅路由的数据包,
ACCEPT
用于接受此类流量。这是一个解决方案。@Crou在所有节点上执行
iptables-P FORWARD ACCEPT
,并立即进行测试,似乎不起作用。我是否打算重新启动节点/a pod/等?能否与所有部署的项目分享部署集群的步骤,我将尝试重新创建问题。
❯ ping 192.168.0.240
PING 192.168.0.240 (192.168.0.240) 56(84) bytes of data.
From 192.168.0.21 icmp_seq=1 Destination Host Unreachable
From 192.168.0.21 icmp_seq=2 Destination Host Unreachable
From 192.168.0.21 icmp_seq=3 Destination Host Unreachable
^C
--- 192.168.0.240 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3095ms
pipe 3