Longish log entry every 4 milliseconds, java- related

[MessieAss]

Hi! I just installed nzyme successfully and logged in to the web interface, anything looked fine. When looking at /var/log/nzyme.log on my debian machine, it had grown to 55M within a few minutes.
It seems something about my java installation (which i have to look up in the first place, it's in place since pre-war time) is logged with every beacon.
Will i have to change my java installation or would some library enable the machine to decode the beacons?
Thanks & greetings,
off-to-dogwalk-timbo

The log looks like this, a few thousand times:
11:36:04.886 [probe-loop-0] INFO horse.wtf.nzyme.dot11.probes.Dot11Probe - Skipping malformed frame on probe [broad-monitor-wlp3s0].
horse.wtf.nzyme.dot11.MalformedFrameException: Could not parse 802.11 tagged parameters.
at horse.wtf.nzyme.dot11.Dot11TaggedParameters.(Dot11TaggedParameters.java:123) ~[nzyme-1.0.0.jar:?]
at horse.wtf.nzyme.dot11.parsers.Dot11BeaconFrameParser.doParse(Dot11BeaconFrameParser.java:40) ~[nzyme-1.0.0.jar:?]
at horse.wtf.nzyme.dot11.parsers.Dot11BeaconFrameParser.doParse(Dot11BeaconFrameParser.java:27) ~[nzyme-1.0.0.jar:?]
at horse.wtf.nzyme.dot11.parsers.Dot11FrameParser.parse(Dot11FrameParser.java:47) ~[nzyme-1.0.0.jar:?]
at horse.wtf.nzyme.dot11.probes.Dot11MonitorProbe.lambda$loop$0(Dot11MonitorProbe.java:240) ~[nzyme-1.0.0.jar:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:834) [?:?]
Caused by: java.lang.ArrayIndexOutOfBoundsException: arr.length: 385, offset: 383, len: 193, arr: 80000000ffffffffffff9a9bcbc78b169a9bcbc78b16e0cf8331d4d90b020000640031140014465249545a21426f7820476173747a7567616e67010882848b968c1298240301060504000100000706444520010d142a01003204b048606c0b0500001b0000460573d000000c2d1aad0903ffffffff000000000000000001000000000000000000003d16060004000000000000000000000000000000000000004a0e14000a002c01c8001400050019007f0805000f0000000040bf0cb2798b33aaff0000aaff0020c005000000fcffc1060000ff380000dd1a00904c0408bf0cb2798b33aaff0000aaff0020c005000000fcffdd180050f2020101000003a4000027a4000042435e0062322f00dd0900037f01010000ff7fdd088cfdf00101020100dd168cfdf0040000494c5103020972018c16000046000000dd0c00040e010102010000000000dd1d0050f204104a0001101044000102103c0001031049000600372a00012030140100000fac040100000fac040100000fac020000d5c1e60b
at org.pcap4j.util.ByteArrays.validateBounds(ByteArrays.java:973) ~[nzyme-1.0.0.jar:?]
at org.pcap4j.util.ByteArrays.getSubArray(ByteArrays.java:738) ~[nzyme-1.0.0.jar:?]
at horse.wtf.nzyme.dot11.Dot11TaggedParameters.(Dot11TaggedParameters.java:95) ~[nzyme-1.0.0.jar:?]

[lennartkoopmann]

Hi! That looks like an unexpected payload in a WiFi frame. Do you think you can send me a PCAP capture so I can investigate what's going on?

What WiFi adapter are you using?

I'll also reconsider the log level here because you should know about the parsing failure, but this is is clearly a lot of content to be logged.

[MessieAss]

Hi! I'm using a

03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)

connected to a tp-link archer c8 running dd-wrt. Would a wireshark capture suffice?
Cheers & thanks for caring,

  tim

[MessieAss]

Anyway, wireshark capture files have a promising file name suffix. I uploaded two files here:
https://www.boneko.de/messieass-intel-centrino.pcapng
https://www.boneko.de/messieass-intel-centrino-running-nzyme.pcapng

Both captures were recorded during idle time, this notebook here connected to ethernet. I hope it's sort of useful.

[MessieAss]

Oh sorry for confusing! I'm running Gnome and NetworkManager on my laptop which do not (yet) coexist with nzyme; the wifi connection of nzyme isn't configured yet. I'll have that fixed in a moment...

[MessieAss]

Well, i've been proven wrong. There seem to be issues with my wifi adapter. Will try again tomorrow.