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.
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.
For the unfamiliar: https://www.youtube.com/watch?v=TJYOkZz6Dck
(CW: gore, subtitles)
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 fuck 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.
In Germany, Mein Kampf is banned except for educational purposes, eg in history class.
Strictly speaking this is incorrect, although the situation is somewhat complicated. There are laws that can be and were used to limit its redistribution (mainly the rule against anti-constitutional propaganda), but there are dissenting judgements saying original prints from before the end of WW2 cannot fall under this, since they are pre-constitutional. One particular reprint from 2018 has been classified as “liable to corrupt the young”, but to my knowledge this only means it cannot be publicly advertised.
What is interesting though is how distribution and reprinting was prevented historically, which is copyright. As Hitlers legal heir the state of Bavaria held the copyright until it expired in 2015 and simply didn’t grant license to anything except versions with scholarly commentary. But technically since then anybody can print and distribute new copies of the book. If this violates any law will then be determined on a case-by-case basis after the fact.
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.
pet open source projects that no one else ever seems to contribute to, not […] software that holds up civilization
SamePicture.jpeg
I’m involved in the development of an addon for the Classic WoW versions (Questie), and the thing I do there is such a convoluted process that not doing it feels like letting my fellow devs and the users down. But you can do development on the PTRs and beta servers, so I haven’t given money to Blizzard in a long time. Now you could argue that this is even worse in regards to supporting Blizzard than just paying for a game, but I rationalise it to myself with the fact that the newer clients will inevitably be used for private servers just like the old ones were (some already are actually).
Neither. Battle.net is Blizzards game launcher and store. They also own that domain, but the name usually refers to the binary.
The WINE_SIMULATE_WRITECOPY=1 %command%
is the Steam launch option you set, with command%
meaning roughly “what Steam would do without any launch options set”.
The whole process was a bit finicky and I did it a few month ago, but from what I remember it went something like this:
Battle.net.exe
in it as a non-Steam game, then remove the installer (not the other way around or the prefix will be deleted)Oh so that’s what you meant. Thought you meant don’t use Lutris at first because of how you worded it. That makes much more sense.
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?