I take my shitposts very seriously.

  • 2 Posts
  • 41 Comments
Joined 1 year ago
cake
Cake day: June 24th, 2023

help-circle
  • Wireguard

    You mean Wireshark? It’s possible. You might even capture the DHCP exchange.

    The two best programs for the job are nmap and arp-scan.

    Nmap is like ping on steroids. You can use it for network discovery, port scanning, fingerprinting, and basic pentesting. As long as the pi can talk to the computer, nmap will sniff it out.

    ARP-scan works on the data link layer to identify hosts using ARP. It should be able to return the IP address of all ethernet devices even if they end up in different subnets. It took me a little over two minutes to scan a /16 subnet with one retry and 0.1 second timeout.

    If you are really concerned about the pi’s address, you should run a local DHCP server on the laptop. dnsmasq for Linux and Mac, but I have no idea what to use on Windows (other than a VM bridged to the ethernet interface).




  • I’ve never used a pi, but it should be possible to mount the root partition and edit the /etc/network/interfaces or /etc/dhcpcd.conf file, or /etc/NetworkManager/conf.d/* if you have NetworkManager (systemctl status NetworkManager to check).

    You should also make sure that sshd is listening for connections from any address (0.0.0.0 and ::).




  • rtxn@lemmy.worldtoSelfhosted@lemmy.worldssh into raspberry without a router
    link
    fedilink
    English
    arrow-up
    29
    arrow-down
    1
    ·
    edit-2
    7 months ago

    Give each device a static address, and set the default gateway to whatever’s on the other end of the cable. You might need a crossover cable, but most NICs can work using a straight-through.

    E.g. set the laptop’s address to 169.254.1.1/16 and default gateway to 169.254.1.2, and the RPi’s address to 169.254.1.2/16 and default gateway to 169.254.1.1. They should be able to talk to each other then.

    If those addresses seem familiar - Windows uses the 169.254.0.0/16 subnet to automatically assign random addresses if DHCP fails, so that if there are several computers in the subnet, they’ll at least have addresses that can talk to each other. It’s called APIPA in Windows, and Zeroconf in the Unixverse.



  • Proxmox VE on a machine that I got almost for free. Intel i3-4160, 10GB RAM, 240GB SSD for the OS, and a non-redundant 1T HDD for storage. The only things I paid for are a second NIC and an 8GB RAM stick.

    PVE is running a pfSense VM, and a bunch of Debian containers:

    • Samba
    • Jellyfin (still setting it up)
    • Twingate Connector

    All internet traffic goes through the pfSense VM. Unfortunately the ISP has put me behind CGNAT and disabled bridge mode, so my internet-facing things (mostly Wireguard and SSH) are pretty much crippled. Right now my best no-cost option is to use Twingate, but I don’t trust it to handle anything other than SSH.






  • Nvidia is unfortunately kind of a dick about Linux support. The open-source Nouveau driver is making great strides, but I don’t think it’ll be ready for general adoption for several years. The proprietary driver (the nvidia-dkms package) is far more usable, but there are always some issues.

    If you want to focus on gaming, you should consider Nobara or Garuda Linux.

    Garuda is based on Arch, and its main selling point is that whatever you need for gaming (Wine, Steam, DXVK, VKD3D) is either installed out of the box, or installed and configured in one click. Since Arch, and by extension, Garuda, is a rolling release, it gets very frequent updates that are always cutting edge, but it might require some maintenance at times.

    Nobara is maintained by Glorious Eggroll, who also maintains custom Wine and Proton releases and has made massive contributions to Linux gaming. It’s based on Fedora, which is a point-release distribution - it receives security updates continuously, and feature updates every few years, so it should require little maintenance.


  • I didn’t realize you were new, it sounded like an issue anyone could have. Gaming on Linux is definitely not a perfect experience. Please don’t be afraid to ask around in the various linux_gaming communities, there are always people who are willing to help.

    What’s your computer like? What brand and model is your GPU? What distribution? If the GPU is Nvidia, do you know if you have the open-source Nouveau or the proprietary Nvidia driver?

    A bit of a glossary:

    • Wine: a compatibility layer that allows Windows executables to run on Linux systems by translating Windows system calls to Linux calls.
    • Proton: a derivative of Wine maintained by Valve, optimized for gaming on Steam.
    • Wineprefix or prefix: a mock-up of a Windows filesystem. The application running inside Wine sees this as the C: drive. The default wineprefix is located in ~/.wine. The system’s root directory is mounted as the Z: drive.
    • Lutris, Bottles, Heroic: graphical front-ends to manage many aspects of your Wine applications.



  • The official flatpak release of Bottles offers sandboxing. It comes from Flatpak itself, so other similar apps (like Heroic) might support it too.

    Another option is to chroot before running Wine (so Z: doesn’t point at the real system root), or su into another user (Wine inherits the user’s privileges). It’s also possible to run Wine inside a container, but GUI support is questionable.

    Ultimately, running an untrusted executable is always a risk, regardless of the OS. If you want near-absolute safety, you’ll want a different machine - either a VM or a heavily firewalled physical machine.