Hello,

I had a working wireguard peer on my laptop, which I didn’t want anymore, so I decided to uninstall wireguard. All was well until I restarted the laptop and now I can’t access the internet anymore.

I think it’s because of some config left over from wireguard, but I’m not sure how to fix it.

Running pop os 22.04.

Any advice?

  • superkret@feddit.org
    link
    fedilink
    arrow-up
    13
    ·
    29 days ago

    sudo traceroute 1.1.1.1

    can show you how far your connection request gets (whether it’s blocked by your pc, your router, or somewhere on the internet).
    You may have to install it first.

    sudo find /etc -name *wg*
    find ~ -name *wg*

    can help find left-over config files.

  • nanook@friendica.eskimo.com
    link
    fedilink
    arrow-up
    4
    ·
    29 days ago

    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.

  • nanook@friendica.eskimo.com
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    29 days ago

    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.

    • anytimesoon@feddit.ukOP
      link
      fedilink
      arrow-up
      1
      ·
      29 days ago

      IP tables have no rules, but netstat is showing traces of WG. Two of the interface names are the same as WG config name I used

    • anytimesoon@feddit.ukOP
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      29 days ago

      I did, but no response

      I changed to a different router and can at least ping that now, but still no internet

      • nanook@friendica.eskimo.com
        link
        fedilink
        arrow-up
        3
        ·
        29 days ago

        @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.

        • anytimesoon@feddit.ukOP
          link
          fedilink
          arrow-up
          3
          arrow-down
          1
          ·
          29 days ago

          Unlikely to be something wrong with that, tbh. Everything else on that network has internet access. The issue is limited to the laptop

          • nanook@friendica.eskimo.com
            link
            fedilink
            arrow-up
            2
            ·
            29 days ago

            @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.

  • bbbhltz@beehaw.org
    link
    fedilink
    arrow-up
    1
    ·
    29 days ago

    Hi

    Did you remove wireguard the meta package or everything wireguard installed? I don’t know Pop but other distros install additional tools and configs like wireguard-dkms.

    Also, if possible, after completely purging every wg you could try booting into a previous kernel on your system to see if that changes anything.