Hi guys,
thanks for the quick responses. I am at home now, so I will try out your
suggestions and reply tomorrow.
Cheers
Iain
On Jul 12 2010, kk yap wrote:
Hi Ricardo and ikf,
Thanks for the refresh. I think ikf was trying to install the flow
entry and it is not matching for some reason. But the refresh is
definitely useful.
Btw, I am replying just to correct a typo. You should return STOP to
drop the packets, not CONTINUE. And do check nox.xml or nox.json in
src/etc to ensure the order of the component being called by
Packet_in_event.
It is always cool to see the community chipping in. Allow me to say
thanks to everyone that have done so, and hope others will help out
too. THANKS.
Regards
KK
On 12 July 2010 08:37, Ricardo Bennesby <ricardo.benne...@gmail.com>
wrote:
> Hello ikf. Some months ago I was with a similar issue. I was trying to
> do a test droping packets. I modified the component called pyswitch.py.
> This is my post:
>
> Thanks Martin. I was looking the code of pyswitch.py and I found this:
>
> # don't forward lldp packets
> if packet.type == ethernet.LLDP_TYPE:
> return CONTINUE
>
> So, if I want to drop any kind of packet is just to specify its type?
> Like use "packet.type == ethernet.TCP_TYPE" to drop packet of tcp
> protocol? Thank you again for help me.
>
> And he answered:
>
> If you want to drop packets at the controller, then yes, you can simply
> "return CONTINUE" in a packet handler after checking the type.
>
> If you'd like packets to be dropped at the switch, you should install
> a flow entry with no actions which matches on the packets you'd like
> dropped. This is preferable since you don't exhaust bandwidth to the
> controller for packets which will ultimately be dropped
>
> I don't know if this will help you, but maybe you can try it. Anyway,
> good luck.
>
_______________________________________________
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
