On Wed Jul 04 09:00:58 2018, john.koss11@... wrote:
> Dear Sir,I have a  wireless WiFi access point which has a single
> ethernet port.
> Thus runs OPENWrt operating system.
>  I installed on this openvswitch.
>
> 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).
> Note
> 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.Looking forward
> very much to receiving your reply!
> Thanks,Best regards,John.


Greetings John,

You've contacted the infrastructure team for the OpenDaylight project which handles resources and infrastructure for the OpenDaylight project. I think you intended to contact the OpenDaylight dev community. I would recommend sending your email to the opendaylight-users mailing list:

    https://lists.opendaylight.org/mailman/listinfo/opendaylight-users

Which will send you to the folks who can help you with OpenDaylight usage issues.

Hope this helps,
Thanh

_______________________________________________
dev mailing list
dev@...
https://lists.opendaylight.org/mailman/listinfo/dev