From mboxrd@z Thu Jan 1 00:00:00 1970 From: filipe abrantes Date: Mon, 20 Sep 2004 02:40:39 +0000 Subject: Re: [LARTC] IPv6 routing question - corrected Message-Id: <414E4327.2010800@netcabo.pt> MIME-Version: 1 Content-Type: multipart/mixed; boundary="------------090804080700010103020402" List-Id: References: <414E38FD.3080003@netcabo.pt> In-Reply-To: <414E38FD.3080003@netcabo.pt> To: lartc@vger.kernel.org This is a multi-part message in MIME format. --------------090804080700010103020402 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit hi and thanks for replying, #ip r g 3030::254 3030::254 via 3030::254 dev eth0 src 2020::2 metric 0 cache mtu 1500 advmss 1440 Alexander Samad wrote: >what do you get when you try > > >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 >>understandable. >> >>hi: >> >>I have this 2 boxes set up like this: >> >> >> 2020::2/128 >>2020::254/128 3030::254/128 >> 192.168.0.2/24 192.168.0.254/24 >>192.168.30.254/24 >> >> +-------+ eth0 eth3 >>+-------+ >> | |======================= | | eth1 >> | A >>| | B | ---- >> | >>| | | >> >>+-------+ +-------+ >> >> >> >> A >> >># 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 >> >># 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) >> >> >> B >> >># 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 >> >># ip -6 r l >>2020::2 dev eth3 metric 1024 mtu 1500 advmss 1440 metric10 64 >>(...plus link local and multicast routes) >> >># cat /proc/sys/net/ipv4/ip_forward >>1 >>#cat /proc/sys/net/ipv6/conf/all/forwarding >>1 >> >> >>The problem is that i can ping 192.168.30.254 from A, but i can't ping >>3030::254 from A, anyone has a clue why this happens? Is there any >>feature i need to turn on or anything misconfigured? Why does it work >>for IPv4 but not for IPv6? >> >> >>A -> B >> >># 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=0 ttl=64 time=0.175 ms >>64 bytes from 192.168.30.254: icmp_seq=1 ttl=64 time=0.122 ms >> >>#ping6 3030::254 >>PING 3030::254(3030::254) 56 data bytes >>>From ::1 icmp_seq=0 Destination unreachable: Address unreachable >>>From ::1 icmp_seq=1 Destination unreachable: Address unreachable >> >> >>Regards >> >>Filipe Abrantes >>_______________________________________________ >>LARTC mailing list / LARTC@mailman.ds9a.nl >>http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ >> >>_______________________________________________ >>LARTC mailing list / LARTC@mailman.ds9a.nl >>http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ >> >> > > > --------------090804080700010103020402 Content-Type: text/html; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable hi and thanks for replying,

#ip r g 3030::254
3030::254 via 3030::254 dev eth0=A0 src 2020::2=A0 metric 0
=A0=A0=A0 cache=A0 mtu 1500 advmss 1440

Alexander Samad wrote:

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.

hi:

I have this 2 boxes set up like this:


             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

             +-------+   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
+-------+                                                   +-------+



  A

# 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

# 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)


  B

# 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

# ip -6 r l
2020::2 dev eth3  metric 1024  mtu 1500 advmss 1440 metric10 64
(...plus link local and multicast routes)

# cat /proc/sys/net/ipv4/ip_forward
1
#cat /proc/sys/net/ipv6/conf/all/forwarding
1


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?


A -> B

# 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

#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


Regards

Filipe Abrantes
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org=
/

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

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