My Wandering

Thursday, May 23, 2013

OSX juniper network connect client has littered your ipv4 routing table with corrupt entries and you need a usable machine again.

sudo -s -- 'killall Network\ Connect ; networksetup -setv4off Wi-FI ; networksetup -setdhcp Wi-Fi'

will do the business...

that murders off the current network connect client

flushes the ipv4 routing table and all ipv4 state associated with the wifi interface and starts it back up again. Oddly this is a big improvement over rebooting twice a week. (and no shutting off the wifi and doing a route -n flush is not suffient).

Monday, October 15, 2012

Originally submitted at Timbuk2

Customize The Eula Mini Messenger

Downsizing what I carry...

By joel jaeggli from east palo alto on 10/14/2012

Pros: Lightweight , High Quality, Attractive

Describe Yourself: Practical, Modern

Was this a gift?: No

So,

I ordered this because I've been looking to downsize into a smaller bag. (the former one was a custom size larger messenger. This involved among other things buying a new laptop.

The EULA indicates that it doesn't quite fit the 11" macbook air. superficially this is true however the dimensions are so close that it wedges in without trouble. none of the timbuk2 sleeves appear to be sufficiently compact to hold an 11" air and fit. So, wool felt sleeve purchased elsewhere solves this issue.

the EULA would be perfect for this application if it were ~ 1/2" larger in width/depth. The back sleeve if you order will not fit the macbook air 11" but does fit an ipad in a protective jacket.

result is, I get:

macbook air
ipad
micro4/3 camera with pancake lens
power supply
assorted cables in the old medium size timbuk2 clear bag
mouse
passport sleeve

and it's full but not bulging.

The eula could be perfect, It isn't but it's rather good. given that it's made of the same material (indeed same color/fabric/lining) as my custom messener I expect that in 5 years I'll still be using it unless I've had to go back to a larger computer. the strap length adjustor is friction based and is not as stiff as the strap adjustor on the larger bags, so it periodically requires adjustment.

eula, loaded

Tags: Picture of Product

contents

Tags: Using Product

(legalese)

Tuesday, November 08, 2011

not installing a bunch of junk in your fib.

you have a route reflector running in a logical system in junos...

the thing has 400k routes but it doesn't really need them, in fact they're just cluttering up the fib.

solution.

routing-options {

...

forwarding-table {

export [ logical-system-fib-compress reject-all ];

}

policy-options {

policy-statement logical-system-fib-compress {

from protocol [ direct static isis ];

then accept;

}

policy-statement reject-all {

then reject;

}

now you've got some igp routes for local color a sensible default and a rib of essentially arbitrary size.

Tuesday, September 06, 2011

emacs keys

http://www.math.uh.edu/~bgb/emacs_keys.html

Wednesday, August 24, 2011

Magic screen incantion:

caption string "%H %c %w"

bind f eval "caption splitonly"

bind F eval "caption always"

Found here

Coupled with:

alias host="ssh username@host -t screen -RR -D"

Means I'm always in the same screen session on that system.

Tuesday, April 05, 2011

Junos 11.1

Appears to dropped on schedule at the end of q1...

now to put that in the lab.

http://www.juniper.net/support/products/junos/dom/11.1/

see what other bundles of joy have fallen in/out as a result.

SSH keep-alive interval...

Adjustiing the ssh keepalive interval down is an essential part of traversing nat translation and stateful inspection devices that reap stale or idle connections...

There are basically three place this parameter can be tuned.

in the sshd_config (to adjust on the server daemon)

ClientAliveInterval 30

in the ssh_config (to adjust for the client on a system-wide basis)

ServerAliveInterval 30

or in the user's ~/.ssh/config file (to adjust just for yourself)

ServerAliveInterval 30

what's the right interval?

I'm persistently afraid of timers with a 60 second interval so I aimed to get below that. A proper approach would be 3x the number of keep-alives as the theoretical timer (60s) but 30s is still about 86400 packets a month just to keep this session alive so increasing the frequency if this works is somewhat wasteful.