Date: Fri, 23 Dec 2011 09:17:09 +0000 From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Marcin Cieslak <saper@saper.info> Cc: freebsd-net@freebsd.org Subject: Re: IPv6 not responding on some aliases (recent 8-stable) Message-ID: <AEB320C2-0345-436E-91B3-CBA760FEF37A@lists.zabbadoz.net> In-Reply-To: <slrnjf75bk.i0d.saper@saper.info> References: <slrnjf53o4.2d1.saper@saper.info> <F2005BBF-1808-4E63-B5F3-71361A95008A@lists.zabbadoz.net> <slrnjf6s3g.i0d.saper@saper.info> <C72FCBE6-AC3B-486B-B487-DA1FDA1F4474@lists.zabbadoz.net> <slrnjf75bk.i0d.saper@saper.info>
next in thread | previous in thread | raw e-mail | index | archive | help
On 22. Dec 2011, at 20:39 , Marcin Cieslak wrote:
>>> Bjoern A. Zeeb <bzeeb-lists@lists.zabbadoz.net> wrote:
>>> I initially thought it's a transport layer issue, since previously =
(before
>>> I changed configuration) 30%-50% SSH connection attempts succeeded
>>> (but prefix was wrong on the "primary" IPv6 address :1000).
>>> Now I get no packets on receiving side at all for those "broken" =
IPv6 addresses.
>>=20
>> Talk to ywhomever is providing in front of you to
>> 1) either relax nd6 table limits or
>> 2) to route a /64 to your host to only have 1 entry in the neighbour =
table.
>>=20
>> That's most likely the problem given my crystal ball and experience.
>=20
> Thank you for insightful analysis!=20
> Seems like this provider has some significant IPv6 takeup, which is
> good news - sorry for hassle, but problems started after upgrade.=20
>=20
> I'll talk to my upstream then, thanks!
Please let us know of the results, especially if my crystal ball was =
wrong.
/bz
--=20
Bjoern A. Zeeb You have to have visions!
Stop bit received. Insert coin for new address family.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AEB320C2-0345-436E-91B3-CBA760FEF37A>