From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alexander Samad <alex@samad.com.au>
Date: Mon, 20 Sep 2004 02:11:00 +0000
Subject: Re: [LARTC] IPv6 routing question - corrected
Message-Id: <20040920021100.GR1554@samad.com.au>
MIME-Version: 1
Content-Type: multipart/mixed; boundary="DNbkntcEGyiBe7B+"
List-Id: <lartc.vger.kernel.org>
References: <414E38FD.3080003@netcabo.pt>
In-Reply-To: <414E38FD.3080003@netcabo.pt>
To: lartc@vger.kernel.org


--DNbkntcEGyiBe7B+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

what do you get when you try=20


ip r g 3030::254

A

On Mon, Sep 20, 2004 at 02:57:17AM +0100, filipe abrantes wrote:
> * sorry for the other schema, it came out a mess. I hope this one is=20
> understandable.
>=20
> hi:
>=20
> I have this 2 boxes set up like this:
>=20
>=20
>              2020::2/128                      =20
> 2020::254/128                3030::254/128
>            192.168.0.2/24                 192.168.0.254/24          =20
> 192.168.30.254/24
>=20
>              +-------+   eth0                                eth3  =20
> +-------+
>               |          |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D |          |   eth1
>               |   A   =20
> |                                                     |   B    | ---- =20
>               |         =20
> |                                                     |          |
>             =20
> +-------+                                                   +-------+
>=20
>=20
>=20
>   A
>=20
> # ip r l
> 192.168.30.254 dev eth0  scope link
> 192.168.0.0/24 dev eth0  scope link
> 169.254.0.0/16 dev lo  scope link
> 127.0.0.0/8 dev lo  scope link
>=20
> # ip -6 r l
> 2020::254 dev eth0  metric 1024  mtu 1500 advmss 1440
> 3030::254 dev eth0  metric 1024  mtu 1500 advmss 1440
> (...plus link local and multicast routes)
>=20
>=20
>   B
>=20
> # ip r l
> 127.0.0.1 dev lo  scope link
> 192.168.0.0/24 dev eth3  proto kernel  scope link  src 192.168.0.254
> 192.168.30.0/24 dev eth1  proto kernel  scope link  src 192.168.30.254
>=20
> # ip -6 r l
> 2020::2 dev eth3  metric 1024  mtu 1500 advmss 1440 metric10 64
> (...plus link local and multicast routes)
>=20
> # cat /proc/sys/net/ipv4/ip_forward
> 1
> #cat /proc/sys/net/ipv6/conf/all/forwarding
> 1
>=20
>=20
> The problem is that i can ping 192.168.30.254 from A, but i can't ping=20
> 3030::254 from A, anyone has a clue why this happens? Is there any=20
> feature i need to turn on or anything misconfigured? Why does it work=20
> for IPv4 but not for IPv6?
>=20
>=20
> A -> B
>=20
> # ping 192.168.30.254
> PING 192.168.30.254 (192.168.30.254) 56(84) bytes of data.
> 64 bytes from 192.168.30.254: icmp_seq=3D0 ttl=3D64 time=3D0.175 ms
> 64 bytes from 192.168.30.254: icmp_seq=3D1 ttl=3D64 time=3D0.122 ms
>=20
> #ping6 3030::254
> PING 3030::254(3030::254) 56 data bytes
> From ::1 icmp_seq=3D0 Destination unreachable: Address unreachable
> From ::1 icmp_seq=3D1 Destination unreachable: Address unreachable
>=20
>=20
> Regards
>=20
> Filipe Abrantes
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>=20
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>=20

--DNbkntcEGyiBe7B+
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBTjw0kZz88chpJ2MRAv/jAJ9z0pJzcr6nRZkre1YZxxOnJoAUagCg4rqT
rDWzdVUIi/PKdjhCW54bVi8=
=G2Hw
-----END PGP SIGNATURE-----

--DNbkntcEGyiBe7B+--
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/