Wind River Support Network

HomeDefectsOVP8-473
Fixed

OVP8-473 : Kernel Configs different in WRL7 and WRL8 - Causes Regression

Created: Mar 14, 2019    Updated: Dec 23, 2019
Resolved Date: Apr 1, 2019
Found In Version: 8.0.0.25
Fix Version: 8.0.0.30
Severity: Severe
Applicable for: Wind River Linux 8
Component/s: Kernel , Userspace

Description

Trying to sending traffic to two VMs, the test topology described as below:
----------------
VM1 with two interfaces say vnet1 and vnet2.
VM2 with two interfaces say vnet3 and vnet4
Eth0br (Linux Bridge) should have two interfaces: eth0(NIC) and vnet1
Testbr0 (Linux Bridge) should have two interfaces vnet2 and vnet3
Eth1br (Linux Bridge) should have two interfaces vnet4 and eth1(nic)
 
Traffic should flow bi-directionally as the following:
Iperf client => Eth0 => eth0br => vnet1 (To VM1) => vnet2 (From VM1) =>testbr0 =>vnet3 (To VM2) => vnet4 (From VM2) => eth1br => eth1 => iperf server
 
When you are sending the traffic, create 8 Flows(Different IP, Port and MAC)
----------------

VM configuration and traffic configuration:
----------
Configure the following to setup “uni-directional one flow” traffic as following:
TG1 should send 100.100.100.100 to 200.200.200.200 with gateway as 100.100.100.1 on vlan 100
TG2 should send 200.200.200.200 to 100.100.100.100 with gateway as 200.200.200.1 on vlan 200

On VM1:
/sbin/sysctl -w net.ipv4.ip_forward=1
service iptables stop
ifconfig eth0 up
ip link add link eth0 name eth0.100 type vlan id 100
ip addr add 100.100.100.1/24 dev eth0.100
ip link set dev eth0.100 up  
ifconfig eth1 up
ip link add link eth1 name eth1.10 type vlan id 10
ip addr add 10.10.10.1/24 dev eth1.10
ip link set dev eth1.10 up
route add -net 200.200.200.0 netmask 255.255.255.0 gw 10.10.10.2

 
On VM2:
/sbin/sysctl -w net.ipv4.ip_forward=1
service iptables stop
ifconfig eth0 up
ip link add link eth0 name eth0.100 type vlan id 10
ip addr add 10.10.10.2/24 dev eth0.10
ip link set dev eth0.10 up  
ifconfig eth1 up
ip link add link eth1 name eth1.200 type vlan id 200
ip addr add 200.200.200.1/24 dev eth1.200
ip link set dev eth1.200 up
route add -net 100.100.100.0 netmask 255.255.255.0 gw 10.10.10.1

No IP/ route configuration is needed on any of the bridges/ interfaces on hypervisor

Steps to Reproduce

VM1 with two interfaces say vnet1 and vnet2.
VM2 with two interfaces say vnet3 and vnet4
Eth0br (Linux Bridge) should have two interfaces: eth0(NIC) and vnet1
Testbr0 (Linux Bridge) should have two interfaces vnet2 and vnet3
Eth1br (Linux Bridge) should have two interfaces vnet4 and eth1(nic)
 
Traffic should flow bi-directionally as the following:
Iperf client => Eth0 => eth0br => vnet1 (To VM1) => vnet2 (From VM1) =>testbr0 =>vnet3 (To VM2) => vnet4 (From VM2) => eth1br => eth1 => iperf server

Configure the following to setup “uni-directional one flow” traffic as following:
TG1 should send 100.100.100.100 to 200.200.200.200 with gateway as 100.100.100.1 on vlan 100
TG2 should send 200.200.200.200 to 100.100.100.100 with gateway as 200.200.200.1 on vlan 200

On VM1:
/sbin/sysctl -w net.ipv4.ip_forward=1
service iptables stop
ifconfig eth0 up
ip link add link eth0 name eth0.100 type vlan id 100
ip addr add 100.100.100.1/24 dev eth0.100
ip link set dev eth0.100 up  
ifconfig eth1 up
ip link add link eth1 name eth1.10 type vlan id 10
ip addr add 10.10.10.1/24 dev eth1.10
ip link set dev eth1.10 up
route add -net 200.200.200.0 netmask 255.255.255.0 gw 10.10.10.2

 
On VM2:
/sbin/sysctl -w net.ipv4.ip_forward=1
service iptables stop
ifconfig eth0 up
ip link add link eth0 name eth0.100 type vlan id 10
ip addr add 10.10.10.2/24 dev eth0.10
ip link set dev eth0.10 up  
ifconfig eth1 up
ip link add link eth1 name eth1.200 type vlan id 200
ip addr add 200.200.200.1/24 dev eth1.200
ip link set dev eth1.200 up
route add -net 100.100.100.0 netmask 255.255.255.0 gw 10.10.10.1

No IP/ route configuration is needed on any of the bridges/ interfaces on hypervisor
Live chat
Online