[SOLVED] Enabling Wireguard disables other interfaces

[blaze8218]

Updated to 22.1.1_3

While Wireguard is enabled it prevents other interfaces from accessing the internet.

In order for interfaces to access the internet i have to have wireguard disabled for it to work. I removed wireguard rebooted and then reinstalled while re-configuring everything as soon as i enable wireguard it halts everything.

Before 22.1.1_3 everything worked.
After handshake no internet.

If i need to provide logs and things i will need help to where and what i need to provide.

Edit: Solved.

I went through the documentation again and re-added NAT and Interface Rules. I just deleted everything and set them again and it worked there was no difference from them before. No idea why it was causing problems in the first place but im glad i was able to get it to work.

[mimugmail]

/usr/local/etc/rc.d/wireguard restart

Via console please

[blaze8218]

• rm -f /var/run/wireguard/wg0.sock
  
• ifconfig wg create name wg0
  [!] Missing WireGuard kernel support (ifconfig: SIOCIFCREATE2: Invalid argument). Falling back to slow userspace implementation.
  
• wireguard-go wg0
  ┌──────────────────────────────────────────────────────┐
  │                                                      │
  │   Running wireguard-go is not required because this  │
  │   kernel has first class support for WireGuard. For  │
  │   information on installing the kernel module,       │
  │   please visit:                                      │
  │         https://www.wireguard.com/install/           │
  │                                                      │
  └──────────────────────────────────────────────────────┘
  
• wg setconf wg0 /dev/stdin
  
• ifconfig wg0 inet 10.10.10.1/24 alias
  
• ifconfig wg0 mtu 1420
  
• ifconfig wg0 up
  
• route -q -n add -inet 10.10.10.2/32 -interface wg0
  
• route -q -n add -inet 0.0.0.0/1 -interface wg0
  
• route -q -n add -inet 128.0.0.0/1 -interface wg0
  
• Backgrounding route monitor

[mimugmail]

So this setup enforces default gateway via tunnel. Just check your settings of endpoint.