You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The local_test_interfaces1.sh has been renamed as flaky_local_test_interfaces1.sh in order to be excluded from the pcn-iptables tests execution as it fails on the new Jenkins slaves.
The script tests the connectivity between two namespaces by using the ping command, expecting to have packet loss when the forwarding policy is not set to ACCEPT on both veth1 and veth2 interfaces exposed by the two namespaces.
When the forwarding policy is set to DROP on both the interfaces, the echo-requests sent from one namespace to the other are correctly dropped.
When the forwarding policy is set to ACCEPT on one of the two interfaces by running pcn-iptables -A FORWARD -i veth1 -j ACCEPT
or pcn-iptables -A FORWARD -i veth2 -j ACCEPT
the echo-requests receive responses instead of having packet loss in the forwarding.
To Reproduce
Install required tools:
sudo apt-get install git net-tools
Clone the Polycube repository:
git clone https://github.com/polycube-network/polycube
cd polycube
git submodule update --init --recursive
Launch the automatic install script:
./scripts/install.sh
Execute the failing test:
cd src/services/pcn-iptables/test
./flaky_local_test_interfaces1.sh
Show test result:
echo $? # will display 1
Expected behavior
The test executes
pcn-iptables -P FORWARD DROP
pcn-iptables -A FORWARD -i veth1 -j ACCEPT
test_fail sudo ip netns exec ns1 ping 10.0.2.1 -c 2 -W 2
expecting the packets to be dropped as forwarding is enabled only on interface veth1 and the echo requests should not receive any reply.
a port was assigned with id 0. Don't assign port id 0 to any port should
be able to fix the issue. notes that this fix is part of fixing 233,
another part of fixing is in libiptc library: need to parse interface,
which is fixed in another commit.
please refer to issue:
#233
a port was assigned with id 0. Don't assign port id 0 to any port should
be able to fix the issue.
please refer to issue:
#233
Signed-off-by: Jianwen Pi<jianwpi@gmail.com>
Describe the bug
The
local_test_interfaces1.sh
has been renamed asflaky_local_test_interfaces1.sh
in order to be excluded from thepcn-iptables
tests execution as it fails on the new Jenkins slaves.The script tests the connectivity between two namespaces by using the
ping
command, expecting to have packet loss when the forwarding policy is not set toACCEPT
on bothveth1
andveth2
interfaces exposed by the two namespaces.When the forwarding policy is set to
DROP
on both the interfaces, the echo-requests sent from one namespace to the other are correctly dropped.When the forwarding policy is set to
ACCEPT
on one of the two interfaces by runningpcn-iptables -A FORWARD -i veth1 -j ACCEPT
or
pcn-iptables -A FORWARD -i veth2 -j ACCEPT
the echo-requests receive responses instead of having packet loss in the forwarding.
To Reproduce
Install required tools:
Clone the Polycube repository:
Launch the automatic install script:
Execute the failing test:
Show test result:
Expected behavior
The test executes
expecting the packets to be dropped as forwarding is enabled only on interface
veth1
and the echo requests should not receive any reply.Please tell us about your environment:
local_test_interfaces1.sh.log
polycubed.log
The text was updated successfully, but these errors were encountered: