Feature Request: Wireguard

Completed

Comments

33 comments

  • Avatar
    Firewalla

    Sorry, the blue and red are really tight on memory. We have seen a bit more "no memory" reboots after the 1.972 release, so unlikely we will be adding any features that may increase memory usage. 

    As of the purple, it is highly possible we will do an early beta, or maybe even release the units in smaller chunks, that may allow us to deliver as early as October or early November. Watch out for beta requests. 

    0
    Comment actions Permalink
  • Avatar
    David Koppenhofer

    Ah, I understand about the memory thing. I thought WireGuard was supposed to be lighter on resources, my mistake.

    On the topic of reboots / restarts (sorry for hijacking the thread): I get a notification when the Firewalla service awakens, but see no log off it in my alarms. It'd be nice to see.

    Good (potential) news about the Purple. I'm keeping my eyes open for any updates. 👍

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    @David

    The problem is not WireGuard ... WireGuard is fairly light. 

    The issue is the rest of the system. Firewalla resource allocation is per network. For example, on the blue today, you have the main network and an OpenVPN network; and adding a WireGuard network ... will increase the resource usage due to a new network that will need to be tracked. (These resources are primarily cache and data structures to track flows and break/assemble traffic)

    Due to how the software was designed, it is also really difficult to remove OpenVPN and only run WireGuard ...

     

    2
    Comment actions Permalink

Please sign in to leave a comment.