Alba Mendez

It definitively should. If you inspect the same as above with `eyes`, you get: ``` { some: { 0: 28, 1: 0, length: 2, parent: { 0: 248, 1: 78,...

I forgot, I'm using keystone 0.9.1

This happens in latest master as well

it is possible, yes a DNS parser is already implemented, see `decode/dns.js` for TLS however you'll have to implement the parsing yourself I think

if you're using windows, see https://github.com/node-pcap/node_pcap/issues/249#issuecomment-586201286

hello, if you're still hitting the problem please send us a `.pcap` of that interface, or the bytes of `raw_packet` which fails decoding

please, send us a .pcap with the captured packets (you can obtain one with i.e. wireshark or tcpdump)

@bipolarmorgan ummm, there's not an easy fix To get this module working on Windows I'm afraid more work is needed, see https://github.com/node-pcap/node_pcap/issues/249#issuecomment-586201286

@PatrickSantoZZ it's not a fix. It's a new feature. We'd need to write an important amount of code to adapt to Windows.

This module has never supported (and can't easily support) windows. That's because on windows you [can't get a pollable socket](https://www.tcpdump.org/manpages/pcap_get_selectable_fd.3pcap.html): > pcap_get_selectable_fd() is not available on Windows. You can work...