On Thu, May 14, 2020 at 04:28:12PM +0200, Jan Tluka wrote:
Modifying firewall is far from the default setting.
The rp_filter became kind of special. Fedora changed the default value to
value 2 (just recently) and RHEL still configures it to 1. But I consider
this as part of default setting.
When I worked on this recipe in the past I simply thought it is
impossible to do the following:
ping 192.168.20.2 -c 100 -i 0.1 -I p5p1.10_0
but it turned out that it's only because of rp_filter setting.
The problem with the current implementation is that test expects the
system is in certain configuration (e.g. rp_filter). We could be more
explicit and add configuration of the rp_filter to the test, sure,
that's what you're proposing in the comment below I guess.
But I doubt the purpose of this test a bit. I'm not even sure what
this test tests. Is it check if rp_filter=1 works as expected?
What's the value of this test for customers? Not quite sure.
Yeah that makes sense. My understanding was that it tests the same
"feature" as the test that separates the VMs into different vlans but
just simulates it on a simpler (just two baremetal hosts) network.
So that makes it a "duplicated" test and if noone in the team sees it as
valuable in this scenario then we can/should remove it... Thanks for the