[OLSR-users] Problem concerning the use of HNA !!
Mon Apr 4 18:49:27 CEST 2005
This issue has been discussed many times before on the list ;-)
OLSR is not responsible for external routing. All olsrd can do is
create an aggregated route to the HNA announce network. The gateway
node must either implement NAT or the nodes in the foregin network must
be able to route back into your OLSR network.
The easiest solution is to set up NAT on your gateway.
Frédéric DELAUNAY wrote:
> I missed something, I tested traceroute and packet from Node C goes well
> to Node B then Node A but after that * * * ... nothing
> I have a question maybe stupid !!! How node (22.214.171.124 in my
> example) could answer to my ping... Should I use a NAT on node A ? Is
> that the solution ?
> thanks again,
> Frédéric DELAUNAY a écrit :
>> Hi all,
>> I have some problems concerning the use of HNA. First of all I have
>> specified on the gateway node the network connecting to it manually in
>> /etc/olsrd.conf. Then I tested with the plugin olsrd_dyn_gw.so.0.3.
>> So I used olsrd.0.4.8 under Debian sarge 126.96.36.199.
>> Here's my topology, 3 nodes connecting with Ethernet.
>> 192.168.100.0 network----------192.168.100.63 (Node A) 10.0.1.2
>> --------------- 10.0.2.1 (Node B) 10.0.2.2 -------- 10.0.3.1 (Node C)
>> So Node A should be my gateway (from that node I can access correctly
>> to Internet and servers on network 192.168.100.0). On node B and C I
>> can see correctly HNA message annoucing Node A as a gateway (within
>> olsr-gui and route on a shell). But when I try to ping a node within
>> the network 192.168.100.0 (ping 192.168.100.254 for example), it
>> doesn't work.
>> So should I do something more ? Have I missed to do something ? Tell
>> me if you need more details...
>> Best Regards,
>> olsr-users mailing list
> olsr-users mailing list
More information about the Olsr-users