It is common practice in current legacy switches to allow dropping fragments if
any classification is used, even tough this does "break communications".
The reasoning is that it is very likely communications would be broken anyway.
Suppose you do something useful by L4 data. 1st frame gets thi
Hi,
I am new to OpenFlow and have been working on OpenFlow v1.0. Though I
haven't used v1.1, I was reading the specifications and had a few questions
about it.
1. What does an 'action bucket' contain? An 'action list' (that is a list of
actions where we can use each action multiple time) OR an 'a
On Tue, Apr 26, 2011 at 12:34:50PM -0700, Srini Seetharaman wrote:
> Could someone that participated in the earlier spec process please
> comment on what the reasoning behind the OFPC_FRAG_DROP is?
OFPC_FRAG_DROP exists because individual IP fragments (except for the
first) does not carry the tran
This question is more appropriate to the openflow-discuss list copied here.
Could someone that participated in the earlier spec process please
comment on what the reasoning behind the OFPC_FRAG_DROP is?
I see that the code is present to drop the packets in the userspace
switch. So, I guess many s
Regarding the reference code, 8 queues are indeed an implementation issue.
Marking packets in userspace to be queued in the kernel (tc) introduces a
linear overhead (each queue is represented by a socket), and thus we limit
the number to 8. You can try to increase the number and see whether
perform
On Tue, Apr 26, 2011 at 11:49:25AM -0300, Victor Torres wrote:
> So does OpenVSwitch (software switches) don't have this limitation? So
> they can use any way they want to classify packets into queues?
Yes, that's correct.
___
openflow-discuss mailing li
Hello,
Thanks for the very fast replies.
I do understand the queues are per-port, sorry.
I was thinking about huge networks with dozens of slices, which one
isolated from the other. And to this end i was planning to use the
queuing system, but this limit of 8 queues would limit me to 8 slices,
i
Hi linbo
Could you please verify the connectivity by setting up an ethernet
bridge (using brctl) between the eth1 and eth2? If the ping worked
fine in the bridge, it should work fine with OpenFlow switching.
Thanks
Srini.
2011/4/26 linbo :
> Yes，I tried the command " ./nox_core -v -i ptcp:6633 p
Yes，I tried the command “ ./nox_core -v -i ptcp:6633 pyswitch ” ，and ping
can work well
Thank you~
2011-04-26
linbo
发件人： Kyriakos Zarifis
发送时间： 2011-04-26 16:11:35
收件人： linbo
抄送： nox-dev; openflow-discuss
主题： Re: [nox-dev] how to add a flow entry through nox to the openflow switch
Hi,
which NOX components are you running? You need do have some component(s)
that will install flow entries on the switch for the ping to go through
have a look here:
http://noxrepo.org/noxwiki/index.php/FAQ#What_does_the_traversal_of_a_packet_through_a_NOX_controlled_network_look_like.3F
2011/4
10 matches
Mail list logo
