See also the "Filter" command below

Interesting usage: dm 2fc000 appears to dump the user configuration in 256-byte blocks. You'll need to increment this in 256 byte blocks to dump the entire config. Yes, the pm command will let you write things here, but since you're writing to volatile ram your "patches" will not survive a soft reset. 

(to add a static route)
rt add {network-hex} {gateway-hex} {netmask-hex} {interface} {type} {proto}

(to delete a static route)
rt delete {network-hex} {gateway-hex} {netmask-hex} {interface} {type} {proto}

Examples:
Add a static route for the 192.168.1.0 network using 192.168.2.21 as a gateway. The '1' is interface 1 (the LAN interface on the OCLM). The '3' is the type of route, which is direct connected. The 'disp d' command shows Type as 4 after I add it, but 3 seems to work fine. The '2' is type of protocol, which appears to always be 2. I'm not sure how they differentiate between types 2 and 4, but I haven't had any need to do so.

rt add c0a80100 c0a80215 ffffff00 1 3 2

Delete the just-added static route:

rt delete c0a80100 c0a80215 ffffff00 1 3 2

Note that NAT does not appear to function for any remote nodes that you may have. You'll be able to see or ping the OCLM on the remote node but nothing behind it.

How to convert dotted-decimal address to hex:

To find the correct hex numbers, each octet should be converted to hex. The simplest way to do this is to use a scientific calculator (the Windows calculator will do), but it can be done by hand. Divide each octet by 16 and keep the remainder. Then convert the result and remainder to a single-character value as shown:

0-9: 0-9
10: A
11: B
12: C
13: D
14: E
15: F

Example:

192/16 = 12, remainder 0
192 decimal = C0 hex

168/16 = 10, remainder 8
168 decimal = A8 hex

1/16 = 0, remainder 1
1 decimal = 01 hex

Thus, something like 192.168.1.0 in decimal is C0A80100 in hex. The most common netmask will be a Class C address, which is 255.255.255.0. This translates to FFFFFF00 in hex.

Errata: do not use a leading zero on the month field else the OCLM interprets the date as an octal expression. 

i.e.

tset 2001 09 11 15 50 00 => error
tset 2001 9 11 15 50 00 => OK
tset 2001 011 11 15 50 00 => OK and month = September (011 octal=9 decimal)

Errata 30-Jan-00:  It has come to my attention that the direction or bound arguments are presently non-functional and have no effect. Filter statements therefore effect packets in both directions. netBIOS filtering may also behave unpredictably when entered through the telnet interface.

Arguments:

command:   a - add entry to table
           l - list the table
           d - delete an entry from the table
           ? - display help
port:     nn - port number to block
protocol:  t - block TCP packets
           u - block UDP packets   
           c - block ICMP packets
           g - block IGMP packets       
           e - block GRE packets (PPTP)
           b - block both TCP and UDP packets
direction: i - inbound
           o - outbound
           b - both inbound and outbound
blocktype: a - Always filter (block)
           c - Only block call initiation

Syntax:

filter ?          | Displays onscreen help (poorly formatted display)
filter l          | Show the current active filter list
filter a 7 c i a  | Adds a filter to always block incoming ICMP packets 
filter a 80 t o a | Adds a filter entry to always block outbound TCP
                  | HTTP packets
filter a 80 t i a | Adds a filter entry to always block inbound TCP
                  | HTTP packets
filter a 80 u o a | Adds a filter entry to always block outbound UDP
                  | packets on port 80 (HTTP)
filter a 80 t o c | Adds a filter entry to block outbound TCP
                  | HTTP packets. This blocks call initiation only.
                  | Once the call is up, these packets will be routed
filter d 0        | Deletes the first entry from the filter list

US Domestic firmware release 5.3.1 appears to be the final release.