Date: Thu, 12 Jul 2018 16:35:22 -0600 From: Alan Somers <asomers@freebsd.org> To: "Frank de Bot (lists)" <lists@searchy.net> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: Removing IPv6 address causes all IPv6 traffic to stop working Message-ID: <CAOtMX2juZihud=bF6%2BaKSTUvZ%2BxiExLzKx%2BiCAnEGB-S-y2HAg@mail.gmail.com> In-Reply-To: <0a96ce18-982e-ac9b-eaab-d9cf2df02d73@searchy.net> References: <0a96ce18-982e-ac9b-eaab-d9cf2df02d73@searchy.net>
next in thread | previous in thread | raw e-mail | index | archive | help
How did you assign the jails' IPv6 addresses in the first place? The usual way is to assign them as /128 aliases, in which case the command to remove them would include a "/128", not "/48". I think when you're deleting a "/48" you're also removing some routes that the jail host is using. -Alan On Thu, Jul 12, 2018 at 4:30 PM, Frank de Bot (lists) <lists@searchy.net> wrote: > On a older server running FreeBSD 10.2 i have a number of jails. For > migration to FreeBSD I'm planning to shutdown the jail, move the data to > the new server and spin up the jail there. IP addresses are alse moved. > > When I remove an IPv6 address with the following command 'ifconfig em0 > inet6 v6address/48 delete', all IPv6 traffic on the server stops > working. I can reach IPv6 from outside to the server and from the server > to outside, but everything on the server (jail to jail for example) > immediatly stops working. IPv4 works normally > Unfortunately it's not feasible to bing-bang migrate everything, > ignoring ipv6 is not possible because a lot of the jails interact with > each other with ipv6 (some even exclusivly) > > What can cause this? > > > Regards, > > Frank de Bot > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2juZihud=bF6%2BaKSTUvZ%2BxiExLzKx%2BiCAnEGB-S-y2HAg>