To setup a default gateway as 10.199.50.1 use the following (note the final ’1′ at the end of the command line.

filer-3170> route add default 10.199.50.1 1

Today I was trying to run a packet trace to capture iSCSI traffic from a Windows box to one of our filers. The trace would only show iSCSI Read’s and no iSCSI Writes, even though I knew that there was write traffic. A packet trace taken from the filer using pktt showed the Reads and Writes I expected – which indicated something strange at the Windows end. It turned out that the cause was TCP/IP offloading. The intel NIC was configured to do the offloading, and evidently ‘hid’ some of the network activity from windump (a tcpdump implementation on Windows). Once I turned off the offloading from inside Windows using the “Advanced” Tab inside the NIC Properties window I was able to see the iSCSI reads and Writes at the Windows end.

My best guess is that the issue is to do with where in the network stack the WinPCAP module is inserted. It seems that some traffic was routed ‘around’ wherever in the stack WinPCAP was listening.

There are many support threads which indicate folks having problems running their Macbook pro’s with external displays.

I found that switching the “Energy Saver” preferences to “Higher Performance” solved my display issues on a 2009 MBP. My recollection is that the energy saver preferences change how the video chipset operates in order to save power.

Previously, I was not able to run my external monitor at the highest (native) resolution in VGA, but found it was fine when using DVI. After I fiddled with the energy saver prefs, the monitor worked in native resolution (1600×1050) in both VGA and DVI.