I think you get a call to the callback when your peer sends an update, not when you send one.

Hello,

though for testing purposes I want to
initiate one update manually.

So if I understand you right it is not
possible to do this, so I need a second
peer to do this right?

Best regard
Marcus

Hello,

what about the function update() of the peer-object?


$peer->update($update);
[download]


Is it not for every peer-object you create? That is what I understand.

Best regards
Marcus

Hello,



thanks for your help. So my next try would be to set up another peer to update and check the results.

I keep this posting uptodate.

Thanks to all who give me some hints and advise!

Best regards
Marcus

Hello,

what I've done so far, I setup a remote peer and I could establish a connection to this remote peer, what I do not understand is how could I handle the incoming update messages?

My first suggestion was, that I could handle the incoming message, checked with tcpdump for incoming connections, via the update_callback subroutine, for testing purposes I put there a print line, however no call fo the callback-sub. What am I missing?

Thanks for your help in advance.

Best regards
Marcus

I don't know. I don't use Net::BGP. You could look through its tests, especially 30-Update.t looks as if it could relate to your problem.

# Constructor for BGP-Update-Object
my $update = Net::BGP::Update->new($nlri,$nlri_ref,$withdrawn_ref);

# Update peer object
print "Update peer object\n";
$peer->update($update);
[download]