This just happened when I tried to identify a device on my internal network, using the nmap -A command. I'm running FreeBSD 14.1-RELEASE-p3 GENERIC on a headless gateway server between my internal network and the internet.
I ran it inside of screen in an ssh session. As soon as I ran it, the ssh session locked and networking stopped. Pinging, requesting a new IP (DHCP), the box became unresponsive. So I had to go hit the power button and restart it. Any ideas?
That was it. Any ideas? I don't know if it took down the whole system or just the network card as I don't have a monitor plugged in (nor video card for that matter).
Here's the point in my /var/log/messages where it happened, you can see the new boot starting.
I ran it inside of screen in an ssh session. As soon as I ran it, the ssh session locked and networking stopped. Pinging, requesting a new IP (DHCP), the box became unresponsive. So I had to go hit the power button and restart it. Any ideas?
Code:
root@skunk ~ % nmap -A 10.0.2.56
Starting Nmap 7.94 ( https://nmap.org ) at 2024-08-29 08:54 EST
That was it. Any ideas? I don't know if it took down the whole system or just the network card as I don't have a monitor plugged in (nor video card for that matter).
Here's the point in my /var/log/messages where it happened, you can see the new boot starting.
Code:
Aug 29 08:47:09 skunk kernel: re1: promiscuous mode enabled
Aug 29 08:47:15 skunk kernel: re1: promiscuous mode disabled
Aug 29 09:25:36 skunk syslogd: kernel boot file is /boot/kernel/kernel
Aug 29 09:25:36 skunk kernel: ---<<BOOT>>---
Aug 29 09:25:36 skunk kernel: Copyright (c) 1992-2023 The FreeBSD Project.