Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)ST
Posts
1
Comments
360
Joined
2 yr. ago

  • You can download the windows iso from windows webpage, but if I remember correctly you have to do it in Windows since it depends on a downloader program.

    It only forces you to use the media creation tool on Windows, everything else it gives you a link to download the ISO.

    I kept a windows partition for years because I never knew if I would need it, it was only when I realised I hadn't touched Windows in months that I felt comfortable removing it

    I'm exactly the same.

  • would I have to change my actual XMPP port? Yes.

    You could port scan portquiz.net to find other unblocked ports if you want to use the same IP, or get a VPS or something to do the VPNing (Oracle cloud have free ones, or a cheap one will do).

  • That's sort of what I mean by "just how the internet works" where "it's that it's anybody's guess if any of the hops will pass it along."

    Like yeah I understand TCP has protections against dropped packets, but that's only because it re-requests the packets it thinks are lost or corrupt.

    Also HTTP and WOL are at a different layer, they're both TCP and UDP respectively, so it shouldn't matter whether if the App layer is obscure or not. Heck the routers of the internet only look at the IP layer, so it can't even tell if it's TCP 443, and you could probably even write your own Transport layer protocol and route it over the internet.

    Although I guess firewalls could do some prioritisation, and wouldn't like this new transport layer, but they're usually near the ends of the connection, not in the middle, and I was taught to prioritise VoIP stuff anyway.

    TCP/IP model for reference:

    • Application (HTTP, WOL, Minecraft, whatever you want)
    • Transport (TCP, UDP, other ones too)
    • IP (IPv4 & IPv6 + older not used (X.25, CLNP, etc) / Sender and Destination)
    • Link (Ethernet and stuff)

    *I have not much experience so I may have made some mistakes, but I'm currently completing a CCNA so it should be somewhat correct.

  • Well it's just UDP so isn't that just how the internet works, but yeah when I did do it, I'd often spam a bunch of packets, sometimes just sending one didn't work, but multiple always worked.

  • A lot of people are saying WOL doesn't work over the internet, but I've got it working.

    Basically port forward UDP 9 to your broadcast address (the last possible IP in your subnet), eg. 192.168.1.255. Then send the WOL to your public IP which will then get broadcasted out over your network by your router.

    Typing this out, I realised this seems like a horrible security practice, so I'll probably disable it soon anyway, now that I've got multiple servers and a failover VPN.

  • Oh, I got shadow banned from Reddit for helping someone run a large language model on their GPU.

    Like I just assumed the user stopped caring until I looked at the post in incognito and my last comment just wasn't there, yet it appears when I log in

    So with the third party apps thing, that was the last straw for me.

  • I just read some more of your comments and thought I might properly explain VLANs:

    VLANs let you create a whole virtual network within your physical network, there can be upto 4096 of them that can be tagged and 1 untagged per port, the VLAN ID defines which one to use.

    A tagged VLAN is often used between routers and switches, so the connected device can pick which VLAN to use, but an untagged VLAN dedicates that port to that VLAN making it appear to the connected device as if it's the physical network.

    Since it's a whole new network you need some sort of router to route between them.

    As a rough example you could have something like: Router --2T--> Switch --2U--> TV, where the T is for tagged and U for untagged. Or replace Router with Pi if you use that, the Pi will access the internet with the (technically untagged) physical network, and route between tagged VLAN 2, meaning you can do everything on the Pi with 1 ethernet port.

    Disclaimer: Most of this was learnt from experience so it might not be completely correct.

  • I believe that's the VLAN for the WAN, basically you only need to enable that if your ISP is using VLANs, but you want to enable VLANs on your LAN. I have the Telstra version of that modem (I recognise the Technicolor UI) and it doesn't allow you to use VLANs like you want to.

    You could probably set up some routing stuff on a raspberry pi though, and use a switch.

    Or if needed put your modem into bridge mode, and acquire a router that supports VLANs, I don't know of any cheap consumer ones, but I'm in the process of switching to OPNsense with an old computer. Unrelated, but in my experience technicolor has severe bufferbloat anyway.

  • Plus having to basically rely on a built-in app database/store to easily install apps

    Someone else has mentioned that all GUI 'stores' suck, and in my experience that's true. I usually find things either from Google, suggestions, or apt search.

    Kinda stinks to me, and not being able to simply download an installer from a website.

    I also thought I might mention that standalone Linux executables do exist, I believe ookla speedtest publish one, and additionally AppImages are really cool in that it's a container the app runs in that you can just double click.

    and having the program, whatever program, up and running reliably within a minute

    I've only had issues with this when I've done something dodgy and I know that I've done it, when it's an app in the middle of development, or snap packages. Anything installed using the distro's repo, Flatpak, or AppImage, has always worked. I still use Windows for study, and I'm pretty sure it takes longer on Windows to go from download to app running.