On 2/14/22 10:18 AM, Tom Ammon wrote:
Laine,
Though I can't remember the particulars, I have a vague memory of the
sysctl settings in that article indeed solving the problem of traffic
not being forwarded on the bridge when I had configured no filtering on
the guest - hence my attempt to s
Laine,
Though I can't remember the particulars, I have a vague memory of the
sysctl settings in that article indeed solving the problem of traffic not
being forwarded on the bridge when I had configured no filtering on the
guest - hence my attempt to share what worked for me. Perhaps it would be
g
On 2/13/22 5:38 PM, Tom Ammon wrote:
Can you post the output of iptables -L?
By default, the bridge module in the kernel sends packets traversing the
bridge to iptables (in the FORWARD chain I believe) for processing. So
if you have configured a DENY policy on the FORWARD chain, or are
oth
The issue has been resolved I had a firewald running on virtual host.
Thank you for the replay.
On 2/13/2022 9:17 PM, Daniel Romero wrote:
Hi,
as Tom says, check iptables forward rules. Also, you can check host
sysctl ipv4/6 global and per interface rules to double check bridge
forward capa
Hi,
as Tom says, check iptables forward rules. Also, you can check host sysctl
ipv4/6 global and per interface rules to double check bridge forward
capabilities. Finally, check your routes on guest vm, especially the
default gw, sometimes you can receive the packet and the answer is sent
through t
Can you post the output of iptables -L?
By default, the bridge module in the kernel sends packets traversing the
bridge to iptables (in the FORWARD chain I believe) for processing. So if
you have configured a DENY policy on the FORWARD chain, or are otherwise
filtering in the forward chain, you'll
