[gnome-network] Re: new modules consensus

On Maw, 2004-08-17 at 16:17, Germán Poó Caamaño wrote:
> May you give some detail or approach that I could follow to get
> in shape nettool? (I mean, traceroute and routing tables or whatever
> else that needs some love).

Lets start with an easy one. The traceroute parser assumes packets
follow a single path. Probably your network looks like that ? but
traceroutes can often look like this

3  aa1-hg3.ilford.broadband.bt.net (  18.333 ms  17.865 ms 
18.091 ms
 4  aa1-fer1G30.ilford.broadband.bt.net (  17.916 ms
aa1-fer2gig3.ilford.broadband.bt.net (  17.809 ms
aa1-fer2G10.ilford.broadband.bt.net (  17.779 ms
 5  aa1-nteatm2.1.ilford.broadband.bt.net (  19.841 ms 
19.867 ms aa1-nteatm2.2.ilford.broadband.bt.net (  18.032
 6  aimless.aaisp.net.uk (  19.893 ms  17.933 ms  19.928 ms

You'll see the output format is a little different and this breaks the
traceroute probe.

Routing in the Linux world is a bit more complex. netstat is sort of a
legacy "simplistic" view of the routing tables. It is mostly there for
backward compatibility with simple setups.

The ip command allows access to the full tables. Each table entry
contains a lot more information than "route" shows.. dev eth0  proto kernel  scope link  src dev eth0  scope link dev lo  scope link
default via dev eth0

It has scopes. It also knows the source ip to use for the route, the
mtu, mss, tcp window, and a lot more things.

There are also multiple routing tables, and the table used can be
selected by routing prefixes and input policy.  (ip rule)

(btw ip link also knows some things about network interfaces that may be
of interest including the queue discipline)


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]