netdev
[Top] [All Lists]

Re: problem with nat-pt - linux

To: Ravikanth Samprathi <rsamprat@xxxxxxxxx>
Subject: Re: problem with nat-pt - linux
From: Pekka Savola <pekkas@xxxxxxxxxx>
Date: Thu, 10 May 2001 20:50:17 +0300 (EEST)
Cc: <netdev@xxxxxxxxxxx>
In-reply-to: <4.3.2.7.2.20010510101741.02094e78@xxxxxxxxxxxxxxxxxxxxx>
Sender: owner-netdev@xxxxxxxxxxx
On Thu, 10 May 2001, Ravikanth Samprathi wrote:
> SETUP:-
> -------------
> I have 2 hosts h1 and h2 both linux-2.4.0.
> h1 is ipv6.
> h2 is ipv4 and ipv6 dual stack.
> in h1, eth0 is ipv6 (fec0::2/96).
> in h2, eth1 is ipv6 (fec0::1/96) and eth2 is ipv4 (10.0.0.1/16).
>
[snip]
> I added a static route in routing table of h1
> route -A inet6 add fec0:0:0:0:0:ffff:10.0.0.1/96 dev eth0
>
> PROBLEM:-
> ------------------
> I am not able to talk (ping6) with eth2-of-h2 from eth0-of-h1.
> Ping6 from h1:-
> ping6 fec0:0:0:0:0:ffff:10.0.0.1
>
> OUTPUT:-
> ---------------
> This is the output of ping6 at h1:-
> PING fec0:0:0:0:0:ffff:10.0.0.1(fec0:0:0:0:0:ffff:a00:1) 56 bytes
>  From ::1: Destination unreachable: Address unreachable
[snip]
>
> This is the output of tcpdump from eth1 of h2:-
> 08:43:35:273492 fec0::2 > ff02::1:ff00:1: icmp6: neighbor sol:
> who has fec0::ffff:a00:1
[snip]

It would appear to me that your route or h2 configuration is wrong; you're
telling h1 that fec0:0:0:0:0:ffff::/96 is on-link, even though the address
you're trying to ping belongs to the other interface on the dual-stack
host.  This causes neighbor solicitations fail.

If you change the route so that the address you're trying to ping is
directed to be sent to fec0::1/96, the dual-stack host interface address,
this should work fine.

Never used NAT-PT on Linux though, so if this is the expected
configuration, can't help..

-- 
Pekka Savola                 "Tell me of difficulties surmounted,
Netcore Oy                   not those you stumble over and fall"
Systems. Networks. Security.  -- Robert Jordan: A Crown of Swords


<Prev in Thread] Current Thread [Next in Thread>