On 23 Jun 2015, at 15:29, Ondrej Zajicek wrote:
>
> Well, they should ignore it if they don't know/like it.
Yes, for sure!
> The problem is specific to IPv6 sessions, IPv4 sessions works fine?
Well... actually no, I had to "enable route refresh off;” on the same peers in
IPv4 and IPv6 :
IPv4 se
Greetings,
If this is truly a bug in Juniper, I'd be happy to log the bug with them.
We'd just need to supply them the tcpdump and reference the RFC where it
says this isn't mandatory.
Kind regards,
Dave Seddon
On Tue, Jun 23, 2015 at 5:37 AM, Raphael Mazelier wrote:
>
>
> Le 23/06/15 15:29, O
Le 23/06/15 15:29, Ondrej Zajicek a écrit :
I considered such option for 1.5.0 but thought it would be unnecessary.
I will probably reconsider that.
It seems that juniper router misbehave on this. So it could be a good one.
--
Raphael Mazelier
On Tue, Jun 23, 2015 at 01:47:41PM +0200, Arnaud Fenioux wrote:
> Hello,
>
> We updated one of our Route-server and noticed that a few number of our peers
> could not establish IPv6 sessions with us.
> The reason in the logs was "Received: Required capability missing???.
>
> After some tcpdump a
Hello,
We updated one of our Route-server and noticed that a few number of our peers
could not establish IPv6 sessions with us.
The reason in the logs was "Received: Required capability missing”.
After some tcpdump and investigation we found that Enhanced Route Refresh
Capability was newly adve
