[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fc462436-af77-2c95-ec79-6cc418ef126e@gmail.com>
Date: Mon, 2 Jul 2018 09:12:25 -0600
From: David Ahern <dsahern@...il.com>
To: Xin Long <lucien.xin@...il.com>,
network dev <netdev@...r.kernel.org>
Cc: davem@...emloft.net, Davide Caratti <dcaratti@...hat.com>,
idosch@...sch.org
Subject: Re: [PATCHv2 net-next 2/2] selftests: add a selftest for directed
broadcast forwarding
On 7/2/18 12:30 AM, Xin Long wrote:
> +ping_ipv4()
> +{
> + sysctl_set net.ipv4.icmp_echo_ignore_broadcasts 0
> + bc_forwarding_disable
> + ping_test $h1 198.51.100.255
> +
> + iptables -A INPUT -i vrf-r1 -p icmp -j DROP
> + bc_forwarding_restore
> + bc_forwarding_enable
> + ping_test $h1 198.51.100.255
> +
> + bc_forwarding_restore
> + iptables -D INPUT -i vrf-r1 -p icmp -j DROP
> + sysctl_restore net.ipv4.icmp_echo_ignore_broadcasts
> +}
Both tests fail for me:
TEST: ping [FAIL]
TEST: ping [FAIL]
Why the need for the iptables rule?
And, PAUSE_ON_FAIL is not working to take a look at why tests are
failing. e.g.,
PAUSE_ON_FAIL=yes ./router_broadcast.sh
just continues on. Might be something with the infrastructure scripts.
Powered by blists - more mailing lists