This group is locked. No changes can be made to the group while it is locked.
Date 1 - 1 of 1
Single Ethernet WiFi AP Connection to OpenDayLight controller Yahoo / Sent
|1 - 1 of 1|
I have a wireless WiFi access point which has a single Ethernet port. An OPENWrt operating system is installed on this wireless access point. I installed on it an openvswitch along with OpenFlow 1.3.
When I use this commands on the WiFi AP:
ovs-vsctl set-controller bridge name tcp: IP of controller: service port
The WiFi becomes unpingable: I mean that I can no longer ping it even from the controller itself.
When I read in the deployment recommendations, I have found out that there should be the followings:
Separate the data network (that connects devices using the network) from the management network (that connects the network devices to OpenDaylight).
Deploying OpenDaylight on a separate, private management network does not eliminate threats, but only mitigates them. By construction, some messages must flow from the data network to the management network, e.g., OpenFlow packet_inmessages, and these create an attack surface even if it is a small one.
However, I have a single Ethernet port for the WiFi AP. How I can separate the management network from the data network on a single ethernet port.
This AP has a single Ethernet port.
Why you don't put a help page on how to connect an OpenFlow enabled switch to an OpenDayLight controller.
Where is it explained such a configuration?
Looking forward very much to receiving your reply!
I need your help!!!
|1 - 1 of 1|