String around my finger
A 'blog to remember things I found.

My Home Page
I work for NIS ITS Monash University Australia.

Index

• hardware 19
• linux 13
• media 24
• misc 21
• monash 18
• networks 33
• oss 1
• security 1
• software 17
• voip 37
• windows 3

Flavours

Links
These are a few of my favourite links.

Subscribe
Subscribe to a syndicated feed of my weblog, brought to you by the wonders of RSS.

GeoURL

Click to call me FWD# 61159

Windows Messenger

Windows messenger claims to enable "video conversations" and to support SIP.

However, first some terminology. Windows Messenger is also known as .NET Messenger. However, MSN Messenger is not the same thing at all. Many people like the extra eye candy in MSN Messenger. Go to Help / About to find out exactly what you have. You may be able to run both, but not at the same time.

Getting Windows Messenger. http://www.microsoft.com/windows/messenger/ is subtitled "Windows Messenger Update for Windows XP". "Note: The latest version of Windows Messenger is available for Windows XP in Windows XP Service Pack 2." (This may be Windows Messenger 5.0).

There is also Windows Messenger for Microsoft Office Live Communications Server 2003 and Microsoft Office Communicator 2005 and Exchange Instant Messaging (IM) Client 4.6 (for Windows 95, Windows 98, or Windows ME).

Inside Windows Messenger - How it Communicates This article discusses ... Session Initiation Protocol- (SIP) based server options.

The latest seems to be Windows Messenger 5.1, dated 3/24/2005.

[ /voip | # ]

6500 upgrade

1. find current image name

# show boot
BOOT variable = sup-bootflash:s72033-pk9s-mz.122-18.SXD.bin,1

2. backup current image to card0:

# copy sup-bootflash:s72033-pk9s-mz.122-18.SXD.bin disk0:
...

3. make space for new image

# format sup-bootflash:
...

4. download new image

# copy scp://130.194.11.103//var/tftp/s72033-pk9s-mz.122-18.SXD3.bin sup-bootflash:
...

5. fix boot variable

# sho run | i boot system
boot system flash sup-bootflash:s72033-pk9s-mz.122-18.SXD.bin
# conf t
(config)# no boot system flash sup-bootflash:s72033-pk9s-mz.122-18.SXD.bin
(config)# boot system flash sup-bootflash:s72033-pk9s-mz.122-18.SXD3.bin
# wri mem

6. check

# sho run | i boot system
boot system flash sup-bootflash:s72033-pk9s-mz.122-18.SXD3.bin
# dir sup-bootflash:s72033-pk9s-mz.122-18.SXD3.bin
    1  -rwx    34838464  Mar 31 2005 17:00:11 +10:00 s72033-pk9s-mz.122-18.SXD3.bin

7. reload

# reload
...

[ /monash | # ]

the 5-in-1 network admin's cable

"... after putting together four simple custom adapters, I now have an ethernet cable, a crossover ethernet cable, a modem cable, a null modem cable, and a Cisco console cable"

Also serial AND Ethernet loopback plug, receive-only ethernet sniffer cable, and "throwing star" LAN tap.

Cisco Cabling Guide for Console and AUX Ports s RTS and CTS reversed on the DB9/RJ45 console cable ??

Yost Serial Device Wiring Standard

Receive-only UTP cables and Network Taps

[ /hardware | # ]

IPv6 Netflow Accounting

Cisco IOS NetFlow Version 9 s template-based. Templates provide an extensible design to the record format, making most of the fields optional. Each data record specifies which template it is using. There can be multiple templates defined, and I think there can be data records with different templates in an export packet.

This is radically different from NetFlow v5 (which we currently use) which has a fixed set of field in each data record (and only one type of data record from each collector).

NetFlow Version 9 Flow-Record Format and RFC3954 define the fields, options and templates. Version 9 includes the fields IPV6_SRC_ADDR, IPV6_DST_ADDR, IPV6_SRC_MASK, IPV6_DST_MASK, IPV6_FLOW_LABEL, IP_PROTOCOL_VERSION (4 or 6), IPV6_NEXT_HOP, BGP_IPV6_NEXT_HOP, and IPV6_OPTION_HEADERS.

How to configure NetFlow V9 export format.

I don't know which of the NetFlow Partners or freshmeat projects support v9.

pmacct promises to account and aggregate IPv4 and IPv6 traffic and do Netflow v9.

[ /networks | # ]