u/lukmly013 💾 (lemmy.sdf.org)

18M I like computers, trains, space, radio-related everything and a bunch of other tech related stuff. User of GNU+Linux.
I am also dumb and worthless.
My laptop is HP 255 G7 running Manjaro and Linux Mint.
I own RTL-SDRv3 and RSP1 clone.

SDF Unix shell username: user224

  • 23 Posts
  • 441 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle





  • Good idea.

    You can still get the newest DD-WRT builds even on the WRT54G.
    That is a Wi-Fi router from 2002.

    Of course, the features are sort of limited. I tried the VPN build (on WRT54GL), but I couldn’t get the OpenVPN client to connect. I found some thread mentioning it may be missing something, but I don’t know if that’s the issue.

    Anyway, without overclocking I’d expect like 2Mbps. I mean, it barely handles HTTPS. Just trying to load the WebUI maxes out the CPU for several seconds if trying to use HTTPS.
    Perhaps it’s not missing anything software-wise, but it’s just so slow it times out during handshake.
    So I just put the std build on it in case it will be useful at some point.


  • My lazy way is NGINX with autoindex.

    If it’s to go over untrusted network (e.g.: internet, school network) I use SSH for port forwarding. Lazy encryption.

    Something like this works just fine:

    worker_processes 1;
    daemon off;
    events {
    }
    http {
            default_type application/octet-stream;
            server {
                    root /storage/emulated/0/sharedfile;
                    listen 127.0.0.1:30000;
                    location / {
                          autoindex on;
                    }
            }
    
    }
    

    sharedfile is a directory with the files.
    On remote machine if I am not mistaken

    ssh -L 127.0.0.1:8080:127.0.0.1:30000 username@host
    

    Then just access it in web browser on 127.0.0.1:8080 or whatever port you chose.
    In PuTTY you can find this under “Tunnels”.

    Of course, you need to have SSH server set up as well.



  • OK-ish. I use Manjaro. It’s a pretty good idea to read Announcements before updating: https://forum.manjaro.org/c/announcements/

    It may have instructions on how to update without borking your system. For example, the February update broke Plymouth, causing systems using it to be unbootable. Sort of. It would actually boot, just to a black screen. On one of the threads someone reported being able to SSH into his PC just fine.

    Or the May update bringing Plasma 6 to stable. The recommendation was to reset Plasma to defaults, log out, stop SDDM and update from TTY. I tested doing exact opposite of that in VM, and it still went fine, except for missing icons, but still a good idea just to be safe.

    But I had some other problems too.

    February update: Booting to black screen. I found threads mentioning the same stuff for this update. Cool. “Remove Plymouth or just don’t use splash”. I… already disabled splash (and quiet to make boot-up cooler).
    Fix: Updating Linux 5.15 LTS to 6.6 LTS. Something changed in 5.15 making it break on my laptop, I guess. I couldn’t even get to TTY without nomodeset.
    Furthermore, the animations became choppy after resuming from sleep.

    May update: Turning on Bluetooth may cause system crash. It would show as “ON”, but actually be inactive while shoving already paired devices. This couldn’t be reversed. Logging out and back in would lead to only the welcome screen and yakuake showing up. Trying to reboot from both yakuake and plain TTY would stop mid-way. After issuing reboot, the system would be mostly dead, but still kinda running. Linux still responded to magic SysRq.
    Fix: Upgrading Linux 6.6 LTS to 6.9.

    So, I can deal with it, and it definitely taught me to use Timeshift. Oh, and the brightness buttons sometimes stop working.