Skip to main content
Bumped by Community user
deleted 12 characters in body; edited title
Source Link
Ghanima
  • 15.9k
  • 16
  • 63
  • 120

Raspberry Pi access point as OVS bridge rather than Linux bridge [Repost]

[Repost]

In my setup I have an OpenVSwitch on a Raspberry Pi.

Using the below tutorial I set up an access point on the Raspberry Pi (This is done by creating a bridge between eth0 and wlan0) I could successfully connect devices to the internet by connecting to the Raspberry Pi.

https://www.raspberrypi.org/documentation/configuration/wireless/access-point.md

Next I needed to connect the OpenVSwitch to the OpenDaylight controller. This is done by creating the an OpenVSwitch bridge between the controller and eth0. But the problem is that eth0 appears busy due to the Raspberry Pi access point.

I tried doing it the other way round i.e. by adding the the wlan0 to the OpenVSwitch bridge. But doing it that way, devices are not able to connect to the raspberry pi and I am not sure what the problem is.

Raspberry Pi access point as OVS bridge rather than Linux bridge [Repost]

[Repost]

In my setup I have an OpenVSwitch on a Raspberry Pi.

Using the below tutorial I set up an access point on the Raspberry Pi (This is done by creating a bridge between eth0 and wlan0) I could successfully connect devices to the internet by connecting to the Raspberry Pi.

https://www.raspberrypi.org/documentation/configuration/wireless/access-point.md

Next I needed to connect the OpenVSwitch to the OpenDaylight controller. This is done by creating the an OpenVSwitch bridge between the controller and eth0. But the problem is that eth0 appears busy due to the Raspberry Pi access point.

I tried doing it the other way round i.e. by adding the the wlan0 to the OpenVSwitch bridge. But doing it that way, devices are not able to connect to the raspberry pi and I am not sure what the problem is.

Raspberry Pi access point as OVS bridge rather than Linux bridge

In my setup I have an OpenVSwitch on a Raspberry Pi.

Using the below tutorial I set up an access point on the Raspberry Pi (This is done by creating a bridge between eth0 and wlan0) I could successfully connect devices to the internet by connecting to the Raspberry Pi.

https://www.raspberrypi.org/documentation/configuration/wireless/access-point.md

Next I needed to connect the OpenVSwitch to the OpenDaylight controller. This is done by creating the an OpenVSwitch bridge between the controller and eth0. But the problem is that eth0 appears busy due to the Raspberry Pi access point.

I tried doing it the other way round i.e. by adding the the wlan0 to the OpenVSwitch bridge. But doing it that way, devices are not able to connect to the raspberry pi and I am not sure what the problem is.

Source Link

Raspberry Pi access point as OVS bridge rather than Linux bridge [Repost]

[Repost]

In my setup I have an OpenVSwitch on a Raspberry Pi.

Using the below tutorial I set up an access point on the Raspberry Pi (This is done by creating a bridge between eth0 and wlan0) I could successfully connect devices to the internet by connecting to the Raspberry Pi.

https://www.raspberrypi.org/documentation/configuration/wireless/access-point.md

Next I needed to connect the OpenVSwitch to the OpenDaylight controller. This is done by creating the an OpenVSwitch bridge between the controller and eth0. But the problem is that eth0 appears busy due to the Raspberry Pi access point.

I tried doing it the other way round i.e. by adding the the wlan0 to the OpenVSwitch bridge. But doing it that way, devices are not able to connect to the raspberry pi and I am not sure what the problem is.