Raspberry pi (running kali linux) can be SSH'd into, but cannot be detected in a nmap scan. Pi also cannot find device on LAN that my computer can [closed] - raspberry-pi

Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 days ago.
Improve this question
This error is driving me crazy.
I have a raspberry pi zero w running kali linux as a headless server. From my Mac I can SSH into it, use command-line tools, etc. However, the raspberry does not show up on an NMAP scan (-sn or sP flags), but can be pinged. Using the terminus app I can SSH into my Mac, but if I try to SSH into my raspberry pi (using the same IP when I SSH from my Mac) the connection times out.
Another error that I think is related: I have a wifi device (smart lightbulb) that interacts with some python code I wrote. From my Mac I can easily send it commands. However, my raspberry pi throws "no route to host" when I try to connect to the lightbulb from it. From my Mac I can ping the lightbulb no problem, but a ping from my raspberry pi cannot find it.
Things I've tried:
Used ufw to disable the kali linux firewall
Reset my raspberry pi and lightbulb
TL;DR -> Raspberry pi does not show up on NMAP scan, can be SSH'd into from certain machines, and can't find a device on the LAN

Related

-bash: raspistill: command not found [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
The community reviewed whether to reopen this question 4 months ago and left it closed:
Original close reason(s) were not resolved
Improve this question
I am trying to hook up my Raspberry Pi Zero W, running Raspberry Pi OS Lite, to a Raspberry Pi NoIR Camera Module V2. After running these commands:
sudo apt update
sudo apt upgrade
and enabling the camera in the raspi-config menu and rebooting per the Raspberry Pi documentation, when I run the command raspistill -v -o test.jpg according to the Raspbery {Pi documentation, I get the below error.
-bash: raspistill: command not found
The documentation says:
This probably means your update/upgrade failed in some way.
I tried it again. I ran update, upgrade commands, rebooted and enabled the camera in the raspi-config multiple times with no change in outcome.
raspistill has been replaced by libcamera.
https://www.raspberrypi.com/documentation/accessories/camera.html#libcamera-and-libcamera-apps

Using VSCode with a Raspberry Pi 1

I'm trying to set-up Raspberry Pi 1 with VSCode so I could run code remotely on it. I've installed VSCode on the Pi, but when trying to launch it with the 'code' command, I get an 'Illegal instruction' error.
I tried connecting remotely from my Windows workstation, but I got an error saying that "the remote's host architecture isn't supported".
My question is, is it possible to install VSCode on the original Pi? If not, what IDE do you use to work remotely on it, besides ssh and VNC?
According to VS Code's official site, Raspberry Pi 1 is not supported.
First-generation Raspberry Pi modules and Raspberry Pi Zero are not supported as they only include an ARMv6 CPU.
Seems to me Raspberry Pi 1 has very low hardware and I'm sure that it will give you hard times when you codding. If you wanna use it anyway, you may continue with a browser-based editor like AWS cloud9.

OpenBSD Unsupported Video Signal [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
Spent a couple hours this evening on the #openbsd irc channel troubleshooting a display issue. Couldn't figure this one out though we had fun trying!
Specs:
USB Stick and Openbsd 6.2 Image
Known good,
Openbsd image installed successfully from this USB, to a virtual env on a separate device, using these instructions
Desktop computer
Motherboard, 64bit Intel processor
On-board graphics only
Currently running Ubuntu 16.04.03 Server
BIOS (legacy enabled) set to boot USB first
Monitor
40" Toshiba LCD TV Model 40UX600U
Symptoms
Start computer on Ubuntu server, displays just fine, no issues
Boot to Openbsd USB stick, bios screen runs, self check passes then monitor displays "Unsupported Video Signal". This is not an Openbsd message, but rather from the monitor itself.
Done so far
Cleanly formatted USB (under supervision)
Installed from USB to virtual env on separate device, no issues, loads Openbsd just fine.
Boot computer to Ubuntu, display works perfect
Boot computer to Openbsd USB, display shows error message above.
Unplug and replug VGA cable
Power off, power on monitor
Suspicions
- Pg. 88 of the Toshiba monitor manual shows a table of Acceptable Signal Formats for PC IN. My hunch is the graphics driver is incompatible with this monitor.
Questions
Is there anything I can do to make this monitor work with a new Openbsd 6.2 install?
How can I check Openbsd monitor compatibility before embarking next time?
Ubuntu has KMS support for the nVidia graphics card but OpenBSD only has support for the old UMS driver. The OpenBSD kernel (probably, I'm not sure) is using 640x480 as resolution and the Linux kernel is using the highest resolution supported by your monitor.
You have two options to "fix" the problem. Install OpenBSD on another computer or with a different monitor (you can also use a laptop with a USB<->HDD adapter), when the installer ask if you want graphics support (or something like that, I don't remember), reply yes. Finish the installation and reboot. Then move the HDD to the original computer and power on the machine. You will see the same message but at some point the system will run xenodm (a graphical launcher for X11 sessions, like xdm), then the monitor will work fine. Unfortunately, you can't see the console messages.
Don't change xorg.conf, your problem is not only related to the monitor. Another option (quite better, imho) is to buy a cheap used ATI graphics card and just install OpenBSD. The ATI graphics cards are fully supported (except the newest ones) and have KMS support. You will only see the message during two or three seconds and after of that, you will see the console. Maybe you will need run the installer on a different computer or with a different monitor, but everything will work fine after of that.
Anyway, OpenBSD uses only a standard mode for the basic console. It doesn't make weird unsupported things. So, probably your monitor has some kind of problem with the lowest VGA resolution/frequency. The problem is that the OpenBSD kernel can't change to a higher resolution during the boot process because it doesn't support the nVidia cards at the kernel level. It uses a userland driver for the nVidia cards, like the Linux/BSD/Unix traditionally used to use.
If you have an old (like 10 years or so) Linux LiveCD/installer, try to run it on your computer. You will see the same problem.

How to run only the LINUX kernel and User programs [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 8 years ago.
Improve this question
is it possible to run only Linux kernel on a system which will load user program instead of an operating system?
I want to work with a raspberry pi with Linux kernel. I am trying to create a server and client programs on raspberry pi and for this i need only a kernel which will work on network drivers.
I want raspberry pi to run the programs when i switch ON it.
Thanks in advance.
:)
Yes it's possible. configuration depends of which init system you choose to use.
In a few words, in the boot process, once the linux kernel is up, it launches the first process named init.
And the init start other processes as needed.
That's what you should use to start your program automatically.
Well, you'll also need to make your own system with tools like Buildroot for example.

BSD Virtual Guest [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
So I am a big fan of VMs, actually got experience enough to switch my development box to a linux distro. At this point I would like to get more experience with BSD and hope to do this with a VM. So the question I have is what configuration is correct?
BSD...
List item
FreeBSD
OpenBSD
PC-BSD (I know it is FreeBSD with a KDE, but might be simpler to get started with)
Which Virtual Machine is best for these guests (on a linux host)
List item
VMWare Workstation (have a license for 7)
Virtualbox 4
QEmu
Other?
Any suggestions from experts would be great. I was able to get FreeBSD and PC-BSD installed on virtualbox 4, however I get horrible resolution that I can't seem to fix.
I found the 'right virtual machine' requires some tinkering. VirtualBox ran Plan9 really slowly, qemu+kvm ran it hundreds of times faster. qemu+kvm also ran an Ubuntu guest at what felt like faster-than-hardware (at least for booting :) but I've read accounts from people that say the exact opposite, that VirtualBox outpaced qemu+kvm. Test them both :) that way you get the experience, and can know which one is more usable for your environments.
As for the BSDs, I ran OpenBSD for years and really liked it. You probably can't go wrong with FreeBSD. Learning both wouldn't be a bad idea -- they have different feature sets and excel at different tasks.
Don't let KDE in PC-BSD sway you too much, the different KDE things ought to be available in all their ports trees. Or try life without KDE or Gnome for a while.
I run FreeBSD 8-STABLE guests in VirtualBox 4.0.4, running on Windows (XP & 7) systems. It works, but there are some caveats. Seamless mode (which you might use with Linuxen) doesn't work, and it takes some configuring to get things set up exactly right. See http://wiki.freebsd.org/VirtualBox for the settings you need.
I played with virtualized PC-BSD, and it worked about the same as FreeBSD, since it is FreeBSD. PC-BSD has some nice features for the newbie to take some of the pain out of installing software.
I have also tried NetBSD as a VirtualBox guest. It "works" (for some definitions of work), but you have to launch the VM with something along the line of "vboxsdl.exe --nopatm --startvm [machine]". This worked for me on one Windows box but not on another. I didn't get around to seeing if X works.
I have not tried OpenBSD, but I seem to recall there being images out there, so it should work to some degree.
I don't have experience with other virtualization software, so can't help you there.