[Olsr-users] Configuration for olsrd.conf

[Henning Rogge]

We only have a small CONFINE test network at our institute, but most
community mesh networks run hundreds of nodes with the current OpenWRT
software.

Henning

On Sun, Mar 2, 2014 at 1:48 PM, ANDERSON JUNIOR GADO DA SILVA
<(spam-protected)> wrote:
> hi, I understand perfectly, this time I'm using 12:09, a version I compiled
> via buildroot is working, I have asked questions on the official list but
> got no response when I gave the command for the terminal / etc / init.d /
> firewall start he appeared several errors and a message that the kernel may
> need to be updated, so I arrived at that conclusion with 3:10 kernel is
> running, already with 3.8 did not work, I kept the same settings.
>
> ps: how many routers have in your network today?
>
> Att
> Anderson Junior
>
>
> 2014-03-02 3:11 GMT-04:00 Henning Rogge <(spam-protected)>:
>
>> Hi,
>>
>> we have running a lot of 12.09 openwrt devices at our institute and
>> never had trouble with iptables... I would NOT suggest to go back to a
>> version more than 4 years old.
>>
>> Maybe you should ask about the problem on an OpenWRT mailing list.
>>
>> Henning Rogge
>>
>> On Sun, Mar 2, 2014 at 4:16 AM, ANDERSON JUNIOR GADO DA SILVA
>> <(spam-protected)> wrote:
>> > hello, Chris W. and Henning Rogge, after several attempts I found where
>> > the
>> > problem was, the 3.8.x kernel openwrt 12.x (this package
>> >
>> > http://downloads.openwrt.org/attitude_adjustment/12.09/ar71xx/generic/openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-factory.bin)
>> > is in serious trouble in the iptables modules, including the nat and
>> > filter,
>> > then actually would never work, I downloaded the version of svn trunk
>> > compiled a new binary and it worked, just not tested it is working on
>> > other
>> > routers, but already took a big step today in the morning back to work
>> > on
>> > it, I'm thinking instead of version 12.x back to 8:09, do you have any
>> > suggestions?
>> >
>> > thanks for calm that had friends with me.
>> >
>> > Att
>> > Anderson Junior
>> >
>> >
>> > 2014-03-01 14:42 GMT-04:00 ANDERSON JUNIOR GADO DA SILVA
>> > <(spam-protected)>:
>> >
>> >> ok, I changed to the 172.11.0.1/24 lan, still did not result, do not
>> >> know
>> >> if pass something in your message, do not speak English, to using
>> >> google
>> >> translator ...
>> >>
>> >> Att
>> >> Anderson Junior
>> >>
>> >>
>> >> 2014-03-01 14:11 GMT-04:00 Chris W. <(spam-protected)>:
>> >>
>> >>>
>> >>>> ok thanks for the feedback, let it
>> >>>> Concerning the mask 255.255.0.0 is a TA in that class and so far I
>> >>>> have
>> >>>> not changed, but soon it'll network.
>> >>>
>> >>> It is overlapping the LAN's 192.168.1.x ...
>> >>>
>> >>>
>> >>>>
>> >>>> regarding vlan, I did not change this pattern that comes with the
>> >>>> openwrt for this router model but suggest me if I change something,
>> >>>> I'll
>> >>>> comment on that vlan to see if it makes a difference.
>> >>>
>> >>> Vlan is right I guess, now when looking at it again ;)
>> >>>
>> >>>
>> >>>>
>> >>>> when the wlan router the other is that the moment they were off, but
>> >>>> now
>> >>>> I'm sending a new output from echo command '/ all' | nc localhost
>> >>>> 2006
>> >>>> here is:
>> >>>>
>> >>>> echo '/all' | nc localhost 2006
>> >>>
>> >>>
>> >>> [...]
>> >>>
>> >>> Meshing well, only the routers' LANs need to be announced via HNA
>> >>> entry
>> >>> to bring the connected machines into play.
>> >>>
>> >>>>
>> >>>> Table: HNA
>> >>>> Destination     Gateway
>> >>>> 0.0.0.0/0 <http://0.0.0.0/0>       10.5.0.1
>> >>>>
>> >>>>
>> >>>> Att
>> >>>> Anderson Junior
>> >>>>
>> >>>>
>> >>> [...]
>> >>>
>> >>> greetings,
>> >>> C
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> >
>> >
>
>
>
>
> --
>
>