[elmiomar]

I want to install the kmod-openvsiwtch kernel  module on my Zodiac WX.
When installing the module, I get the following error:

Collected errors:
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-openvswitch:
 *    kernel (= 4.4.132-1-33d452ad71ac13bc6dc71df37efa5ec7) *    kernel (= 4.4.132-1-33d452ad71ac13bc6dc71df37efa5ec7) *    kernel (= 4.4.132-1-33d452ad71ac13bc6dc71df37efa5ec7) *    kernel (= 4.4.132-1-33d452ad71ac13bc6dc71df37efa5ec7) *    kernel (= 4.4.132-1-33d452ad71ac13bc6dc71df37efa5ec7) *    kernel (= 4.4.132-1-33d452ad71ac13bc6dc71df37efa5ec7) *    kernel (= 4.4.132-1-33d452ad71ac13bc6dc71df37efa5ec7) *    kernel (= 4.4.132-1-33d452ad71ac13bc6dc71df37efa5ec7) *    kernel (= 4.4.132-1-33d452ad71ac13bc6dc71df37efa5ec7) *    kernel (= 4.4.132-1-33d452ad71ac13bc6dc71df37efa5ec7) *    kernel (= 4.4.132-1-33d452ad71ac13bc6dc71df37efa5ec7) *
 * opkg_install_cmd: Cannot install package kmod-openvswitch.

My current kernel version is 4.4.71.

[Paul Zanna]

Sometimes when applications are updated that have kernel dependencies they are set to require the latest possible kernel version at the time. Unfortunately, as kernel updates can't be done in isolation they require a complete resync with OpenWRT and full recompile so it is not possible to create and test a new firmware release for every minor kernel release.

If it helps I'll see if we can include OVS pre-installed in the next firmware release.

Regards,
Paul

[elmiomar]

Hi Paul,

Thanks for the reply!
I updated the kernel using the latest build version (v1.20 Build 20180621_5).

Indeed, openvswitch (and tools like ovs-vsctl or ovs-ofctl) comes pre-installed in this version. However, the OVS switch that is running (called ovslan), has a pre-configured controller IP address (192.168.1.136). I assigned this address (and other addresses on the same subnet) to our ODL controller, but it seems like the OVS switch does not connect properly to the controller. I can see on the controller that a new switch is connected, but the flows do not appear on the switch.

I assume the controller and the ovslan should be on the same subnet. Because when I set the controller on a different subnet than the ovslan, I can't access the switch anymore on 192.168.1.0/24.

Any ideas where the issue might be?

Cheers,
Omar

[Paul Zanna]

Hi Omar,

The controller IP address and port can change to whatever you like by going to System->Starup and modifying the settings in the startup script, there are more details here. The controller also runs in-band so it can be anywhere that has IP connectivity from the WX.

If the controller is not running any applications that will install the required flows you will lose connectivity on the LAN port and for the wireless clients because there are no flows to allow the traffic. It is set to "fail stand-alone" mode by default so if you stop the controller it will allow traffic again.

Regards,
Paul