rusmanis

.CER to .CRT openssl x509 -inform PEM -in <filepath>/certificate.cert -out certificate.crt sudo mkdir /usr/local/share/ca-certificates/new-crt sudo cp new-crt.crt /usr/local/share/ca-certificates/new-crt sudo update-ca-certificates

$ curl http://ifconfig.me $ curl http://ipecho.net/plain $ curl ifconfig.co $ curl http://www.icanhazip.com $ curl http://indent.me $ curl http://bot.whatismyipaddress.com $ curl https://diagnostic.opendns.com/myip $ curl http://checkip.amazonaws.com $ curl http://whatismyip.akamai.com Text from  Link Picture from  Link

https://kb.fortinet.com/kb/documentLink.do?externalID=FD33101 The ESP packet invalid error is due to an encryption key mismatch after a VPN tunnel has been established. When an IPSec VPN tunnel is up, but traffic is not able to pass through the tunnel, Wireshark (or an equivalent program) can be used to determine whether there is an encryption mismatch. A mismatch could occur for many reasons, one of the most common is the instability of an ISP link (ADSL, Cable), or it could effectively be any device in the physical connection. The following information is required to troubleshoot the problem. 1) Take a packet sniffer trace on both FortiGates. 2) Run the "diag vpn tunnel list” command a few times on both FortiGates when generating traffic that will pass through the tunnel. In the following example, the error message was seen on the recipient FortiGate: date=2010-12-28 time=18:19:35 devname=Kosad_VPN device_id=FG300B3910600118 log_id=0101037132 type=event subtype=ipsec pri=critica...

Zabbix Proxy RAM config Content is copyed from  ZNIL.NET 2.1  Install Raspbian You download NOOBS: 5  Configure the Zabbix proxy We open the configuration file nano /etc/zabbix/zabbix_proxy.conf and adjust at least the following lines: Server = IP or DNS name of the Zabbix server to be reported to # Hostname -> under this name we also have to create the proxy on the main server! Hostname = zabbixproxy # Increase command timeout. This is how long the proxy waits for replies from scripts, checks and agents Timeout = 30 # New 3.4 feature - RemoteCommands now also work behind proxies EnableRemoteCommands = 1 LogRemoteCommands = 1 # Database and log in the RAM disk (do not change the lines if not desired) LogFile = / var / ramdisk / zabbix_proxy.log LogFileSize = 4 DBName = / var / ramdisk / zabbixproxy.db https://www.raspberrypi.org/downloads/noobs/ I recommend the normal variant, not the Lite - especially if you are on the go in company networks.  Noobs ...