Can't access internet after wireguard uninstall
from anytimesoon@feddit.uk to linux@lemmy.ml on 24 Nov 10:13
https://feddit.uk/post/20395369

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?

#linux

threaded - newest

nanook@friendica.eskimo.com on 24 Nov 10:16 next collapse

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.uk on 24 Nov 12:07 collapse

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

superkret@feddit.org on 24 Nov 10:30 next collapse

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.

anytimesoon@feddit.uk on 24 Nov 12:07 collapse

All I got was wget, so this is clean

CameronDev@programming.dev on 24 Nov 11:28 next collapse

Give the output of route, maybe there is a left over route.

nanook@friendica.eskimo.com on 24 Nov 11:31 collapse

@CameronDev @anytimesoon This is why I suggested netstat -nr

CameronDev@programming.dev on 24 Nov 11:36 collapse

Yup, didn’t read your comment properly, but that will also work.

anytimesoon@feddit.uk on 24 Nov 12:08 collapse

The output was pretty much the same from this as from netstat -nr

I would share it here, but I can’t access the internet from that machine

nanook@friendica.eskimo.com on 24 Nov 12:11 next collapse

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

anytimesoon@feddit.uk on 24 Nov 12:48 collapse

I’m not entirely sure which of the list is the default route is, but absolutely see my WiFi router on the list. Took a picture as recommended by @CameronDev

<img alt="1000005757" src="https://feddit.uk/pictrs/image/df027372-729f-4a04-ba80-976b29e317b2.webp">

nanook@friendica.eskimo.com on 24 Nov 12:55 next collapse

@anytimesoon Assuming 192.168.1.1 is your wifi router, it looks correct. Can you ping that IP?

anytimesoon@feddit.uk on 24 Nov 13:15 collapse

Nope. Destination host is unreachable when pinging

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

[deleted] on 24 Nov 12:57 collapse

.

CameronDev@programming.dev on 24 Nov 12:28 collapse

~~Take a photo of the output? First few lines are most important, but ideally all would be good. ~~

Edit: actually, dont want to crowd the kitchen, good luck!

nanook@friendica.eskimo.com on 24 Nov 12:59 next collapse

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 on 24 Nov 12:59 collapse

Sorry formatting is whack, Friendica does not understand tabs.

anytimesoon@feddit.uk on 24 Nov 13:23 next collapse

So that looks similar to what I have. Wonder why it’s not working

CameronDev@programming.dev on 24 Nov 23:59 collapse

Looks like you need to use [code] on friendica?

wiki.friendi.ca/docs/bbcode#code_blocks

nanook@friendica.eskimo.com on 24 Nov 13:33 next collapse

Did you try to ping the router IP, 192.168.1.1 and see if it responded?

anytimesoon@feddit.uk on 24 Nov 13:46 collapse

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 on 24 Nov 13:58 collapse

@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.uk on 24 Nov 14:09 collapse

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 on 24 Nov 14:13 collapse

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

anytimesoon@feddit.uk on 24 Nov 14:37 collapse

No worries. Thanks for your help! I’ll post here if/when I find a solution

bbbhltz@beehaw.org on 24 Nov 20:03 collapse

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.