Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: nsp: juniper

Disappearing Routes (J/SRX)

 

 

nsp juniper RSS feed   Index | Next | Previous | View Threaded


crogers at sinewam

Jul 9, 2012, 5:09 PM

Post #1 of 2 (308 views)
Permalink
Disappearing Routes (J/SRX)

Hello everyone,

I have a /127 from a provider for a P2P link (for BGP) that I'm having some
trouble with... My provider is 2001:db8:: and I'm 2001:db8::1.

I added the IP to the interface, and as normal both the 2001:db8::/127
direct route and 2001:db8::1/128 local route are added to the inet6.0 route
table. However if I try to ping my own IP with that interface, I get the
following:

> ping 2001:db8::1
PING6(56=40+8+8 bytes) 2001:db8::1 --> 2001:db8::1
ping: sendmsg: Can't assign requested address
ping6: wrote 2001:db8::1 16 chars, ret=-1
ping: sendmsg: Can't assign requested address
ping6: wrote 2001:db8::1 16 chars, ret=-1
ping: sendmsg: Can't assign requested address
ping6: wrote 2001:db8::1 16 chars, ret=-1

After canceling the ping, both 2001:db8::/127 and 2001:db8::1/128 are no
longer listed in my inet6.0 table.

However, from start to finish outside hosts are able to ping my IP
(2001:db8::1).

I've tried this on both a SRX220 and J4350, running various versions of
11.4. All security features have been completely disabled, IPv6 is in
packet mode.

Is there something obvious that I've missed, or has anyone else seen this
before?

Thanks for any feedback
-Chris
_______________________________________________
juniper-nsp mailing list juniper-nsp [at] puck
https://puck.nether.net/mailman/listinfo/juniper-nsp


crogers at sinewam

Jul 9, 2012, 7:27 PM

Post #2 of 2 (289 views)
Permalink
Re: Disappearing Routes (J/SRX) [In reply to]

Yup, it was a duplicate address. Not sure how I missed it, but none the
less, thanks!

On Mon, Jul 9, 2012 at 8:31 PM, Diogo Montagner
<diogo.montagner [at] gmail>wrote:

> Check the show ipv6 neighbors and also the show interface.
>
> The show ipv6 neighbors will tell you if the ND is working fine. The
> show interface will tell you if it is disable due to DAD.
>
> HTH
> ./diogo -montagner
> JNCIE-M 0x41A
>
>
> On Tue, Jul 10, 2012 at 8:09 AM, Chris Rogers <crogers [at] sinewam> wrote:
> > Hello everyone,
> >
> > I have a /127 from a provider for a P2P link (for BGP) that I'm having
> some
> > trouble with... My provider is 2001:db8:: and I'm 2001:db8::1.
> >
> > I added the IP to the interface, and as normal both the 2001:db8::/127
> > direct route and 2001:db8::1/128 local route are added to the inet6.0
> route
> > table. However if I try to ping my own IP with that interface, I get the
> > following:
> >
> >> ping 2001:db8::1
> > PING6(56=40+8+8 bytes) 2001:db8::1 --> 2001:db8::1
> > ping: sendmsg: Can't assign requested address
> > ping6: wrote 2001:db8::1 16 chars, ret=-1
> > ping: sendmsg: Can't assign requested address
> > ping6: wrote 2001:db8::1 16 chars, ret=-1
> > ping: sendmsg: Can't assign requested address
> > ping6: wrote 2001:db8::1 16 chars, ret=-1
> >
> > After canceling the ping, both 2001:db8::/127 and 2001:db8::1/128 are no
> > longer listed in my inet6.0 table.
> >
> > However, from start to finish outside hosts are able to ping my IP
> > (2001:db8::1).
> >
> > I've tried this on both a SRX220 and J4350, running various versions of
> > 11.4. All security features have been completely disabled, IPv6 is in
> > packet mode.
> >
> > Is there something obvious that I've missed, or has anyone else seen this
> > before?
> >
> > Thanks for any feedback
> > -Chris
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp [at] puck
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
>
_______________________________________________
juniper-nsp mailing list juniper-nsp [at] puck
https://puck.nether.net/mailman/listinfo/juniper-nsp

nsp juniper RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.