Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - scline

#1
Do you have an example of the commands your running in that cron? service wireguard start/restart does not appear to correctly get traffic flowing. I see the tunnels up but traffic wont flow until I hit Apply in the UI. If there is a wg command I can cron I would be happy to simply do that :)
#2
Odd issue that has plagued this install over the past year, was hoping the most recent update would fix it but it does not.

Whenever the device reboots I have to manually log into the UI and hit "Apply" on the main WireGuard configuration page for the service to start correctly. I have attempted to uninstall and reinstall with no improvements, my next step being a complete OS rebuild that I am trying to avoid.

When I hop on the console/shell after a reboot I see the following:
root@pdx1fw1:~ # service wireguard status
Unable to access interface: Device not configured


Starting it via CLI does not work correctly, while the status/interfaces are created. Traffic is not actually passible untill I login to the UI and again hit "Apply" on the config page
root@pdx1fw1:~ # service wireguard start
[#] ifconfig wg create name wg0
[#] wg setconf wg0 /dev/stdin
[#] ifconfig wg0 inet 192.168.255.3/24 alias
[#] ifconfig wg0 mtu 1420
[#] ifconfig wg0 up
[#] route -q -n add -inet 10.2.0.0/16 -interface wg0
[#] route -q -n add -inet 10.1.0.0/16 -interface wg0
[+] Backgrounding route monitor

root@pdx1fw1:~ # service wireguard status
interface: wg0
  public key: <snip>
  private key: (hidden)
  listening port: 51280

peer: <snip>
  endpoint: <snip>:51280
  allowed ips: 10.1.0.0/16
  latest handshake: 1 minute, 8 seconds ago
  transfer: 15.31 KiB received, 852 B sent
  persistent keepalive: every 30 seconds

peer: <snip>
  endpoint: <snip>:51280
  allowed ips: 10.2.0.0/16
  latest handshake: 1 minute, 8 seconds ago
  transfer: 8.96 KiB received, 3.83 KiB sent
  persistent keepalive: every 30 seconds


CLI Start command, while it appears to look functional, does not actually pass traffic untill I hit "Apply" in the UI so I am not able to fix this with a cron. Anyone know some additional troubleshooting steps I can take before I rebuild from scratch? Remote sides are setup the same and do not have this issue.