Do you have latest drivers / software / firmware installed on everything that traffic does thru? Is PPPoE used? Wired and/or Wireless? Do you block ICMP? Does your firewall “filter” packets on each side of the wg interface? I spent a good 3 hours tracking down an issue where just SSH sessions would randomly hang after 10-30 secs, turned out that the wifi driver for my driver was causing it and needed an upgrade. Have you tried restarting network equipment between these hosts? Modems and/or switches/gateways? I’ve seen modems starting to drop random packets after being for long periods of time so it might be worth a shot.
Restarted services and both routers plenty of times (I update everything at least monthly, this problem being present for half a year or so). This is not just a random issue, the websites affected are always the same, while the other websites that work, always work. Running up-to-date everything.
I have a firewall on the site B side, I already tried to allow all traffic between the interfaces (allows all from LAN to wg0, allow all from wg0 to LAN), did not work. No firewall on site A side.
Worth noting is that when I use OpenVPN on site B to connect to site C and redirect all traffic, everything works flawlessly, even these sites. From site B to A via wg, only partially. Both tunnels use the same interface name, so they use the same firewall rules on site B.
I thought it could be a MTU problem, but then, would it not make sense for all packets to be dropped instead of just some very specific websites? The behavior is constant and easily replicable. Websites that don’t work are duckduckgo, all stack exchanges and server faults, reddit and some others I don’t remember off the top of my head (I rarely ever go to those sites, so I never complained, but there seems to be more sites, like the download page for nixOS iso that fails TLS handshake).
The only ones who have ICMP disabled are those guys at MS, where the traffic stops responding back to tracepath or mtr. ae22-0.rwa03.vie.ntwk.msn.net
The problem is that these sites work on the router wg client, which is using the same VPN as the clients behind the router. The tracepath works on none until that over there.
I will look over the MTU on the clients and lower it, but I doubt it will change anything.
not necessarily a problem but, I’ve been on ubuntu a while and i think i want to go to just straight debian or venture into fedora - but i really like the ubuntu’s spin of gnome 3.36.
How difficult is it to replicated or is there a way to side install it.
Not sure what exactly you’re referring to here, i.e. what’s different compared to “stock” GNOME. Not to mention 3.36 like what… 3 years old? So you won’t find that in Fedora. F36 is on GNOME 42 I believe, F37 on 43.
If Ubuntu is using a custom theme you should be able to just install it from the theme store? I don’t use GNOME so not sure what the right name or place for that is.
I want to switch from PopOS to Mint 21. PopOS uses systemd-boot and Linux Mint still uses grub2. What do I need to do to prepare for the transition? I’m going to stick with Mint so ideally I’d like to switch to grub so its what mint is expecting.
Ugh, OK so… I think I asked this ages ago but didn’t get an answer and I never followed up on it. But now with 3 monitors + a TV this is getting really annoying.
I’m on Fedora KDE on X11 (can’t go Wayland for a variety of reasons), and my monitors are driving me insane. I have 3 Monitors: 2 (Gigabyte AD27QD + FI27Q) are connected via DP, 1 (second FI27Q) is connected via HDMI, and the TV (some LG OLED) is of course also HDMI.
This issue affects all 4 displays at this point. When I turn them off, everything behaves normally (-ish, see below). However when I turn them on, the displays are disconnecting for a split-second and then getting reattached (I assume this is the handshake to read the EDID).
That in itself wouldn’t be a big deal, but more often then not this rearranges the displays in either KDE or X11 or I don’t know where and it messes with the screen layout. In addition to that, due to the monitor “disconnecting”, it moves all the programs over to another desktop and sometimes it moves them back, but usually it doesn’t. So I end up rearranging my windows again.
I’d get if it was doing that when I turned the display off (because… well, it’s hard to see anything on it), but not when it’s turning it on.
Is there any solution to this other then waiting and hoping Wayland magically fixes that issue when I’m able to use it in like 5 years? Some kind of X11 configuration (like IDK a higher timeout for registering the disconnect or something), or a setting in KDE itself?
It’s getting really frustrating and I don’t get how this is even a thing with standard connectors and protocols… but I can’t be the only one with this issue, right? How are people like Wendell dealing with that when they are using like 8 Monitors…
i3 / Sway are the only two WM environments that handles multiple monitor setups in a sane way IMO.
Every screen is treated as it’s own virtual desktop, basically.
How this is not default across every Linux WM at this point boggles my mind. I understand you do not want decorations such as start menu or gnome bar on everything, well, allow for turning it on/off on a per Screen basis then, but otherwise keep the virtual desktops intact.
By treating each screen as it’s own virtual desktop it becomes trivial to assign a default VD to a certain screen. If it exists, cool, put it there. If not, hide it under the main screen if nothing else is assigned. And then have a presentation VD for things like Powerpoint and demos.
This approach is not only sane, it is easy to implement, the only thing you need to take into account is whether or not screen decorations like the Gnome sidebar or top bar is a part of the desktop and which desktop any given screen should show as default. You could even mirror the screens easily, just assign the same VD to two screens!
To answer your question though, got the same problem and annoyance, no way to solve it yet.
Has anyone run into flakyness with hitting the set critical power level not always triggering the system to power down (or sleep in my case)? Sleep itself has been working great (a welcome change) and the trigger goes off sometimes but not always. I’ve noticed this in Ubunto 20.04, MX 22.2.1 KDE, and Kubuntu 22.04.1. I tend to have music playing when it fails as well.
I looked at those briefly in the past and I don’t think those are really for me.
Maybe I just need to try them out one day, but I also don’t wanna get stuck configuring a window manager for all eternity.
Thanks for the input anyway.
That this is a common issue and just accepted as normal just blows my mind. Is no Linux dev working with more then 1 monitor and therefore not getting annoyed by this?
Well at least it’s not closed (because CONFIRMED).
One thing I forgot to mention though: The issue with the screen arangement is (for the most part anyway) related to the screen/plug mapping in the plasmashellrc, as seding around the plugs properly and then restarting plasma fixes it. It might be going deeper then that, but that is a way to fix it 90% of the time. The other 10% it doesn’t, and that’s because it actually moves around the display coordinates in the Display Config, occasionally with 2 or more monitors ending up on top of each other. Like… how does that even happen.
Anyway, I even wrote myself a .desktop file with said sed and plasma restart to make it less of a pain in the rear, but still… doesn’t always work (and that only fixes the screen arangement anyway, the window positions aren’t fixable with that).
I imagine they’ve got multiple monitors and don’t have the problem.
My work laptop with two extra monitors runs Kubuntu/X11, and doesn’t have a problem; on resuming from sleep, or switching off/on monitors, windows remain where they were.
Do you already have a Xorg configuration file, where you define monitor resolutions and positions?
Because if you don’t, try that first. It might just be enough that X always uses the same position in it’s layout.
