Ethernet plugged in but there is no internet. I have no idea what happened. I just took a normal update like I always do and after that it was all gone. WiFi connects no problem, but there is no internet. Unplugged Ethernet and replugged it back in. Nothing. I dualboot with windows, internet works fine there, so there is no hardware issue. Went into a live environment and chrooted into it and reinstalled network manager and still not a fucking thing. Not sure what these are now. I know about the lo one, but never seen the second wired connection or the virbr0. Any idea how to get my Internet back? I really don’t want to reinstall the system because of this. And btw, I even tried a hotspot from my phone and a wire tether from it and still no internet.
System is endeavour OS with KDE on Wayland.

screenshot

  • InnerScientist@lemmy.world
    10·
    14 days ago

    No one can ping 4.4.4.4, it doesn’t answer pings.

    This seems like a dns issue, check cat /etc/resolv.conf and try setting the dns server in Networkmanager to “8.8.8.8”.

      • penquin@lemm.eeOP
        21·
        14 days ago

        My resolve.conf has this only

        search lan
nameserver 192.168.... the rest of the IP address

        What do I change in here?

        • InnerScientist@lemmy.world
          3·
          14 days ago

          That seems correct, don’t change anything in there, try the command dig @<routerip> www.google.com or nslookup www.google.com <router ip> if the dig command is not found.

            • some_guy@lemmy.sdf.org
              5·
              14 days ago

              Fwiw, you don’t really need to worry about your 192.168 address. It’s local to your network. I’m also on 192.168.1.x as it’s the most common internal address scheme for routers. But there are some that use 10.0.1.x or other variations.

              We would need to know the external IP address that your ISP gives you to do anything with it. That should definitely be blocked out entirely if it appears in a screenshot or command output.

              https://en.wikipedia.org/wiki/Private_network

            • InnerScientist@lemmy.world
              3·
              14 days ago

              …that’s the valid response, does ping www.google.com work and curl www.google.com return a bunch of text?

              If ping www.google.com doesn’t work then your system isn’t using the correct dns server, though your local dns server works (as seen by the prior dig).

              If curl works then…you have a working internet connection, maybe check the browser settings for proxy or something.

              • penquin@lemm.eeOP
                14·
                14 days ago

                I’m doing another chroot and I will reinstall the whole plasma desktop to see if that works. If not, I’m nuking the fucker and starting over. Best part of Linux, these fucking random issues.

        • superkret@feddit.org
          1·
          14 days ago

          Nameserver should be the IP of your router.
          But you should check/set that with nmtui, then NetworkManager overwrites that file itself.

            • superkret@feddit.org
              2·
              14 days ago

              You only need one. Standard is to use your router IP as local nameserver.
              If your internet provider has issues with name resolutions, which happens sometimes, you can instead set 8.8.8.8 (Google’s nameserver) or 1.1.1.1 (Cloudflare’s nameserver). But then you can’t ping other devices in your local network by name, and loading websites can be a tiny bit slower.

              • penquin@lemm.eeOP
                11·
                14 days ago

                Do I put the ipv4 address in there or the ipv4 default gateway? Because I see these two and they’re not the same IP. Now, I have the ipv4 default gateway in resolv.conf

                • superkret@feddit.org
                  2·
                  14 days ago

                  On a home internet with just one router provided by your internet provider, your router is the gateway and the local nameserver.
                  So you can put the ipv4 of the router in everywhere it asks for default gateway or nameserver.

            • InnerScientist@lemmy.world
              2·
              14 days ago

              DNS turns a domain name into an IP which can then be used to send data through your router, a dns server is the server which is used to do this conversion (www.google.com turns into an IP 1.2.3.4 (that isn’t the actual IP of google)).

              There are many dns servers, normally your local devices use your router as the dns server, which forwards it to your ISP which they further transfer it over global dns servers.

              Alternatively you could use Google’s DNS server (8.8.8.8) or cloudflares DNS server (1.1.1.1) but if the one on your router works then just use it.

              nameserver is the same as DNS server

              Tldr: set the router IP as your dns server, you only need this one.

              • some_guy@lemmy.sdf.org
                2·
                14 days ago

                Tldr: set the router IP as your dns server, you only need this one.

                With a few more words: set the router to use 8.8.8.8 or 1.1.1.1 and then set your computer to use 192.168.1.1 (or whatever your router’s IP is). Hope that is clearer for anyone who needs it.

              • penquin@lemm.eeOP
                12·
                14 days ago

                I put my gateway there. Fuck, man. This is so stupid and annoying… I’m about to fucking nuke the whole fucking thing. I’m running out of patience. Why the fuck would they push a hardware update that fucks shit up like this?

      • penquin@lemm.eeOP
        12·
        14 days ago

        I set nameserver 1.1.1.1 and also 8.8.8.8 and still nothing.