• 10 Posts
  • 219 Comments
Joined 6 months ago
cake
Cake day: December 28th, 2023

help-circle






  • N0x0n@lemmy.mltoLinux@lemmy.mlVLC Player
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    1 month ago

    Same here 👋 still i’m a bit sad I had to move on from VLC… It was always one of the first software I would install on my setup… But that was mostly on windows.

    On linux/macos, MVP seems to work way better. I’m very thankfull for all these years of service, but everything has an end and like ICQ ended recently, VLC will probably die off in a few years…

    Except if they make a come back? Who knows !






  • N0x0n@lemmy.mltoSelfhosted@lemmy.world2 ports for 2 applications
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 month ago

    Not OP, but thanks for the write up !

    Regarding macvlan’s with docker, I tried to use them in the past and while I liked the idea of having every container on it’s own mac /ip address in the home network space, I couldn’t get the host to communicate directly with them.

    Everyone on the LAN could talk to my containers, except the host itself. IIRC there was/is some tricky part where you have to change the default route and create new iptables to make it work that way, but It seemed rather hacky and not secure at all.

    Now that I’m a bit more experienced with docker and all, do you know if this is possible or still one of the downside of macvlan’s?

    Edit: reference. I see he updated his post in 2023, maybe worth a new shot !!


  • You’re right, but only if you are an experienced IT guy in enteprise environnement. Most users (myself included) on Lemmy do not have the necessary skills/hardware to properly configure and protect their networking system, thats way I consider something like wireguard way more secure than opening an SSH port.

    Sure SSH key based configuration is also doing a great job but there is way more error prone configuration with an SSH connection than a wireguard tunnel.


  • Opening ports on your router is never safe ! There’re alot of bots trying to bruteforce opening ports on the web (specially ssh port 22)

    With SSH I would disable the password authentication a only used key based authentication. Also disable root access. (Don’t know how it works with forgero though)

    I would recommend something like wireguard, you still need to open a port on your router, but as long as they don’t have your private key, they can’t bruteforce it. (You can even share the wireguard tunnel with your friend :))

    Also use a reverse proxy with your docker containers.

    There are a lot of things you could do to secure everything, but If you relatively new to selfhosting, there’s a steep learning curve and a lot of time needed to properly secure everthing up. You could be safe by doing nothing for a few months but as soon as someone got into your system, you’re fucked !

    But don’t discourage yourself, selfhosting is fun !





  • N0x0n@lemmy.mltoLinux@lemmy.mlHow terminal works
    link
    fedilink
    arrow-up
    9
    ·
    edit-2
    1 month ago

    Heyy thank you very much for sharing your thoughts and knowledge with us !!!

    Very interesting and the write up is easy to follow up ! That’s the kind of cool blogpost we will be missing when the internet will be dead brained and flooded with AI shit…

    Will you integrate an RSS feed to your blogposts? So I could get your feeds directly into my RSS feeder? 😁