On Fri, Feb 17, 2023 at 12:03 PM John Covici <cov...@ccs.covici.com> wrote: <SNIP> > Well, some progress, but no joy. I found actual messages from > netconsole and it seems no matter what device I put for the source, > netconsole says it doesn't exist. I tried my eno1, and also eth0 and > eth1. In my normal boot sequence, I see that udev renamed eth1 to > eno1, but netconsole still said it does not exist. So, I may have to > use the serial console method, I have to find my cables for that. I > did also try to add net.ifnames=0 to my boot options, but no joy > there. > > -- > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici wb2una > cov...@ccs.covici.com
John, I did a bad job at trying to point you in this direction the other day, and in my testing I'm not sure how well it works. However another option you might investigate is on the receiving end you can apparently set the transmitter's IP address by using the transmitter's mac address. Supposedly you would execute something like the following, with extra spaces added for readability: sudo arp -s 192.168.86.244 90:e6:ba:10:a3:e7 temp which supposedly says 'when you see a packet with this mac address associate it with this IP address'. The temp part says don't add it to the permanent tables. After executing this you are supposed to be able to use tools that filter by IP address but I didn't have great results. Hope this helps, Mark
