From mboxrd@z Thu Jan 1 00:00:00 1970 From: filipe abrantes Date: Mon, 20 Sep 2004 10:54:06 +0000 Subject: Re: [LARTC] IPv6 routing question - corrected Message-Id: <414EB6CE.4020006@netcabo.pt> MIME-Version: 1 Content-Type: multipart/mixed; boundary="------------030306090208010501030302" 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. --------------030306090208010501030302 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Hi, It's like this: A eth0 ====== eth3 B eth1 eth0: 192.168.0.2/24 2020::2/128 eth3 192.168.0.254/24 2020::254/128 eth1 192.168.30.254 3030::254/128 I'm trying to ping B's eth1 address from A, but it only works in IPv4, in IPv6 it does not work, unless i put a route via eth3's address. regards Filipe Alexander Samad wrote: >Hi > >Sorry having a bit of a problem reading your diagram but is the >destination on the wire or is routed via box B > >have you tried a tcpdump on B to see what it sees ? > >A > > >On Mon, Sep 20, 2004 at 03:40:39AM +0100, filipe abrantes wrote: > > >>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 / _L_A_R_T_C_@_m_a_i_l_m_a_n_._d_s_9_a_._n_l >> _h_t_t_p_:_/_/_m_a_i_l_m_a_n_._d_s_9_a_._n_l_/_m_a_i_l_m_a_n_/_l_i_s_t_i_n_f_o_/_l_a_r_t_c HOWTO: _h_t_t_p_:_/ >> _/_l_a_r_t_c_._o_r_g_/ >> >> _______________________________________________ >> LARTC mailing list / _L_A_R_T_C_@_m_a_i_l_m_a_n_._d_s_9_a_._n_l >> _h_t_t_p_:_/_/_m_a_i_l_m_a_n_._d_s_9_a_._n_l_/_m_a_i_l_m_a_n_/_l_i_s_t_i_n_f_o_/_l_a_r_t_c HOWTO: _h_t_t_p_:_/ >> _/_l_a_r_t_c_._o_r_g_/ >> >> >> > > > --------------030306090208010501030302 Content-Type: text/html; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Hi,

It's like this:
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0
A eth0 =3D=3D=3D=3D=3D=3D eth3=A0 B eth1

eth0:
=A0=A0=A0 192.168.0.2/24
=A0=A0=A0 2020::2/128

eth3
=A0=A0=A0 192.168.0.254/24
=A0=A0=A0 2020::254/128

eth1
=A0=A0=A0 192.168.30.254
=A0=A0=A0 3030::254/128


I'm trying to ping B's eth1 address from A, but it only works in IPv4, in IPv6 it does not work, unless i put a route via eth3's address.

regards

Filipe

Alexander Samad wrote: 
Hi

Sorry having a bit of a problem reading your diagram but is the
destination  on the wire or is routed via box B

have you tried a tcpdump on B to see what it sees ?

A


On Mon, Sep 20, 2004 at 03:40:39AM +0100, filipe abrantes wrote:
  
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
          +-------+
                        |          |=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
          |                                                     |   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=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 / _=08L_=08A_=08R_=08T_=08C_=08@_=08m_=08a_=08=
i_=08l_=08m_=08a_=08n_=08._=08d_=08s_=089_=08a_=08._=08n_=08l
          _=08h_=08t_=08t_=08p_=08:_=08/_=08/_=08m_=08a_=08i_=08l_=08m_=08a=
_=08n_=08._=08d_=08s_=089_=08a_=08._=08n_=08l_=08/_=08m_=08a_=08i_=08l_=08m=
_=08a_=08n_=08/_=08l_=08i_=08s_=08t_=08i_=08n_=08f_=08o_=08/_=08l_=08a_=08r=
_=08t_=08c HOWTO: _=08h_=08t_=08t_=08p_=08:_=08/
          _=08/_=08l_=08a_=08r_=08t_=08c_=08._=08o_=08r_=08g_=08/

          _______________________________________________
          LARTC mailing list / _=08L_=08A_=08R_=08T_=08C_=08@_=08m_=08a_=08=
i_=08l_=08m_=08a_=08n_=08._=08d_=08s_=089_=08a_=08._=08n_=08l
          _=08h_=08t_=08t_=08p_=08:_=08/_=08/_=08m_=08a_=08i_=08l_=08m_=08a=
_=08n_=08._=08d_=08s_=089_=08a_=08._=08n_=08l_=08/_=08m_=08a_=08i_=08l_=08m=
_=08a_=08n_=08/_=08l_=08i_=08s_=08t_=08i_=08n_=08f_=08o_=08/_=08l_=08a_=08r=
_=08t_=08c HOWTO: _=08h_=08t_=08t_=08p_=08:_=08/
          _=08/_=08l_=08a_=08r_=08t_=08c_=08._=08o_=08r_=08g_=08/

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