Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connecting a remote interface without creating a VLAN on top #5710

Merged
merged 1 commit into from
May 23, 2022
Merged

Connecting a remote interface without creating a VLAN on top #5710

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 8 additions & 9 deletions examples/use-cases/Kernel2RVlanMultiNS/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,9 +85,9 @@ spec:
- name: NSM_CONNECT_TO
value: "registry.nsm-system:5002"
- name: NSM_SERVICES
value: "private-bridge.${FIRST_NAMESPACE} { vlan: 200; via: gw1 }"
value: "private-bridge.${FIRST_NAMESPACE} { vlan: 0; via: gw1 }"
- name: NSM_CIDR_PREFIX
value: 172.10.1.0/24,100:201::/64
value: 172.10.1.0/24
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we clipping v6 out of the example here?

EOF
```

Expand Down Expand Up @@ -217,7 +217,7 @@ spec:
- name: NSM_SERVICES
value: "blue-bridge.${SECOND_NAMESPACE} { vlan: 300; via: gw1 }, green-bridge.${SECOND_NAMESPACE} { vlan: 400; via: gw1 }"
- name: NSM_CIDR_PREFIX
value: 172.10.2.0/24,100:202::/64
value: 172.10.2.0/24
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we clipping v6 out of the example here?

Copy link
Contributor Author

@ljkiraly ljkiraly May 23, 2022 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@edwarnicke: Currently this TC does not check IPv6 connections - can be confusing. IPv6 for nse-remote-vlan is tested by Kernel2KernelRvlanInternal

EOF
```

Expand Down Expand Up @@ -344,12 +344,11 @@ Setup a docker container for traffic test:
docker run --cap-add=NET_ADMIN --rm -d --network bridge-2 --name rvm-tester rvm-tester tail -f /dev/null
docker exec rvm-tester ip link set eth0 down
docker exec rvm-tester ip link add link eth0 name eth0.100 type vlan id 100
docker exec rvm-tester ip link add link eth0 name eth0.200 type vlan id 200
docker exec rvm-tester ip link add link eth0 name eth0.300 type vlan id 300
docker exec rvm-tester ip link add link eth0 name eth0.400 type vlan id 400
docker exec rvm-tester ip link set eth0 up
docker exec rvm-tester ip addr add 172.10.0.254/24 dev eth0.100
docker exec rvm-tester ip addr add 172.10.1.254/24 dev eth0.200
docker exec rvm-tester ip addr add 172.10.1.254/24 dev eth0
docker exec rvm-tester ip addr add 172.10.2.254/24 dev eth0.300
docker exec rvm-tester ip addr add 172.10.2.253/24 dev eth0.400
docker exec rvm-tester ethtool -K eth0 tx off
Expand Down Expand Up @@ -385,7 +384,7 @@ do
status=2
fi
done
docker exec rvm-tester ping -c 1 ${IP_ADDR[$nsc]} -I eth0.200
docker exec rvm-tester ping -c 1 ${IP_ADDR[$nsc]} -I eth0
if test $? -ne 0
then
status=1
Expand Down Expand Up @@ -425,7 +424,7 @@ Check vlan (300 and 400) from tester container:
status=0
for nsc in "${NSCS_BLUE[@]}"
do
for vlan_if_name in eth0.100 eth0.200 eth0.400
for vlan_if_name in eth0.100 eth0 eth0.400
do
docker exec rvm-tester ping -w 1 -c 1 ${IP_ADDR_BLUE[$nsc]} -I ${vlan_if_name}
if test $? -eq 0
Expand All @@ -441,7 +440,7 @@ do
done
for nsc in "${NSCS_GREEN[@]}"
do
for vlan_if_name in eth0.100 eth0.200 eth0.300
for vlan_if_name in eth0.100 eth0 eth0.300
do
docker exec rvm-tester ping -w 1 -c 1 ${IP_ADDR_GREEN[$nsc]} -I ${vlan_if_name}
if test $? -eq 0
Expand Down Expand Up @@ -483,7 +482,7 @@ Check first vlan from tester container:
status=0
for nsc in "${NSCS[@]}"
do
for vlan_if_name in eth0.200 eth0.300 eth0.400
for vlan_if_name in eth0 eth0.300 eth0.400
do
docker exec rvm-tester ping -w 1 -c 1 ${IP_ADDR[$nsc]} -I ${vlan_if_name}
if test $? -eq 0
Expand Down