It's not entirely clear to me what you're trying to accomplish here. Is it that when you get a packet to any of the .2/.3./.4, you want to duplicate it and send it to the other two also? If so, I think this is just three rules, one which matches on each address. The actions for these are two rewrites and two outputs. You know the IP address you want to rewrite to, but you'll also need to figure out the MAC address which goes with the IP address, and you'll need to figure out which port to send on. The former is the job of ARP (though you could also potentially just learn it), and the latter is basic learning behavior. You could implement these in the controller (the l3_learning component does this), but it may also be possible to get some help from the OFPP_NORMAL virtual output port.
-- Murphy On Apr 10, 2013, at 8:53 AM, Kouvakas Alexandros wrote: > Hello again, > I want to install some flows manually to the OF switch. I have an overlay > network with a subnet 192.168.3.1/24. The central node with the OVS is the > one with the IP 192.168.3.1 and there are 3 hosts connected directly to the > central. It's more or less like the Openflow tutorial with mininet. > > What I want to do, is when the OF switch receives a packet, let's say from > the node 192.168.3.2, to forward it to the nodes for example 192.168.3.4 and > 192.168.3.3. I would like to use the IPs of the nodes and not the MAC > addresses or ports. In this kind of topology there is not any real > usefulness, but in the future I am planning to have a more complicated > overlay network with many nodes connected to each other. In the latter case I > will try to direct the packet through a path that I will choose. > > Is there any example of how I can do that? Do you think it is better to alter > the code of l2_learning.py or start from the scratch? > > > 2013/3/29 Murphy McCauley <[email protected]> > On Mar 29, 2013, at 3:28 AM, Felician Nemeth wrote: > > >>> My node has python version 2.6.2. > >> > >> Note that you may run into some problems here -- POX's requirement is > >> Python 2.7. > > > > I'd like to mention that it is sometimes not straightforward to install > > a new python version. In which case, pythonbrew is really useful. > > > > https://github.com/utahta/pythonbrew > > This is a good tip, so I added it to the manual. Thanks. > > Between pythonbrew, PyPy, and the recent patches, I think the world for > 2.6-ers is decent. The manual could probably be refactored a bit to put all > the Python-version stuff in one place, but that's a project for another time > or person. :) > > It sure would have been nice if 2.6 had been phased out before Python 3 > really started getting deployed, but it's looking like that's not going to > happen. Oh well. :) > > -- Murphy > > > > -- > Kouvakas Alexandros
