AZTCOFW / DOCUMENTATION
General
Configuration guides, troubleshooting and practical advice for AZTCOFW.
Articles
9 resultsAZTCOFW Documentation
Download AZTCO FW PDF Documentation By Click Here
Default Configurations
WAN IP: DHCP LAN: 192.168.2.254/24 WebConfig: Protocol: HTTPS Port:5687 User Name: admin Password: aztco
Design Considerations
One of the main considerations when choosing a WireGuard implementation layout is whether to use one tunnel with many peers, or one tunnel per peer. Routing to WireGuard Peers WireGuard uses what it calls “Cryptokey Rout
Mobile IPsec
Mobile IPsec allows creation of a so-called “Road Warrior” style VPN, named after the variable nature of anyone who is not in the office that needs to connect back to the main network. It can be a sales person using Wi-F
webConfigurator default Certificate expiring
In case your default webConfigurator certificate is expiring soon or as below still expired some time ago, this is not really an critical issue and will not affect AZTCO-FW from functioning as before. This certificate is
WireGuard
WireGuard Settings Design Considerations WireGuard Limitations Configure a WireGuard Tunnel Assign a WireGuard Interface WireGuard and Rules / NAT WireGuard Routing WireGuard Overview WireGuard is a new VPN Layer 3 proto
WireGuard and Rules / NAT
There are multiple concerns with firewall rules for WireGuard. External Traffic Firewall rules must pass traffic on WAN to the WireGuard Listen Port for a tunnel if remote WireGuard peers will initiate connections to thi
WireGuard Limitations
There are a few limitations of the WireGuard implementation in FreeBSD which must be taken into consideration when deciding if WireGuard fits the needs of a use case. Response Sourcing WireGuard does not bind itself to a
WireGuard Routing
WireGuard can work with both static and dynamic routing, depending on the environment. Static Routing Several components go into static routing for WireGuard peer networks. Automatic The GUI has a mechanism to automatica