Re: [pox-dev] Regarding flow entries
On Nov 14, 2014, at 7:12 PM, Padma Jayasankar wrote: > HI, > 1. I am getting the following entry in all switches. What does this entry > denote? >cookie=0x0, duration=100.653s, table=0, n_packets=34, n_bytes=1394, > idle_age=1, priority=65000,dl_dst=01:23:20:00:00:01,dl_type=0x88cc > actions=CONTROLLER:65535 I'm guessing this is the output from ovs-ofctl or dpctl or something. It's probably worth learning to use the tool; it probably has a man page. It should also be pretty clear if you take a look at the OpenFlow spec. The high points of this entry are that packets with the destination MAC 01:23:20:00:00:01 and Ethertype 0x88cc are sent to the controller. 0x88cc is LLDP. And if you look up the OUI of the MAC address, you'll see that it's Nicira Networks. This is the multicast MAC address used for Nicira-style discovery. You're probably running the POX discovery component, which installs table entries like this. > 2. I am using POX with Mininet and OVSK. I am using l2_multi routine.This > deletes all the flow entries when a link failure(link down) event is raised. > I want to change this , so that it deletes entries pertaining the failed > link alone.How to achieve this? I tried with the following code > ie) How to delete entries of a switch that has outport or inport as the > specified port number > > clear = of.ofp_flow_mod(command=of. > OFPFC_DELETE,out_port=port1) > sw1.connection.send(clear) > > clear = > of.ofp_flow_mod(command=of.OFPFC_DELETE,match=of.ofp_match(in_port=port2)) > sw2.connection.send(clear) > > But it is not behaving as expected What's it doing instead? > Please clarify. > > Thanks and Regards, > Padma V
[pox-dev] Regarding flow entries
HI, 1. I am getting the following entry in all switches. What does this entry denote? *cookie=0x0, duration=100.653s, table=0, n_packets=34, n_bytes=1394, idle_age=1, priority=65000,dl_dst=01:23:20:00:00:01,dl_type=0x88cc actions=CONTROLLER:65535* 2. I am using POX with Mininet and OVSK. I am using l2_multi routine.This deletes all the flow entries when a link failure(link down) event is raised. I want to change this , so that it deletes entries pertaining the failed link alone.How to achieve this? I tried with the following code ie) *How to delete entries of a switch that has outport or inport as the specified port numbe*r * clear = of.ofp_flow_mod(command=of.* *OFPFC_DELETE,out_port=port1)* *sw1.connection.send(clear)* *clear = of.ofp_flow_mod(command=of.* *OFPFC_DELETE,match=of.ofp_**match(in_port=port2)) * *sw2.connection.send(clear)* But it is not behaving as expected Please clarify. Thanks and Regards, Padma V
Re: [pox-dev] pox console with ipython
At one point, I think I made some tweaks to make sure that it worked with ipython if you just run ipython pox.py. Have you tried that? Maybe it's gotten broken -- I'll admit to not testing that regularly (ever :) ). Also if you run py --completion, you can often get some tab-completion with even without ipython. -- Murphy On Nov 14, 2014, at 1:07 PM, Alison Chan wrote: > Hey pox-dev, > > Is there any component that is like py, but provides the enhanced > features of the ipython console? I often use the py console to push > static flows and prototype stuff before it goes into my real > controller code, but I especially miss the tab completion that ipython > gives me. > > If there is such a component, then awesome, but if not, then I could > write one and send a PR. > > Cheers, > -- > Alison Chan > Kettering University > chan7...@kettering.edu > +1 909 278 7753
[pox-dev] openflow multipath
Hi all, I want to know does anybody know something about openflow multipath feature or use it before? Can anybody give some advices how to set it using command line that the flow entry with multipath feature?
[pox-dev] pox console with ipython
Hey pox-dev, Is there any component that is like py, but provides the enhanced features of the ipython console? I often use the py console to push static flows and prototype stuff before it goes into my real controller code, but I especially miss the tab completion that ipython gives me. If there is such a component, then awesome, but if not, then I could write one and send a PR. Cheers, -- Alison Chan Kettering University chan7...@kettering.edu +1 909 278 7753
Re: [pox-dev] encapsulate/decapsulate packet from one host to L2/L3 of another host
This doesn't have much to do with Mininet or OpenFlow or POX's usual use-cases, which all have to do with switches. You're describing atypical behavior you want a *host* to implement. Off the top of my head, I don't know a way to get what you want with any normal Linux networking configuration or even OVS (though if you wanted to use OVS, it's not clear why you'd have hosts in the middle of the topology anyway). A pretty common way to do what you want would be to write a userspace program which opens AF_PACKET "raw" sockets on the two interfaces and does the encapsulation. This could also be done with libpcap. Indeed, you could do it with POX's pxpcap library pretty easily if performance wasn't an issue. If performance was really an issue, you'd probably use something like Intel's DPDK. As a sidenote, you'll want to watch out for the MTU. -- Murphy On Nov 13, 2014, at 9:14 PM, david jhon wrote: > Hi everyone, > > I have created following topology in mininet: > > h1-s1--h2---s2--h3-s3-h4 > > I want to ping h4 from h1 but I want every packet between h1 <---> h4 to pass > through h2 and h3 such that a packet coming from h1 is encapsulated in L2 and > L3 packet of h2 and then forward this modified packet to s2, s2 should > forward the encapsulated packet to h3, h3 should remove l2/l3 headers > appended by h2 and forward this decapsulated packet to s3 which in turn > should be forwarded to h4 by s3. > > How can I make this thing happen in mininet and pox? > > Any suggestion/tip/link or help is welcomed. > > Thanks and Regards, > > David > >
