Oh yeah, can’t use the same IP range as your LAN, that will lead to problems. :D Glad it’s fixed.
Out of curiosity, does forwarding work now without the output (-o) command in PostUp?
Oh yeah, can’t use the same IP range as your LAN, that will lead to problems. :D Glad it’s fixed.
Out of curiosity, does forwarding work now without the output (-o) command in PostUp?
Like I said in another thread on this post, I’m pretty sure that’s because they are forwarding input but not output in the PostUp rules. Setting a /32 in AllowedIPs works fine for me.
What are you trying to say? That reply also shows AllowedIPs set to a /32 on the server side.
I don’t think that’s what the setting does. Anyway, I have them set to a /32 IP in my server config and it works nonetheless. I get full access to the /24 behind the server from the client.
You have ALL traffic being routed over Wireguard here.
Please correct me if I’m wrong, but isn’t it the other way around? All Wireguard traffic is forwarded to the local interface.
I think the problem might be your PostUp/PostDown lines have an in-interface (-i) but are missing an out-interface (-o) for the forwarding. Try this:
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o ens3 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o ens3 -j MASQUERADE
Linux users can’t even agree […] so how am I supposed to pick one with any confidence?
Easy. You make a post like the OP, count the positive mentions of distros in the comments, and bam, you have your distro of choice. It’s called the Linux newbie roulette and works kind of like the magic hat in Harry Potter that sorts you into your house.
Not yet, but you probably will be able to in the future.
Right so WhatsApp and messenger are gatekeepers and they must allow interoperation with who anyone who wants to ie me running my own signal instance?
There are several stipulations on interoperability in the new regulation (Ctrl+F “interop”). To my understanding it is stipulated that they have to make interoperability possible for certain third parties, but how to go about this is not exactly specified on a technical level - meaning the specific way to implement this is left to the gatekeeper. So your Signal server may or may not be able to depending on how exactly they go about this.
They also need to interoperate with signal hence if a works with b and c works with a why wouldn’t b work with c?
No they need to enable interoperability period. Says nothing about Signal (the software) per se. Meta has announced they plan on implementing it based on the Signal protocol (not Signal messenger software, not Signal server software).
Cos if thats hoe it works or if im not allowed to interoperate with WhatsApp or messenger in the first place then this juat seems like its handing the monopoly away from the companies to the government and giving the people removed all.
To my knowledge the aim of the regulation is exactly that, to allow anybody interoperability with these “core platform services”. The status quo is that the regulations has been announced by the EU, it has gone into effect, and Meta has announced how they will implement interoperability to comply. Once the implementation is available and then found lacking in regard to the regulation it would be up to the affected third party to sue Meta over it.
Not with Signal messenger, the company running it hasn’t been designated as a gatekeeper under the DMA rules. You can see which services will be affected on the Wiki page (only WhatsApp and Facebook Messenger currently).
Signal protocol ≠ Signal messenger
AFAIK you could always have selfhosted a Signal server, you just can’t interact with the “normal” Signal messenger and its network.
No, the DMA has nothing to do with RCS, at least not directly.
Yes, WhatsApp and Facebook Messenger were initially just XMPP servers, but have since had proprietary expansions.
In the context of the DMA both of them will be forced to make interoperability with other third-party messengers possible, since Meta has been designated a “gatekeeper” under the new regulation. Meta has announced they plan on doing so via an implementation of the Signal protocol.
There are some provisions in the Digital Markets Act that go in that direction. It only took effect roughly 3 months ago though, so remains to be seen if it works out as intended.
So WINE was just imagined into existence? Or maybe it was a wizard with a magic spell?
GP is simply wrong on this one. While it is an open source project with a lot of volunteer involvement, there are companies like CodeWeavers and Valve which directly or indirectly contribute to development. You can get support from CodeWeavers AFAIK, but that means paying them.
Why do people get so uppity when I simply ask questions? I never claimed that anyone owed me anything. I never asked for anything.
Well you did ask for something, which is replies to your questions. And your reaction to those replies, whether intended or not, comes off as “uppity” as well. Hence the downvotes and hostility (not to say that I support that from either side of the conversation).
I am unwilling to learn.
Then why are you wasting peoples time with asking questions?
I’ve wasted hundreds of hours trying to learn to use Linux for basic tasks after everyone assured me it was “so easy” and not gotten anywhere. I’m done trying to learn.
Running software on an OS it wasn’t made for is anything but a basic task. Try running various Linux software on Windows and you will see. If you want to run software made for Windows easily the way to do that is using the version of Windows it was created for.
What people mean by “basic tasks” is usually browsing and office, and there is Linux-native software for that.
Someone posted Zorin OS elsewhere, which appears to be exactly that.
Not really. It has deeper integration of Wine into the system by default, but it is still a Linux OS running a compatibility layer for Windows software. This will not save you if you are unwilling to learn, there will still be various problems. Some software will simply not work, or only partially work, or require additional configuration to work.
In summary, if your definition of “basic tasks” is running arbitrary Windows software then doing it on Windows is the way to go.
Nah, this one was a direct link on purpose. But the edit box swallowed the @lemmy.ca
part at the end due to trying user name auto-completion, so thanks for making me re-read the post. Good bot!
Ah with that link it’s easy to track down what happened.
First you go to the community on the server in question: https://lemmy.world/c/alberta@lemmy.ca
Then you click on Modlog in the sidebar: https://lemmy.world/modlog/3835
And since there is pretty much nothing in it we immediately see the entry for your post saying:
reason: Deceptive content. Calling to abuse government system.
Note that when you compare your servers Modlog that entry is missing there, so yes, only removed for people connecting through lemmy.world.
Not sure how appeals work there, you can probably reply to the account that notified you, or go to the !support@lemmy.world community.
Do you mean not initially designed to support? Because at least for displays and networking (in the sense of being able to send X events over the network) that seems wrong, a network capable display server is basically X’s entire purpose? And for keyboards and mice there are extensions now, so x.org as a standard now very much supports those by design. Actually to my knowledge Wayland basically just forked their keyboard standard, the X Keyboard Extension.
First I heard of this, but since it seems to be just some software that runs on the hardware of car manufacturers it seems rather unlikely. But very theoretically possible, if the car manufacturer was using default process scheduling in a CPU constrained machine and now switches to real-time scheduling in an update. But that was possible for years before this news, the code has just been mainlined to the default kernel now. If the car manufacturer cared about that they would probably have done it already with a patched kernel.