[Jool-list] HINT: Jool capability
Alberto Leiva
ydahhrk at gmail.com
Mon May 18 13:43:38 CDT 2020
> 1. Node B is not under my control i know its ipv4 addres only. Like 104.x.x.x
1.1. Then what is the problem with "ping6 2001:ab5::104.X.X.X"?
> 2. Node A and jool machine are in my internal network as range for ipv4 is 172.x.x.x and ipv6 is 2001:xxxx....
2.1. If you ping 104.x.x.x from Jool, does it work?
2.2. If you ping ::ffff:68c6:b6f7 from Jool, does it work?
On Mon, May 18, 2020 at 1:35 PM Kunal Chauhan <atkunalchauhan at gmail.com> wrote:
>
> Alberto,
>
> Actually i might have missed to explain below points for latest scenerio.
>
> 1. Node B is not under my control i know its ipv4 addres only. Like 104.x.x.x
>
> So i can not add any thing at node B side
>
> 2. Node A and jool machine are in my internal network as range for ipv4 is 172.x.x.x and ipv6 is 2001:xxxx....
>
> On 18 May 2020 11:47 p.m., "Alberto Leiva" <ydahhrk at gmail.com> wrote:
>>
>> Ok, then enable IPv6 forwarding in Jool if you haven't already:
>>
>> kunal at JOOL:~# sysctl -w net.ipv6.conf.all.forwarding=1
>>
>> And make sure A and B can reach each other through Jool's machine. For example:
>>
>> kunal at A:~# ip route add ::ffff:68c6:b6f7 via <Jool machine's
>> A-facing IPv6 address>
>>
>> ---
>>
>> kunal at B:~# ip route add 2001:ab5:0:1::/64 via <Jool machine's
>> B-facing IPv6 address>
>>
>> Then, do the ping:
>>
>> kunal at A:~# ping6 ::ffff:68c6:b6f7
>>
>> Which should create the following packet flow:
>>
>> 1. A sends ping request "2001:ab5:0:1::x -> ::ffff:68c6:b6f7"
>> 2. Jool does not translate that packet, but its Linux host instead
>> routes it normally towards B.
>> 3. B replies "::ffff:68c6:b6f7 -> 2001:ab5:0:1::x"
>> 4. Jool does not translate that packet, but its Linux host instead
>> routes it normally towards A.
>> 5. A receives the reply.
More information about the Jool-list
mailing list