On Tue, 14 Feb 2023 16:25:55 -0500,
Rich Freeman wrote:
>
> On Tue, Feb 14, 2023 at 2:54 PM John Covici <cov...@ccs.covici.com> wrote:
> >
> > On Tue, 14 Feb 2023 14:08:34 -0500,
> > Rich Freeman wrote:
> >>
> > > will be displayed on the console briefly. You can also enable a
> > > network console, which will send the dmesg output continuously over
> > > UDP to another device.
> >
> > OK, how would I set up logging to a network and what would I have to
> > do on another computer -- which in my case is Windows?
>
> The docs are at:
> https://www.kernel.org/doc/Documentation/networking/netconsole.txt
>
> (you can also google for linux netconsole for some wiki articles on it)
>
> I have on my command line: netconsole=@/,6666@10.1.0.52
>
> That IP is the host I want the log traffic to go to. (Read the docs
> if you have a more complicated networking setup - I assume that will
> just run ARP and send stuff out without using a gateway/etc.)
>
> Then on a receiving linux host I'd run (I think - it has been a while):
> nc -u -l -p 6666
>
> Now, you mentioned Windows. I've never used it, but nmap has a
> program available in a windows version called ncat that might do the
> job: https://nmap.org/ncat/
>
> You just want to make sure you have it listening on port 6666 for UDP.
> Make sure you use UDP or you won't receive anything.
>
> If it is working you should get a ton of log spam when your host boots
> - anything that shows up in dmesg will show up in the network console.
> It is sent in realtime.
Sounds great -- I notice you ommitted the ip address, my network
device is brought up by a systemd unit file, will I need to specify
the device, then? I was thinking of netconsole=@192.168.0.1/eno1 --
would this be correct, assuming the ip address is correct?
--
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
