Date: Tue, 26 Apr 2022 01:25:14 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 263288] IPv6 system not responding to Neighbor Solicitation Message-ID: <bug-263288-7501-YG2LTW3Kp8@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-263288-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-263288-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263288 --- Comment #17 from wcarson.bugzilla@disillusion.net --- (In reply to Zhenlei Huang from comment #16) Hmm, I don't think 2600:3c00::/64 is dedicated to my host, however 2600:3c00:e000:0137::/64 is. Here is the response I got back from my provid= er: ##### To be perfectly clear: 2600:3c00::/64 is shared insofar as other customers = have VMs with IPv6 addresses on the same IPv6 subnet. Your SLAAC-assigned IPv6 address - 2600:3c00::f03c:91ff:feb0:a56f - is a /128 range, which essential= ly makes it a single IPv6 address which only your VM can use. The addresses wi= thin your /64 range - 2600:3c00:e000:0137::/64 - can only be used by the VM it's routed towards. ##### --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-263288-7501-YG2LTW3Kp8>