For some reason I am getting an "Index was outside the bounds of the array" when I am parsing the packet. Please see attached screenshot. Any ideas on how I can prevent this?
What kind of packet is producing that exception? Invalid packets can result in exceptions being thrown. If it happens you can sometimes catch the packet using wireshark, thats how I normally debug issues like that.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You could apply a packet filter at the sharppcap level to only include
ipv4 packets or you could just catch and ignore those exceptions if
thrown per c#.
Status: open
Labels: index error
Created: Fri Jan 04, 2013 01:42 PM UTC by Greg Smythe
Last Updated: Fri Jan 04, 2013 01:47 PM UTC
Owner: nobody
For some reason I am getting an "Index was outside the bounds of the array"
when I am parsing the packet. Please see attached screenshot. Any ideas on
how I can prevent this?
I, too, am getting this index error. The previous version of Packet.Net did not have this issue. I do need to see and parse TCPv6 packets so filtering them out is not an option.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Greg.
What kind of packet is producing that exception? Invalid packets can result in exceptions being thrown. If it happens you can sometimes catch the packet using wireshark, thats how I normally debug issues like that.
It looks like an IPV6 packet. Since I'm not interested in those is there a way to just ignore them?
You could apply a packet filter at the sharppcap level to only include
ipv4 packets or you could just catch and ignore those exceptions if
thrown per c#.
Chris
On Fri, Jan 4, 2013 at 11:30 AM, Greg Smythe gsmythe@users.sf.net wrote:
Related
Bugs: #17
Thank you for your help, setting a filter fixed it right up!
Thanks,
Greg
I, too, am getting this index error. The previous version of Packet.Net did not have this issue. I do need to see and parse TCPv6 packets so filtering them out is not an option.