KDOG.how

In this blog post, I would like to share how easy it is to move the failover routing decision making  process from your internet edge routers to your awesome  Palo Alto Firewall(s). Of course they are situations where it can be  useful, especially when a company decides  to use dual basic  broadband connections for a super small micro remote office where the service provider only hands you static point to point public IPs. Lets get down  straight to the configuration  (Woof) : Policies > Policy Based Forwarding > Add  As per any firewall policy, all policies are read top down the 1st policy should be for your most preferred link and your backup link policy must be configured just after it. Name: Give your policy a name Tags :  Optional attribute to quickly find stuff when troubleshooting Zone/Interface : Incoming source packet zone(s) Address : Is this for a specific IP / if using PAT then (any) should suffice Destina...

Here's a quick and fairly reliable syslog collector that we have used. OS: Ubuntu 16.04.2 CPU: Dual Core RAM: 4GB or 8GB Software Package: syslog-ng Goal: Collect log from multiple sources and place them into logical files and folder. With that said, let get started... First, disable rsyslog so that it can not interfere with syslog-ng service and reboot the server. Issue the following command to disable the service from start up.  #sudo systemctl disable rsyslog Upon reboot, install syslog-ng and enable the service. #sudo apt-get install syslog-ng #sudo systemctl enable syslog-ng Create a new configuration file for syslog-ng service.  #sudo nano /etc/syslog-ng/conf.d/syslog.conf ------------------------------------------------------------- options { chain_hostnames(no); create_dirs(yes); dir_perm(0755); dns_cache(yes); keep_hostname(yes); log_fifo_size(2048); log_msg_size(8192); perm(0644); time_reopen(10); use_dns(yes); use_f...