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

  • Eugenia@lemmy.mlEnglish
    01·
    6 days ago

    That’s why I don’t use rolling releases (except debian-testing, which is actually stable). Because these kinds of things are bound to happen 1-5 times a year.

  • ThunderLegend@sh.itjust.worksEnglish
    0·
    7 days ago

    Hey man I have no idea if it is the same, I’m a noon, but I had issues with a kernel update recently with my Debian home server and lost Ethernet too. I couldn’t fix but I reverted the kernel update and voila my ethernet started working again. If this bothers you and like me you don’t have much knowledge years you could try that .

    • penquin@lemm.eeOP
      0·
      6 days ago

      I appreciate you. No worries. I already tried reverting the kernel. Still didn’t work. They pushed a firmware update and it fucked shit up.

      • rudyharrelson@lemmy.radio
        1·
        6 days ago

        I wanna say fwupd/lvfs manages firmware updates on Arch (and lots of other distros) these days.

        You may be able to roll back the latest firmware update with fwupdmgr. What’s the output of fwupdmgr get-devices in your terminal? Also, what is the make/model of the ethernet port that is now on the fritz? You can search for it on the website here: https://fwupd.org/ in the “search for firmware” bar at the top, then you may be able to install the old version with fwupdmgr.

  • rudyharrelson@lemmy.radio
    0·
    7 days ago

    I’m not familiar with EndeavourOS, but I’ll ask a few questions to get the troubleshooting process started:

    With the ethernet cable plugged in, can you access your local router config page (if you have one)? e.g.: 192.168.1.1. If not, what happens when you ping the router’s address in the terminal?

    If you’re able to successfully ping/access your router, can you ping a well-known IP address such as 8.8.8.8 (google DNS) or 1.1.1.1 (cloudflare DNS)?

    • penquin@lemm.eeOP
      0·
      7 days ago

      I can ping my gateway, nameserver, Google DNS 8.8.8.8, 1.1.1.1, but it freezes on 4.4.4.4. I even get really good latency, too

      • InnerScientist@lemmy.world
        0·
        7 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
            0·
            7 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
              0·
              7 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.

                • InnerScientist@lemmy.world
                  0·
                  7 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.

            • superkret@feddit.org
              0·
              7 days ago

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

                • InnerScientist@lemmy.world
                  1·
                  7 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.