[Olsr-users] Windows Network Disconnect Destroys Mesh

Tue Jun 14 21:52:04 CEST 2016

Thanks for the quick responses everyone,

The problem occurs even when the windows machine is not running olsrd, and
is just connected to one of the nodes via direct ad-hoc to the network, so
I don't think it is an issue of compatibility with the outdated version,
but an issue with the new version, or perhaps I am just not doing something
right?

Attached (PacketsLinux.txt) is the tcpdump from a Linux node at the event
of the crash, as soon as I disconnected the Windows machine from its direct
ad-hoc connection (no olsr running on Windows side).

Also attached (PacketsWindows.txt) is the tcpdump on the windows side at
the event of a crash.

Strange thing is this: as soon as I disconnected, the tcpdump stopped
spitting out information completely, as if disconnecting somehow turned off
the  interfaces on all of the nodes.

On Monday, June 13, 2016, Ferry Huberts <(spam-protected)
<javascript:_e(%7B%7D,'cvml','(spam-protected)');>> wrote:

> Agreed,
>
> Can you please make a trace/tcpdump (on the olsr port) on the windows node
> AND on one of the Linux nodes when you crash the mesh?
>
> On 13/06/16 20:30, Henning Rogge wrote:
>
>> HI Ferry,
>>
>> I think we should get a tcpdump of this...
>>
>> if he manages to crash a current node with some "outdated windows
>> olsr", anyone could do it. It would be a bug in the current code.
>>
>> Henning
>>
>> On Mon, Jun 13, 2016 at 8:17 PM, Ferry Huberts <(spam-protected)>
>> wrote:
>>
>>> First try to upgrade all nodes to the same version.
>>> The latest would be preferred.
>>>
>>>
>>> On 13/06/16 18:31, Ray Berotsfield wrote:
>>>
>>>>
>>>> Hello all, this is my first post. I have a mesh network consisting of 7
>>>> linux based computers and two Windows 7 based computers. All devices run
>>>> OLSRd, the Linux machines run the latest release (0.9.0.3) and the
>>>> Windows machine runs an older release (0.5.6-r3). The Linux machines are
>>>> configured to connect to the network and run OLSRd on boot. The Windows
>>>> machine is configured to first connect to the ad-hoc network of the
>>>> nearest neighbor and then run olsrd. When running, all devices work
>>>> flawlessly, I can ping all other nodes without any issues and have
>>>> tested many different Geospatial positions of the various nodes.
>>>> However, there seems to be a serious vulnerability of the mesh
>>>> concerning the Windows machine network disconnect button or shutdown.
>>>> While the mesh is running, if I click on the network icon in the bottom
>>>> right hand corner of the screen and click on the ad-hoc network and
>>>> choose disconnect, the entire Mesh goes down. I cannot ping any other
>>>> nodes from any devices on the mesh. To fix it I have to restart every
>>>> single node. The same problem occurs when I shutdown a Windows machine
>>>> by pressing the shutdown button in the Start menu. The only time I don't
>>>> have those issue is if I unplug the windows machine without shutting
>>>> down normally. Does anyone know what I should do to fix this or what the
>>>> root of the problem may be?
>>>>
>>>>
>>>>
>>>>
>>> --
>>> Ferry Huberts
>>>
>>> --
>>> Olsr-users mailing list
>>> (spam-protected)
>>> https://lists.olsr.org/mailman/listinfo/olsr-users
>>>
>>
> --
> Ferry Huberts
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20160614/7ecf27b4/attachment.html>
-------------- next part --------------
03:44:27.208337 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:27.231292 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:27.660350 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:27.709031 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:27.952713 IP6 WINDOWSCOMPNAME.62386 > ff02::1:3.5355: UDP, length 46
03:44:27.953089 IP WINDOWSCOMPNAME.50055 > 224.0.0.252.5355: UDP, length 46
03:44:28.055199 IP6 WINDOWSCOMPNAME.62386 > ff02::1:3.5355: UDP, length 46
03:44:28.055363 IP WINDOWSCOMPNAME.50055 > 224.0.0.252.5355: UDP, length 46
03:44:28.153533 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:28.209888 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:28.259305 IP6 WINDOWSCOMPNAME.62683 > ff02::1:3.5355: UDP, length 43
03:44:28.259661 IP WINDOWSCOMPNAME.53324 > 224.0.0.252.5355: UDP, length 43
03:44:28.367209 IP6 WINDOWSCOMPNAME.62683 > ff02::1:3.5355: UDP, length 43
03:44:28.367405 IP WINDOWSCOMPNAME.53324 > 224.0.0.252.5355: UDP, length 43
03:44:28.570314 IP WINDOWSCOMPNAME.137 > 192.168.1.10.137: UDP, length 50
03:44:28.574690 IP 192.168.1.10 > WINDOWSCOMPNAME: ICMP 192.168.1.10 udp port 137 unreachable, length 86
03:44:28.709784 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:29.109545 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:29.177138 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:29.834522 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:30.011174 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:30.083052 IP WINDOWSCOMPNAME.137 > 192.168.1.10.137: UDP, length 50
03:44:30.087471 IP 192.168.1.10 > WINDOWSCOMPNAME: ICMP 192.168.1.10 udp port 137 unreachable, length 86
03:44:30.281574 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:30.698789 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:30.912905 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:31.196207 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:31.313581 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:31.596162 IP WINDOWSCOMPNAME.137 > 192.168.1.10.137: UDP, length 50
03:44:31.600471 IP 192.168.1.10 > WINDOWSCOMPNAME: ICMP 192.168.1.10 udp port 137 unreachable, length 86
03:44:31.621476 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:31.813378 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:32.147070 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:32.313761 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:33.110104 IP6 WINDOWSCOMPNAME.50198 > ff02::1:3.5355: UDP, length 43
03:44:33.110394 IP WINDOWSCOMPNAME.58992 > 224.0.0.252.5355: UDP, length 43
03:44:33.171667 arp who-has 192.168.1.10 (b8:27:eb:92:b0:67 (oui Unknown)) tell WINDOWSCOMPNAME
03:44:33.215961 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:33.218580 IP6 WINDOWSCOMPNAME.50198 > ff02::1:3.5355: UDP, length 43
03:44:33.218727 IP WINDOWSCOMPNAME.58992 > 224.0.0.252.5355: UDP, length 43
03:44:33.656518 arp who-has 192.168.1.12 tell WINDOWSCOMPNAME
03:44:33.716864 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:33.718455 arp reply 192.168.1.10 is-at b8:27:eb:92:b0:67 (oui Unknown)
03:44:33.994606 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:33.997713 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 56
03:44:34.170016 arp who-has 192.168.1.12 tell WINDOWSCOMPNAME
03:44:34.214876 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:34.215680 arp reply 192.168.1.12 is-at b8:27:eb:c4:86:4f (oui Unknown)
03:44:34.215702 IP WINDOWSCOMPNAME.137 > 192.168.1.12.137: UDP, length 50
03:44:34.216847 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:34.296454 IP 192.168.1.12 > WINDOWSCOMPNAME: ICMP 192.168.1.12 udp port 137 unreachable, length 86
03:44:34.704335 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:34.715029 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:35.135139 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:35.168408 IP WINDOWSCOMPNAME.137 > 192.168.1.12.137: UDP, length 50
03:44:35.217881 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 56
03:44:35.228961 IP 192.168.1.12 > WINDOWSCOMPNAME: ICMP 192.168.1.12 udp port 137 unreachable, length 86
03:44:35.627825 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:35.718553 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:36.204321 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:36.216371 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:36.652169 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:36.681524 IP WINDOWSCOMPNAME.137 > 192.168.1.12.137: UDP, length 50
03:44:36.719201 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:36.795004 IP 192.168.1.12 > WINDOWSCOMPNAME: ICMP 192.168.1.12 udp port 137 unreachable, length 86
03:44:37.163957 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:37.220562 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:37.720055 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:38.085952 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:38.195706 IP6 WINDOWSCOMPNAME.57733 > ff02::1:3.5355: UDP, length 90
03:44:38.196088 IP WINDOWSCOMPNAME.57919 > 224.0.0.252.5355: UDP, length 90
03:44:38.220846 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:38.303934 IP6 WINDOWSCOMPNAME.57733 > ff02::1:3.5355: UDP, length 90
03:44:38.304155 IP WINDOWSCOMPNAME.57919 > 224.0.0.252.5355: UDP, length 90
03:44:38.508966 IP6 WINDOWSCOMPNAME.52366 > ff02::1:3.5355: UDP, length 42
03:44:38.509341 IP WINDOWSCOMPNAME.51514 > 224.0.0.252.5355: UDP, length 42
03:44:38.615867 IP6 WINDOWSCOMPNAME.52366 > ff02::1:3.5355: UDP, length 42
03:44:38.616036 IP WINDOWSCOMPNAME.51514 > 224.0.0.252.5355: UDP, length 42
03:44:38.721396 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:38.819059 IP WINDOWSCOMPNAME.137 > 224.0.0.252.137: UDP, length 50
03:44:39.109198 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:39.222725 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:39.313695 arp who-has WINDOWSCOMPNAME tell 192.168.1.12
03:44:39.313717 arp reply WINDOWSCOMPNAME is-at ac:9e:17:59:67:98 (oui Unknown)
03:44:39.519469 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:39.723577 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:39.936074 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:40.123358 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:40.331801 IP WINDOWSCOMPNAME.137 > 224.0.0.252.137: UDP, length 50
03:44:40.464865 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:40.624923 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:41.026077 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:41.125366 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 56
03:44:41.362174 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:41.626054 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:41.844910 IP WINDOWSCOMPNAME.137 > 224.0.0.252.137: UDP, length 50
03:44:41.874386 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:42.126011 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:42.362827 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:42.525601 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:42.955219 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:43.026653 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:43.413134 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:43.424278 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:43.921942 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 56
03:44:43.929754 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:44.403437 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:44.428063 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:44.797818 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:44.927972 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28
03:44:45.354919 IP 192.168.1.12.698 > 255.255.255.255.698: UDP, length 28
03:44:45.428743 IP 192.168.1.10.698 > 255.255.255.255.698: UDP, length 28