Hi, i have a small problem with bgp (ROS 3.3), when using ipv6 and ipv4 at the same time.
I would establish a peer, between two routers (ROS on one, Quagga on the other one), and everything works, but just one at time..
I can estabilish and have the ipv4 session working, i can establish and have the ipv6 session working, but if both are enabled, the second session is not established.
Reported error is route,bgp,error Duplicate remote RouterId: xxx.xxx.xxx.xxx
Remote router id IS the same for both sessions, of course, as it's the same router.
Bye,
Ricky

shouldn 't you make just one session, and just enable the ipv6 adress family under the advanced tap.
we are doing it that way now.

I wanted to know if there's no other way.. usually (for what "usually" may mean when talking about ipv6 ) your router can work in dual-stack mode, having both ipv4 and ipv6 running at the same time.
Reason os pretty obvious i guess, you can keep running ipv4 and deploy ipv6.
If i can't do that with MT yet, i can live with it
i just needed to know if i'm doing something wrong

as far i know, you are running dual stacked, but enabling this in advanced.
the only thing different is that there is one BGP session both for ipv4 and ipv6.

on my junos and cisco IOS i can't run 2 sessions to the same router with the same id eather...

BUT

there is a way to get this running.

make a new BGP instance.
and run your IPV6 session in that instance.
that should works, as we have this running for a another reason with our iBGP.
there are some other issues to take care of when making muliple BGP instances, but just try it.

as far i know, you are running dual stacked, but enabling this in advanced.
the only thing different is that there is one BGP session both for ipv4 and ipv6.

on my junos and cisco IOS i can't run 2 sessions to the same router with the same id eather...

I can't tell how to do that on IOS and Junos, but actually you CAN run ipv4 and ipv6 on the same machine at the same time.. i usually run on quagga, and it does run too..

there is a way to get this running.

make a new BGP instance.
and run your IPV6 session in that instance.
that should works, as we have this running for a another reason with our iBGP.
there are some other issues to take care of when making muliple BGP instances, but just try it.

Yes and no...i thought to run two bgp instances.. it's no problem, as the "propagation" problems within multiple instances can be safely ignored, as anyway ipv4 and ipv6 instances are independent from each other.
The problem comes when you have connect the router to a non mt router.
Since on quagga (but i think on cisco and juniper too), router id is single, the mt box refuses to establish the second session as remote router id is duplicated...

point taken, our iBGP sessions are all on MT routers...

maybe a idea as MT BGP is a bit buggy.... setup a quagga box for your sessions and use BGP reflection to your MT boxes.
have'nt done that but should work....