-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for 0x886c #40
Comments
Hey Paolo!
The first binary is the destination MAC address, the second binary is The raspberry pi thread you linked to has the protocol details: https://www.google.ch/patents/US20070263631 The header format: https://patentimages.storage.googleapis.com/US20070263631A1/US20070263631A1-20071115-D00005.png Could you provide a packet dump in pcap format? Feel free to anonymize
See pkt:decode/1,2. They'll return the decoded headers and the remaining |
I'm not very familiar with these tools and I'm not sure if I got any 0x886c packet in a dump I made with Running out of time I googled for them and I found this issue of Wireshark. There is a link to a pcap file with a 0x886c packet. Would that be good enough? Thanks for the reference to |
Thanks for trying! I'll have a look at the links, they look like a good start. I have to order an rpi3 anyway so I'll be able to add support for the other frames types then. If you run into any more issues or have any questions, please feel free to let me know! |
I was running epcap inside an Elixir program on a Raspberry PI 3 when I run into this error
34924 is 0x886c.
I googled and found https://www.raspberrypi.org/forums/viewtopic.php?t=146246&p=963226
If I understood that correctly, it's the builtin wifi card of the PI that is sending those packets.
I don't know what a LARQ is and I don't really now what I've been doing, but this fixed that:
It's probably a hack but I hope it helps adding proper support for these packets.
decapsulate
now returns something likeMaybe it's not the Erlang way, but it could return
unknown
instead of failing when it doesn't know how to decapsulate something. The client would fail anyway if it doesn't handle that, or could decide to keep going on.The text was updated successfully, but these errors were encountered: