Sometimes you are not happy if you get more than you want....

[Vesna Manojlovic]

Hi Harald,

I will try to troubleshoot this for you, but I might be wrong...

On 4/15/11 10:02 AM, Harald Michl wrote:

 > 1. is it a rtconfig-bug or is something wrong with the autnum-object
 > of AS1120?

> echo "@RtConfig import AS1120 193.203.0.25 AS16099 193.203.0.155" | ./rtconfig -disable_access_list_cache -cisco_skip_route_maps -cisco_use_prefix_lists
> 
> I'd expect _one_ prefix-list beeing generated - currently only for IPv4. But I get two:
> 
> no ip prefix-list pl100
> ip prefix-list pl100 permit 194.153.217.0/24
> ip prefix-list pl100 deny 0.0.0.0/0 le 32

this one is from policy the line in your object:

import:         from AS16099 action pref=100; accept AS16099

And this one...
> !
> no ip prefix-list pl101
> ip prefix-list pl101 permit 4.53.84.128/26
> ip prefix-list pl101 permit 4.53.146.192/26
> ip prefix-list pl101 permit 77.80.0.0/17
> [snip]
> ip prefix-list pl101 permit 217.116.64.0/20
> ip prefix-list pl101 permit 217.149.224.0/20
> ip prefix-list pl101 deny 0.0.0.0/0 le 32

is maybe from this policy line:
import:         from AS-ACO-IX action pref=100; accept AS-ACO-IX

AS16099 is a member of AS-ACO-IX ,
so *maybe* the "rtconfig" picks it up, and expands for the whole set??
(e.g. 77.80/17 is also announced by the member of ACO-IX set...)

I find that weird explanation, but as a famous fictional character would 
say: "When you have eliminated the impossible, whatever remains, however 
improbable, must be the truth".

Hmm, I think there are few more things to be eliminated as impossible 
till we come up with the truth...

> 2. is there a newer release available than 5.0.0?

I think there is not.

> thanks in advance for any hints,
 > Harald

I hope this helps a little bit,
Vesna
RIPE NCC Trainer