Hi How to post a new thread?
> From: openflow-discuss-requ...@lists.stanford.edu > Subject: openflow-discuss Digest, Vol 54, Issue 36 > To: openflow-discuss@lists.stanford.edu > Date: Tue, 23 Apr 2013 02:22:14 -0700 > > Send openflow-discuss mailing list submissions to > openflow-discuss@lists.stanford.edu > > To subscribe or unsubscribe via the World Wide Web, visit > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss > or, via email, send a message with subject or body 'help' to > openflow-discuss-requ...@lists.stanford.edu > > You can reach the person managing the list at > openflow-discuss-ow...@lists.stanford.edu > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of openflow-discuss digest..." > > > Today's Topics: > > 1. Re: how to drop packets (???) > 2. port no 6633 and 6634 (Varun Moruse) > 3. Re: port no 6633 and 6634 (Ben Pfaff) > 4. Re: port no 6633 and 6634 (Eric Chou) > 5. Fw: message ..... (Travis Dargie) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 23 Apr 2013 11:19:41 +0800 > From: ??? <seamus...@gmail.com> > To: Varun Moruse <varunmor...@rediffmail.com> > Cc: openflow-discuss <openflow-disc...@mailman.stanford.edu>, > openflowdiscuss <openflow-discuss@lists.stanford.edu> > Subject: Re: [openflow-discuss] how to drop packets > Message-ID: <3b1voco4av4ef67ccn3j4noi.1366687127...@email.android.com> > Content-Type: text/plain; charset="utf-8" > > Hi, > > You can try an empty action list. In openflow 1.0, empty action list means > "drop" > > Varun Moruse <varunmor...@rediffmail.com>??? > > >Hello, > > I have deployed openflow tutorial mininet VM using Virtualbox > >successfully. > > > > I > > have one query, I want to make my system work like firewall If I want > >to drop packets from one particular host , how should I do it? > >Does it need modification of existing file OR any other way???? > >with following commands, > >dpctl add-flow tcp:127.0.0.1:6634 in_port=1,actions=output:2 > >do we have any other action option like drop or something else??? > >Please let me know ... > >Thanks N Regards, > > Varun. > > > >_______________________________________________ > >openflow-discuss mailing list > >openflow-discuss@lists.stanford.edu > >https://mailman.stanford.edu/mailman/listinfo/openflow-discuss > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://mailman.stanford.edu/pipermail/openflow-discuss/attachments/20130423/7bce94ef/attachment-0003.html> > > ------------------------------ > > Message: 2 > Date: 23 Apr 2013 03:37:40 -0000 > From: "Varun Moruse" <varunmor...@rediffmail.com> > To: "mininet-discuss " <mininet-disc...@lists.stanford.edu>, > "openflow-discuss " <openflow-disc...@mailman.stanford.edu> > Subject: [openflow-discuss] port no 6633 and 6634 > Message-ID: <20130423033740.11353.qm...@f4mail-235-131.rediffmail.com> > Content-Type: text/plain; charset="utf-8" > > Hello, > what is significance of port numbers 6633 and 6634? > what does they mean and do we use them interchangebly???? > Thanks n regards, > Varun > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://mailman.stanford.edu/pipermail/openflow-discuss/attachments/20130423/71361f49/attachment-0001.html> > > ------------------------------ > > Message: 3 > Date: Mon, 22 Apr 2013 21:19:54 -0700 > From: Ben Pfaff <b...@nicira.com> > To: Varun Moruse <varunmor...@rediffmail.com> > Cc: mininet-discuss <mininet-disc...@lists.stanford.edu>, > openflow-discuss <openflow-disc...@mailman.stanford.edu> > Subject: Re: [openflow-discuss] port no 6633 and 6634 > Message-ID: <20130423041954.gd26...@nicira.com> > Content-Type: text/plain; charset=us-ascii > > On Tue, Apr 23, 2013 at 03:37:40AM -0000, Varun Moruse wrote: > > what is significance of port numbers 6633 and 6634? > > what does they mean and do we use them interchangebly???? > > 6633 is generally used for OpenFlow. > I don't know what port 6634 is used for. > > > ------------------------------ > > Message: 4 > Date: Mon, 22 Apr 2013 21:34:51 -0700 > From: Eric Chou <eric.cho...@gmail.com> > To: Ben Pfaff <b...@nicira.com> > Cc: mininet-discuss <mininet-disc...@lists.stanford.edu>, > openflow-discuss <openflow-disc...@mailman.stanford.edu> > Subject: Re: [openflow-discuss] port no 6633 and 6634 > Message-ID: <53e489e7-7c00-4831-bf95-eedf1adfa...@gmail.com> > Content-Type: text/plain; charset="windows-1252" > > Hi, in the words of the tutorial: > > Most OpenFlow switches can start up with a passive listening port (in your > current setup this is 6634)? > so the switch actively registers to 6633 and passively listens on 6634. > Doesn't need to be 6634. > > In the case of multiple switches, such as: > sudo mn --topo linear,3 --mac --switch ovsk --controller remote > mininet> net > c0 > s1 lo: s1-eth1:h1-eth0 s1-eth2:s2-eth2 > s2 lo: s2-eth1:h2-eth0 s2-eth2:s1-eth2 s2-eth3:s3-eth2 > s3 lo: s3-eth1:h3-eth0 s3-eth2:s2-eth3 > h1 h1-eth0:s1-eth1 > h2 h2-eth0:s2-eth1 > h3 h3-eth0:s3-eth1 > mininet> > > The first switch listens on 6634, second on 6635, third on 6636 (I asked this > a few days ago and answered by Bob Lantz): > > mininet> h1 ping -c3 h2 > PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. > 64 bytes from 10.0.0.2: icmp_req=1 ttl=64 time=14.6 ms > 64 bytes from 10.0.0.2: icmp_req=2 ttl=64 time=0.612 ms > 64 bytes from 10.0.0.2: icmp_req=3 ttl=64 time=0.049 ms > > --- 10.0.0.2 ping statistics --- > 3 packets transmitted, 3 received, 0% packet loss, time 2000ms > rtt min/avg/max/mdev = 0.049/5.093/14.618/6.739 ms > mininet> h1 ping -c3 h3 > PING 10.0.0.3 (10.0.0.3) 56(84) bytes of data. > 64 bytes from 10.0.0.3: icmp_req=1 ttl=64 time=23.3 ms > 64 bytes from 10.0.0.3: icmp_req=2 ttl=64 time=0.484 ms > 64 bytes from 10.0.0.3: icmp_req=3 ttl=64 time=0.062 ms > > --- 10.0.0.3 ping statistics --- > 3 packets transmitted, 3 received, 0% packet loss, time 2000ms > rtt min/avg/max/mdev = 0.062/7.970/23.365/10.887 ms > mininet> > > mininet@mininet-vm:~$ dpctl dump-flows tcp:127.0.0.1:6634 > stats_reply (xid=0x331cebd): flags=none type=1(flow) > cookie=0, duration_sec=10s, duration_nsec=749000000s, table_id=0, > priority=65535, n_packets=3, n_bytes=294, > idle_timeout=10,hard_timeout=30,icmp,in_port=1,dl_vlan=0xffff,dl_vlan_pcp=0x00,dl_src=00:00:00:00:00:01,dl_dst=00:00:00:00:00:03,nw_src=10.0.0.1,nw_dst=10.0.0.<skip> > mininet@mininet-vm:~$ > mininet@mininet-vm:~$ dpctl dump-flows tcp:127.0.0.1:6635 > stats_reply (xid=0xcf8ab798): flags=none type=1(flow) > cookie=0, duration_sec=8s, duration_nsec=108000000s, table_id=0, > priority=65535, n_packets=1, n_bytes=42, > idle_timeout=10,hard_timeout=30,arp,in_port=2,dl_vlan=0xffff,dl_vlan_pcp=0x00,dl_src=00:00:00:00:00:01,dl_dst=00:00:00:00:00:03,nw_src=10.0.0.1,nw_dst=10.0.0.3,nw_proto=2,actions=output:3 > cookie=0, duration_sec=8s, duration_nsec=113000000s, table_id=0, > priority=65535, n_packets=1, n_bytes=42, > idle_timeout=10,hard_timeout=30,arp,in_port=3,dl_vlan=0xffff,dl_vlan_pcp=0x00,dl_src=00:00:00:00:00:03,dl_dst=00:00:00:00:00:01,nw_src=10.0.0.3,nw_dst=10.0.0.1,nw_proto=1,actions=output:2 > mininet@mininet-vm:~$ > mininet@mininet-vm:~$ dpctl dump-flows tcp:127.0.0.1:6636 > stats_reply (xid=0x413119ba): flags=none type=1(flow) > cookie=0, duration_sec=10s, duration_nsec=105000000s, table_id=0, > priority=65535, n_packets=1, n_bytes=42, > idle_timeout=10,hard_timeout=30,arp,in_port=2,dl_vlan=0xffff,dl_vlan_pcp=0x00,dl_src=00:00:00:00:00:01,dl_dst=00:00:00:00:00:03,nw_src=10.0.0.1,nw_dst=10.0.0.3,nw_proto=2,actions=output:1 > cookie=0, duration_sec=10s, duration_nsec=116000000s, table_id=0, > priority=65535, n_packets=1, n_bytes=42, > idle_timeout=10,hard_timeout=30,arp,in_port=1,dl_vlan=0xffff,dl_vlan_pcp=0x00,dl_src=00:00:00:00:00:03,dl_dst=00:00:00:00:00:01,nw_src=10.0.0.3,nw_dst=10.0.0.1,nw_proto=1,actions=output:2 > mininet@mininet-vm:~$ > > > Eric > > On Apr 22, 2013, at 9:19 PM, Ben Pfaff <b...@nicira.com> wrote: > > > On Tue, Apr 23, 2013 at 03:37:40AM -0000, Varun Moruse wrote: > >> what is significance of port numbers 6633 and 6634? > >> what does they mean and do we use them interchangebly???? > > > > 6633 is generally used for OpenFlow. > > I don't know what port 6634 is used for. > > _______________________________________________ > > openflow-discuss mailing list > > openflow-discuss@lists.stanford.edu > > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://mailman.stanford.edu/pipermail/openflow-discuss/attachments/20130422/21d212ff/attachment-0001.html> > > ------------------------------ > > Message: 5 > Date: Tue, 23 Apr 2013 10:22:11 +0100 (BST) > From: Travis Dargie <travisloves...@ymail.com> > To: openflow discuss <openflow-disc...@mailman.stanford.edu>, openflow > discuss <openflow-discuss@lists.stanford.edu>, openflow discuss owner > <openflow-discuss-ow...@lists.stanford.edu> > Subject: [openflow-discuss] Fw: message ..... > Message-ID: > <1366708931.80665.yahoomail...@web172501.mail.ir2.yahoo.com> > Content-Type: text/plain; charset="utf-8" > > Single Mom Makes $89,844/Yr in Her Spare Time on The Computer Without Selling > Anything > > http://oem-carbon.com/hwork55.html > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://mailman.stanford.edu/pipermail/openflow-discuss/attachments/20130423/8eb3fc4b/attachment.html> > > ------------------------------ > > _______________________________________________ > openflow-discuss mailing list > openflow-discuss@lists.stanford.edu > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss > > > End of openflow-discuss Digest, Vol 54, Issue 36 > ************************************************
_______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
