[Olsr-users] Inquiry about secure plugin of OLSR

[Zack Genesis]

Well Im register...
Similarly I didnt get your mail through the list as well...
Which I used to recieve

On Thu, May 12, 2011 at 8:30 PM, Rogge Henning <
(spam-protected)> wrote:

> The keyfile contains a 16 byte binary key... so you can use any character
> you want.
>
> Henning Rogge
>
> P.S.: Could it be that you are not registered on the olsr-users
> Mailinglist? I don't get your mails at home through the list.
>
> --
> Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
> Kommunikation, Informationsverarbeitung und Ergonomie FKIE
> Kommunikationssysteme (KOM) Neuenahrer Straße 20, 53343 Wachtberg,
> Germany Telefon +49 228 9435-961,   Fax +49 228 9435 685
> mailto:(spam-protected) http://www.fkie.fraunhofer.de
> GPG: E1C6 0914 490B 3909 D944 F80D 4487 C67C 55EC CFE0
>
> > -----Ursprüngliche Nachricht-----
> > Von: Zack Genesis [mailto:(spam-protected)]
> > Gesendet: Donnerstag, 12. Mai 2011 14:26
> > An: Rogge Henning
> > Cc: (spam-protected); Markus Kittenberger
> > Betreff: Re: Inquiry about secure plugin of OLSR
> >
> > Sorry to bother again...
> >
> >
> > A quick question... Regarding the secure plugin Key...
> > Other than Alphanumeric... Can the key or password be input
> > by using Non-alphanumeric character?
> >
> >
> > On Thu, May 12, 2011 at 2:06 PM, Henning Rogge
> > <(spam-protected)> wrote:
> >
> >
> >       On Wed May 11 2011 17:01:36 Zack Genesis wrote:
> >       > I see... I get your point there...
> >       > Other than the blackhole route method which might
> > somehow block off unicast
> >       > packet.
> >       > Is there a way to convert unicast packets in to OLSR
> > packet... maybe
> >       > something like encapsulate Non-olsr packet into olsr packet?
> >       > If it can be done... will the packet be block off by
> > the secure plugin??
> >
> >       I think you still misunderstand the purpose of the
> > OLSRd daemon. Its a pure
> >       routing daemon that decides about forwarding rules to
> > other nodes and tell the
> >       kernel about it.
> >
> >       It's neither designed nor able to handle unicast
> > traffic of the network. One
> >       reason an OLSRd mesh is pretty fast even on slow
> > hardware is that the traffic of
> >       the network does not need to be transfered into userspace.
> >
> >       The only thing I see what you could do is to write an
> > OLSR plugin that somehow
> >       controls your local firewall to block of unwanted
> > packages. But even then an
> >       attacker would just spoof his IP address.
> >
> >       Using IPsec for unicast might be the better sollution.
> >
> >
> >       Henning Rogge
> >
> >       --
> >       Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
> >       Kommunikation, Informationsverarbeitung und Ergonomie FKIE
> >       Kommunikationssysteme (KOM)
> >       Neuenahrer Straße 20, 53343 Wachtberg, Germany
> >       Telefon +49 228 9435-961 <tel:%2B49%20228%209435-961> ,
> >   Fax +49 228 9435 685 <tel:%2B49%20228%209435%20685>
> >       mailto:(spam-protected)
> > http://www.fkie.fraunhofer.de
> >       GPG: E1C6 0914 490B 3909 D944 F80D 4487 C67C 55EC CFE0
> >
> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20110512/af536584/attachment.html>