Home page : http://www.sofaraway.org/projects/yalg/
Author : Fabien Tassin <fta@sofaraway.org>
Supported protocols are :
Note: if you use rsh and get "poll: protocol failure in circuit setup", this means that the reverse connection for the stderr channel is filtred somewhere in your network. If your rsh comes from the "net-kit" package, you can apply this patch (it is against netkit-rsh 0.16.1) and then use the '-s' flag that does not connect stderr.
Keys are a single string representing the label (the description). It must be unique.
Values can be of several types :
Here is an example :
my $defipvers = 'IPv4';
my $defiptype = 'unicast';
my $hosts = {
'New York' => 'host1.domain.net',
'London' => 'lon1',
'Rio' => 'Rio',
'Paris' => { 'host' => 'paris-v6',
'ip' => [ 'IPv4', 'IPv6' ],
},
'Sydney' => { 'host' => 'r1.syd.aust.domain.net',
'ip' => [ [ 'IPv4', 'multicast' ],
[ 'IPv4', 'unicast' ] ],
},
};
This will give :
| Label | Hostname | IPv4 | IPv6 | ||
|---|---|---|---|---|---|
| unicast | multicast | unicast | multicast | ||
| London | lon1 | Yes | No | No | No |
| New York | host1.domain.net | Yes | No | No | No |
| Paris | paris-v6 | Yes | No | Yes | No |
| Rio | Rio | Yes | No | No | No |
| Sydney | r1.syd.aust.domain.net | Yes | Yes | No | No |
Notes: as it is stored in a hash table, data ordering is lost. Hostnames are not resolved by yalg but by the command which is launched to talk to the equipement (see $rcmd).
Refer to the code for an example.
Note: values can be equal or different as netnum and net6num for a given AS sometimes differ.
$ perl -cw yalg.pl Content-type: text/html yalg.pl syntax OK
On the top left, select a router (or more if "Multiple hosts" is checked), choose a command, optionnaly add an argument then submit with "Probe".
IPv4: 3.0.0.1
193.251.128.79
IPv6: 2001:688::1
2001:688:0:1234::1
2001:688::193.251.151.79
IPv4: 3.0.0.0/8
193.251.128.0/19
IPv6: 2001:688::/35
2001:688:0:1234::1/128
^re(gexp)? [_^]?\d+[_\$]?$"
regexp 234 any AS path matching 234 (this includes AS234, AS1234, AS2345, AS12345...) re ^234 any AS path starting with 234 (this includes AS234, AS2345..) re _234 any AS path containing an AS starting with 234 re _234_ any AS path containing exactly AS234 re ^234_ any AS path starting exactly with AS234 re _234$ any AS path ending with AS234
Feel free to visit and to register to http://www.traceroute.org/.
Note: if you are using yalg or any other looking glass for IPv6, please, contact me.