Katie Thanks for this enlightening reply.

-----Original Message----- From: Katie Petrusha [mailto:katie@ripe.net] Sent: 14 January 2004 11:38 To: Sven Huster Cc: irrtoolset@ripe.net Subject: Re: Problem with inet-rtr object

Dear Sven,

As far as I can see from your AS20738 aut-num object:

aut-num: AS20738 import: from AS2529 action pref=100; accept AS-DEMON AND NOT {0.0.0.0/0} export: to AS2529 announce AS-MAGMOM

Your peering description of AS2529 is not detailed enough for RtConfig to select your policy correctly. You may try something like:

import: from AS2529 <peerIP> at <localIP> action ... export: to AS2529 <peerIP> at <localIP> announce ...

...

If your aut-num doesn't have full specification of the peering, like:

import: from AS1 export to AS2

then all possible interface addresses will be selected from your inet-rtr object, as there's no indication which local/remote IP pair you use for the peer.

4 interfaces in the inet-rtr => 4 route-maps generated, quite logical Sven