Hi Yang, > What does the following mean ? Sorry for my poor English. "that speaks > OSPF/BPG" >>If by router you mean something that speaks OSPF/BPG/etc, then there >>is other work that I can point you to that does this.
What Rob means is that the controller speaks (= sends/receives/understands) routing protocol messages like OSPF / BGP / RIP. Based on this information the control plane would determine the routing information base (RIB) and generate the forwarding tables (i.e FIB) to process packets in the data plane. > Whether can I run the zebra or quagga on the PCs which were installed > openflow switch, but how the packets will forward ? using the FIB or flow > table. If you use Quagga (or XORP or any Linux-based routing engine) it will generate forwarding on the Linux IP table and not directly in the flow table of the OpenFlow switch that you decide to install in the PC. Basically you need a "glue" to combine the routing control plane of Quagga with the OpenFlow-capable forwarding substrate. >>What is the specific "router" functionality you're looking for? > What the specific "router" I want is that just forwarding the packets. The > switch need to forward the packet and link the hosts in different > subnet(different broadcast domain). So, basically what you want is longest prefix matching on IP headers and MAC header re-write actions (along TTL decrement). OpenFlow does support this type of traditional router forwarding functionality but you need a controller application that sets the flow rules and actions according the routing procotol engine (e.g., Quagga). We have developed a solution for this called QuagFlow ( http://conferences.sigcomm.org/sigcomm/2010/papers/sigcomm/p441.pdf ) that we expect to be publicly available by the end of the month. -Christian > > > Best regards > ------------------ > Yang > 2011-03-10 > > ------------------------------------------------------------- > 发件人：Rob Sherwood > 发送日期：2011-03-10 12:11:18 > 收件人：杨宇 > 抄送：openflow-discuss > 主题：Re: Re: [openflow-discuss] How the openflow switch worked as a router? > >>Hi Yang, >> >>I'm afraid you're going to have to ask your question more precisely - >>the traditional notions of switch vs. router become very fuzzy with >>OpenFlow. >> >>It really depends on the functionality you're looking for. For >>example, if you believe that the relevant differences has to do with >>broadcast domains, i.e., that a switch controls traffic within a >>broadcast domain and a router controls traffic between broadcast >>domains, then OpenFlow makes this messy because it allows you to >>arbitrarily control the size of the broadcast. >> >>If the difference between switch and router that you're concerned >>about is that traditionally, a switch does pure forwarding, but an IP >>router does hop-by-hop mac address rewriting and TTL decrementing, >>then you will need to write a controller module that does this. That >>is, I don't believe that nox ships with a module that does "routing" >>in this form. >> >>If by router you mean something that speaks OSPF/BPG/etc, then there >>is other work that I can point you to that does this. >> >>What is the specific "router" functionality you're looking for? >> >>- Rob >>. >> >> >> >>2011/3/9 杨宇 <[email protected]>: >>> Hi, Rob >>> In the webpage >>> http://www.openflow.org/foswiki/bin/view/OpenFlow/Deployment/ >>> I did not see anything about how to configure the switches that works >>> like a router. In this webpage , PCs are in the same subnet. What I need >>> is how to configure the controllers and the switches that Pcs are in >>> different subnets. >>> Thanks. >>> >>> ------------------ >>> Yang >>> 2011-03-10 >>> >>> ------------------------------------------------------------- >>> 发件人：Rob Sherwood >>> 发送日期：2011-03-10 06:02:27 >>> 收件人：杨宇 >>> 抄送：openflow-discuss >>> 主题：Re: [openflow-discuss] How the openflow switch worked as a router? >>> >>> The way you configure your controller (e.g., nox) is independent of whether >>> the underlying switch/router is mininet or if it is real hardware. >>> >>> For more information, I would check out the HOWTO section of the deployments >>> webpage: >>> >>> http://www.openflow.org/foswiki/bin/view/OpenFlow/Deployment/ >>> >>> Good luck, >>> >>> - Rob >>> . >>> >>> >>> 2011/3/9 杨宇 <[email protected]> >>> >>>> Hi,all >>>> I want to establish a real network using openflow, the controller use >>>> nox and each switch are used to working as routers.How should I configure >>>> these switches? >>>> I have read the tutorial in the page >>>> http://openflowswitch.org/wk/index.php/HOTITutorial2010#Testing_your_router >>>> but the section 7 about how to create router is not very clear, and it >>>> used in the mininet?How can I set the openflow in the real network, and how >>>> a openflow switch worked as a router. >>>> thanks. >>>> The topology is following: >>>> >>>> >>>> controller >>>> / \ >>>> / (eth0) \ (eth0) >>>> Switch1 Switch2 >>>> / (eth1) \(eth1) >>>> / \ >>>> Host1 Host2 >>>> host1: 192.168.10.11 >>>> host2: 192.168.20.22 >>>> >>>> Switch1: >>>> eth1:192.168.10.1 >>>> eht0:192.168.0.1 >>>> Switch2: >>>> eth1:192.168.20.2 >>>> eth0: 192.168.0.2 >>>> Controller(Nox):192.168.0.100 >>>> >>>> >>>> >>>> * * >>>> >>>> > >>>> Email: [email protected] >>>> ------------------------------------------------------ >>>> >>>> _______________________________________________ >>>> openflow-discuss mailing list >>>> [email protected] >>>> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss >>>> >>>> >>> > _______________________________________________ > openflow-discuss mailing list > [email protected] > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss > -- Christian _______________________________________________ openflow-discuss mailing list [email protected] https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
