Re: patch: bad ipv6 neighbor solicitation

2009-12-15 Thread Dennis Glatting
This patch works for me. On Mon, 14 Dec 2009, Li, Qing wrote: Please find the more proper fix at http://people.freebsd.org/~qingli/nd6-patch.diff I realized I was slightly off in my previous email after I spent a bit more time looking through the problem. Both prefixes are present

Re: patch: bad ipv6 neighbor solicitation

2009-12-15 Thread Tom Pusateri
f Li, Qing >> Sent: Tuesday, December 15, 2009 1:46 PM >> To: Tom Pusateri >> Cc: freebsd-...@freebsd.org; freebsd-stable@freebsd.org >> Subject: RE: patch: bad ipv6 neighbor solicitation >> >> Thanks for reporting back. I asked you for a routing table dump >>

RE: patch: bad ipv6 neighbor solicitation

2009-12-15 Thread Li, Qing
ebsd- > sta...@freebsd.org] On Behalf Of Li, Qing > Sent: Tuesday, December 15, 2009 1:46 PM > To: Tom Pusateri > Cc: freebsd-...@freebsd.org; freebsd-stable@freebsd.org > Subject: RE: patch: bad ipv6 neighbor solicitation > > Thanks for reporting back. I asked you for a routing table du

RE: patch: bad ipv6 neighbor solicitation

2009-12-15 Thread Li, Qing
gt; Cc: freebsd-...@freebsd.org; freebsd-stable@freebsd.org > Subject: Re: patch: bad ipv6 neighbor solicitation > > I didn't think this routing patch was related to the "bad neighbor > solicitation messages" as suggested in the subject field but I tried it > anyway. It d

Re: patch: bad ipv6 neighbor solicitation

2009-12-15 Thread Tom Pusateri
I didn't think this routing patch was related to the "bad neighbor solicitation messages" as suggested in the subject field but I tried it anyway. It does not fix my IPv6 problem. I still get "bad neighbor solicitation messages" and freebsd 8 doesn't respond to 4/5 IPv6 pings. Thanks, Tom On D

patch: bad ipv6 neighbor solicitation

2009-12-14 Thread Li, Qing
Please find the more proper fix at http://people.freebsd.org/~qingli/nd6-patch.diff I realized I was slightly off in my previous email after I spent a bit more time looking through the problem. Both prefixes are present but one was marked off-link due to the fact only a single prefix rou