Hi Albert, Thanks for the feedback.
After getting the invalid packet, oor is no longer running. I can't say if it just stops or crashes. So I guess that *this* is not the normal behavior. BR Holger -- Von einem Gerät mit virtueller Tastatur gesendet > Am 25.08.2016 um 16:07 schrieb Albert López <alo...@ac.upc.edu>: > > Hi Holger, > > This is the normal behavior. You are sending an invalid packet to the UDP > port which OOR is not able to identify. > This should not crash the program. If it is your case then let me know. > > Best regards > > Albert > >> On 05/08/16 13:22, Holger Zuleger wrote: >> Hi, >> >> I have a problem (not just this one) with oor running on a openwrt box. >> I did a udp port scan just to see if the LISP ports are reachable from >> outside. >> >> The oor (debug) message in the log file looks like: >> >> [2016/8/4 20:4:42] DEBUG-3: Unknown LISP message type 0 >> [2016/8/4 20:4:42] DEBUG: Received (null), IP: 88.198.13.165 -> >> 185.122.6.226, UDP: 50823 -> 4342 >> [2016/8/4 20:4:42] DEBUG: xTR: Unidentified type (0) control message >> received >> [2016/8/4 20:4:42] DEBUG: xTR: Failed to process LISP control message >> >> So far so good, but then oor stops. Actually I don't know if it crashes >> or just exits. >> Anyone seen this so far? >> >> Best regards >> Holger >> >> >> >> >> _______________________________________________ >> Users mailing list >> Users@openoverlayrouter.org >> http://mail.openoverlayrouter.org/cgi-bin/mailman/listinfo/users >
_______________________________________________ Users mailing list Users@openoverlayrouter.org http://mail.openoverlayrouter.org/cgi-bin/mailman/listinfo/users
