[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bird-users
Subject:    Re: Incorrect manual next hop attribute
From:       Jordan <jgrigorov () neterra ! net>
Date:       2013-02-18 7:16:36
Message-ID: 5121D554.2010307 () neterra ! net
[Download RAW message or body]

Unfortunately changing it in the export filter also doesn't work.
In birdc command line I see the correctly modified next hop but the bgp 
update sends the local address.
Is there any other solution we can test?
If you plan to implement such an option to never touch the next hop 
address when should we expect it?
[prev in list] [next in list] [prev in thread] [next in thread]