[Olsr-users] OLSRd - can't understand routing

[Derek C]

Hi all again,

I've been investigating further and I see some weird routing stuff.

My setup is like this: -

    |
  INTERNET
    |
   NIC1 (Internet connection with NAT)
 UBUNTU SERVER
   NIC2 (5.0.0.1 with OLSRd)
    |
 5GHZ-RADIO--------
  |     |         | (Transparent bridges - radio links - 1KM)
  |     |         |
  |     |         |
 ETH0  ETH0      ETH0
OLSRD1   OLSRD2   OLSRD3
 2.4GHZ   2.4GHZ   2.4GHZ
5.1.0.1  5.1.0.2   5.1.0.3

And those antennas pick up about 10 remote nodes (5.10.0.1 - 5.10.0.10)

The weird thing is this:

I have a remote node that is showing up in the main server as being
available at 5.1.0.1.  So I ssh in there and find that it thinks that node
is available via 5.1.0.3 (which it really is as that's where it is
geographically located).

I wonder why OLSRd, in the main Ubuntu server, thinks the remote node is
available via the wrong node?

It could be my transparent bridging but I wouldn't have thought so?

thanks for any advice!

Derek
On Wed, February 18, 2009 8:05 pm, Derek C wrote:
> Hi all,
>
>
> Me again.  I'm still testing a smallish network (around 10 nodes but
> spread over a couple of KM).
>
> What I've done is put up three nodes with Internet access - the Internet
> access is via 5.8Ghz point-to-point links and I've linked eth0 of my OLSRd
>  (PC engines WRAP boards) to via transparent [tunnel] bridges back to a
> NIC
> on a DELL server running Ubuntu with OLSRd too.
>
> This means that the three nodes all have a single hop to their gateway
> and only one gateway - I thought this was a good idea to have no
> connection/NAT problems associated with multiple gateways.
>
> Currently all remote nodes are one-hop to an Internet connected node
> (i.e.
> two logical/OLSRd hops to the DELL server in the datacentre).
>
> What I don't understand is this:
>
>
> If I go into a remote node and do a "netstat -rn" I can see that it has a
>  default route via a nearby Internet connected node - good stuff - and
> the node has Internet access too - perfect!.
>
> BUT If I ssh into the DELL server (the only gateway HNA node) I sometimes
>  DONT see the remote node's IP in a "netstat -rn" and I cannot ping it
> either.
>
> I don't understand how that remote node is actually working and getting
> traffic back & forth if the routing is not propagating across the OLSRd
> routed network.
>
> I'm not doing any funny stuff with NAT on the remote nodes (other than
> NATTing 192.168.0.0/16 so that people get Internet access of a public AP
> in the nodes - my OLSRd network is 5.0.0.0/8.
>
> Does the above make any sense to anyone?
>
>
> thanks v much!
>
>
> Derek
>
>
> P.S.
> One of my typical remote OLSRd nodes:
>
>
> UseHysteresis        no
> TcRedundancy         2
> MprCoverage          1
> LinkQualityLevel     2
> LinkQualityWinSize   10
>
>
> DebugLevel	     0
>
>
> #Hna4 {
> #     0.0.0.0 0.0.0.0
> #     }
>
>
> #LoadPlugin "olsrd_dyn_gw.so.0.4"
> #{
> #    PlParam "Interval" "60"
> #    PlParam "Ping" "151.1.1.1"
> #    PlParam "Ping" "194.25.2.129"
> #    }
>
>
> LoadPlugin "olsrd_httpinfo.so.0.1"
> {
> PlParam "Net" "5.0.0.0 255.0.0.0"
> PlParam "port" "8080"
> }
>
>
> LoadPlugin "olsrd_txtinfo.so.0.1"
> {
> PlParam "port" "8081"
> PlParam "Host" "127.0.0.1"
> }
>
>
> Interface "ath0"
> {
> Ip4Broadcast 255.255.255.255
> HelloInterval         2.0
> HelloValidityTime     20.0
> }
>
>
>
>
>
>
>
> --
> --
> Derek C
> In Ireland
>
>
>
>
> --
> Olsr-users mailing list
> (spam-protected)
> http://lists.olsr.org/mailman/listinfo/olsr-users
>
>


-- 
--
Derek C
In Ireland