OpenWISP Firmware (OWF as short) is a set of scripts (shell and web cgi) that sits on top of OpenWrt. It provides a daemon for retrieving an OpenWRT configuration of the following components from a OpenWISP Manager instance:
- layer 2 traffic shaping
- openvpn (layer 2, tap)
- custom shell script
OpenWISP Firmware also provides a web GUI for:
- configuring basic network parameters
- configuring basic OpenWISP server settings
- performing a set of test to spot and resolve most common problems that may prevent OWF to work correctly
OpenWISP Firmware currently works on the last OpenWrt release and we are working to keep it up to date with OpenWrt edge development.
How to install¶
Please see the [[Installation]]
OpenWISP Firmware FAQ¶
- Where access point configuration are stored?
- Configuration are stored in “private” folder in your owm installation as gzipped tarball
- How firmware can recognize configuration changes?
- Thanks to an MD5 sum between his tarball and the tarball stored in OWM
- Which configuration handles OWF itself and wich one will be pushed by OWM?
A. OWF Handles all access point from the boot to the configuration and so on until poweroff, the only configuration that OWM will push into the access point are network related both wired or wireless.
- And what about l2vpn_server?
A. A Layer 2 VPN Server is useful to encapsulate traffic between your device, connected to an access point, and pubblic network, so we can provide an ad-hoc configuration for you all configuration will be stored in the “private/l2vpn_server” folder in your owm installation.
- How VPN certificated are renewed?
A. Setup VPN will never expire, but l2vpn will expires, when certificate will be renewed will be sent to te AP’s trough configuration service.