On 7/9/20 5:17 PM, stefan.schm...@farmpartner-tec.com wrote:
> Hello,
>
> > Well, theory still holds I would say.
> >
> > I guess that the multicast-traffic from the other host
> > or the guestsdoesn't get to the daemon on the host.
> > Can't you just simply check if there are any firewall
> > rules configuredon the host kernel?
>
> I hope I did understand you corretcly and you are referring to iptables?
I didn't say iptables because it might have been
nftables - but yesthat is what I was referring to.
Guess to understand the config the output is
lacking verbositybut it makes me believe that
the whole setup doesn't lookas I would have
expected (bridges on each host where theguest
has a connection to and where ethernet interfaces
that connect the 2 hosts are part of as well -
everythingconnected via layer 2 basically).
> Here is the output of the current rules. Besides the IP of the guest
> the output is identical on both hosts:
>
> # iptables -S
> -P INPUT ACCEPT
> -P FORWARD ACCEPT
> -P OUTPUT ACCEPT
>
> # iptables -L
> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination
>
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination
> SOLUSVM_TRAFFIC_IN  all  --  anywhere             anywhere
> SOLUSVM_TRAFFIC_OUT  all  --  anywhere             anywhere
>
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination
>
> Chain SOLUSVM_TRAFFIC_IN (1 references)
> target     prot opt source               destination
>            all  --  anywhere             192.168.1.14
>
> Chain SOLUSVM_TRAFFIC_OUT (1 references)
> target     prot opt source               destination
>            all  --  192.168.1.14         anywhere
>
> kind regards
> Stefan Schmitz
>
>

_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Reply via email to