After Fortigate upgrade v6.4 > v7.0.1 (or later) the S2S-dialup VPNs did not work anymore. Tunnel negotiation is successful and phase 1 and 2 get up. Traffic from spoke is routed into the tunnel, but is seems that the traffic is not received by the hub.
«Fortigate S2S-Dialup VPN – Traffic does not run through IPsec tunnel anymore» weiterlesen We have created a combined CheatSheet for the FortiAnalyzer and FortiManager OS version 7.0. We have divided sections into FortiAnalyzer Logging, FortiAnalyzer Reporting and FortiManager to find the needed commands faster.
We hope that this will contribute to quick solutions of existing problems.
256 total views
Update – 10. November 2021: It seems that the server «45.75.200.89» is not in use anymore – it is «not reachable» at the moment. Please use «194.69.172.53» instead.
Blogpost – 3. November 2020:
From time to time customers noticed that the Fortigate cannot reach the Fortiguard Servers anymore.
This is displayed in the Dashboard or users are complaining that the Webfilter or DNS Filter Service is not working anymore.
«FortiGuard Servers are not reachable» weiterlesen5,633 total views
We have adapted our CheatSheet for FortiOS version 7.0 and added new commands. The Cheat Sheet is divided into different sections. Depending on the topic, you can find the necessary commands to display more information or find problems.
We hope that this will contribute to quick solutions of existing problems.
546 total views
Today WatchGuard launched a new page where you can see the status of WatchGuard Cloud Services.
https://status.watchguard.com/
For each region, you’ll find the current status separated by products and the major features that WatchGuard provides. Every line has a simple status indicator to communicate its condition:
«WatchGuard announced new «Service Status Page»» weiterlesen179 total views
For some reasons Fortigates are are not able to load the FortiGuard DDNS server list. Therefore you are not able to configure DynDNS on your Fortigate anymore. In the WebUI you will see following error message under Network > DNS > FortiGuard DDNS and you are not able to list any server with the drop-down menu.
«Error message: «Unable to load FortiGuard DDNS server list»» weiterlesen420 total views, 1 views today
Netzwerk & Security Administratoren kennen die Problematik. Um Zugriff auf eine serielle Konsole zu bekommen, benötigt es einen Adapter, da kaum mehr ein Notebook einen alten DB9 (DE-9) Anschluss hat. Kein Hersteller liefert aber ein USB Konsolenkabel direkt auf RJ45 Ports, welche heute bei praktisch allen Netzwerk & Security Devices der Standard sind.
Die nervigen Adapter und die teilweise mühsame Treiber Unterstützung hat uns bewogen, ein eigenes Boll Konsolen Kabel entwickeln zu lassen. Folgende Bilder illustrieren das schön:
Konsolen Access früher:
Just like for FortiGate releases we created and publish here a collection of CLI commands for troubleshooting the FortiAnalyzer appliances.
FortiAnalyzer Version 6.4
During the lifecycle of firewalls, they are often replaced with a newer model, but you would like to keep the configuration. In this case, there are several possibilities, which we present in this blog post:
1. FortiConverter Service
2. FortiConverter Tool
3. Partial Config Transfer
4. Full Config Transfer
Den deutschen Artikel dazu finden Sie hier: So übertragen Sie eine FortiGate Konfiguration auf ein neueres Modell
«How to transfer a FortiGate configuration to a newer model» weiterlesen
Öfters sehen wir Fragen oder Probleme zur korrekten Subnettierung von Netzen. Mit dem folgenden Raster kann man schnell und einfach die richtige Anzahl Host oder die Subnetzmaske herausfinden.
Die erste Adresse des Subnetz nennt man Netzadresse. Diese kann nicht für Hosts verwendet werden (Bsp. 192.168.10.0 bei einem Subnetz von 255.255.255.0 oder /24)
Ebenso die letzte Adresse des Subnetz. Diese ist die Broadcast Adresse und steht Clients nicht zur Verfügung (Bsp. 192.168.10.255 bei einem Subnetz von 255.255.255.0 oder /24)
Die verbleibenden IP Adressen können von Hosts genutzt werden (Anzahl Hosts in der Tabelle, also 256-2= 254 bei einem Subnetz von 255.255.255.0 oder /24)
«Netzwerk Subnettierung» weiterlesen
