<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Henning,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I see what you mean about the there being a default route towards eth0 anyways. It does exist and points right at the physical router to which eth0 is attached which should be the NAT that you refer to. I guess on Android, where there is no eth0 but you might want to set up the cell device as a NAT, then the iptables should be necessary. I need to spend more time to figure out why nslookup wasn’t working without the iptables on the Raspberry PI. I will report back, hopefully with good information, when I have figure something meaningful out. Thanks for the insights.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Yes your understanding is correct “ </span>If I understand you correctly you can ping 192.168.18.2 from your Android device right?<span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> “. What I don’t understand is the DUP and flakiness with the ping.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Peter E.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Henning Rogge [mailto:hrogge@gmail.com] <br><b>Sent:</b> Monday, July 18, 2016 10:43 PM<br><b>To:</b> Peter Emanuel<br><b>Cc:</b> olsr-dev<br><b>Subject:</b> Re: [Olsr-dev] Propagating a default gateway OLSRv2<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><div><p class=MsoNormal>On Mon, Jul 18, 2016 at 7:00 PM, Peter Emanuel <<a href="mailto:peter@sistreaming.com" target="_blank">peter@sistreaming.com</a>> wrote:<o:p></o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Because using iptables was the only way I could make it work with HNA in Version 1. I will run another test today to see if it works without it. Why is it dangerous in your estimation? All I am doing is using eth0 as a NAT to the mesh network. Will this conflict with the olsr routing?</span><o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I admit I am no specialist for NAT scenarios, but wouldn't a normal static routing entry combined with the NAT iptables rule be the normal way?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>There should be the default route towards eth0 on the gateway anyways.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>(continued below)<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Henning Rogge [mailto:<a href="mailto:hrogge@gmail.com" target="_blank">hrogge@gmail.com</a>] <br><b>Sent:</b> Monday, July 18, 2016 5:33 AM</span><o:p></o:p></p><div><div><p class=MsoNormal><br><b>To:</b> Peter Emanuel<br><b>Cc:</b> olsr-dev<br><b>Subject:</b> Re: [Olsr-dev] Propagating a default gateway OLSRv2<o:p></o:p></p></div></div></div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Hmm?<o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>You are using IPtables to forward traffic between eth0 and wlan0?<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>That sounds dangerous at best. Why do you do this?<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Henning<o:p></o:p></p></div></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Fri, Jul 15, 2016 at 10:47 PM, Peter Emanuel <<a href="mailto:peter@sistreaming.com" target="_blank">peter@sistreaming.com</a>> wrote:<o:p></o:p></p><div><div><p>I have an update on this. I stumbled into a prior discussion on this forum from 2012 about this exact problem. The solution was to change the netmask on the WiFi from 255.255.255.0 to 255.255.0.0. This definitely helped as there were default gateways specified in each of the nodes in the chain pointing at each connected/edge node. (I personally don't understand why this changed anything as all of my nodes were on the same subnet - 192.168.18.x. This is probably my own lack of understanding).<o:p></o:p></p><p> <o:p></o:p></p><p>My gateway to the Internet was node 192.168.18.2. I was able to ping this IP from the last node in my chain of my 6 nodes (192.168.18.201) but couldn't get to the Internet although the DNS lookup appeared to work fine. I tried accessing <a href="http://youtube.com" target="_blank">youtube.com</a> and <a href="http://google.com" target="_blank">google.com</a>. Again, once my edge node was 1 hop from the gateway, everything started working as expected (192.168.18.201 connected to 192.168.18.3).<o:p></o:p></p><p> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><img border=0 width=624 height=115 id="_x0000_i1029" src="cid:image001.png@01D1E1EA.33269B20"><o:p></o:p></p><p> <o:p></o:p></p></div></div></div></div></div></div></div></div></blockquote><div><p class=MsoNormal>If I understand you correctly you can ping 192.168.18.2 from your Android device right?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Henning<o:p></o:p></p></div></div></div></div></div></body></html>