<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<title>Konsole output</title>
<div>
<span style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;">i also tried
to crash olsr. (on LEDE trunk from yesterday) but i think its
some kind of hanging-process/deniel-of-service-attack instead
of a code-crash.<br>
olsr will restart (due to olsr-watchdog) and doesnt have a
dump/core-file for gdb for me<br>
<br>
> Dec 22 14:50:00 2016 user.notice OLSR watchdog: Process
died - restarting!</span></span><br>
<span style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;">
<div><span style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;">> [
1369.947516] TCP: request_sock_TCP: Possible SYN
flooding on port 9090. Sending cookies. Check SNMP
counters.</span><br>
<br>
problem: a telnet connect to jsonplugin (also from outside
of the device) will deny/halt/stop all other
jsonplugin-calls. if you then wait too long the
olsr-watchdog will cause a olsr-restart. sp2ong, please
have a look in dmesg/logread for such messages.<br>
<br>
at doku (<a class="moz-txt-link-freetext" href="http://www.olsr.org/?q=jsoninfo_plugin">http://www.olsr.org/?q=jsoninfo_plugin</a>) i read <br>
</span><br>
<span style="font-family:monospace">"If no address is
specified, then localhost (127.0.0.1) is allowed by
default."<br>
<br>
but that doesnt seems to work any more!? On my testdevice
there are no PlParams for jsonplugin, BUT i can make
telnet/nc connection from outside/other meshnodes. when i
ask for "/routes" a message appears "403 Forbidden</span><span
style="font-family:monospace">". the port is open, and one
connection to that will block/dos the jsonplugin.<br>
</span></div>
<br>
<br>
mfg ufo<br>
</span>
<br>
</span></div>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<br>
<br>
<div class="moz-cite-prefix">On 22.12.2016 09:50, Ferry Huberts
wrote:<br>
</div>
<blockquote
cite="mid:72e49092-b7f2-869e-5966-c003859edb84@hupie.com"
type="cite">It all works for me, on Linux with glibc
<br>
<br>
I really need a backtrace to be able determine what is going on.
<br>
Run olsrd under gdb please to generate a backtrace.
<br>
<br>
On 22/12/16 09:47, <a class="moz-txt-link-abbreviated" href="mailto:sp2ong@wp.pl">sp2ong@wp.pl</a> wrote:
<br>
<blockquote type="cite">I have check similar txtinfo plugin use
telnet command and when I have
<br>
request /rou and /lin all information were showed and OLSRD
process
<br>
not crash
<br>
<br>
2016-12-22 9:44 GMT+01:00 <a class="moz-txt-link-rfc2396E" href="mailto:sp2ong@wp.pl"><sp2ong@wp.pl></a>:
<br>
<blockquote type="cite">Hi
<br>
<br>
I know this information about scripts from changelog but I
have tray
<br>
get manually information from jsonplugin use simple unix
command
<br>
<br>
echo /routes | nc 127.0.0.0.1 9090
<br>
<br>
where 9090 is port for jsonplugin and when I have ask plugin
jsoninfo
<br>
about 'routes' OLSRD process crash
<br>
<br>
I can do similar use telnet command:
<br>
<br>
telnet 127.0.0.1 9090
<br>
<br>
and when next send command /mid all information is showed but
when I
<br>
have send command in telnet session /routes main OLSRD process
crash
<br>
<br>
If I send bad command to jsoninfo I have proper info about
invalid requests :
<br>
telnet 127.0.0.1 9090
<br>
/lin
<br>
HTTP/1.1 404 Not Found
<br>
Date: Thu, 22 Dec 2016 08:39:05 GMT
<br>
Server: OLSRD JSONINFO
<br>
Connection: close
<br>
Content-Type: application/vnd.api+json
<br>
Access-Control-Allow-Origin: *
<br>
Access-Control-Allow-Methods: GET, POST, OPTIONS
<br>
Access-Control-Allow-Headers: Accept, Origin, X-Requested-With
<br>
Access-Control-Max-Age: 1728000
<br>
Content-Length: 0
<br>
Cache-Control: no-cache
<br>
<br>
When I have send correct request like /mid I receive all
iformation:
<br>
<br>
telnet 127.0.0.1 9090
<br>
/mid
<br>
HTTP/1.1 200 OK
<br>
Date: Thu, 22 Dec 2016 08:41:24 GMT
<br>
Server: OLSRD JSONINFO
<br>
Connection: close
<br>
Content-Type: application/vnd.api+json
<br>
Access-Control-Allow-Origin: *
<br>
Access-Control-Allow-Methods: GET, POST, OPTIONS
<br>
Access-Control-Allow-Headers: Accept, Origin, X-Requested-With
<br>
Access-Control-Max-Age: 1728000
<br>
Content-Length: 465
<br>
Cache-Control: no-cache
<br>
<br>
{"pid": 27325,"systemTime":
<br>
.....
<br>
<br>
<br>
but when I have try use /links or /routes not inforation and
OLSRD
<br>
stop working and it lis look like crash process because I must
again
<br>
restart olsrd
<br>
<br>
telnet 127.0.0.1 9090
<br>
/links
<br>
Connection closed by foreign host
<br>
<br>
<br>
<br>
<br>
<br>
2016-12-22 9:18 GMT+01:00 Ferry Huberts
<a class="moz-txt-link-rfc2396E" href="mailto:mailings@hupie.com"><mailings@hupie.com></a>:
<br>
<blockquote type="cite">
<br>
<br>
On 22/12/16 09:10, <a class="moz-txt-link-abbreviated" href="mailto:sp2ong@wp.pl">sp2ong@wp.pl</a> wrote:
<br>
<blockquote type="cite">After success compile olsrd 0.9.5 I
have update package on my openwrt router
<br>
I have use plug-in jsoninfo to get information 'links' and
'routes'
<br>
use following command:
<br>
<br>
echo /links | nc 127.0.0.1 9090
<br>
<br>
Now after upgrade to v0.9.5 plugin jsoninfo crash olsrd
when I have
<br>
</blockquote>
<br>
Please provide your commands and the backtrace.
<br>
<br>
Also - from the changelog - read this:
<br>
<br>
Note: The txtinfo and jsoninfo plugins were 'merged' to use
a common
<br>
codebase for receiving requests and dispatching
replies. Also,
<br>
these plugins were subjected to review and fixes. As a
result:
<br>
- request handling has become much stricter, e.g. a
txtinfo
<br>
request '/links' will no longer work since the
correct request is
<br>
(and has always been) '/lin'.
<br>
- some fixes change the format and/or content of
txtinfo and/or
<br>
jsoninfo output. An example is the txtinfo output of
the request
<br>
'/mid' when 'vtime' is enabled on txtinfo; this has
been broken
<br>
since the end of 2009 (c555a44).
<br>
- invalid requests will return HTTP error status code
<br>
"Not Found" (404) when HTTP headers are enabled, and
report
<br>
an error in the output when they are not enabled.
<br>
- requests without output will return HTTP error
status code
<br>
"No Content" (204) when HTTP headers are enabled,
and report
<br>
an error in the output when they are not enabled.
<br>
<br>
It is VERY strongly advised to check your scripts and
applications
<br>
interfacing with olsrd txtinfo and/or jsoninfo before
switching
<br>
to this version of olsrd.
<br>
<br>
<br>
<blockquote type="cite">use check following
<br>
parameters
<br>
<br>
links
<br>
routes
<br>
topology
<br>
interfaces
<br>
<br>
when I have check following parameters
<br>
<br>
hna
<br>
gateways
<br>
mid
<br>
neighbors
<br>
2hop
<br>
sgw
<br>
<br>
I have information from jsoninfo and olsrd not crash
<br>
<br>
I have check olsrd 0.9.5 compiled and running on debian
all working OK
<br>
but under openwrt
<br>
crash process when I want to get information about links
and routes
<br>
<br>
Anybody have similar problems with olsrd 0.9.5 running
under openwrt ????
<br>
<br>
Regards
<br>
<br>
Waldek
<br>
<br>
</blockquote>
<br>
--
<br>
Ferry Huberts
<br>
<br>
</blockquote>
</blockquote>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>