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).
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:
*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.
Like the other guy said, they're probably not doing DPI to actually check for XMPP, so if something like portquiz.net:5222 loads, then you could host a VPN on the same ports as XMPP and have unrestricted internet.
Yeah, I only really used it when the computer running my tunnel wasn't on, but that's not an issue for me anymore.
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.
I think the author was trying to compare how Linus didn't have 8MB then, but 8GB being common today.
But yeah, I still agree that part could be worded better, so I added some suggested words:
Linus didn't have a machine with 8MB RAM [back then]
[However] Today, machines with 8GB RAM [1024 times that of 8MB] are very common.
I doubt it, here's the original author, and the username doesn't match with OPs.
Dear OP, I implore you to continue in your endeavours of posting the artistic compositions, I don't have the Instagram and find great delight in the visual depictions that you present!
I don't know about the newest models, but I've had a pretty good experience with Brother printers, CUPS works fine, and they do release their own driver if you really want to use that.
I believe Microsoft published the spec and opened up the patents for exfat a while ago. So Linux has had a pretty good exfat driver from Samsung since Kernel 5.7.
I think you forgot a /s
I don't think it's required anymore, but it's definitely still recommended.