Skip to main content

Posts

  A Quick Introduction to BGP BGP, or Border Gateway Protocol, was created in the late 1980s by the Internet Engineering Task Force as a replacement for Interior Gateway Protocol (IGP) and Exterior Gateway Protocol (EGP). Its purpose is to connect different autonomous systems on the Internet. The first version, BGP-1, was defined in 1989 in a document called RFC 1105. The current version, BGP-4, was defined in 1995 in another document called RFC 1771. BGP and IPv4 & IPv6 BGP, or Border Gateway Protocol, is responsible for distributing routing information for both IPv4 and IPv6 addresses. It is an exterior gateway protocol, which means that it is used to exchange routing information between different Autonomous Systems (ASes) and not within a single AS. BGP has two versions: iBGP (Internal BGP) for routers within the same AS and eBGP (External BGP) for routers in different ASes. eBGP is generally used between network Providers so that they can share or advertise routes between each
Recent posts

WordPress Image Optimization — ShortPixel

  This Article is based on a longer article Ben Davidson at  Web Review Star . WordPress Image Optimization — ShortPixel If you are running WordPress as your website platform. Then one thing that you always have to keep in mind is site speed. Site speed is linked to SEO, and if you want your blog, or Online Store to show up in Google, then speed is as important as keywords, content, backlinks etc.  There are many benefits to ensuring your site is as fast as it can be. Most people will tell you that you should use Caching plugins for WordPress, or CDN networks like  Fastly  or  Cloudflare  to ensure your website is fast. They are not wrong, but there is more to speed than just caching, and fast web hosts.  Image Opti m ization is just 1 part of that but often a part that is overlooked. Regarding Site Speed, of course, the basics are always the same Fast Web Host Only a few Plugins Fast Theme Caching and or CDN Core web technologies like HTTP/2, QUIC, Brotli, etc. will get you 80% of the

Welcome to the new home of www.joe-ma.co.za

Hi all I have moved all the content over to blogspot. in the hopes of adding more features and getting the access speed up. All the articles are here including the most popular ones like Cisco DynDNS config and Cisco Static DHCP. ALL of them are waiting for you folks to go check out. I hope these How-Tos are going to help you. Please check on the "Blog Archive" on the left side of the screen for all the articles, or check the Right side for the Labels. In the Label box you will see the tags like Cisco Dynamic DNS Rancid Tacacs+ FreeBSD etc. I will be moving the www.joe-ma.co.za domain over to blogspot in the next 2 months or so.

Configuring FreeBSD Postfix Mailscanner and Mailwatch

Configuring Mailscanner Mailwatch and Postfix for FreeBSD The Install guide is here I have split the install guide and the configuration guide as they are pretty involved and might cause confusion if they where put together. I will start off with the easier stuff like clamav and then move on to spamassassin and postfix and then finally to mailscanner and mailwatch. if you have not already read the Install Guide Which might be helpful to newcomers here is a summery of what has been installed. Apache and php - this is for the Mailwatch web frontend. Mysql - This is where mailscanner will log info and where your black and white lists will live. Mailwatch - Mailwatch is the web front end to help monitor and manage Mailscanner. Spamassassin - This is the system that checks the mail content looking for spam. Clamav - the Antivirus scanner that Mailscaner will use Mailscanner - The server that uses all of the above to keep your mail clean and spam free. Ok now that that is over: Confi

FreeBSD, Postfix, Mailscanner and Mailwatch Installation

Installing postfix, mailscanner and mailwatch on FreeBSD I have setup a number of servers using mailscanner and postfix to do antispam and antivirus checking. This particular example will show you how to set the server up as a mail gateway. i.e. all inbound and outbound mail will go via this server. You can also use the server as a pop3/imap4 server and doing so, does make life a little easier as you don't have to worry about the transport and relay_hosts files. At a later stage I will show that info too..... when I get a chance. This my seem strange but as there is quite a bit involved in installing and configuring I am splitting this into two How-To's this one, The install How-To and the configuration How-To First off its probably best to start on a new install of FreeBSD. Once you have done the initial portsnap fetch and portsnap extract Right here we go. Two things you might want to do is force your NIC to 100MB full duplex and install lsof Type in ifconfig and check if the

Logging to syslog-ng on FreeBSD

Logging Cisco devises to syslog on FreeBSD Overview What we are going to do here is get a FreeBSD server up and running with syslog-ng, so that we can log information from our Cisco devises to it. This How-To will be pretty detailed and we will be logging data from Cisco Routers Switches and Cisco PIX Firewalls. We are going to get the syslog-ng daemon to create the log files automatically and to log to a new file each day, with a date stamp in the file name. Installation This is probable the easiest part All you have to do is “cd /usr/ports/sysutils/syslog-ng” and run “make install clean” Now that the port is installed you can edit the syslog-ng startup script to change the following line from NO to YES : ${syslog_ng_enable:="NO"} : ${syslog_ng_enable:="YES"} also add syslog_ng_enable="YES" to your /etc/rc.conf file Save the file, then edit your /etc/rc.conf file and add syslog_ng_enable="YES" and also add syslogd_enable="NO" this wil

Securing PHP4

There are many things to take into account when it comes to trying to secure anything not only PHP or Apache or Postfix or anything else 1. You and your users still need to be able to use it 2. The server can be as secure as possible but a few lines of bad code can really screw up your morning. There are a few things to keep in mind when configuring the php.ini file Firstly its probably not a bad idea to chroot your apache server, there are a few very good examples on how to do this on the web Just do a search in google or something in your php.ini file add the following safe_mode = On safe_mode_gid = Off expose_php = Off register_globals = Off display_errors = Off log_errors = On error_log = "filename" safe_mode = On By switching on the safe_mode, you have just made your server probably twice as secure as it was before. Safe mode will ensure that only the owner of the file or script is able to read or execute that file or script Here is an example -rw-rw-r-- 1 joeuser j