[OLSR-users] Re: [olsr-dev] re-routing though a node problem.
Sat Sep 18 22:24:09 CEST 2004
First of all - OLSR is in no way responsible for forwarding/routing of
only maintains routes that are used by the IP stack.
However, olsrd enables IP forwarding on GNU/Linux systems by writing 1 to
/proc/sys/net/ipv4/ip_forward for IPv4. Still, there might be firewall rules
(or other issues) blocking this traffic, you could try flushing iptables
if this is
a pure testbed.
Thomas Capricelli wrote:
> I'm having a problem with olsrd-0.4.5 ( i know 0.4.7 is out, but i have
>this on all nodes and haven't updated yet)
>I have three nodes ( 10.0.10.7, 11 and 12). For some reason 7 can't see 11, and as such,
>is using 12 for routing. that is
> 7 <-> 12 <-> 11
>This can be seen from (berlioz=7)
> (spam-protected) /home/orzel> route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 10.0.10.11 10.0.10.12 255.255.255.255 UGH 2 0 0 wlan0
>But i can't ping 11 :
> (spam-protected) /home/orzel> ping 10.0.10.11
> PING 10.0.10.11 (10.0.10.11) 56(84) bytes of data.
> --- 10.0.10.11 ping statistics ---
> 4 packets transmitted, 0 received, 100% packet loss, time 2999ms
>I can ping 12, and connect to it. From 12, i can ping 11.
> (spam-protected) /home/orzel> ssh (spam-protected)
> # ping 10.0.10.11
> PING 10.0.10.11 (10.0.10.11): 56 data bytes
> 64 bytes from 10.0.10.11: icmp_seq=0 ttl=64 time=27.6 ms
> 64 bytes from 10.0.10.11: icmp_seq=1 ttl=64 time=10.1 ms
>So it seems 12 is refusing to relay packets from 7 to 11. How can that be ? what should
>I do ? On a 'classical' server, i would use iptables to enable NAT/masquerading. But with
>olsr, i thought olsrd would take care of that.
>If this is a bug from 0.4.5 fixed in 0.4.7, i'll be just happy of course :)
>Thomas Capricelli <(spam-protected)>
>olsr-dev mailing list
More information about the Olsr-users