5
endor
6y

Network management from the terminal is such a pain in the ass on linux! Far too many different config files in many different places, and I have no idea which works with which!
Just now I managed to fuck something up in my RPi's config, so I don't have wifi access anymore and I didn't have time to find its ip address while connected through ethernet :/
Fuck's sake

Comments
  • 0
    @amatrelan it's not that I don't have backups either: I just didn't have a (quick) way to reload the original config to get it working again. Now I'll have to figure out how to pull the SD out (since the RPi is buried in a 3d printer) or patiently find the ip with nmap
  • 1
    You can use Wireshark, just unplug the Pi, tell Wireshark to listen to your ethernet port and plug the Pi back in. That's how I used to do it.

    Otherwise you can send a ping to
    255.255.255.255 (broadcast ip)

    And follow up with arp -a (at least on windows, Idk about linux' arp commands)
  • 1
    Oh, and give your Pi a hostname, that way you can use that to connect instead of an ip on lan
  • 1
    @FMashiro oooh fancy, never thought of that! Thank you, I'll give it a try!
Add Comment