Snort mailing list archives
Large receive offload, good or bad?
From: elof () sentor se
Date: Thu, 30 Aug 2012 11:25:40 +0200 (CEST)
Snort says: "FYI: Please note that, by default, snort will truncate packets larger than the default snaplen of 15158 bytes. Additionally, LRO may cause issues with Stream5 target-based reassembly. It is recommended to disable LRO, if your card supports it." Questions: LRO sounds like a good thing - aggregating multiple incoming packets from a single stream into a larger buffer before they are passed higher up the networking stack will reduce CPU overhead. If one does not use target-based reassembly in snort, can/should LRO be enabled? What's you opinion? Is there any other reasons to disable LRO? Otherwise I think LRO should be enabled by default... /Elof ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Snort-users mailing list Snort-users () lists sourceforge net Go to this URL to change user options or unsubscribe: https://lists.sourceforge.net/lists/listinfo/snort-users Snort-users list archive: http://www.geocrawler.com/redir-sf.php3?list=snort-users Please visit http://blog.snort.org to stay current on all the latest Snort news!
Current thread:
- Large receive offload, good or bad? elof (Aug 30)
- Re: Large receive offload, good or bad? Joel Esler (Aug 30)
- Re: Large receive offload, good or bad? Peter Bates (Aug 30)
- Re: Large receive offload, good or bad? Joel Esler (Aug 30)