[OOR-Users] OOR configuration
Albert López
alopez at ac.upc.edu
Wed Jan 11 11:06:09 CET 2017
Dear Marian,
Welcome to our community. I will try to answer inline.
On 10/01/17 15:01, Marian Aretu wrote:
>
> Hello,
>
> My name is Marian Aretu, and I am using your open source
> implementation of LISP protocol.
>
> The network that we try to emulate with OOR is composed of 5 Virtual
> Machines (Ubuntu Linux).
>
> With each VM, we are trying to emulate a different component of LISP
> protocol: MN (named MN1), xTR1, MS, xTR2 and another MN (named ES1).
>
> Our goal, for now, is to manage communication between MN1 and ES1, but
> we are getting stuck in the configuration of oor.
>
> We are setting the IP routes in the VMs, but when we run oor, the
> following message is received:
>
> /[2017/1/9 15:1:25] DEBUG: add_route: added route to the system: src
> addr: -, dst prefix:0.0.0.0/1, gw: -, table: 254/
>
> /[2017/1/9 15:1:25] DEBUG: add_route: added route to the system: src
> addr: -, dst prefix:128.0.0.0/1, gw: -, table: 254/
>
> Does this message mean that we need to add the routes also via oor,
> somehow?
>
> If yes, how can we manage to add the routes using oor?
>
No, the routes should be added by OOR automatically. If you use "ip
route", you should be able to see them.
One thing that you have to take care is that MN and XTRs need to have a
valid default route associated with the RLOC's interface configured
before starting OOR. If we don't have this default route, OOR will not
work. If you have two or more interfaces, then you will need to have one
default route per interface (you can use different metric per each one)
> Another matter is that we are not sure if we are configuring oor
> right. You can find attached an example of our configuration for MN1
> (IP addresses may be subject of change).
>
> Can you please help us with an example of a simple network that uses
> oor and the configuration file for that network?
>
I attach an example of an OOR testbed. Addresses with 10.0.X.X are in
the RLOC space and addresses with 192.168.x.x are in the EID space.
Please, let me know if this fits with your scenario.
Some notes:
*
ms.conf : I also added the site 192.168.2.0/24 with more specifics
-> This will accept more specific prefixes with same authentication
information. For instance, this site can be used to register 256 MN,
all of them using the same password
*
In the database mapping, I used rloc-address but it is possible to
use rloc-iface where we specify the interface of the RLOC instead
of the IP address. If a database mapping has more that one rloc, we
can add here as many as we need.
*
In your scenario you don't need to configure PeTRs. They are used to
interconnect LISP with no LISP sites. We don't have PeTR
implementation yet.
I hope this will help to have a first contact with OOR. Please, let me
know if you need more help.
Best regards
Albert
> Thank you very much,
>
> Marian Aretu
>
> cid:id002
>
> cid:id003
>
>
>
> *Marian Aretu
> *Software Engineer
>
> GMV AEROSPACE Software Factory
>
>
>
> GMV
> Isaac Newton, 11
> P.T.M. Tres Cantos
> E-28760 Madrid
>
> Mobile: +34 666 299 821 /
>
> +40 767 348 428
> www.gmv.com <http://www.gmv.com/>
>
> cid:id004 <http://www.gmv.com/b2_gmv>
>
>
>
>
>
> cid:id005 <http://www.facebook.com/infoGMV>
>
>
>
>
>
> cid:id006 <http://www.twitter.com/infoGMV_es>
>
>
>
>
>
> cid:id007 <http://www.youtube.com/infoGMV>
>
>
> <http://www.innovation2011.es/index.php?id=86>
>
> ------------------------------------------------------------------------
>
> This message including any attachments may contain confidential
> information, according to our Information Security Management System,
> and intended solely for a specific individual to whom they are
> addressed. Any unauthorised copy, disclosure or distribution of this
> message is strictly forbidden. If you have received this transmission
> in error, please notify the sender immediately and delete it.
>
> ------------------------------------------------------------------------
>
> Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede
> contener información clasificada por su emisor como confidencial en el
> marco de su Sistema de Gestión de Seguridad de la Información siendo
> para uso exclusivo del destinatario, quedando prohibida su divulgación
> copia o distribución a terceros sin la autorización expresa del
> remitente. Si Vd. ha recibido este mensaje erróneamente, se ruega lo
> notifique al remitente y proceda a su borrado. Gracias por su
> colaboración.
>
> ------------------------------------------------------------------------
>
> Esta mensagem, incluindo qualquer ficheiro anexo, pode conter
> informação confidencial, de acordo com nosso Sistema de Gestão de
> Segurança da Informação, sendo para uso exclusivo do destinatário e
> estando proibida a sua divulgação, cópia ou distribuição a terceiros
> sem autorização expressa do remetente da mesma. Se recebeu esta
> mensagem por engano, por favor avise de imediato o remetente e
> apague-a. Obrigado pela sua colaboração.
>
>
> PPlease consider the environment before printing this e-mail.
>
> ------------------------------------------------------------------------
> This message including any attachments may contain confidential
> information, according to our Information Security Management System,
> and intended solely for a specific individual to whom they are
> addressed. Any unauthorised copy, disclosure or distribution of this
> message is strictly forbidden. If you have received this transmission
> in error, please notify the sender immediately and delete it. Thank you.
> ------------------------------------------------------------------------
> Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede
> contener información clasificada por su emisor como confidencial en el
> marco de su Sistema de Gestión de Seguridad de la Información siendo
> para uso exclusivo del destinatario, quedando prohibida su divulgación
> copia o distribución a terceros sin la autorización expresa del
> remitente. Si Vd. ha recibido este mensaje erróneamente, se ruega lo
> notifique al remitente y proceda a su borrado. Gracias por su
> colaboración.
> ------------------------------------------------------------------------
> Esta mensagem, incluindo qualquer ficheiro anexo, pode conter
> informação confidencial, de acordo com nosso Sistema de Gestão de
> Segurança da Informação, sendo para uso exclusivo do destinatário e
> estando proibida a sua divulgação, cópia ou distribuição a terceiros
> sem autorização expressa do remetente da mesma. Se recebeu esta
> mensagem por engano, por favor avise de imediato o remetente e
> apague-a. Obrigado pela sua colaboração.
> ------------------------------------------------------------------------
>
>
> _______________________________________________
> Users mailing list
> Users at openoverlayrouter.org
> http://mail.openoverlayrouter.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openoverlayrouter.org/pipermail/users/attachments/20170111/3308c9a2/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 222 bytes
Desc: not available
URL: <http://mail.openoverlayrouter.org/pipermail/users/attachments/20170111/3308c9a2/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4338 bytes
Desc: not available
URL: <http://mail.openoverlayrouter.org/pipermail/users/attachments/20170111/3308c9a2/attachment-0001.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1306 bytes
Desc: not available
URL: <http://mail.openoverlayrouter.org/pipermail/users/attachments/20170111/3308c9a2/attachment-0004.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1309 bytes
Desc: not available
URL: <http://mail.openoverlayrouter.org/pipermail/users/attachments/20170111/3308c9a2/attachment-0005.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1279 bytes
Desc: not available
URL: <http://mail.openoverlayrouter.org/pipermail/users/attachments/20170111/3308c9a2/attachment-0006.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1323 bytes
Desc: not available
URL: <http://mail.openoverlayrouter.org/pipermail/users/attachments/20170111/3308c9a2/attachment-0007.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: oor-testbed.zip
Type: application/x-zip-compressed
Size: 29468 bytes
Desc: not available
URL: <http://mail.openoverlayrouter.org/pipermail/users/attachments/20170111/3308c9a2/attachment-0001.bin>
More information about the Users
mailing list