Architecture Issues and Solutions

Rsync is not automated

To get around this, it would be best to implement Rsync as a cron job that runs from a script I create or find online that I can customize. Dropping this script into /etc/cron.hourly, cron.daily, or cron.weekly would be ideal

VRRP

VRRP compared to the Hot Standby Routing Protocol (HSRP) is (according to routerfreak.com) lesser known by network engineers. This could be an issue if this was an organization actively hiring. However, another issue is that with VRRP, there is only one master router while all others listen. This gives a bit less flexibility, while HSRP has a master and standby, with other routers listening in the case of both going down. While in this environment it would be overkill, this would be likely a better protocol to use in a larger organization using multiple routers.

PNetworking Issues with OPT

For my latest project, I scraped using the entire OPT network because of issues I was having with NAT. Once completed, I did a post-mortem to troubleshoot the OPT network and found there was a lack of port forwarding and my firewall and NAT rules have become incredibly messy. This has always been a larger issue of mine since it becomes harder to keep track. Going through and properly labeling my rules so I do not become lost and waste time messing with my firewall is now a priority as well as keeping my network map updated and creating a summary of my environment so far. This will also help with reaching out to others I know for advice since I often explain things and realize even I have no idea what is going on