You can use this wireshark filter to restrict results to the network you are interested in:

ip.addr == 10.10.0.0/16

Since we are not specifying a source or destination (i.e. ip.src or ip.dst), the filter will match both. If you want to reverse it then:

!(ip.addr == 10.10.0.0/16)

I'll often use the same method to filter the results on a specific IP address, preserving both ends of the conversation:

ip.addr == 10.10.10.50

 Nslookup under osx is tricky to use interactively as it doesn't support readline. When you try to use the command history you get the following:

 Rather than installing the remote exchange management tools and the pain that causes, you can use powershell remoting. To setup powershell to connect to the exchange server pop the following into a powershell prompt on your client machine:

 Sometimes you need to find out if you are running a 32bit or a 63bit Windows operating system. You can do this quickly from the command line:

 wmic os get osarchitecture

Another option is using the following environmental variable:

 echo %PROCESSOR_ARCHITECTURE%

Short and sweet.

 As of the 25/06/12 you need to use the bloody release and will also need to have a floppy drive attached. You can add the floppy drive through the VMware gui or add the following to your vmx file:

floppy0.fileType = "file"
floppy0.fileName = "path_to_/floppy_image/Omni.flp"
floppy0.clientDevice = "FALSE"
floppy0.startConnected = "FALSE"

If you want to create a virtual floppy image then use the following on Os X:

 Use the following from a terminal to get the file size in bytes:

wc -c ~/screenlog.0  

Which in this case will output:

76974 /Users/edward/screenlog.0

Showing my screenlog.0 is 76974 bytes.

 When removing subinterfaces from a SSG550 we were getting the following error:

Unable to remove interface, interface ethernet0/0.1:1 is in use the interface cannot be set

Where ethernet0/01:1 is the interface you are trying to remove. After some experimentation we found that you have to make sure you have removed the check box under the NTP server service option. If the subinterface is still running NTP you will be unable to remove the subinterface.

How about:

Multi-queue support for VMXNET3 drivers. New support for VMXNET3 drivers provides the ability to scale throughput in a VMware vSphere 5 environment by assigning multiple cores to the Vyatta virtual machine. 

Sounds good to me.

 Sometimes you need to use the operating system file manager rather than a terminal so a quick way of opening it can be seen below. For the Windows command line:

explorer .

The OS X terminal:

open .

The Ubuntu console:

nautilus . 

This will work for parent folders ".." as well as current directory. Note, in case you are interested to do the same in Haiku OS just use the OS X version.

 Vmware Fusion already includes a basic preboot execution environment (pxe) firmware. It is however possible to load other pxe firmwares into Fusion just like flashing ROMs into real network adapters. Two examples of pxe compliant boot loaders are gpxe and ipxe. Ipxe seems to be based on gpxe but they have generally similar features sets. These features include DNS, HTTP, iSCSI chainloading and more. To access these extra features we need to get hold of the ROM files which can be downloaded from here (right click and choose save as):