Re: [nox-dev] routing module
Hi Linbo. I attached a script in Python that Bob Lantz sent me once. If you are using Mininet is just edit the file with your topology and change the hosts IPs to the desired ones. In this case you will not have to be worried about switch. I think the script solve you problem. But you can also configure switch with ifconfig command and set it as default route to the host in subnet. Then you can create ARP packets or insert entries in its ARP entries, using the command *arp -s ip_of_default_switch mac_of_default_switch, *as explained in exercise of Router Creating. Let me know the result after you try it. Hope it helps. Best Regards. 2011/9/4 linbo li...@csnet1.cs.tsinghua.edu.cn ** Hi Ricardo. Thank you for your reply. I have read the page: http://www.openflow.org/wk/index.php/OpenFlow_Tutorial#Create_Router, and I try it,is there anything else to do except configing the ip address,routing info ? Does the SW need to be configed ?If so,how to config it? Thank you! 2011-09-05 -- linbo -- *发件人：* Ricardo Bennesby *发送时间：* 2011-09-03 08:22:41 *收件人：* linbo *抄送：* nox-dev *主题：* Re: [nox-dev] routing module Hi Linbo. You can take a look on this link, it might helps: http://www.openflow.org/wk/index.php/OpenFlow_Tutorial#Create_Router This exercise of create a router to link two subnets helped on my group ongoing research. We are developing a NOX component that can do routing between two or more Networks or Domains. We are using multiples Mininets. Each Mininet represents a domain. If you have any doubt, feel free to ask. Best regards. 2011/9/1 linbo li...@csnet1.cs.tsinghua.edu.cn ** I want to know whether nox implement the function that enalbe two hosts in different subnets ping each other? Here is my topo: host1 host2 host3 host4 | | | | OFSWE1--OFSWC1---OFSWE2=== == 192.168.1.0/24 192.168.2.0/24 _||___ 1.Can host1 ping host3,the routing module can do this? 2.and I also want to know how the routing module to recompute the route path when a link failure happend? Hope someone can help me. Thank you! 2011-09-02 -- linbo ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev -- Ricardo Bennesby da Silva Ciência da Computação - UFAM LabCIA - Laboratório de Computação Inteligente e Autonômica !DSPAM:1,4e61735132087516139689! -- Ricardo Bennesby da Silva Ciência da Computação - UFAM LabCIA - Laboratório de Computação Inteligente e Autonômica script.py Description: Binary data ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] routing module
Hi Ricardo. Thank you for your reply. I have read the page: http://www.openflow.org/wk/index.php/OpenFlow_Tutorial#Create_Router, and I try it,is there anything else to do except configing the ip address,routing info ? Does the SW need to be configed ?If so,how to config it? Thank you! 2011-09-05 linbo 发件人： Ricardo Bennesby 发送时间： 2011-09-03 08:22:41 收件人： linbo 抄送： nox-dev 主题： Re: [nox-dev] routing module Hi Linbo. You can take a look on this link, it might helps: http://www.openflow.org/wk/index.php/OpenFlow_Tutorial#Create_Router This exercise of create a router to link two subnets helped on my group ongoing research. We are developing a NOX component that can do routing between two or more Networks or Domains. We are using multiples Mininets. Each Mininet represents a domain. If you have any doubt, feel free to ask. Best regards. 2011/9/1 linbo li...@csnet1.cs.tsinghua.edu.cn I want to know whether nox implement the function that enalbe two hosts in different subnets ping each other? Here is my topo: host1 host2 host3 host4 | | | | OFSWE1--OFSWC1---OFSWE2=== == 192.168.1.0/24 192.168.2.0/24 _||___ 1.Can host1 ping host3,the routing module can do this? 2.and I also want to know how the routing module to recompute the route path when a link failure happend? Hope someone can help me. Thank you! 2011-09-02 linbo ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev -- Ricardo Bennesby da Silva Ciência da Computação - UFAM LabCIA - Laboratório de Computação Inteligente e Autonômica !DSPAM:1,4e61735132087516139689! ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] routing module
Hi Linbo, if you want to do traditional IP routing and forwarding on OpenFlow networks you may want to have a look at RouteFlow: https://sites.google.com/site/routeflow/ The second tutorial we are about to release demonstrates a four router network running OSPF: https://sites.google.com/site/routeflow/documents/tutorial2-four-routers-with-ospf You can look in the code to see how IP forwarding rules are installed in the OpenFlow switches. -Christian On Fri, Sep 2, 2011 at 02:30, linbo li...@csnet1.cs.tsinghua.edu.cn wrote: ** Hi,Srini Seetharaman : Thank you for your help ! You are so warm-hearted,I will read the paper you provided. I have checked the mail list ,but unfortunately I didn't found anybody write that code. 2011-09-02 -- linbo -- *发件人：* Srini Seetharaman *发送时间：* 2011-09-02 13:22:18 *收件人：* linbo *抄送：* nox-dev *主题：* Re: Re: [nox-dev] routing module Thank you Srini Seetharaman ！ Besides conventional IP routing,which type of communication does nox support? Basic NOX comes with MAC learning switch and shortest path routing. How the nox decide a path from a source host to the destination host? If you used the routing module, it uses the shortest path algorithm described in http://www.dis.uniroma1.it/~demetres/docs/dapsp-full.pdf Are all the experiments until now in the same subnet or didn't use conventional IP routing? I can't speak for all the experimenters using NOX. It's possible there are others who wrote code for conventional IP routing. !DSPAM:1,4e60680a32083662284889! __ Information from ESET Smart Security, version of virus signature database 6428 (20110901) __ The message was checked by ESET Smart Security. http://www.eset.com ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev -- Christian ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] routing module
Hi Linbo. You can take a look on this link, it might helps: http://www.openflow.org/wk/index.php/OpenFlow_Tutorial#Create_Router This exercise of create a router to link two subnets helped on my group ongoing research. We are developing a NOX component that can do routing between two or more Networks or Domains. We are using multiples Mininets. Each Mininet represents a domain. If you have any doubt, feel free to ask. Best regards. 2011/9/1 linbo li...@csnet1.cs.tsinghua.edu.cn ** I want to know whether nox implement the function that enalbe two hosts in different subnets ping each other? Here is my topo: host1 host2 host3 host4 | | | | OFSWE1--OFSWC1---OFSWE2=== == 192.168.1.0/24 192.168.2.0/24 _||___ 1.Can host1 ping host3,the routing module can do this? 2.and I also want to know how the routing module to recompute the route path when a link failure happend? Hope someone can help me. Thank you! 2011-09-02 -- linbo ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev -- Ricardo Bennesby da Silva Ciência da Computação - UFAM LabCIA - Laboratório de Computação Inteligente e Autonômica ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
[nox-dev] routing module
I want to know whether nox implement the function that enalbe two hosts in different subnets ping each other? Here is my topo: host1 host2 host3 host4 | | | | OFSWE1--OFSWC1---OFSWE2=== == 192.168.1.0/24 192.168.2.0/24 _||___ 1.Can host1 ping host3,the routing module can do this? 2.and I also want to know how the routing module to recompute the route path when a link failure happend? Hope someone can help me. Thank you! 2011-09-02 linbo ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] routing module
No, you need to write code to make it behave as a IP router. Please look at this earlier thread: http://noxrepo.org/pipermail/nox-dev/2011-April/007494.html On Thu, Sep 1, 2011 at 7:23 PM, linbo li...@csnet1.cs.tsinghua.edu.cn wrote: I want to know whether nox implement the function that enalbe two hosts in different subnets ping each other? Here is my topo: host1 host2 host3 host4 | | | | OFSWE1--OFSWC1---OFSWE2=== == 192.168.1.0/24 192.168.2.0/24 _||___ 1.Can host1 ping host3,the routing module can do this? 2.and I also want to know how the routing module to recompute the route path when a link failure happend? Hope someone can help me. Thank you! 2011-09-02 linbo ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] routing module
Thank you Srini Seetharaman ！ Besides conventional IP routing,which type of communication does nox support? How the nox decide a path from a source host to the destination host? Are all the experiments until now in the same subnet or didn't use conventional IP routing? Thank you 2011-09-02 linbo 发件人： Srini Seetharaman 发送时间： 2011-09-02 11:42:08 收件人： linbo 抄送： nox-dev 主题： Re: [nox-dev] routing module No, you need to write code to make it behave as a IP router. Please look at this earlier thread: http://noxrepo.org/pipermail/nox-dev/2011-April/007494.html On Thu, Sep 1, 2011 at 7:23 PM, linbo li...@csnet1.cs.tsinghua.edu.cn wrote: I want to know whether nox implement the function that enalbe two hosts in different subnets ping each other? Here is my topo: host1 host2 host3 host4 | | | | OFSWE1--OFSWC1---OFSWE2=== == 192.168.1.0/24 192.168.2.0/24 _||___ 1.Can host1 ping host3,the routing module can do this? 2.and I also want to know how the routing module to recompute the route path when a link failure happend? Hope someone can help me. Thank you! 2011-09-02 linbo ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev !DSPAM:1,4e60509032081270696225! __ Information from ESET Smart Security, version of virus signature database 6428 (20110901) __ The message was checked by ESET Smart Security. http://www.eset.com ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] routing module
Hi,Srini Seetharaman : Thank you for your help ! You are so warm-hearted,I will read the paper you provided. I have checked the mail list ,but unfortunately I didn't found anybody write that code. 2011-09-02 linbo 发件人： Srini Seetharaman 发送时间： 2011-09-02 13:22:18 收件人： linbo 抄送： nox-dev 主题： Re: Re: [nox-dev] routing module Thank you Srini Seetharaman ！ Besides conventional IP routing,which type of communication does nox support? Basic NOX comes with MAC learning switch and shortest path routing. How the nox decide a path from a source host to the destination host? If you used the routing module, it uses the shortest path algorithm described in http://www.dis.uniroma1.it/~demetres/docs/dapsp-full.pdf Are all the experiments until now in the same subnet or didn't use conventional IP routing? I can't speak for all the experimenters using NOX. It's possible there are others who wrote code for conventional IP routing. !DSPAM:1,4e60680a32083662284889! __ Information from ESET Smart Security, version of virus signature database 6428 (20110901) __ The message was checked by ESET Smart Security. http://www.eset.com ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
[nox-dev] Routing Module
Hi, I built and run nox according to the instructions given in the wiki page[1]. But I couldn't get routing module running. nox_core complains that it is not installed. That is, /usr/local/src/nox/build/src# ./nox_core -v -i ptcp:6633 routing 1|nox|INFO:Starting nox_core (/usr/local/src/nox/build/src/.libs/lt-nox_core) 2|nox|DBG:Application installation report: 3|nox|DBG:built-in event dispatcher: Current state: INSTALLED Required state: INSTALLED Dependencies: 4|nox|DBG:topology: Current state: NOT_INSTALLED Required state: INSTALLED Dependencies: 'discovery' not found 5|nox|DBG:built-in DSO deployer: Current state: INSTALLED Required state: INSTALLED Dependencies: 6|nox|DBG:routing_module: Current state: NOT_INSTALLED Required state: INSTALLED Dependencies: 'topology' not installed, 'nat_enforcer' not found 7|nox|DBG:routing: Current state: NOT_INSTALLED Required state: INSTALLED Dependencies: 'routing_module' not installed, 'authenticator' not found 8|nox|ERR:Application 'discovery' description not found. How can I install missing modules? Best. [1] http://noxrepo.org/noxwiki/index.php/NOX_Installation ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] Routing Module
If you check your configure log, I think you'll see that Python is disabled (most likely because Twisted isn't installed). If you fix this, you'll probably find routing will work. -- Murphy On Jul 8, 2011, at 4:14 AM, Volkan YAZICI wrote: Hi, I built and run nox according to the instructions given in the wiki page[1]. But I couldn't get routing module running. nox_core complains that it is not installed. That is, /usr/local/src/nox/build/src# ./nox_core -v -i ptcp:6633 routing 1|nox|INFO:Starting nox_core (/usr/local/src/nox/build/src/.libs/lt-nox_core) 2|nox|DBG:Application installation report: 3|nox|DBG:built-in event dispatcher: Current state: INSTALLED Required state: INSTALLED Dependencies: 4|nox|DBG:topology: Current state: NOT_INSTALLED Required state: INSTALLED Dependencies: 'discovery' not found 5|nox|DBG:built-in DSO deployer: Current state: INSTALLED Required state: INSTALLED Dependencies: 6|nox|DBG:routing_module: Current state: NOT_INSTALLED Required state: INSTALLED Dependencies: 'topology' not installed, 'nat_enforcer' not found 7|nox|DBG:routing: Current state: NOT_INSTALLED Required state: INSTALLED Dependencies: 'routing_module' not installed, 'authenticator' not found 8|nox|ERR:Application 'discovery' description not found. How can I install missing modules? Best. [1] http://noxrepo.org/noxwiki/index.php/NOX_Installation ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] Routing Module
hi volkan you should rebuild your nox, maybe this will take you a long time. try: cd /home/openflow/noxcore ./boot.sh cd build ../configure make -j ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] Routing module
Yes that would be my fault, I was not running any traffic when I sent you the example. Here it is: ^C10:58:16 a...@pcepatr39[src]$ sudo ./nox_core -v -i ptcp:2525 routing 1|nox|DBG:Starting nox_core (/opt/nox-0.5.0~full~beta/src/.libs/lt-nox_core) 2|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/webapps/storagews/meta.xml'. 3|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/webapps/webserver/meta.xml'. 4|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/coreapps/pyrt/meta.xml'. 5|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/coreapps/switch/meta.xml'. 6|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/coreapps/simple_c_app/meta.xml'. 7|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/coreapps/simple_c_py_app/meta.xml'. 8|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/coreapps/hub/meta.xml'. 9|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/coreapps/examples/meta.xml'. 00010|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/discovery/meta.xml'. 00011|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/storage/meta.xml'. 00012|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/directory/meta.xml'. 00013|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/bindings_storage/meta.xml'. 00014|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/flow_fetcher/meta.xml'. 00015|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/tests/meta.xml'. 00016|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/topology/meta.xml'. 00017|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/authenticator/meta.xml'. 00018|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/switchstats/meta.xml'. 00019|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/user_event_log/meta.xml'. 00020|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/routing/meta.xml'. 00021|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/configuration/meta.xml'. 00022|pyrt|DBG:Loading a component description file 'nox/coreapps/pyrt/meta.xml'. 00023|pyrt|DBG:Loading a component description file 'nox/coreapps/switch/meta.xml'. 00024|pyrt|DBG:Loading a component description file 'nox/coreapps/simple_c_app/meta.xml'. 00025|pyrt|DBG:Loading a component description file 'nox/coreapps/simple_c_py_app/meta.xml'. 00026|pyrt|DBG:Loading a component description file 'nox/coreapps/hub/meta.xml'. 00027|pyrt|DBG:Loading a component description file 'nox/coreapps/examples/meta.xml'. 00028|pyrt|DBG:Loading a component description file 'nox/netapps/discovery/meta.xml'. 00029|pyrt|DBG:Loading a component description file 'nox/netapps/storage/meta.xml'. 00030|pyrt|DBG:Loading a component description file 'nox/netapps/directory/meta.xml'. 00031|pyrt|DBG:Loading a component description file 'nox/netapps/bindings_storage/meta.xml'. 00032|pyrt|DBG:Loading a component description file 'nox/netapps/flow_fetcher/meta.xml'. 00033|pyrt|DBG:Loading a component description file 'nox/netapps/tests/meta.xml'. 00034|pyrt|DBG:Loading a component description file 'nox/netapps/topology/meta.xml'. 00035|pyrt|DBG:Loading a component description file 'nox/netapps/authenticator/meta.xml'. 00036|pyrt|DBG:Loading a component description file 'nox/netapps/switchstats/meta.xml'. 00037|pyrt|DBG:Loading a component description file 'nox/netapps/user_event_log/meta.xml'. 00038|pyrt|DBG:Loading a component description file 'nox/netapps/routing/meta.xml'. 00039|pyrt|DBG:Loading a component description file 'nox/netapps/configuration/meta.xml'. 00040|pyrt|DBG:Loading a component description file 'nox/webapps/storagews/meta.xml'. 00041|pyrt|DBG:Loading a component description file 'nox/webapps/miscws/meta.xml'. 00042|pyrt|DBG:Loading a component description file 'nox/webapps/switchconfig/meta.xml'. 00043|pyrt|DBG:Loading a component description file 'nox/webapps/default_switch_approval/meta.xml'. 00044|pyrt|DBG:Loading a component description file 'nox/webapps/webserver/meta.xml'. 00045|pyrt|DBG:Loading a component description file 'nox/webapps/webservice/meta.xml'. 00046|sqlite3-impl|WARN:Transactional storage file not given in the command line; defaulting to 'testing.sqlite' 00047|sqlite3-impl|DBG:Opening the SQLite database at 'testing.sqlite'. 00048|sqlite3-impl|DBG:SQLite 'CREATE TABLE IF NOT EXISTS NOX_SCHEMA_META (GUID INTEGER PRIMARY KEY NOT NULL,NOX_TABLE TEXT NOT NULL,NOX_TYPE INTEGER NOT NULL,NOX_VERSION INTEGER NOT NULL)' 00049|sqlite3-impl|DBG:SQLite 'CREATE TABLE IF NOT EXISTS NOX_SCHEMA_TABLE (GUID INTEGER PRIMARY KEY NOT NULL,NOX_TABLE TEXT NOT NULL,NOX_COLUMN TEXT NOT NULL,NOX_TYPE INTEGER NOT NULL)'
Re: [nox-dev] Routing module
Should it not also advertise that routing assumes that either spanning tree is running or that the physical topology contains no loops to function correctly. Martin Casado wrote: Ah, I'm starting to understand what is going on. Routing has no notion of subnets, vlans etc. It doesn't operate like a standard ipv4 router (perhaps the name should be changed to avoid confusion). Routing operates as follows: - It pulls in the authenticator component which tracks MAC addresses and the switch ports they are bound to - For each packet in which the destination MAC address has been discovered, a point to point route is calculated and a flow entry is added to each switch along path. - If the destination MAC has not been discovered, the packet is flooded It doesn't, however, have an ARP stack. So if you're host is configered with the first switch as the next hop, the ARP packet will be flooded, to no effect. This is a roundabout way of saying that, yes in order to operate correctly, all hosts must be on the same subnet. hope this all makes sense, .martin The switch application does not work under my vlan configuration, and it should not as each the two end hosts reside in different subnets. It seems that the routing module expects all datapaths to be within the same openflow vlan instance. Basically this means that if H1 is in one vlan instance and H2 is in the other, then these hosts will never be able to communicate. I do not know if this issue is specific to hardware openflow implementations, but I believe so. The solution that I have found so far is to put all datapaths in the same vlan. This seems to solve the problem, and the routing module picks up routes. Let me know if I have missed something. Cheers. Martin Casado wrote: What I don't understand is why I don't see packets sent to Nox in the debugging output you sent out. I would expect some output from authenticator or routing. My suspicion is that the switch is not forwarding packets to Nox under the VLAN configuration you're testing. Does the switch application work under your VLAN configuration? Hi Martin, If I put the two end hosts in the same vlan and ping them it works fine. But when they are in different vlans the arp requests are not resolved, the only flow which is added is the one I quoted in my original email. So I am positive that the packets are making it to nox. What is the scenario in which the routing module works best? Could you give me some pointers as to how the routing module works? Thanks for your help, On Oct 13, 2009, at 9:30 PM, Martin Casado wrote: All I see are the LLDP packets being received. Are you sure that packets from the end hosts are making it to Nox? If not, perhaps there is a switch mis-configuration. What happens if you run switch instead of routing? If this doesn't work as well, then it is almost certainly a switch issue. .martin -- Ali Al-Shabibi Doctoral Student PH-ATD CERN - European Organization for Nuclear Research Office: 513 R-018 ali.al-shab...@cern.ch Tel : +41 22 767 86 46 Mob : +41 78 609 04 84 ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
Re: [nox-dev] Routing module
Perhaps. I think the disconnect is that routing is intended to be an independent component which uses a centralized dynamic all-pairs shortest path algorithm. Not a full replacement for an L3 routing stack (and definitely not a L3 routing stack with VLANs, ARP, and spanning tree). It does not include loop or broadcast support precisely because these may be handled by a separate component. Some deployments use spanning tree on the switch, some within the controller (Glen at Stanford has a spanning tree component for this purpose), and it may be desirable to use static MACs and handle broadcast along a different processing path (we use to do this). The goal is two build logically contained components which are useful in a broader context. That said, Nox certainly suffers from lack of documentation in general. Per component documentation would go a long way. .martin Should it not also advertise that routing assumes that either spanning tree is running or that the physical topology contains no loops to function correctly. Martin Casado wrote: Ah, I'm starting to understand what is going on. Routing has no notion of subnets, vlans etc. It doesn't operate like a standard ipv4 router (perhaps the name should be changed to avoid confusion). Routing operates as follows: - It pulls in the authenticator component which tracks MAC addresses and the switch ports they are bound to - For each packet in which the destination MAC address has been discovered, a point to point route is calculated and a flow entry is added to each switch along path. - If the destination MAC has not been discovered, the packet is flooded It doesn't, however, have an ARP stack. So if you're host is configered with the first switch as the next hop, the ARP packet will be flooded, to no effect. This is a roundabout way of saying that, yes in order to operate correctly, all hosts must be on the same subnet. hope this all makes sense, .martin The switch application does not work under my vlan configuration, and it should not as each the two end hosts reside in different subnets. It seems that the routing module expects all datapaths to be within the same openflow vlan instance. Basically this means that if H1 is in one vlan instance and H2 is in the other, then these hosts will never be able to communicate. I do not know if this issue is specific to hardware openflow implementations, but I believe so. The solution that I have found so far is to put all datapaths in the same vlan. This seems to solve the problem, and the routing module picks up routes. Let me know if I have missed something. Cheers. Martin Casado wrote: What I don't understand is why I don't see packets sent to Nox in the debugging output you sent out. I would expect some output from authenticator or routing. My suspicion is that the switch is not forwarding packets to Nox under the VLAN configuration you're testing. Does the switch application work under your VLAN configuration? Hi Martin, If I put the two end hosts in the same vlan and ping them it works fine. But when they are in different vlans the arp requests are not resolved, the only flow which is added is the one I quoted in my original email. So I am positive that the packets are making it to nox. What is the scenario in which the routing module works best? Could you give me some pointers as to how the routing module works? Thanks for your help, On Oct 13, 2009, at 9:30 PM, Martin Casado wrote: All I see are the LLDP packets being received. Are you sure that packets from the end hosts are making it to Nox? If not, perhaps there is a switch mis-configuration. What happens if you run switch instead of routing? If this doesn't work as well, then it is almost certainly a switch issue. .martin ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
Re: [nox-dev] Routing module
Can you send the output if you run with -v? Hello, I am trying to implement a monitoring protocol. For this I am relying on the routing module. I have a simple setup involving three openflow-enabled hardware switches. Below is the topology: ++Vl 1++Vl 2++ H1--| R1 |--| R2 |--| R3 |--H2 ++++++ R1 and R2 share vlan 1 (ip 192.168.1.0/24) and R2 and R3 share vlan 2 (ip address 192.168.2.0/24). H1 (192.168.1.1) and H2 (192.168.2.1) are end hosts. Each vlan instance connects to the controller and is correctly picked up by nox as it registers the correct number of datapaths and switches. When I run, nox_core -i ptcp:2525 routing, I obtain the following output: a...@pcepatr39[src]$ sudo ./nox_core -i ptcp:2525 switch routing [sudo] password for ash: NOX 0.5.0~full~beta (nox_core), compiled Oct 13 2009 14:43:43 Compiled with OpenFlow 0x97 (exp) 1|sqlite3-impl|WARN:Transactional storage file not given in the command line; defaulting to 'testing.sqlite' 2|discovery|WARN:new link detected (00:00:2e:98:ca:40:00:66 p:45 - 00:00:2e:9a:ea:00:00:66 p:45) 4|discovery|WARN:new link detected (00:00:2e:9a:ea:00:00:65 p:41 - 00:00:2e:98:8c:c0:00:65 p:41) 5|discovery|WARN:new link detected (00:00:2e:9a:ea:00:00:66 p:45 - 00:00:2e:98:ca:40:00:66 p:45) 6|discovery|WARN:new link detected (00:00:2e:98:8c:c0:00:65 p:41 - 00:00:2e:9a:ea:00:00:65 p:41) So the links are correctly detected by the discovery module. But when I attempt to ping H2 from H1. The only flow then I see setup is: duration=11s, table_id=0, priority=65535, n_packets=9, n_bytes=540, idle_timeout=60,hard_timeout=0,arp,in_port=48,dl_vlan=0x,dl_src=00:50:da:6e:ac:7f, dl_dst=ff:ff:ff:ff:ff:ff,nw_src=0.0.0.0,nw_dst=0.0.0.0,nw_proto=0,tp_src=0,tp_dst=0,actions=FLOOD And no other flows are setup and no messages are sent out by the routing module. Am I missing something about the routing module? From the manual it seems like it is supposed to setup flows on each router from source till the destination. I am running this on 3 hp 3500s, with nox 0.5.0 full. Thanks for your help, ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
Re: [nox-dev] Routing module
All I see are the LLDP packets being received. Are you sure that packets from the end hosts are making it to Nox? If not, perhaps there is a switch mis-configuration. What happens if you run switch instead of routing? If this doesn't work as well, then it is almost certainly a switch issue. .martin Here you go, thanks! a...@pcepatr39[src]$ sudo nox_core -v -i ptcp:2525 routing 1|nox|DBG:Starting nox_core (nox_core) 2|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/webapps/storagews/meta.xml'. 3|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/webapps/webserver/meta.xml'. 4|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/coreapps/pyrt/meta.xml'. 5|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/coreapps/switch/meta.xml'. 6|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/coreapps/simple_c_app/meta.xml'. 7|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/coreapps/simple_c_py_app/meta.xml'. 8|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/coreapps/hub/meta.xml'. 9|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/coreapps/examples/meta.xml'. 00010|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/discovery/meta.xml'. 00011|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/storage/meta.xml'. 00012|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/directory/meta.xml'. 00013|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/bindings_storage/meta.xml'. 00014|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/flow_fetcher/meta.xml'. 00015|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/tests/meta.xml'. 00016|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/topology/meta.xml'. 00017|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/authenticator/meta.xml'. 00018|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/switchstats/meta.xml'. 00019|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/user_event_log/meta.xml'. 00020|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/routing/meta.xml'. 00021|pyrt|DBG:Loading a component description file '/usr/local/bin/nox/netapps/configuration/meta.xml'. 00022|pyrt|DBG:Loading a component description file 'nox/coreapps/pyrt/meta.xml'. 00023|pyrt|DBG:Loading a component description file 'nox/coreapps/switch/meta.xml'. 00024|pyrt|DBG:Loading a component description file 'nox/coreapps/simple_c_app/meta.xml'. 00025|pyrt|DBG:Loading a component description file 'nox/coreapps/simple_c_py_app/meta.xml'. 00026|pyrt|DBG:Loading a component description file 'nox/coreapps/hub/meta.xml'. 00027|pyrt|DBG:Loading a component description file 'nox/coreapps/examples/meta.xml'. 00028|pyrt|DBG:Loading a component description file 'nox/netapps/discovery/meta.xml'. 00029|pyrt|DBG:Loading a component description file 'nox/netapps/storage/meta.xml'. 00030|pyrt|DBG:Loading a component description file 'nox/netapps/directory/meta.xml'. 00031|pyrt|DBG:Loading a component description file 'nox/netapps/bindings_storage/meta.xml'. 00032|pyrt|DBG:Loading a component description file 'nox/netapps/flow_fetcher/meta.xml'. 00033|pyrt|DBG:Loading a component description file 'nox/netapps/tests/meta.xml'. 00034|pyrt|DBG:Loading a component description file 'nox/netapps/topology/meta.xml'. 00035|pyrt|DBG:Loading a component description file 'nox/netapps/authenticator/meta.xml'. 00036|pyrt|DBG:Loading a component description file 'nox/netapps/switchstats/meta.xml'. 00037|pyrt|DBG:Loading a component description file 'nox/netapps/user_event_log/meta.xml'. 00038|pyrt|DBG:Loading a component description file 'nox/netapps/routing/meta.xml'. 00039|pyrt|DBG:Loading a component description file 'nox/netapps/configuration/meta.xml'. 00040|pyrt|DBG:Loading a component description file 'nox/webapps/storagews/meta.xml'. 00041|pyrt|DBG:Loading a component description file 'nox/webapps/miscws/meta.xml'. 00042|pyrt|DBG:Loading a component description file 'nox/webapps/switchconfig/meta.xml'. 00043|pyrt|DBG:Loading a component description file 'nox/webapps/default_switch_approval/meta.xml'. 00044|pyrt|DBG:Loading a component description file 'nox/webapps/webserver/meta.xml'. 00045|pyrt|DBG:Loading a component description file 'nox/webapps/webservice/meta.xml'. 00046|sqlite3-impl|WARN:Transactional storage file not given in the command line; defaulting to 'testing.sqlite' 00047|sqlite3-impl|DBG:Opening the SQLite database at 'testing.sqlite'. 00048|sqlite3-impl|DBG:SQLite 'CREATE TABLE IF NOT EXISTS NOX_SCHEMA_META (GUID INTEGER PRIMARY KEY NOT NULL,NOX_TABLE TEXT' 00049|sqlite3-impl|DBG:SQLite 'CREATE TABLE IF NOT EXISTS
[nox-dev] Routing Module and Weights
Hi, I made some minor changes to the routing/discovery module to handle link updates (weight-based) on top of add/remove. Even though it seems to work for my purposes, I am not convinced how closely the module implements the dynamic-all pairs algorithm.. Could somebody comment on it? Also, is there a recommended place where I could add two routing modules for the same controller? (let's say same connectivity graph but different weights) Thanks, Yiannis p.s. let me know if you want a patch from the changes... ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
