Date: Thu, 6 May 2010 16:08:22 -0700 From: "Loren M. Lang" <lorenl@north-winds.org> To: freebsd-net@freebsd.org Subject: IPv6 Mobility through a FreeBSD Router Message-ID: <20100506230822.GA19497@alzatex.com>
next in thread | raw e-mail | index | archive | help
--XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I have a Linux server acting as a Home Agent for IPv6 Mobility and a separate Linux client acting as a Mobile Node with a FreeBSD 7.2 router in-between. The FreeBSD router itself is not participating in mobility, it's just the Foreign Router that the Mobile Node happens to be attached to. When I initiate IPv6 Mobility on the Linux client I see it sending out IPv6 Mobility Binding Updates to the Home Agent and I see Binding Acknowledgements coming back in on the outside interface of the FreeBSD router, but they don't appear on the inside interface as if FreeBSD is refusing to route them. The only difference is that Binding Acknowledgements use a Type 2 Mobility Routing Header. Does FreeBSD drop all IPv6 packets using a Routing Header even when it's not Type 0 and not destined for FreeBSD? --=20 Loren M. Lang lorenl@north-winds.org http://www.north-winds.org/ Public Key: ftp://ftp.north-winds.org/pub/lorenl_pubkey.asc Fingerprint: 10A0 7AE2 DAF5 4780 888A 3FA4 DCEE BB39 7654 DE5B --XsQoSWH+UP9D9v3l Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFL40vmjRsbG+gOq+wRAg2+AKC0HZdtgA0cMrLZCykZEHJdj4ykJACbBI/F jF1E5wGU/UcU6BxEC/D5ikk= =tzfh -----END PGP SIGNATURE----- --XsQoSWH+UP9D9v3l--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100506230822.GA19497>