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
wireshark: Add Bluetooth #89461
wireshark: Add Bluetooth #89461
Conversation
Only applies to Linux
How to disable Bluez support for wireshark-cli by default? |
@Izorkin: Ideally someone adds a flag to wireshark, but in the meantime you might get away with using |
@bjornfor this variant not worked:
wireshark-cli building with bluetooth. |
I was thinking something like
(untested) |
This variation works:
Create PR? |
Motivation for this change
Add support for captuing live data from bluetooth interfaces.
Note: This only works on linux and has been appropriately gated.
It is debatable whether or not libpcap should include bluez support by default on linux.
If it's default enabled then no changes are needed for wireshark (or any other application that want to use it) but iptables must disable it (to avoid a libpcap -> bluez -> dbus -> systemd -> iptables -> libpcap cycle).
If it's default disabled then wireshark needs to enable it but iptables needs no changes.
I've implemented the latter but the change is trivial if prefered.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)