Posts Tagged ‘Mac OS X 10.6’

How-To Install or Update Mac OS X Snow Leopard 10.6.7 on the Asus Eee PC 1005HA Netbook

Wednesday, March 23rd, 2011

Few days ago Apple released the latest update for Mac OS X Snow Leopard 10.6.7 .
Here is the tutorial on how to install or update Mac OS X Snow Leopard 10.6.7 on the Asus Eee PC 1005HA Netbook.

Prerequisites

Yes, you have no alluciantions: the legacy kernel we gonna use is the same prepared for Mac OS X 10.6.6, I tried and it works fine with 10.6.7 on the Asus EeePC 1005HA. I don’t know if it works on other hackintosh systems and netbooks. Please comment about your experience.

Step 1

Follow the instruction of my previous post:

How-To install Mac OS X Snow Leopard 10.6.6 on the Asus Eee PC 1005HA Netbook

following that how-to you can skip the part that let you update from Mac OS X 10.6.0 to Mac OS X 10.6.6 an substituite it with the following content of Step 2.

Step 2 (Upgrade to Mac OS X Snow Leopard 10.6.7)

  1. Copy MacOSXUpdCombo10.6.7.dmg in the USB stick.
  2. Uncompress legacy_kernel-Mac_OS_X_10.6.6.tgz and to legacy_kernel-Mac_OS_X_10.6.6.pkg and copy it on the USB stick.
  3. Insert the USB Stick on the Netbook then mount and run the MacOSXUpdCombo10.6.6.dmg.
  4. When the installation is finished it will ask to restart:
    DO NOT RESTART THE SYSTEM YET!!
  5. Install ‘legacy_kernel-Mac_OS_X_10.6.6.pkg’.
    This install an older version of the kernel that is still compatible with the unficcial extensions we previously installed before the upgrade.
  6. Again, substitute the Extensions for the misbehaving devices:
    1. Copy ‘SleepEnabler.kext’ to ‘/Extra/Extensions/’.
      This fix the hibernation/sleep feature.
    2. Copy again ‘~/Desktop/SnowLeopardAsus/Extra/IO80211Family.kext’ to ‘/Extra/Extensions/’ folder.
      This makes the system to recognize and install the Wi-Fi card.
    3. Copy again ‘~/Desktop/SnowLeopardAsus/Kext/AppleIntelGMA950.kext’ to ‘/System/Library/Extensions/’.
    1. Copy again ‘~/Desktop/SnowLeopardAsus/Kext/AppleIntelIntegratedFramebuffer.kext’ to ‘/System/Library/Extensions/’.
      This fixes the video card and add the option to choose 1024×600 resolution.
  7. Now, most important, fire the command ‘fixkext’ with root privileges or using sudo:
    $ sudo fixkext
  8. VERY IMPORTANT: Run Disk Utility and Repair Disk Permisions
    Without this operation your system will reveal really unstable!!!
  9. Now you can reboot the system

Now go back to:

How-To install Mac OS X Snow Leopard 10.6.6 on the Asus Eee PC 1005HA Netbook

and read the last two sections: What still doesn’t work and Last Adjustments

Mac OS X Server 10.6 Open Directory Replica: “Kerberos is: Stopped”

Friday, March 18th, 2011

It is common that the configuration process of a Mac OS X Snow Leopard Server 10.6 as an Open Directory Replica for your Open Directory Master comes with some problematic issues: it’s very common that the Kerberos service is not initialized properly and will appear in the ‘Server Admin’ Open Directory’s Overview panel as ‘Kerberos is: Stopped‘.

Googoling about this problem I found that is a fault in the DNS name resolution the most common reason that breaks the configuration of the kerberos service preventing the Open Directory Replica server to be recognized and associated with the proper FQDN (Fully Qualified Domain Name).

The fix to this problem is not complicated but will force us to carefully perform these operations:

  1. First things first, although this is a recommended option for local domain naming, make sure that your domain name  is NOT ending in ‘.local.
    In Mac OS X by default the ‘.local’ domains are resolved by the Bonjour service, with priority over the DNS service.
    I recommend to choose a non public domain name like ‘.private’, ‘.lcl’, ‘.my’, ‘.office’…. and so on.
  2. After that, make sure your DNS is PERFECTLY configured to serve FQDN names (i.e. replica.mynetwork.private.) and that one of this name is fully matching to the replica’s hostname(with the exception of the tail ‘.’ ).
  3. Also check the DHCP service, if activated, to be delivering the correct search domain and the IP address of the DNS server able to resolve the name of your Open Directory Master and Replica servers.
  4. Adjust the Replica server’s hostname accordingly to the DNS settings.You can modify the hostname of your replica server with the ‘scutil’ command:
    # scutil --set HostName replica.mynetwork.private
  5. Now decommission the replica server to a standalone directory using the Open Directory Assistant to change the server’s role.

Now the most important operations are done.
Now I recommend a reboot of the system and a double-check of the DNS and hostname configuration using the following commands:

# hostname

The ‘hostname’ command will show the hostname that should appear like the FQDN configured in the DNS service.

# changeip --checkhostname

The ‘changeip’ command will perform a more accurate check on the hostname, using the system calls used by the other system processes and application.

# nslookup replica.mynetwork.private

The ‘nslookup’ command will check that the DNS server is returning the appropriate IP for the requested domain name.

Now it’s time to re-configure the server as a Open Directory Replica, you can use again the Open Directory Assistant. Provide the requested information and when the process is terminated, if you’re lucky enough, the problem will be fixed and the ‘Server Admin’ will show ‘Kerberos is: running.

Unfortunately I’ve not been so lucky when I encountered this problem my first time: for my replica server the Kerberos service was still in ‘Stopped’ status.

After a couple of headaches and a lot of wasted time I figured out that one of the main Kerberos’ configuration files ‘/Library/Preferences/edu.mit.Kerberos’ was missing. This was proof that for some reason the ‘kdcsetup’ process hasn’t been executed.

To fix this issue it is necessary to perform the manual procedure to configure and initialize the kerberos process that actually is the last portion of the manual procedure to join a Replica to an existing Open Directory domain, consisting of:

# /usr/sbin/kdcsetup -c /LDAPv3/127.0.0.1 -a diradmin -p -v 1

This command will create the file /Library/Preferences/edu.mit.Kerberos.

# /usr/sbin/kdb5_util -r

The ‘kdb5_util’ will load information from the initial.dump file from the previous step into the REALM.

# kdcsetup -e

The ‘kdcsetup’ command will enable kdcmond and kadmind in the configuration for launchd.

Now the Kerberos services should have been started on the replica server.

Reboot the system to make sure it’s started automatically at the system initialization.

How-To install Mac OS X Snow Leopard 10.6.6 on the Asus Eee PC 1005HA Netbook

Monday, February 21st, 2011

How-To Install or Update Mac OS X Snow Leopard 10.6.7 on the Asus Eee PC 1005HA Netbook is now available:
https://www.marcomc.com/index.php/2011/03/how-to-install-or-update-mac-os-x-snow-leopard-10-6-7-on-the-asus-1005ha-netbook/

This is a step-by-step procedure to install Mac OS X Snow Leopard 10.6.6 on the Asus Eee PC 1005HA Netbook having everything working 100%.

Resources

Prerequisites

For British users only

Installer preparation

  1. Use ‘Disk Utility’ to dump the  Mac OS X 10.6.0 Installation DVD on the 8GB USB stick.
  2. Run the MobUSB package and choose as intall destionation the newly created partition on the USB stick (that will probably bring the name of “Mac OS X Snow Leopard 10.6 Retail”, but the name is not importat).
    DO NOT INSTALL IT ON YOUR SYSTEM’S PARTITION!!
  3. Copy the file ‘SnowLeopardAsus.zip’ and ‘SleepEnabler.kext’ into the root of the USB stick

ModUSB install the Chamaleon Boot Loader on the USB stick letting any PC to detect it as a bootable drive, also and most importantly it installs the required kext modules (drivers) to support most of the hardware of your PC/Netbook that otherwise would not be officilay supported by the Apple’s installation disc.
ModUSB differently from myHack tool autodect the hardware you PC has installed and choose the appropriate kext to activate or deactivate.

System Installation

Insert the USB stick on a USB port of your PC/Netbook and force the boot from USB instead of harddrive. On the Asus EeePC 1005HA you need to hold de ESC button during the BIOS initialization.
Now you can perform a standard Mac OS X installation.
during the installation process you need to run the Disk Utility form the Utilities manu to create a partition for Mac OS X Extended (with Journaling).
If you want to keep you Windows installation you need to perform additional modification of you partition before starting the installation process (this will be explained in a separate tutorial).
Ad the end of the installation process you will be returned an error saying that was not possible to complete the installation, THIS IS NORMAL, and it’s due to the fact that the installation system wasn’t capable to install the native Apple’s EFI boot loader, thanks to ModUSB previosly installed on the USB stick this installation will include by default the automatically chosen kext modules and the Chameleon boot loader.
Mind that if we would have use the myHack tool kext and boot loader would have not been installed on the new system and we should have booted the new installed system using as boot loader the USB stick.

First Boot

After the first system bot you’ll notice that everything is working with a couple of Glitches:

  1. sound is noisy/buzzing
  2. you cannot choose a screen resolution other than 800×600 (kext is loaded)
  3. Wi-Fi card is not detected, (kext is loaded).
  4. MMC card reader may not work.
  5. The Keyboard’s Fn keys are not working
  6. Hibernaton/sleep activate when you close the netbook lead but the PC never awakes

Make things working

  1. Install fixkext utility, everytime we add or remove kext form the kext libraries we have to regenerate the mkext cache file using fixkext utility that also takes care that all the kext modules have the right permissions and ownership.
  2. Copy the ‘SleepEnabler.kext’ file and decompress the ‘SnowLeopardAsus.zip’ into the desktop of the newly installed system.
  3. Install Extension for unrecognized devices:
    1. Copy ‘~/Desktop/SnowLeopardAsus/Extra/AsusHotkeys.kext’ to ‘/Extra/Extensions/’ folder.
      This makes working the Keyboard’s Fn keys such the screen brightness and the volume adjustment.
    2. Copy ‘~/Desktop/SnowLeopardAsus/Extra/IO80211Family.kext’ to ‘/Extra/Extensions/’ folder.
      This makes the system to recognize and install the Wi-Fi card.
    3. Copy ‘~/Desktop/SnowLeopardAsus/Extra/IOSDHCIBlockDevice.kext’ to ‘/Extra/Extensions/’ folder.
      This makes the system to recognize and install the MMC card reader.
  4. Backup the Extensions for misbehaving devices:
    1. Create a folder named ‘Old Extensions’ on your Desktop.
    2. Copy ‘/System/Library/Extensions/VoodooHDA.kext’ to ‘~/Desktop/Old Extensions/’.
    3. Copy ‘/System/Library/Extensions/AppleIntelGMA950.kext’ to ‘~/Desktop/Old Extensions/’.
    4. Copy ‘/System/Library/Extensions/AppleIntelIntegratedFramebuffer.kext’ to ‘~/Desktop/Old Extensions/’.
  5. Substitute the Extensions for the misbehaving devices:
    1. Copy ‘SleepEnabler.kext’ to ‘/System/Library/Extensions/’.
      This fix the hibernation/sleep feature.
    2. Copy ‘~/Desktop/SnowLeopardAsus/Kext/AppleIntelGMA950.kext’ to ‘/System/Library/Extensions/’.
    3. Copy ‘~/Desktop/SnowLeopardAsus/Kext/AppleIntelIntegratedFramebuffer.kext’ to ‘/System/Library/Extensions/’.
      This fixes the video card and add the option to choose 1024×600 resolution.
    4. Copy ‘~/Desktop/SnowLeopardAsus/Kext/VoodooHDA.kext’ to ‘/System/Library/Extensions/’.
    5. Double click on ‘~/Desktop/SnowLeopardAsus/VoodooHDA.prePane’ and confirm to ‘Replace’ the preference pane.
      This fixes the audio card issues.
  6. Now, most important, fire the command ‘fixkext’ with root privileges or using sudo:
    $ sudo fixkext

    This will make sure that all the copies Extension will have the right permissions and ownership and will recreate the kext’s cache.
    The kernel can now load the extensions at the next boot

  7. Restart the system and everything should work.

Now you have a fully functional Mac OS X Snow Leopard 10.6.0 running on you Asus EeePC 1005AH.

What still doesn’t work

When awakening form hibernate/sleep mode the USB disks (if any attached) will be not ejected properly (will persist also after the upgrade to Mac OS X Snow Leopard 10.6.6).

 

Now also available:

How-To Install or Update Mac OS X Snow Leopard 10.6.7 on the Asus Eee PC 1005HA Netbook

Upgrade to Mac OS X Snow Leopard 10.6.6

  1. Copy MacOSXUpdCombo10.6.6.dmg in the USB stick.
  2. Uncompress legacy_kernel-Mac_OS_X_10.6.6.tgz and to legacy_kernel-Mac_OS_X_10.6.6.pkg and copy it on the USB stick.
  3. Insert the USB Stick on the Netbook then mount and run the MacOSXUpdCombo10.6.6.dmg.
  4. When the installation is finished it will ask to restart,
    DO NOT RESTART THE SYSTEM YET!!
  5. Install ‘legacy_kernel-Mac_OS_X_10.6.6.pkg’.
    This install an older version of the kernel that is still compatible with the unficcial extensions we previously installed before the upgrade.
  6. Again, substitute the Extensions for the misbehaving devices:
    1. Copy ‘SleepEnabler.kext’ to ‘/System/Library/Extensions/’.
      This fix the hibernation/sleep feature.
    2. Copy ‘~/Desktop/SnowLeopardAsus/Kext/AppleIntelGMA950.kext’ to ‘/System/Library/Extensions/’.
    1. Copy ‘~/Desktop/SnowLeopardAsus/Kext/AppleIntelIntegratedFramebuffer.kext’ to ‘/System/Library/Extensions/’.
      This fixes the video card and add the option to choose 1024×600 resolution.
  7. Now, most important, fire the command ‘fixkext’ with root privileges or using sudo:
    $ sudo fixkext.
  8. No you can reboot the system

What still doesn’t work

— as reported by Eugene —
If you’re getting a kernel panic it is likely due to sleepenabler.kext you need to get one compatible with 10.6.6 from www.kexts.com

Wireless works fine on routers working only in “g” mode but not for mixed “g/n” or even “n”.
A solution is to replace the wireless card:

  1. The chip that you want to look for is Broadcom BCM94322 Half Mini PCIe card. It is also called Dell 1510 or DW1510, there are alse HP variants as well. This is the same chipset as Apple’s Airport Express card in MacBook Pro.
  2. Here is a you tube video: http://youtu.be/yehHh0GmnU0 for the hardware installation.
  3. You need the original IOFamily80211.kext (the one we installed through this guide is not the stock apple one, but modified for the 1005HA card).
  4. Download the patch and run through the terminal following the post here http://www.insanelymac.com/forum/index.php?showtopic=51725.
  5. Optional step is rebranding the Broadcom card so that computer thinks its actually Apple Airport Extreme and not a 3rd party card.
    This gives you speeds up to 300Mbps (the way “n” is intended)

Last Adjustments

After rebooting the system will work exactly as before without the need to install new extensions, anyway you may experience that your microphone is not ‘listening’ so what you need to do is to enter the System Preferences and click on the VoodooHDA pane then:

  1. Select ‘Microphone (fixed)’ from the dropdown menu
  2. Click on the round button that will activate all the available adjustable options
  3. It may help to adjust the ‘Mic’ bar and the ‘Recording Level’ bar

Open ‘Disk Utility‘, select the System drive, run ‘Repair Permissions‘, this will fix possible permissions gone bad during the hackintosh installation 😉
Should fix problems with Javascript crashing in Safari, Chrome and Firefox.

THIS IS IT! Enjoy and please feel free to post any fix suggestion or link/post your tutorial for other models.

How-To user EtherApe graphical network monitor with Windows, Mac OS X or Linux

Monday, February 14th, 2011

EtherApe is a graphical network monitor for Unix that come with most of the GNU/Linux distrubution but is not, now is present in MacPorts for Mac OS X and but has no porting for Windows as well.

The best use of EtherApe is when it’s installed on a server (or any GNU/Linux machine) connected to the last-hop of your network to allow it to ‘sniff’ (analyze) the whole traffic getting in-and-out of your network. I suggest to put it on the  switch or hub that connects your network to the router.

Normally we monitor and manage our network from our workstation trying to access as less as possible the screen of our servers. Because EtherApe would be installed on one of our servers to visualize its output on our screen avoiding the user of screen remotization like VNC, TeamViewer or LogMeIn we need to use X11 protocol forwarding via SSH.

This solution implies that we have and X11 service running on our workstation.
If we are working on a Linux machine it can’t be more easy as we mostprobably are working on a X11 implementation.
If run Mac OS X then we ned to installe Apple’s X11, and you can find the installer inside the Installation disc.

For Windows the game is more tough because it’s not a Unix based system and a X11 server implementation is not part of the standard applications offered as part of the installation options.
Fortunately come in hand the project Xming a free implementation of X Server for Windows: http://www.straightrunning.com/XmingNotes/

The steps to visualize EtherApe on your workstation are:

  1. Install EtherApe on your GNU/Linux server:
    i.e. on a GNU/Debian server: 

    # apt-get install etherape
  2. Install X11 on your workstation:
    1. On Linux most probably you have installed x.org package
    2. On Mac OS X you install the package that you find in the installation disc
    3. for windows you need to donlaod the public release of Xming:
      http://sourceforge.net/project/downloading.php?group_id=156984&filename=Xming-6-9-0-31-setup.exe
  3. Install an SSH client on your workstation
    1. On Linux and Mac OS X it is part of the base system installtion
    2. On Windows you need to install PuTTY:
      http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe
  4. Enable X11 forwarding through SSH on your server:
  5. Edit the file /etc/ssh/sshd_config and add or modify the X11 forwarding setting to
    X11Forwarding yes

    then restart the SSH service to load the new configuration

  6. On Windows only configure Xming to connect via the SSH client to your Linux server and specify to run the program xterm (or any other terminal application you have installed on your server) and specify as connecting user root or any sudoer user because EtherApe needs root privileges to turn the network card in listening mode.
  7. run EtherApe from the ssh connection just fireing the command ‘etherape’

Have fun!

Serial Number and Product Key Finder for Mac

Friday, January 21st, 2011

How many times have you installed a software at your office and then after many years you find out thatthe installation disc or (worst!) the serial number (or product key) shipped with the disc are lost?

When changing your old Mac to a new Mac you may had prefered to start from a brand new installation instead of restoring from a Time Machine backup, especially if you come from a PowerPC environment and you want to migrate to an Intell processor machine.
If this is the case you want to know what are the serial numbers of all yuor purchased software.

Product Key Finder for Mac is the small and free utility that you really need, and if you like it there’s a Windows version as well.

You can download the Product Key Finder from the official home page of the project:
http://mac-product-key-finder.com/

Enjoy!

How-To install and configure ntop 4 on Mac OS X

Sunday, January 16th, 2011

“ntop is a network probe that shows the network usage”, this is the brief description of ntop extracted from the official ‘overview’ page of www.ntop.org.

the reason why I like ntop is that it gives us a immediate projection of what is happening in our network NOW! with graphical and table representations of the current, recent and past network statistics.

When the network is stuck, you can know why, and you can know it immediately. You can then take the proper action to ditch the cause 😉

This is not all, there are amazing information you can have from this ‘small’ Italian tool…

In this post I will describe an as-easy-as-possible installation procedure to install ntop in you Mac OS X Server Snow Leopard (I didn’t test this on previous version, but as far as MacPorts is available for older version it shouldn’t be an issue to follow the same steps)

Preface

The easiest way ever would be to fire the command

$ sudo port install ntop

but as always happens the easiest way is not the best way, in facts the MacPort version of ntop is 3.3, quite old respect the current stable version 4.0.3.

Also, the installation of ntop through the port tool doesn’t install and configure it as a service but only as a tool to be run occasionally.

One of the reasons I prefer to install ntop 4.0.3 instead of 3.3 is that it gives us the option to visualise the “Hosts World Map” directly in Google Maps and the “Local Network Traffic Map” giving us an idea where our network users and services and clients are connecting to and from. Of course many other improvements are available in the latest version, but these are the coolest according to me 😀

Another reason to manually install ntop and follow the procedure below is to install and configure it as a daemon (LaunchDaemon) launched by ‘launchd’.

What will will do then, is to download, compile and install the ntop 4.0.3 directly from its official website and rely on MacPorts to install it’s compiling and installing dependencies.

Prerequisites

  1. The -latest- sources of ntop.
  2. Xcode (required by MacPorts), you can install it from Mac OS X Server Snow Leopard installation disk, ‘Optional Installs’ folder.
  3. Workgroup Manager, it’s part of the Server Admin Tools and needs to be downloaded from Apple support and installed, unless you are running Mac OS X Server.
  4. MacPorts, you can download and install it from www.macports.org.
  5. wget, to be installed via MacPorts

Preparation of system

    1. Make sure you have installed Xcode and MacPorts and Worgroup Manager.
    2. Create a ‘src’ folder where to store and compile the ntop sources:
$ mkdir ~/src
$ cd ~/src
    1. Install wget:
$ sudo port install wget
  1. Fetch the latests source archive from www.ntop.org:
    $ wget wget http://ignum.dl.sourceforge.net/project/ntop/ntop/Stable/ntop-4.0.3.tgz
    $ tar xvzf ntop-4.0.3.tgz
    $ cd ~/src/ntop-4.0.3
  2. install ntop dependencies from MacPorts needed to compile and run ntop:
    $ sudo port install depof:ntop

    this command do not istall ntop from MacPorts but only its dependencies.

    This step could take several minutes because it will download, compile and install a lot of ports (libraries).

  3. Creation of the a localuser and local groupntop via ‘Workgroup Manager’:
    1. Create the new local group ntop ntop_group
    2. Create the new local user ntop with primary group ntop ntop_user

      Leave the password blank prevent any possibility of login and also do not specify the home folder, of if you really need to specify one choose /usr/local/etc/ntop.

       

       

       

       

       

       

       

       

       

       

       

       

       

      ntop_group_assignation

      This procedure can be executed in command-line as well using the ‘dscl’ command, but you will have to assign the Primary User ID manually retrieving it from the directory service using other scripts.
      The Workgroup Manager calculate the first available User ID automatically.

  4. install mako (needed for “Host World Map” feature of ntop):
    $ sudo easy_install mako
  5. install of graphviz (contains ‘dot’, needed for “Local Network Traffic Map” feature of ntop):
    $ sudo port install graphviz

Compilation

Make sure to be in ‘~/src/ntop-4.0.3’ folder then

  1. fire the script that checks the dependencies:
    $ ./autogen.sh
  2. and proceeds with the compilation:
    $ make

Installation

 

    1. Run the script that installs ntop and its libraries in the proper places:
      $ sudo make install
    2. Create the LaunchDaemon scripts to make the service running as a daemon:
      $ sudo touch /Library/LaunchDaemons/org.ntop.ntop.plist
    3. copy and paste the following lines into org.ntop.ntop.plist
#-----BEGIN OF org.ntop.ntop.plist-----
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
   <key>KeepAlive</key>
   <dict>
      <key>NetworkState</key>
      <true/>
   </dict>
   <key>Label</key>
   <string>org.ntop.ntop</string>
   <key>ProgramArguments</key>
   <array>
      <string>/usr/local/bin/ntop</string>
      <string>@/usr/local/etc/ntop/ntop.conf</string>
      <string>--user</string><string>ntop</string>
      <string>--db-file-path</string><string>/usr/local/var/ntop</string>
      <string>--daemon</string>
</array>
</dict>
</plist>
#-----END OF org.ntop.ntop.plist-----
  1. Create the configuration file to pass additional custom parameters
    $ sudo touch /usr/local/etc/ntop/ntop.conf
  2. copy and paste the following lines into ntop.conf
    (in this example I put the ‘vital’ paramenteres, you can specify more parameters, but the ones placed in the the LaunchDaemon file will NOT be overloaded by the parameters present on the ntop.conf file)

    #-----BEGIN OF ntop.conf-----
    # interface(s) that ntop will capture on
    #  DEFAULT: The 1st sisernet device, e.g. sis0 
    
    --interface en0
    
    # Configures ntop not to trust MAC addrs.
    # This is used when port mirroring or SPAN
    #--no-mac
    
    # Logging messages to syslog (instead of the console):
    #  NOTE: To log to a specific facility, use --use-syslog=local3
    #  NOTE: The = is REQUIRED and no spaces are permitted.
    
    #--use-syslog
    -L
    
    # Tells ntop to track only local hosts as specified
    # by the --local-subnets option
    
    #--track-local-hosts
    
    # Sets the port that the HTTP webserver listens on
    #  NOTE: --http-server 3000 is the default
    
    #--http-server 3000
    
    # Sets the port that the optional HTTPS webserver listens on
    
    #--https-server 3001
    
    # Sets the networks that ntop should consider as local.
    # NOTE: Uses dotted decimal and CIDR notation.
    # Example: 192.168.0.0/24
    # The addresses of the interfaces are always
    # local and don't need to be specified.
    
    #--local-subnets 192.168.2.0/24
    
    # Sets the domain.
    # ntop should be able to determine this automatically.
    
    #--domain domain.my
    #-----END OF ntop.conf-----
  3. Set the correct file and folder permissions. VERY IMPORTANT!
    $ sudo chmod 644 /Library/LaunchDaemons/org.ntop.ntop.plist
    $ sudo chown -R ntop /usr/local/var/ntop
    $ sudo chown -R ntop /usr/local/etc/ntop

Configuration
Set the password for the admin user of ntop database (from the web interface you’ll be able to create other users with different degree of administration)

$ sudo ntop -t o -u ntop -P /usr/local/var/ntop --set-admin-password

Conclusion

Now start the service using the launchctl command and it will run as a daemon:

$ sudo launchctl load /Library/LaunchDaemons/org.ntop.ntop.plist

You will be able to access ntop through port 3000 (by default) of your server:

http://domain.my:3000

Click on this link to download here the archive containing my prepared copies of org.ntop.ntop.plistand ntop.conf files

If you found this how-to useful, please leave a feedback, it will be really appreciated.

Enjoy!

How-To connect to VMware Server Console via Mac OS X

Sunday, January 2nd, 2011
Listen to me!
Audio MP3
download mp3

If you like, as I do,  to administer your network from a workstation runnig Mac OS X and you enjoyed the installation of a VMware Server infrastructure, you will certanly will be disappointed to discover that THERE IS NOT a VMWare Console plug-in for Mac OS X version of Firefox or for Safari.

You still are able to access the VMware Infrastructure Web Access to create, modify, run and stop your virtual machines, but you will not be able to visualize the screen of virtualized servers unless you installed Remote Desktop, Terminal Service or other remotisation solutions suche LogMeIn or TeamViewer or a standart VNC server in the guest operating system.

But what to do if you need to access the BIOS settings of your virtual machines, what if you need to access them in a pre-OS status in case there is some trouble with the OS? What if you are running a virtualized GNU/Linux server and you cannot access it via SSH service?

The right solution came to my hand after a long time searching the web, and fortunately it’s fast and easy to apply and first of all is not tricky and unelegant like forwarding the X11 service via SSH (like many other blogs would suggest).

Here we go, what we need to do is to enable the VNC feature of the VMware server for each Virtual Machine configuration:

  1. Access the VMWare Infrastructure web Access
    (usually at https://<yourserver_domain_name>:8333/ui/)
  2. Select the Virtual Machine instance
  3. Select the ‘Summary’ tab
  4. click on the ‘Configure VM’ option of the ‘Commands’ navigation pane

    VM_Commands

  5. select the ‘Advanced’ tab and start adding the following ‘Configuration Parameters’:
    • RemoteDispaly.vnc.enabled =  true
    • RemoteDisplay.vnc.password = <choosen_password>
    • RemoteDisplay.vnc.port = 5900 (a different port for each Virtual Machine is recommended)
    VM_Configuration

    VM_Configuration

    * note that the RemoteDisplay.vnc.key is automatically generated by the VMware server

  6. run any VNC client pointing at <yourserver_domain_name>:5900 and you’ll be able to interact with your virtual machine from your Mac and even from you iPad or iPhone!!!!

How-To change MAC address of your ethernet network card with Mac OS X

Monday, November 15th, 2010

If using Mac OS X you find yourself in a situation to test the correct functionality of a DHCP server or you need to force the lease af a different IP address from a DHCP server, you may want to change the MAC address of your ethernet network card so to be recognised as a new client of the network.

To change the Mac address with Mac OS X, you need to fire the following command:

$ sudo ifconfig en0 ether 00:xx:xx:xx:xx:xx
(just modify the lat two digitas of your current MAC address)

How-To open multiple instances of an application with OS X

Sunday, October 10th, 2010
Listen to me!
Audio MP3

download mp3
It happened to me to have the need to run at the same time the Skype application in Mac OS X  being logged with two different accounts, this was needed to test the messaging and file sharing capabilities or simply to be able to receive calls on two different accounts or registered numbers at the same time.

That practice is not actually permitted with the current version of Skype for Mac OS X (Skype Version 2.8.0.251) so I had to find a DIY solution.

At the beginning I tried to copy the application bundle and launch it, wishing that the system was recognising this as a distinct application but unfortunately that didn’t work and Mac OS X was complaining that the application was already running and it could not open a second instance of it (due to a conflict of resources).

I then started wondering why in GNU/Linux (that is a not-so-far cousin of Mac OS X UNIX subsystem), wasn’t that difficult to launch from command-line a second instance of an application, so it came to my mind the ‘open’ command that sometimes I use with AppleScript to launch some applications.

Reading the manual of ‘open’ I discovered these two ‘magical’ options:

  • The ‘-n’ option, that guarantees the opening of a new instance of the application;
  • The ‘-a’ option, that permits to specify the name of an application without the bundle extension ‘.app’ and without specifying the absolute path of the application (that in this case would generally be ‘/Applications/Skype.app’;

I ended up with this ‘best solution’ to open a second (or further) copy of an application with Mac OS X using the given CLI command ‘open’ as follows:

# open -na <application_name>

How-To set the Bundle attribute to a file in Mac OS X

Friday, September 10th, 2010

If you want to make a folder to appear like a Bundle File (a single transportable file) preventing the user to access a file (and possibly mess with its content) what you have to do is to set the Bundle attribute with this simple CLI command:

SetFile -a B <bundle file name>

You can use this technique if you want to restore the bundle attribute after a bundle-file (a directory container with bundle attribute) is transported through a bundle-incompatible file system like Linux and Windows file systems generally are.