<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:14pt"><div style="RIGHT: auto"><SPAN style="RIGHT: auto">Hi Arjun,</SPAN></div>
<div style="RIGHT: auto"><SPAN style="RIGHT: auto"></SPAN> </div>
<div style="RIGHT: auto"><SPAN style="RIGHT: auto">Is it possible that you provide a simple network diagram on where is your gateway, node D, node C and node A?</SPAN></div>
<div style="RIGHT: auto"><SPAN style="RIGHT: auto"></SPAN> </div>
<div style="RIGHT: auto"><SPAN style="RIGHT: auto">I am also facing some problems in configuring a gateway for my OLSR mesh.</SPAN></div>
<div style="RIGHT: auto"><SPAN style="RIGHT: auto"></SPAN> </div>
<div style="RIGHT: auto"><SPAN style="RIGHT: auto">Probably, I can get some inputs <VAR id=yui-ie-cursor></VAR>from your problem.</SPAN></div>
<div style="RIGHT: auto"><SPAN style="RIGHT: auto"></SPAN> </div>
<div style="RIGHT: auto"><SPAN style="RIGHT: auto">Rdgs,</SPAN></div>
<div style="RIGHT: auto"><SPAN style="RIGHT: auto">Paul</SPAN></div>
<div style="RIGHT: auto"><SPAN style="RIGHT: auto"></SPAN> </div>
<div><BR></div>
<DIV style="FONT-FAMILY: arial, helvetica, sans-serif; FONT-SIZE: 14pt">
<DIV style="FONT-FAMILY: times new roman, new york, times, serif; FONT-SIZE: 12pt">
<DIV dir=ltr><FONT size=2 face=Arial>
<DIV style="BORDER-BOTTOM: #ccc 1px solid; BORDER-LEFT: #ccc 1px solid; PADDING-BOTTOM: 0px; LINE-HEIGHT: 0; MARGIN: 5px 0px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px; HEIGHT: 0px; FONT-SIZE: 0px; BORDER-TOP: #ccc 1px solid; BORDER-RIGHT: #ccc 1px solid; PADDING-TOP: 0px" class=hr contentEditable=false readonly="true"></DIV><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Arjun <akarjun@gmail.com><BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> Vigneswaran R <vignesh@atc.tcs.com> <BR><B><SPAN style="FONT-WEIGHT: bold">Cc:</SPAN></B> olsr-users@lists.olsr.org <BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, 14 February 2012, 5:50<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [Olsr-users] trouble with NAT and smart gateway<BR></FONT></DIV><BR>
<DIV id=yiv1213268297>Hi Vignesh,
<DIV>I need NAT because node D is constrained to talk only to 192.168.1.2. I therefore masquerade the packets coming in from the mesh to translate their source ip addresses to 192.168.1.2. I think my problem is more to do with congestion of the mesh network due to high bandwidth usage by my application which runs on node A.</DIV>
<DIV>Thanks much!</DIV>
<DIV>Arjun.</DIV>
<DIV><BR></DIV>
<DIV><BR>
<DIV class=yiv1213268297gmail_quote>On Mon, Feb 13, 2012 at 2:32 AM, Vigneswaran R <SPAN dir=ltr><<A href="mailto:vignesh@atc.tcs.com" rel=nofollow target=_blank ymailto="mailto:vignesh@atc.tcs.com">vignesh@atc.tcs.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class=yiv1213268297gmail_quote>
<DIV>On Saturday 11 February 2012 03:38 AM, Arjun wrote:<BR>[...]
<DIV class=yiv1213268297im><BR>
<BLOCKQUOTE type="cite">I have to use the NAT iptables rule on Node C, because Node D (192.168.1.1) can only talk to 192.168.1.2, which is IF2 on Node C. So packets originating from the OLSR mesh must have their source ips masqueraded to 192.168.1.2. Now that I think of it, maybe I can nose around inside the linux box on Node D (which is actually a commercial toy) and see if I can open it up to connect to ip addresses other than 192.168.1.2.</BLOCKQUOTE><BR></DIV>I think, NAT can be removed from your setup due to the following reason,<BR><BR>1. OLSR machines have route to D (and it's network) via C (because of HNA)<BR>2. So, the packets originated from OLSR mesh reach C and then forwarded to D.<BR> -- Here, C does simple IP Forwarding (no NATting)<BR> -- And the forwarded packets will have the source IP unmodified<BR>3. Since D doesn't have route to that source IP, it will send the reply packets to/via the default gateway (which is C, I
believe).<BR>4. When C receives this reply packet, it routes it to the proper destination in the OLSR mesh.<BR><BR><BR>Regards,<BR>Vignesh
<DIV class=yiv1213268297im><BR><BR><BR>
<BLOCKQUOTE type="cite">
<DIV>I think the problems I have are most likely due to mobility, because the toy moves reasonably fast, and leaky UDP streams. I will shorten the Hello/TC intervals and see if that helps. Do let me know if any other suggestion comes to mind.</DIV>
<DIV>Thanks again!</DIV>
<DIV>Arjun.</DIV>
<DIV><BR></DIV>
<DIV><BR>
<DIV class=yiv1213268297gmail_quote>On Fri, Feb 10, 2012 at 2:46 PM, Markus Kittenberger <SPAN dir=ltr><<A href="mailto:Markus.Kittenberger@gmx.at" rel=nofollow target=_blank ymailto="mailto:Markus.Kittenberger@gmx.at">Markus.Kittenberger@gmx.at</A>></SPAN> wrote:<BR>
<BLOCKQUOTE style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class=yiv1213268297gmail_quote>afair smart-gateway does not do anything useful for your setup,.
<DIV>as its only for hna announcements of <A href="http://0.0.0.0/0" rel=nofollow target=_blank>0.0.0.0/0</A> (and useful only if u have multiple nodes announcing this)</DIV>
<DIV><BR></DIV>
<DIV>anyways to simplify things, do not use smartgateway, hna alone is enough!</DIV>
<DIV><BR></DIV>
<DIV>and if possible (to simplify more) also remove the NAT in your testcase, use a static route on your target towards the mesh inestead,..<BR><BR>or just try (and verify the amount of packetloss of) an udp stream to node C, and not the node behind C,.. (so you can leave away the hna too)</DIV>
<DIV><BR></DIV>
<DIV>if this simplified setup works, you have issues with nat/hna,..</DIV>
<DIV>if not, you have problems with mobility (which usually can causes "some" packetloss, and maybe just too much for your udp stream)</DIV>
<DIV><BR></DIV>
<DIV>
<DIV class=yiv1213268297gmail_quote>
<DIV>On Fri, Feb 10, 2012 at 7:07 PM, Arjun <SPAN dir=ltr><<A href="mailto:akarjun@gmail.com" rel=nofollow target=_blank ymailto="mailto:akarjun@gmail.com">akarjun@gmail.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class=yiv1213268297gmail_quote>
<div>However, when I move node B out of range from the gw, i.e. node C, so that it is 2 hops away, which I confirmed from debug output from the txtinfo plugin, it is not able maintain connectivity (tcp and udp streams) with node D</div></BLOCKQUOTE></DIV>
<DIV>and is it able to maintain conenctivtiy with C?<BR>or atleast with A? </DIV>
<DIV>
<BLOCKQUOTE style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class=yiv1213268297gmail_quote>
<div>and my application on node B breaks down. Are there any settings I am forgetting,</div></BLOCKQUOTE></DIV>
<DIV>if (and only if) u are moving out of range fast, u might need shorter hello/tc intervals,..</DIV>
<DIV>
<BLOCKQUOTE style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class=yiv1213268297gmail_quote>
<div>or is it that UDP data over OLSR is not a good idea.</div></BLOCKQUOTE></DIV>
<DIV>as long as u do not expect no packetloss, udp works fine,.. <SPAN><FONT color=#888888><BR></FONT></SPAN></DIV><SPAN><FONT color=#888888>
<DIV><BR></DIV>
<DIV>
<DIV><BR>Markus</DIV>
<DIV><BR></DIV></DIV></FONT></SPAN></DIV></DIV></BLOCKQUOTE></DIV><BR></DIV><BR>
<FIELDSET></FIELDSET> <BR></BLOCKQUOTE><BR></DIV></DIV><BR>--<BR>Olsr-users mailing list<BR><A href="mailto:Olsr-users@lists.olsr.org" rel=nofollow target=_blank ymailto="mailto:Olsr-users@lists.olsr.org">Olsr-users@lists.olsr.org</A><BR><A href="https://lists.olsr.org/mailman/listinfo/olsr-users" rel=nofollow target=_blank>https://lists.olsr.org/mailman/listinfo/olsr-users</A><BR></BLOCKQUOTE></DIV><BR></DIV></DIV><BR>-- <BR>Olsr-users mailing list<BR><A href="mailto:Olsr-users@lists.olsr.org" ymailto="mailto:Olsr-users@lists.olsr.org">Olsr-users@lists.olsr.org</A><BR><A href="https://lists.olsr.org/mailman/listinfo/olsr-users" target=_blank>https://lists.olsr.org/mailman/listinfo/olsr-users</A><BR><BR></DIV></DIV></div></body></html>