Date: Fri, 12 Oct 2007 13:55:42 -0700 From: "Kevin Oberman" <oberman@es.net> To: "Jiusheng Liu" <liujiusheng@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: When interface becomes down, ipv6 direct routes are not deleted Message-ID: <20071012205542.248944500E@ptavv.es.net> In-Reply-To: Your message of "Fri, 12 Oct 2007 22:38:04 %2B0800." <b711fdc0710120738l491c37f6h1899a07ef19eff64@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_1192222542_15222P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Fri, 12 Oct 2007 22:38:04 +0800 > From: "Jiusheng Liu" <liujiusheng@gmail.com> > Sender: owner-freebsd-net@freebsd.org > > When I make the interface down by ifconfig, all the direct routes are > not deleted. And the addresses state are not changed. And I can even > ping those address in this interface. > Is this correct, or a bug? I test it in vmware virtual machine. > > This is my first post to this mailing list, and I don't know if it is > the right place. > Any ideas are appreciated, thank you in advance. Looks like the right place to me. There has been some discussion about the deletion of routes whan an interface is configured DOWN, but there are several problems that this causes. Basically, ifconfig should not touch routing information. I'm not sure whet you mean by "the addresses state". The address of an interface should certainly not be changed by setting it DOWN. It should retain the address since it should not need reconfiguration when it is set to UP. (DHCP assigned addresses are an exception to this.) You should not be able to ping the down interface. If you really are, something is broken, although it may have to do with the vmware operation. I don't know much detail about how they network between host and client system. If they are really using the loopback, then things pings would work. And putting an entry in /etc/hosts for the local system name that points to 127.0.0.1 is fairly common and is required for many software things to work right. An external system should not be able to ping that interface. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1192222542_15222P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFHD99Okn3rs5h7N1ERAhJeAJwLW/mGdnJb4j4bud+2EDBoVflm7wCaAth7 8Va9BiMQ8NM1YyVeCUTaqIE= =UX43 -----END PGP SIGNATURE----- --==_Exmh_1192222542_15222P--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071012205542.248944500E>