Skip Navigation
nanook

Owner of Eskimo North

Posts 0
Comments 307
Dell is so frustrating
  • @eugenia @drascus I'm running 6.12.1, everything still works fine, so no indication of dropped support.

  • Can't access internet after wireguard uninstall
  • @anytimesoon I'm a bit at a loss then. I do have a Comcast router that is weird in that ARP only works at boot time so if I plug a new device into it, it won't route for that device unless I reboot it.

  • Can't access internet after wireguard uninstall
  • @anytimesoon With that different router, now try a traceroute 1.1.1.1, if you get a response from the first hop, 192.168.1.1, then something is wrong with the NAT on the router or your cable service or fiber or whatever it is, is not working.

  • Can't access internet after wireguard uninstall
  • Did you try to ping the router IP, 192.168.1.1 and see if it responded?

  • Can't access internet after wireguard uninstall
  • Sorry formatting is whack, Friendica does not understand tabs.

  • Can't access internet after wireguard uninstall
  • This is what mine looks like for contrast:
    0.0.0.0 50.251.249.54 0.0.0.0 UG 0 0 0 bridge0
    50.251.249.48 0.0.0.0 255.255.255.248 U 0 0 0 bridge0
    192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0

    In my case, 50.251.249.54 is my gateway and .48 my broadcast. I am static routed so no NAT.

  • Can't access internet after wireguard uninstall
  • @anytimesoon The 192.168.1.0 route looks problematic since your default is within that you should not need that route and it may be causing issues. I would try deleting that route.

  • Can't access internet after wireguard uninstall
  • @anytimesoon Assuming 192.168.1.1 is your wifi router, it looks correct. Can you ping that IP?

  • Can't access internet after wireguard uninstall
  • @anytimesoon @CameronDev It should be as both commands do more or less the same thing, the question is your default route correct and are there any other routes that might be misdirecting your data.

  • Can't access internet after wireguard uninstall
  • I would look at your interface configuration and your routing, ip addr show, netstat -nr and go from there. Also might check iptables, iptables -L -n and make sure there aren't any iptable rules blocking your access.

  • Wine 9.22 Enables Wayland Driver By Default
  • This is an application where Wayland is appropriate.

  • Btrfs should've been Wayland
  • @possiblylinux127 I agree with you, it's not, but people here keep touting it as such and that is my issue. X-forwarding works great for me, I use it daily. I use it to access servers in my hosting service from my home office. I can fire up x2go if I need a remote console but most of the time a terminal and an app is quicker. I have no issues with lag, I'm sorry for those that do but it is just not a problem for me.

  • Btrfs should've been Wayland
  • @lancalot @possiblylinux127 I tried it once, it pissed itself and corrupted the entire file system to the point where I couldn't recover, went back to ext4. Had similar experience with xfs.

  • Btrfs should've been Wayland
  • @hummus273 I am mistaken, it is only the mode setting for the X-server that is handled in the kernel. At any rate it works well for my needs.

  • Btrfs should've been Wayland
  • @hummus273 Yes actually in my case it does. The kernel has an X-server built in but ONLY for Intel graphics and I happen to have Intel graphics. Sorry if you're not familiar enough with X or the kernel to know that but that is a fact.

  • Btrfs should've been Wayland
  • @Aganim @loutr This makes sense, these people that have some irrational emotion attachment to Wayland in spite of it's lack of functionality, do not. Now, if they have a use case that makes sense to them, they're playing a game that needs 200fps, then fine, but if the use case doesn't fit then don't use it.

  • Btrfs should've been Wayland
  • @possiblylinux127 Again rdp, vnc, x2go, ONLY work for full desktops, they do not work for individual applications. If I've got a terminal session into a server and decide I want to fire up synaptic, X does that for me, Wayland doesn't and the overhead of starting an entire desktop to run a single app for a few minutes does not make sense.

  • Btrfs should've been Wayland
  • @possiblylinux127 @loutr I like to get work done, some tools are helpful to that end, Rust for example, superior to C in as much as it makes it much more difficult to make mistakes with memory allocation without resorting to the grossness of garbage collection, but when new things only detract from work flow, then yea I prefer the older things that work. When new things benefit it, Rust for example, or the latest kernels in terms of efficiency, then I use them. I don't like change for changes sake, I like change when it improves things, in my use case, Wayland does not do that.

  • Btrfs should've been Wayland
  • @hummus273 Waypipe would involve a lot of userland / kernel exchanges avoided by using the kernel based mode setting Xserver. It happens to work well with my hardware. And I don't see any noticeable latency issues and not all apps work with Wayland hence I have no motivation to change to Wayland and every motivation to avoid it. Sorry if that gets someone's panties in a wad.