1 |
On Thu, Feb 16, 2023 at 6:50 AM John Covici <covici@××××××××××.com> wrote: |
2 |
> |
3 |
> The sending computer has two nics, eno1 for the internal network and |
4 |
> eno2 is on the internet. So, my netconsole stanza said |
5 |
> netconsole=@192.168.0.1/eno1,@192.168.0.2 |
6 |
|
7 |
Is CONFIG_NETCONSOLE enabled for your kernel? |
8 |
|
9 |
I'm not sure if the kernel will assign the names eno1/2 to interfaces |
10 |
- I think those might be assigned by udev, which probably won't have |
11 |
run before the kernel parses this instruction. You might need to use |
12 |
eth0/1 - and your guess is as good as mine which one corresponds to |
13 |
which. |
14 |
|
15 |
If it isn't one of those it might not hurt to put the target mac |
16 |
address in there just to be safe. I haven't needed that but maybe |
17 |
there are situations where ARP won't work (it would be needed if you |
18 |
are crossing subnets, in which case you'd need the gateway MAC). Keep |
19 |
in mind that this is a low-level function that doesn't use any |
20 |
routing/userspace/etc. It was designed to be robust in the event of a |
21 |
PANIC and to be able to be enabled fairly early during boot, so it |
22 |
can't rely on the sorts of things we just take for granted with |
23 |
networking. |
24 |
|
25 |
> |
26 |
> The box which is at 192.168.0.2 has netcat (windows version) and I |
27 |
> tried the following: |
28 |
> netcat -u -v -l 192.168.0.2 6666 and I also tried 192.168.0.1 6666 |
29 |
> which is the ip address of the linux console which I am trying to |
30 |
> debug. |
31 |
> |
32 |
> I also tried 0.0.0.0 6666 which did not work either, but I think the |
33 |
> windows firewall was blocking, and I did fix that, but did not try the |
34 |
> 0.0.0.0 after that. |
35 |
> |
36 |
|
37 |
So I'm pretty sure that netcat requires listing the destination IP, |
38 |
since it has to open a socket to listen on that IP. You can |
39 |
optionally set a source address/port in which case it will ignore |
40 |
anything else, but by default it will accept packets from any source. |
41 |
|
42 |
I was definitely going to suggest making sure that a windows firewall |
43 |
wasn't blocking the inbound connections. That's fairly default |
44 |
behavior on windows. |
45 |
|
46 |
-- |
47 |
Rich |