Closed ttcoder closed 8 months ago
Ok with the build "fixed" with a couple changed lines, I tried on metal to see if I could listen to the LOG from another computer : I configured to send the UDP packets to another laptop on the same LAN (they can ping each other), but no joy...
The "listener" laptop is running
nc -l -p 9
I'm probably doing something wrong, since my net-fu is quite weak :-)
Silly me, nc obviously works on TCP by default, it needs the -u flag to listen to UDP traffic:
nc -l -u -p 9
And then it works great (I seem to get "dropped packets" on the Tx side after a while, but not a problem for me since I'm after boot-up diagnostic only)
Anywyay I'm good on this ticket :-) (I can apply the build "fixes" on my own etc)
Good to hear that it works after fixing the obvious build fixes. @jschlatow may we add a recipe for this component, so that it's build regularly?
@chelmuth I added recipes for udp_log and log_udp in commit d066bac and fixed the build errors with commit 2de95f6.
Merged to staging incl. Fixes
marker.
Seems the LOG session API changed a while back and this component needs adapting, since the logging write() now has "void" return type? :
With a couple changes I got it to build and run (at least in qemu), will test its actual networking traffic on bare metal later on.
I'm still in 23.05 so it might be that this was fixed already and I'm just behind the curve.