Distribution tree of area fidotest for last 30 days
221/6
+ 221/1
| + 221/360
| L 134/101
+ 154/10
| L 2320/105
| L 2320/107
+ 5020/1042
| + 5020/715
| | L 5023/24
| + 3634/12
| | L 153/7715
| | L 229/426
| | + 342/200
| | | L 342/201
| | + 229/664
| | + 15/0
| | | L 340/400
| | | L 340/1101
| | L 229/307
| L 5075/128
+ 218/840
| + 770/1
| | + 80/1
| | | L 801/188
| | L 633/280
| L 218/700
+ 341/234
+ 460/58
| L 460/256
+ 301/1
+ 341/66
| + 280/464
| | + 240/1120
| | | L 371/0
| | | L 371/52
| | + 396/45
| | + 203/0
| | | L 201/0
| | | L 201/137
| | + 712/848
| | L 240/5832
| | L 320/219
| L 902/26
| L 90/1
| L 900/106
L 153/757
This is how it looks from my node.
$ hpttree -d 30 fidotest
hpttree/lnx 1.9
Distribution tree of area fidotest for last 30 days
| | + 2:154/10
+ 2:3634/12
| L 2:229/426
| + 2:342/200
| | L 2:342/201
| + 2:229/664
| + 2:15/0
| | L 2:340/400
| | L 2:340/1101
| L 2:229/307
| + 2:15/0Except, a lot of the above should be zone 1. I also think there was
| | L 2:340/400
| | L 2:340/1101
| L 2:229/307
one or more zone 3 addresses in your tree too, that were shown as Z2.
Hello Nil,
On Wed, 01 May 2024 18:29:00 +0300, you wrote to Fidotest Tree:
This is how it looks from my node.
$ hpttree -d 30 fidotest
hpttree/lnx 1.9
Distribution tree of area fidotest for last 30 days
| | + 2:154/10
+ 2:3634/12
| L 2:229/426
| + 2:342/200
| | L 2:342/201
| + 2:229/664
| + 2:15/0
| | L 2:340/400
| | L 2:340/1101
| L 2:229/307
Except, a lot of the above should be zone 1. I also think there was one
or more zone 3 addresses in your tree too, that were shown as Z2.
| + 2:15/0
| | L 2:340/400
| | L 2:340/1101
| L 2:229/307
Except, a lot of the above should be zone 1. I also think there
was one or more zone 3 addresses in your tree too, that were
shown as Z2.
It's a funny historical "bug", because looking at many SEEN-BYs you
have to guess which zone (of the four) it is now. HptTree seems to
default everything to z2.
Except, a lot of the above should be zone 1. I also think there was one or
more zone 3 addresses in your tree too, that were shown as Z2.
My fidotest robot strips the zone because of this. Someone should make hpttree to search the nodelist for the correct zone. ;)
>> Except, a lot of the above should be zone 1. I also think
>> there was one or more zone 3 addresses in your tree too, that
>> were shown as Z2.
TK> My fidotest robot strips the zone because of this. Someone
TK> should make hpttree to search the nodelist for the correct
TK> zone. ;)
I think you just volunteered yourself. ;)
I really appreciate the decision made at some point to have
network numbers unique across all zones.
Distribution tree of area fidotest for last 30 days
221/6
+ 154/10
| + 226/18
| L 3634/12
| L 135/115
+ 341/66
+ 221/1
| + 203/0
| | L 201/0
| | L 201/137
| + 320/219
| + 280/464
| | + 396/45
| | | L 387/18
| | + 240/1120
| | | + 291/111
| | | L 371/0
| | | L 371/52
| | + 310/31
| | L 633/280
| L 221/360
+ 301/1
| L 103/705
+ 341/234
L 218/840
L 218/700
L 229/426
+ 229/307
| L 229/308
L 229/664
Your robot can see the world through the small hole somewhere in the middle of a small Europe, whereas my robot have visibility into a huge country which covers both Europe and Asia, and as a result the output[...]
is a bit longer.
Distribution tree of area fidotest
2:5020/1042
+ 2:221/6
| + 2:341/234
| + 2:154/10
| | + 2:3634/12
| | | + 2:135/115
| | | | + 2:135/205
| | | | L 2:135/366
| | | L 2:123/160
| | + 2:2320/105
| | | L 2:2320/107
| | + 2:226/44
| | L 2:226/18
| + 2:221/1
| | + 2:203/0
| | | L 2:201/0
| | | L 2:201/137
| | + 2:280/464
| | | + 2:633/280
Your robot can see the world through the small hole somewhere in
a middle of a small Europe, whereas my robot have visibility
into the huge country which covers both Europe and Asia, and as a
result the output is a bit longer.
Distribution tree of area fidotest[...]
2:5020/1042
+ 2:221/6
| + 2:341/234
| + 2:154/10
| | + 2:3634/12
| | | + 2:135/115
| | | | + 2:135/205
| | | | L 2:135/366
| | | L 2:123/160
| | + 2:2320/105
| | | L 2:2320/107
| | + 2:226/44
| | L 2:226/18
| + 2:221/1
| | + 2:203/0
| | | L 2:201/0
| | | L 2:201/137
| | + 2:280/464
| | | + 2:633/280
Except yours thinks everyone is in zone 2....
| + 2:154/10
| | + 2:3634/12
| | | + 2:135/115
| | | | + 2:135/205
| | | | L 2:135/366
| | | L 2:123/160
| | + 2:2320/105
| | | L 2:2320/107
| | + 2:226/44
| | L 2:226/18
Except yours thinks everyone is in zone 2....
Very true. I have zero FNT peering with Z3, so my view of world is
limited but still a bit wider than the original post.
| + 2:154/10
| | + 2:3634/12
| | | + 2:135/115
| | | | + 2:135/205
| | | | L 2:135/366
| | | L 2:123/160
| | + 2:2320/105
| | | L 2:2320/107
| | + 2:226/44
| | L 2:226/18
Except yours thinks everyone is in zone 2....
Very true. I have zero FTN peering with Z3, so my view of world
is limited but still a bit wider than the original post.
Or Z1, apparently, since all of the above quoted links are Z1..
starting with my own. :(
| | + 2:280/464
| | | + 2:633/280
[...]
Except yours thinks everyone is in zone 2....
Very true. I have zero FNT peering with Z3, so my view of world is
limited but still a bit wider than the original post.
BTW, we can fix it by establishing a binkp link. if you are interested, netmail me the session/pkt/areafix pwd.
| | + 2:280/464
| | | + 2:633/280
[...]
Except yours thinks everyone is in zone 2....
Very true. I have zero FNT peering with Z3, so my view of world
is limited but still a bit wider than the original post.
Even so, 633/280 is a zone 3 system. %-)
BTW, we can fix it by establishing a binkp link. if you are
interested, netmail me the session/pkt/areafix pwd.
I doubt that would fix the issue, if the software is lacking in
knowing other zones.
| Sysop: | Saxainden |
|---|---|
| Location: | Littleton, CO |
| Users: | 30 |
| Nodes: | 10 (2 / 8) |
| Uptime: | 23:49:24 |
| Calls: | 355 |
| Messages: | 37,119 |