Networking and System Administration

Installation of NFS on server Considering how powerful NFS is and the flexibility it gives you it is amazingly simple to set up. I expected it to be on a par with setting up Samba which can be a complete nightmare. Typically when setting up Samba one would use Swat or another configuration tool. With NFS set us is as easy as entering the paths you want exported into /etc/exports and making sure the correct packages are installed. There are two implementations of NFS one runs in kernel space (nfs-kernel-server) the other in user space (nfs-user-server). The kernel space implementation is faster and more stable but if something goes wrong it could bring your box down. In reality the kernel space NFS implementation very rarely fails. I have been running it for years (and on at least one occasion for 150 days straight) and have had it fail only a couple of times. The times it did fail it simply needed restarting. In fact the only way I have even managed to get it to make a noise is when...

Step 1:Install the subversion apt-get install subversion libapache2-svn Step 2: Create the repository svnadmin create /svn Configuration Edit the directory /etc/apache2/mods-enabled/dav_svn.conf # Uncomment this to enable the repository, DAV svn # Set this to the path to your repository SVNPath /svn # Uncomment the following 3 lines to enable Basic Authentication AuthType Basic AuthName “Subversion Repository” AuthUserFile /etc/apache2/dav_svn.passwd Require valid-user Save and exit the file Creation of user htpasswd -cm /etc/apache2/dav_svn.passwd imran New password: Re-type new password: Adding password for user imran Enable ssl (if required) #a2enmod ssl This will enable the ssl if you have problem to set it. Migration Export by :Dumping the existing repository root@jupiter:/svn# svnadmin dump svn > reposdump.dmp Import by: root@saturn:/srv# svnadmin load srv-jupiter

After installing the IPcop got the following error messages When running update the Error is: HTTP::Response=HASH(0x82a3c14)->code registered md5 When running download the Error is: HTTP::Response=HASH(0x82a3c68)->code The reason is that now snort.org publish rules now on current branch that are no more compatible with snort-2.6.1.5 We have manually add the current branch, to - date it is 2. You can find on snort if you have your account on snort.org under My Account-->My Oinkcodes along with the code (You must have account at snort to access code and use snort in IPCOP). Here is a solution, it is a manual fixation in the code. Open the /usr/local/bin/snortrules.pl in and editor. root@firewall:/etc/snort # nano /usr/local/bin/snortrules.pl Change the value to 2.8 at line no 55. my $rulesbranch= "2.8" ; # version should match snort branch version Save the change. Remember you must have to add the oink code in IPCOP--> Services-->INTRUSION DETECTION. Save-Appl...