Simone Margaritelli
Simone Margaritelli
it seems caused by a bug in `com.apple.iokit.IONetworkingFamily` rather than bettercap itself ... relevant info: ```panic(cpu 0 caller 0xffffff80026da1ed): Kernel trap at 0xffffff7f8395db7a, type 14=page fault, registers: CR0: 0x0000000080010033, CR2:...
can you produce a panic with the `keepsyms=1` kernel boot arg? that'll make it much more readable
it seems clear to me this is a 10.14.2 bug rather than bettercap's, closing this since upgrading to 10.14.3 seems to fix the issue
well, it looks like a 10.14.2 bug with newer hardware ...
as far as i can see #496 is not adding a new module but changing the default behaviour of an existing one, did i get it right? i'd merge right...
this should be fixed with the latest version
that one .. oh ok so it's not fixed at all ... great XD
@adamsj182 > The problem now is that none of these settings persist between runs. I can't find where the conf files are located and I've concluded they're embedded somewhere in...
the supported channels are parsed from the output of `iw info`, i just pushed a commit that uses iwlist instead and only falls back on iw if iwlist is not...