[j-nsp] ipInIp interface got the same IPV6 address on both end?
zeng watchthinker
watchthinker at hotmail.com
Wed Nov 2 09:58:11 EST 2005
Your explaination of OSPF3 sounds correct because I can see the neighbor is
built on the RID.
I should spend more time in RFCs.....
>From: "Rafal Szarecki (WA/EPO)" <rafal.szarecki at ericsson.com>
>To: "zeng watchthinker"
<watchthinker at hotmail.com>,<Guy.Davies at telindus.co.uk>
>CC: <juniper-nsp at puck.nether.net>
>Subject: RE: [j-nsp] ipInIp interface got the same IPV6 address on both
end?
>Date: Wed, 2 Nov 2005 15:39:00 +0100
>
>OSPFv3 use RID to run and build LSDB. The interface addressing is just
information carried by protocol. This is oposite to OSFPv2 and very
similiar to ISIS (IPv4). So this can be a reason of working OSPFv3 and not
working RIPng.
>
>In your case let's try to manualy assigne address to link and do not use
eui-64 automagic.
>
>Rafał Szarecki JNCIE
>
>skype me <callto://Rafal_Szarecki/>
>
>
>
> > -----Original Message-----
> > From: juniper-nsp-bounces at puck.nether.net
> > [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of
> > zeng watchthinker
> > Sent: Wednesday, November 02, 2005 3:32 PM
> > To: Guy.Davies at telindus.co.uk
> > Cc: juniper-nsp at puck.nether.net
> > Subject: RE: [j-nsp] ipInIp interface got the same IPV6
> > address on both end?
> >
> > Actually I want to setup a tunnel between 2 logical routers
> > and use IPV4 tunnneling IPV6 traffic.
> >
> > It is strange I can have OSPF3 get to full status and learn
> > routes while with RIPng I learn no route even I use a policy
> > to export local routes to RIPng...
> >
> > juniper at p3# run show ripng neighbor logical-router r1
> > Source Dest
> > In
> > Neighbor State Address Address
> > Send Recv Met
> > -------- ----- ------- -------
> > ---- ---- ---
> > ip-0/0/0.0 Up fe80::2a0:a5ff:fe12:6920 ff02::9
> > yes yes 1
> >
> > [edit logical-routers]
> > juniper at p3# run show ripng neighbor logical-router r2
> > Source Dest
> > In
> > Neighbor State Address Address
> > Send Recv Met
> > -------- ----- ------- -------
> > ---- ---- ---
> > ip-0/0/0.1 Up fe80::2a0:a5ff:fe12:6920 ff02::9
> > yes yes 1
> >
> > [edit logical-routers]
> > juniper at p3# show r1 protocols ospf3
> > area 0.0.0.0 {
> > interface ip-0/0/0.0;
> > }
> >
> > [edit logical-routers]
> > juniper at p3# show r2 protocols ospf3
> > area 0.0.0.0 {
> > interface ip-0/0/0.1;
> > }
> >
> > [edit logical-routers]
> > juniper at p3# run show ospf3 neighbor logical-router r1
> > ID Interface State Pri Dead
> > 10.0.6.2 ip-0/0/0.0 Full 128 36
> > Neighbor-address fe80::2a0:a5ff:fe12:6920
> >
> > [edit logical-routers]
> > juniper at p3# run show ospf3 neighbor logical-router r2
> > ID Interface State Pri Dead
> > 10.0.6.1 ip-0/0/0.1 Full 128 37
> > Neighbor-address fe80::2a0:a5ff:fe12:6920
> >
> >
> > >From: "Guy Davies" <Guy.Davies at telindus.co.uk>
> > >To: "zeng watchthinker" <watchthinker at hotmail.com>
> > >Subject: RE: [j-nsp] ipInIp interface got the same IPV6
> > address on both
> > end?
> > >Date: Wed, 2 Nov 2005 14:16:34 -0000
> > >
> > >Shouldn't the network element of the address (i.e. the first
> > 64 bits)
> > >be
> > unique? A /64 is associated with a single link. You're
> > creating two separate links here unless you're trying to
> > create an ip-in-ip tunnel between your two logical routers on
> > the same physical router??? You've created the them both
> > using the same stub. The fact that the eui-64 mechanism
> > creates the same address is not entirely unexpected because I
> > suspect it uses a single MAC to derive the addresses
> > (although it would have been handy in some ways for the
> > device to create different host portions of the address).
> > >
> > >Rgds,
> > >
> > >Guy
> > >
> > >-----Original Message-----
> > >From: juniper-nsp-bounces at puck.nether.net
> > [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of
> > zeng watchthinker
> > >Sent: 02 November 2005 14:04
> > >To: juniper-nsp at puck.nether.net
> > >Subject: [j-nsp] ipInIp interface got the same IPV6 address
> > on both end?
> > >
> > >I made 2 ipip interface in 2 logical routers. While I find
> > the same IPV6
> > address is created on these two ipip interface.
> > >
> > >Seems there is some problem?
> > >
> > >[edit logical-routers]
> > >juniper at p3# show r1 interfaces
> > >ip-0/0/0 {
> > > unit 0 {
> > > tunnel {
> > > source 10.0.4.5;
> > > destination 10.0.4.6;
> > > }
> > > family inet {
> > > address 1.1.1.1/30;
> > > }
> > > family inet6 {
> > > address 2:10::/64 {
> > > eui-64;
> > > }
> > > }
> > > }
> > >}
> > >
> > >juniper at p3# show r2 interfaces
> > >ip-0/0/0 {
> > > unit 1 {
> > > tunnel {
> > > source 10.0.4.6;
> > > destination 10.0.4.5;
> > > }
> > > family inet {
> > > address 1.1.1.2/30;
> > > }
> > > family inet6 {
> > > address 2:10::/64 {
> > > eui-64;
> > > }
> > > }
> > > }
> > >
> > >juniper at p3# run show interfaces terse
> > >Interface Admin Link Proto Local Remote
> > >gr-0/0/0 up up
> > >ip-0/0/0 up up
> > >ip-0/0/0.0 up up inet 1.1.1.1/30
> > > inet6 2:10::2a0:a5ff:fe12:6920/64
> > > fe80::2a0:a5ff:fe12:6920/64
> > >ip-0/0/0.1 up up inet 1.1.1.2/30
> > > inet6 2:10::2a0:a5ff:fe12:6920/64
> > > fe80::2a0:a5ff:fe12:6920/64
> > >
> > >_________________________________________________________________
> > >享用世界上最大的电å邮件系统†MSN Hotmailã€
http://www.hotmail.com
> > >
> > >_______________________________________________
> > >juniper-nsp mailing list juniper-nsp at puck.nether.net
> > http://puck.nether.net/mailman/listinfo/juniper-nsp
> > >
> > >This e-mail is private and may be confidential and is for
> > the intended
> > recipient only. If misdirected, please notify us by
> > telephone and confirm
> > that it has been deleted from your system and any copies
> > destroyed. If you
> > are not the intended recipient you are strictly prohibited
> > from using,
> > printing, copying, distributing or disseminating this e-mail or any
> > information contained in it. We use reasonable endeavours to
> > virus scan
> > all e-mails leaving the Company but no warranty is given that
> > this e-mail
> > and any attachments are virus free. You should undertake
> > your own virus
> > checking. The right to monitor e-mail communications through
> > our network
> > is reserved by us.
> > >
> > >
> >
> > _________________________________________________________________
> > å…费下载 MSN Explorer: http://explorer.msn.com/lccn
> >
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > http://puck.nether.net/mailman/listinfo/juniper-nsp
> >
_________________________________________________________________
ÏíÓÃÊÀ½çÉÏ×î´óµÄµç×ÓÓʼþϵͳ¡ª MSN Hotmail¡£ http://www.hotmail.com
More information about the juniper-nsp
mailing list