[Olsr-users] OLSR deployment question

[Deepak Lal]

Thank you for your response.

> LTE: I wonder if it is a good idea to have your "LTE Backbone" an attached network. Maybe use this as kind of Internet provider, where traffic to destinations that are not
> reachable with OLSR send the core router via the LTE link. Maybe you will add NAT later. You could check SmartGateway functionality.

This will be a private network with no access to internet. The objective is that all clients/hosts on LTE network should be able to reach clients on the mesh network and vice-versa. NAT
therefore will not work since NAT is used for "outgoing" connections only but here the networks need to communicate.

> No, this ethernet is your attached network.

OK Thanks.  My confusion though is that can I have an attached network that is on the same network as the OLSR interface?  If not, then does it mean that I will end up with three networks [😊]
1) LTE network (192.168.3.0/24)
2) Mesh OLSR network (192.168.2.0/24)
3) Clients that will connect to the radios that are meshing (192.168.4.0/24) e.g.?

> Good question. With NAT, clients in/around the vehicle can access a central server, as NAT hides addressing in the vehicle.

But as mentioned, I need to be able to reach clients in vehicle directly and not just initiate connections from the vehicle (NAT)

> Maybe use another routing protocol and redistribute.

In other words, could I also run OLSR on the LTE network? or would another protocol serve better?

Deepak
________________________________
From: Teco Boot <(spam-protected)>
Sent: February 13, 2017 1:56 PM
To: Deepak Lal
Cc: (spam-protected)
Subject: Re: [Olsr-users] OLSR deployment question

Hi,
> Op 13 feb. 2017, om 15:50 heeft Deepak Lal <(spam-protected)> het volgende geschreven:
>
> I have the following problem and believe that OLSR might help. I am not an expert and therefore would appreciate some feedback/help.
>
> Refer: https://www.dropbox.com/s/qqcqspdhtaykvjk/Drawing1.png?dl=0
[https://www.dropbox.com/temp_thumb_from_token/s/qqcqspdhtaykvjk?preserve_transparency=False&size=1024x1024&size_mode=2]<https://www.dropbox.com/s/qqcqspdhtaykvjk/Drawing1.png?dl=0>

Drawing1.png<https://www.dropbox.com/s/qqcqspdhtaykvjk/Drawing1.png?dl=0>
www.dropbox.com
Shared with Dropbox



>
> Drawing1.png
> www.dropbox.com<http://www.dropbox.com>
> Shared with Dropbox
>
>
>
> Network: We are deploying a small experimental network that will be LTE based with a eNodeB and multiple user endpoints. The LTE will be specific network address (192.168.1.0/24). The user endpoints can either be LTE phones or RADIOS installed in vehicles.
>
> The vehicle RADIOS will have two interfaces (LTE and Mesh).  The LTE interface in the radio will be on the 192.168.1.0 subnet and the mesh interface will be on the 192.168.2.0/24 subnet.
>
> 1) The radios will "Mesh" with other radios. Depending upon location, some vehicles might have both LTE and mesh links active at same time.
> 2) It is possible for the mesh network to be "split" in two or three separate networks
>
>
> Question 1: I am thinking of running OLSR on on the radio on mesh network and configuring the LTE as an attached network. Is this OK?

MESH: yes, run OLSR on it.

LTE: I wonder if it is a good idea to have your "LTE Backbone" an attached network. Maybe use this as kind of Internet provider, where traffic to destinations that are not reachable with OLSR send the core router via the LTE link. Maybe you will add NAT later. You could check SmartGateway functionality.


> Question 2: Since the radio also has an ethernet interface for connecting laptops, I assume I will have to BRIDGE the mesh interface on the radio with any attached client  that I want to be part of the mesh network?

No, this ethernet is your attached network.


> Question 3: How will the LTE network "know" how to reach a client (laptop) in a vehicle that is on the mesh? Keep in mind that the vehicle can move and connect to a different mesh

Good question. With NAT, clients in/around the vehicle can access a central server, as NAT hides addressing in the vehicle.

I have a somewhat similar topology, where I use VPN on the LTE/(other) backbone links. The VPN has some kind of floating static routing. This provides any to any communication without scalability problems of MANET in the VPN tunnels. LTE is the public Internet.

Others run OLSR on the backbone links. For smaller networks this might work.

Maybe use another routing protocol and redistribute.


Teco


>
>
> Any other feedback or ideas much appreciated.
>
> Thanks
> --
> Olsr-users mailing list
> (spam-protected)
> https://lists.olsr.org/mailman/listinfo/olsr-users
Olsr-users Info Page<https://lists.olsr.org/mailman/listinfo/olsr-users>
lists.olsr.org
To see the collection of prior postings to the list, visit the Olsr-users Archives. Using Olsr-users: To post a message to all the list members, send ...




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20170213/c8e8dfea/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OutlookEmoji-😊.png
Type: image/png
Size: 488 bytes
Desc: OutlookEmoji-😊.png
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20170213/c8e8dfea/attachment-0001.png>