<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div><font face="sans-serif">I'd be happy to continue working on this if it can benefit others, but I had to bail and add dual stack to the node (against my wishes).</font></div><div><br></div><div>Thanks,</div><div>Kurt</div><div><br></div><div id="composer_signature"><div style="font-size:85%;color:#575757" dir="auto">Sent from Samsung Galaxy smartphone.</div></div><div><br></div><div style="font-size:100%;color:#000000"><!-- originalMessage --><div>-------- Original message --------</div><div>From: Alberto Leiva <ydahhrk@gmail.com> </div><div>Date: 12/22/17 10:29 (GMT-06:00) </div><div>To: Kurt Lund <kurt@realacquisitions.com> </div><div>Cc: jool-list@nic.mx </div><div>Subject: Re: [Jool-list] Help with routing loop? </div><div><br></div></div>> I think this is a separate problem. Let me see if I can reproduce it.<br><br>Wait. It returns me an empty file even when I wget via IPv4 directly.<br><br>I think there's something funny going on with this service.<br><br>On Fri, Dec 22, 2017 at 10:23 AM, Alberto Leiva <ydahhrk@gmail.com> wrote:<br>>> Now when I "tracepath6 -n 2000:ffff::73.xxx.67.1 from the test<br>>> host, I get:<br>>> ...<br>>> If I "tracepath 73.xxx.67.1" from the jool host, I get a real<br>>> trace with real names that goes "no reply" one step earlier.<br>><br>> I can't explain the "goes 'no reply' one step earlier" thing, but as<br>> for the rest, check this out:<br>><br>> https://jool.mx/en/usr-flags-global.html#--source-icmpv6-errors-better<br>><br>>> Specifically, I cannot "wget http://whatsmyip.org". It returns<br>>> an empty file.<br>><br>> I think this is a separate problem. Let me see if I can reproduce it.<br>><br>> On Fri, Dec 22, 2017 at 2:17 AM, Kurt Lund <kurt@realacquisitions.com> wrote:<br>>> I followed the instructions very carefully, but had to use a different<br>>> prefix (I used 2000:ffff::/96, that I stole from the old NAT-PT<br>>> documentation) because I (stupidly) used the whole /64 that was given to me<br>>> when setting up my dual stack nodes, so Jool complained when I tried to use<br>>> a /96 in the config.<br>>><br>>> It "works" in that I can use Jool to connect to a IPV4 device in my network<br>>> from a IPv6-only node, but any attempt to connect outside my network has<br>>> issues.<br>>><br>>> IPv6 side: 2604:xxxx:0:a::/64<br>>> IPv4 side: 216.xxx.228.0/29 AND 216.xxx.228.8/29<br>>> Jool setup: Centos 7, single NIC<br>>> Kernel module "jool" loaded with "modprobe --first-time jool<br>>> pool6=2000:ffff::/96"<br>>> IPv4: using host address of 216.xxx.228.6<br>>> IPv6: using host address of 2604:xxxx:0:a:e6::e406<br>>><br>>> Text IPv6 host: 2604:xxxx:0:a:4::2<br>>> Test IPv4 host: 216.xxx.228.13 (although it is a dual stack node, I have<br>>> confirmed that Jool was used to translate the IP)<br>>><br>>> Test: "ssh 2000:ffff::216.xxx.228.13" (confirmed on target by "netstat -an<br>>> | grep 216.xxx.228.6" and finding only one entry -- me)<br>>> "jool --bib --display" shows the mapping:<br>>> TCP:<br>>> [Dynamic] 216.xxx.228.6#62327 - 2604:xxxx:0:a:4::2#35038<br>>><br>>> Now when I "tracepath6 -n 2000:ffff::73.xxx.67.1 from the test host, I get:<br>>><br>>> 1?: [LOCALHOST] 0.029ms pmtu 1500<br>>> 1: 2604:xxxx:0:a:e6::e406 144.339ms asymm 2<br>>> 1: 2604:xxxx:0:a:e6::e406 5.092ms asymm 2<br>>> 2: 2000:ffff::49xx:4301 1.151ms asymm 3<br>>> 3: 2000:ffff::49xx:4301 1.469ms asymm 4<br>>> 4: 2000:ffff::49xx:4301 1.226ms asymm 5<br>>> 5: 2000:ffff::49xx:4301 2.073ms asymm 6<br>>> 6: 2000:ffff::49xx:4301 2.538ms asymm 7<br>>> 7: 2000:ffff::49xx:4301 3.340ms asymm 8<br>>> 8: 2000:ffff::49xx:4301 3.512ms asymm 9<br>>> 9: 2000:ffff::49xx:4301 9.436ms asymm 7<br>>> 10: 2000:ffff::49xx:4301 7.961ms asymm 5<br>>> 11: 2000:ffff::49xx:4301 11.584ms asymm 6<br>>> 12: 2000:ffff::49xx:4301 11.678ms asymm 7<br>>> 13: no reply<br>>> 14: no reply<br>>> 15: no reply<br>>><br>>> If I "tracepath 73.xxx.67.1" from the jool host, I get a real trace with<br>>> real names that goes "no reply" one step earlier.<br>>><br>>> Maybe this is not a big deal (it only seems to mask ICMP stuff) but I also<br>>> can't access public nodes with other (more important) protocols.<br>>> Specifically, I cannot "wget http://whatsmyip.org". It returns an empty<br>>> file.<br>>><br>>> HELP!!<br>>><br>>> Thanks,<br>>> Kurt Lund<br>>> kurt@realacquisitions.com<br>>> RealAcquisitions.com<br>>><br>>> _______________________________________________<br>>> Jool-list mailing list<br>>> Jool-list@nic.mx<br>>> https://mail-lists.nic.mx/listas/listinfo/jool-list<br>>><br></body></html>