Skip to content
DnsLister Forum

Where domain hunters compare notes

I am in 10th I just messed up my mac book internet 😭

My hands are still shaking I feel like I wanna scream…
I genuinely thought I had permanently destroyed my MacBook, and if my parents found out, I was never going to be allowed to touch a computer until college.

Context: I am currently in 10tha and building a custom desktop dual-engine web browser (RAW Browser) with an integrated dual-mode VPN.
–1, Browser only
— 2. Full device
First I made it work with wire guard and pi hole on microsoft azure VPS server which I got access form github developer pack 13 to 17 one. so no credit card linked.

How it works I am using socks 5 tunnel to route my traffic.

Where I messed up
I was changing wiregard to VLESS REALITY and once it was installed I restarted the mac and internet was not working.

The Panic: I had completely forgotten that when I originally installed WireGuard, I set up a macOS Launch Daemon (com.raw.wireguard.plist) to auto-connect the VPN in the background every time the Mac booted up.

Because WireGuard operates at the OS kernel level, it forcefully hijacked the system's entire routing table using AllowedIPs = 0.0.0.0/0. When my Mac booted up, the hidden daemon triggered. But because my remote Azure server was now dead my Mac started aggressively throwing 100% of my internet traffic into a dead digital black hole.

I logged in to find my internet completely severed. In a panic, I tried to run sudo wg-quick up ./wg0.conf to "fix" it, which only locked the dead static routes in further. I then tried to gracefully kill the tunnel using wg-quick down, but because I had already deleted the config files, the command failed.

My Mac was permanently trapped with a dead static route.

How I fixed: [with internet no ai was here to save me 😭]

  1. I forcefully wiped the entire macOS BSD kernel routing table: sudo route flush
  2. I did a hard hardware bounce of my Wi-Fi interface from the terminal to force a new DHCP lease: sudo ifconfig en0 down && sleep 2 && sudo ifconfig en0 up
  3. I checked ping 8.8.8.8—it worked! But websites still wouldn't load because WireGuard had hijacked my DNS resolvers.
  4. I forcefully rebuilt the DNS stack using Apple's network setup utility: sudo networksetup -setdnsservers "Wi-Fi" 8.8.8.8 1.1.1.1

Suddenly, the internet sprang back to life.

This was really a terrifying experience to me.

Source: r/it · by /u/Visible_Prize5715

Leave a Reply

Your email address will not be published. Required fields are marked *