Jump to content

[6.12.2] Wireguard disables itself after 1 second

By OmegaXis

· 874 views
  • Solved
  • Minor

Previous issue

[6.12.1] Wireguard deactivates itself after about 1 minute. - Stable Releases - Unraid

 

All was good for a bit on 6.12.2, until yesterday.  Wireguard now disables itself even faster.

 

So far I have tried making small changes again (NAT and such) all previous troubleshooting can be seen in previous post.

 

New log posted.

 

network config is the same as before.

 

 

chipshop-diagnostics-20230706-1021.zip

    • User Feedback

    Recommended Comments

    Rookie

    OmegaXis

    Members

    Even setting up a brand new wireguard connection is resulting in immediate failures,

  • Quote
    • Veteran

    bonienl

    Community Developer

    The wireguard log shows a duplicate network address in your wg0 configuration and it doesn't look complete

     

    wg-quick up wg0 (autostart)
    [#] ip link add wg0 type wireguard
    [#] wg setconf wg0 /dev/fd/63
    [#] ip -4 address add 192.168.126.1 dev wg0
    [#] ip link set mtu 1420 up dev wg0
    [#] ip -4 route add 192.168.126.4/32 dev wg0
    [#] ip -4 route add 192.168.126.3/32 dev wg0
    [#] ip -4 route add 192.168.126.2/32 dev wg0
    [#] ip -4 route add 192.168.128.0/24 dev wg0
    RTNETLINK answers: File exists
    [#] ip link delete dev wg0

     

    Can you delete the wg0 tunnel and re-create?

     

    wg1 is correct and has the expected entries

     

    wg-quick up wg1 (autostart)
    [#] ip link add wg1 type wireguard
    [#] wg setconf wg1 /dev/fd/63
    [#] ip -4 address add 10.253.1.1 dev wg1
    [#] ip link set mtu 1420 up dev wg1
    [#] ip -4 route add 10.253.1.2/32 dev wg1
    [#] logger -t wireguard 'Tunnel WireGuard-wg1 started';/usr/local/emhttp/webGui/scripts/update_services
    [#] iptables -t nat -A POSTROUTING -s 10.253.1.0/24 -o br0 -j MASQUERADE
    [#] ip -4 route flush table 201
    [#] ip -4 route add default via 10.253.1.1 dev wg1 table 201
    [#] ip -4 route add 192.168.128.0/24 via 192.168.128.1 dev br0 table 201

     

  • Quote
    • Rookie

    OmegaXis

    Members

    I think what happened here is a mis understanding of how the peer allowd IP's work, i believed that you needed to add the ip address of the network here as well to make the connections work to the other servers on the network.

     

    seems to be resolved.

  • Quote

    • Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...