TapBridge allows a real host to participate in an ns-3 simulation as if it were one of the simulated nodes. Nodes are simulated, the network is real. The primary use for this configuration is to generate repeatable experimental results in a real-world network environment that includes all of the ns-3 tracing, logging, visualization and statistics gathering tools. This allows ns-3 applications and protocol stacks attached to a simulation node to communicate over real hardware. Instead of an ns-3 channel connecting ns-3 nodes, real hardware provided by the testbed can be used. This allows ns-3 simulations to read frames from and write frames to a network device on the host. These two options are covered by two different kinds of ns-3 modules: FdNetDevice and TapBridge.įdNetDevice can read and write from a file descriptor, which can be associated to a network device (via raw socket). Another possibility is to drive a simulated network with packets from real nodes. It means, that packets originating from simulated nodes can be processed by a real network. In that mode, the simulator can exchange packets in real-time with the outside world. Ns-3 network simulator has ability to work in so called real-time/emulation mode. Architecture: single ns-3 thread or multiple processes?.How to achieve communication of ns-3 process with TAP interfaces in distinct namespaces?.Anyways, I wish you the best of luck with your project. > In case you end up using some of my work, I would appreciate some > Everything is in spanish, but I don't think Google Translate will give > different statistics of a network consisting on VirtualBox instances and > consists on the development of a Java application in order to keep track of > part of my paper was the section 6.2 (you might find it interesting, it > limiting it to turning on and off the different interfaces, as the main > However, the configuration changes made through NETCONF were VERY simple, > network of OpenVSwitches in Mininet and managed it through NETCONF. > interested in section 6: "Prueba de concepto", more specifically in 6.1: Attached on this message you will find what I did (it's not > Reply to this email directly, view it on GitHubĮl jue., 20 feb. > You are receiving this because you were mentioned. Do you have your project details anywhere? > I found your original post from Google, and I'm interested in running a In case you end up using some of my work, I would appreciate some Part of my paper was the section 6.2 (you might find it interesting, itĬonsists on the development of a Java application in order to keep track ofĭifferent statistics of a network consisting on VirtualBox instances andĮverything is in spanish, but I don't think Google Translate will give you Limiting it to turning on and off the different interfaces, as the main However, the configuration changes made through NETCONF were VERY simple, Network of OpenVSwitches in Mininet and managed it through NETCONF. Interested in section 6: "Prueba de concepto", more specifically in 6.1: Attached on this message you will find what I did (it's notĬompleted as I can't find it □). All this is possible but I do not think anyone has demonstrated such a hybrid network yet. SIL for netconfd or confd etc.), and OpenDaylight integrating the NETCONF southbound node model. ietf-network-bridge), device implementation (e.g. This is something that requires a model (e.g. This is translated to edit-config + commit on the NETCONF southbound interface.ĭevelop/enhance the existing network based YANG model implementation in OpenDaylight for flow enabled nodes so they can be used transparently in a hybrid network with the openflow nodes ( ). That said if you have an implementation of nodes with NETCONF interface instead of OpenFlow you have 2 options:ĭirectly accessing the node model datastores mounted as NETCONF devices in OpenDaylight - see for example deleting a container using the RESTCONF interface. I think the intention was to use NETCONF as northbound interface and manage the OpenDaylight controller (the yangcli command lines do exactly that). I am not sure your project assignment has a requirement to use NETCONF as southbound interface to the nodes since mininet has OpenFlow implementation that is the default and supported southbound interface for flow enabled nodes network model in OpenDaylight. # mn -topo linear,3 -mac -controller=remote,ip=127.0.0.1,port=6633 -switch ovs,protocols=OpenFlow10 Your OpenDaylight will listen on port 6633 for incoming OpenFlow connections and add to the openflow network all connecting nodes. mininet nodes are managed over OpenFlow (not NETCONF). Well OpenDaylight is running a NETCONF server (along with RESTCONF) for a network (not node) based YANG model.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |