netfix testers?

[Joel Newkirk]

On Mon, 20 Oct 2008 11:46:12 +1100, roguemoko at roguewrt.org wrote:
> Joel Newkirk wrote:
>> I've posted a tarball of my networking fixes to
>> http://newkirk.us/om/testing/netfix-j1.tar.gz, and a writeup on it at
>> http://jthinks.com/better-freerunner-networking for anyone interested.
> Wiki
>> seemed inappropriate (at least at this time), and the writeup is too
> long
>> to post on the ML, IMHO.
> 
> Awesome. I'll upgrade/backup/test at my earliest convenience (prolly a
> couple of days at this point).
> 
> I'll let you know how I go.
> 
> Sarton

Thanks!

I have to apologize - I just flashed to SHR to test this and (re)discovered
that busybox's substitute for 'ip' doesn't support route metrics - I've
been installing my own from http://newkirk.us/om/iproute2_2.6.26_armv4t.ipk
in my setup script I usually run after flash and forgotten that important
factor.  I'm pretty sure the older 'route' command substitute in busybox
supports metric, will give it a test run.  

So this solution currently depends on both resolvconf and full
(non-busybox) iproute2.  Angstrom only has iproute2 packaged for Arm9 IIRC.
The resolvconf package (included with 2008.x but not SHR or Raster) is
available from the OM repository.  

Also, if you power up with USB already plugged in, it doesn't bring usb0 up
automatically at first, since udev doesn't emit a 'power plugged in' signal
- it's necessary to unplug and plug back in.  I'll look into triggering at
startup as well.

j

PS - just checked, and busybox-as-'route' DOES support route metric
setting, so I'm going to alter my scripts to use 'route' instead of 'ip
route' and make sure it behaves as expected.  Update tomorrow.


**separately: I think the full iproute2 package should be in the OM build
tree - apart from allowing far more advanced routing controls than
busybox's poor substitute, it includes the 'tc' traffic control command to
give access to the full breadth of the kernel's IP traffic management - of
little direct use on FR as a terminal, much more useful if it's a gateway -
they build bridge-utils, iproute seems more generally useful.  It builds
cleanly under dev toolchain.

busybox 'ip':
Usage: ip [OPTIONS] {address | route | link | tunnel | } {COMMAND}

iproute2 'ip':
Usage: ip [ OPTIONS ] OBJECT { COMMAND | help }
       ip [ -force ] [-batch filename
where  OBJECT := { link | addr | addrlabel | route | rule | neigh | ntable
|
                   tunnel | maddr | mroute | monitor | xfrm }
       OPTIONS := { -V[ersion] | -s[tatistics] | -d[etails] | -r[esolve] |
                    -f[amily] { inet | inet6 | ipx | dnet | link } |
                    -o[neline] | -t[imestamp] }

iproute2 'ip route help':
Usage: ip route { list | flush } SELECTOR
       ip route get ADDRESS [ from ADDRESS iif STRING ]
                            [ oif STRING ]  [ tos TOS ]
       ip route { add | del | change | append | replace | monitor } ROUTE
SELECTOR := [ root PREFIX ] [ match PREFIX ] [ exact PREFIX ]
            [ table TABLE_ID ] [ proto RTPROTO ]
            [ type TYPE ] [ scope SCOPE ]
ROUTE := NODE_SPEC [ INFO_SPEC ]
NODE_SPEC := [ TYPE ] PREFIX [ tos TOS ]
             [ table TABLE_ID ] [ proto RTPROTO ]
             [ scope SCOPE ] [ metric METRIC ]
INFO_SPEC := NH OPTIONS FLAGS [ nexthop NH ]...
NH := [ via ADDRESS ] [ dev STRING ] [ weight NUMBER ] NHFLAGS
OPTIONS := FLAGS [ mtu NUMBER ] [ advmss NUMBER ]
           [ rtt TIME ] [ rttvar TIME ]
           [ window NUMBER] [ cwnd NUMBER ] [ initcwnd NUMBER ]
           [ ssthresh NUMBER ] [ realms REALM ] [ src ADDRESS ]
           [ rto_min TIME ]
TYPE := [ unicast | local | broadcast | multicast | throw |
          unreachable | prohibit | blackhole | nat ]
TABLE_ID := [ local | main | default | all | NUMBER ]
SCOPE := [ host | link | global | NUMBER ]
FLAGS := [ equalize ]
MP_ALGO := { rr | drr | random | wrandom }
NHFLAGS := [ onlink | pervasive ]
RTPROTO := [ kernel | boot | static | NUMBER ]
TIME := NUMBER[s|ms|us|ns|j]