Re: error with ndp only on sparc64

"mailing BSD" <[email protected]>
Newsgroups gmane.os.openbsd.sparc
Message-ID <[email protected]>
Hello,

I am now on OpenBSD 4.6 on sparc64, but can't use ndp.
now ndp work well, but I can't add the route after ndp :(

[root@fw-new ndp]# ndp -s 2a01:e35:2433:500:20e:a6ff:fe23:be89
00:03:ba:04:ef:fa proxy
[root@fw-new ndp]# route add -inet6  2a01:e35:2433:500:20e:a6ff:fe23:be89
fec0::20e:a6ff:fe23:be89
route: writing to routing socket: File exists
add host 2a01:e35:2433:500:20e:a6ff:fe23:be89: gateway
fec0::20e:a6ff:fe23:be89: File exists

Can you help me?

Thank's

On Mon, 9 Jun 2008 17:56:27 +0200, Claudio Jeker wrote
> On Fri, May 30, 2008 at 11:02:52AM +0200, mailing BSD wrote:
> > Hello,
> > 
> > I try to configure my french FREE IPV6 access.
> > I may use proxy ndp because I have just a /64 ipv6 network
> > and I use an OpenBSD FW.
> > 
> > I try with a i386 openbsd FW, and ndp work well.
> > 
> > But,with my Netra AC200 and OpenBSD 4.3, I have this error:
> > 
> > # ndp -s 2a01:e35:2433:500:20e:a6ff:fe23:be89 00:03:ba:04:ef:f2 proxy    
       
> > ndp: writing to routing socket: Network is unreachable
> > 
> > 00:03:ba:04:ef:f2 is the mac addr on my external interface
> > and 2a01:e35:2433:500:20e:a6ff:fe23:be89 is the internal IPV6 addr
> > 
> > If I try to configure the route before ndp:
> > 
> > # route add -inet6  2a01:e35:2433:500:20e:a6ff:fe23:be89
fec0::20e:a6ff:fe23:be89
> > add host 2a01:e35:2433:500:20e:a6ff:fe23:be89: gateway
fec0::20e:a6ff:fe23:be89
> > # ndp -s 2a01:e35:2433:500:20e:a6ff:fe23:be89 00:03:ba:04:ef:f2 proxy
> > set: cannot configure a new entry
> > 
> > It is a SPARC64 bug? I ask it on IPV6 list, but no reply.
> > Am I alone with this error?
> >
> 
> This was a bug in ndp that caused every 64bit architecture to fail.
> But it is fixed now in rev. 1.42 of ndp.c.
> How they came up with a 28byte long sockaddr_in6 is beyond my imagination.
> 
> -- 
> :wq Claudio


--
Eric JANTZEN - http://cv.jantzen.fr
Lyon
FRANCE
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.