Page 1 of 1

CHR neighbour discovery problem

Posted: Wed Feb 07, 2018 9:11 pm
by sid5632
I've already emailed this to support@mikrotik.com ...

I have been finding Neighbour discovery on Winbox very unreliable with CHR VMs.
I started looking with Wireshark at the MNDP protocol packets and made the following observation.

On a Real Routerboard, the first 4 bytes of the UDP payload are (per packet) like this:
00 00 2d 02
00 00 2d 03
00 00 2d 04
00 00 2d 05
etc.

On a CHR, the equivalent bytes are:
8d 05 00 00
8e 05 00 00
8f 05 00 00
90 05 00 00

Winbox does eventually discover the CHR, but it takes a random (long) amount of time to do so.
This looks like a classic big-endian/little-endian problem with CHR in what it puts into the MNDP header - the rest of the data in the packet is OK.

If I log into the routers themselves, then CHRs never show up on a real router's neighbour list, and other CHRs never show up a a CHR's neighbour list.
I suspect this is also the same problem.

Re: CHR neighbour discovery problem

Posted: Tue Jun 19, 2018 4:25 am
by killersoft
Hmm.
Just noticed that too. The CHR shows up in other MT devices, but winbox does not..
Weird..

Re: CHR neighbour discovery problem

Posted: Tue Jun 19, 2018 8:19 am
by sid5632
Almost needless to say, support have not done anything about this.
You might have thought they could have tried this on any CHR and hardware unit out of the box.
But no, they demanded Supouts for this trivial, perfectly repeatable case. Sometimes you just wanna cry. I gave up. Why should I waste my time?

Re: CHR neighbour discovery problem

Posted: Tue Jun 19, 2018 11:02 am
by mrz
Looks to me like host configuration problem.

I can see from CHR all other CHRs and other devices in neighbor list, Winbox discovers all CHRs with no problems:
[admin@MikroTik] /ip neighbor> print
# INTERFACE ADDRESS MAC-ADDRESS IDENTITY VERSION
0 ether1 2.2.2.2 08:00:27:8B:66:7F MikroTik 7.0beta...
1 ether1 10.155.101.1 D4:CA:6D:73:98:18 3C22-at... 6.42 (s...
2 ether1 10.155.101.100 00:0C:42:00:D4:AF MikroTik 6.42rc5...
3 ether1 10.155.101.233 08:00:27:A6:62:3E MikroTik 7.0alph...
4 ether1 10.155.101.234 D4:CA:6D:8E:A8:2F MikroTik 6.42rc5...
5 ether1 10.155.101.235 D4:CA:6D:8E:A8:1F MikroTik 6.42 (s...
...

Re: CHR neighbour discovery problem

Posted: Tue Jun 19, 2018 11:05 am
by quackyo
0 ether1 2.2.2.2 08:00:27:8B:66:7F MikroTik 7.0beta...
3 ether1 10.155.101.233 08:00:27:A6:62:3E MikroTik 7.0alph...
...
You tease.... :)

Re: CHR neighbour discovery problem

Posted: Thu Jun 21, 2018 2:38 am
by sid5632
Looks to me like host configuration problem.
Configuration of what? My Windows machine? How? What? Where?
C'mon, give me something to go on.

It'll be nice if somebody actually said what exactly those 4 bytes mean in post #1.

Re: CHR neighbour discovery problem

Posted: Wed Oct 31, 2018 8:36 pm
by wispmikrotik
Looks to me like host configuration problem.

I can see from CHR all other CHRs and other devices in neighbor list, Winbox discovers all CHRs with no problems:
[admin@MikroTik] /ip neighbor> print
# INTERFACE ADDRESS MAC-ADDRESS IDENTITY VERSION
0 ether1 2.2.2.2 08:00:27:8B:66:7F MikroTik 7.0beta...
1 ether1 10.155.101.1 D4:CA:6D:73:98:18 3C22-at... 6.42 (s...
2 ether1 10.155.101.100 00:0C:42:00:D4:AF MikroTik 6.42rc5...
3 ether1 10.155.101.233 08:00:27:A6:62:3E MikroTik 7.0alph...
4 ether1 10.155.101.234 D4:CA:6D:8E:A8:2F MikroTik 6.42rc5...
5 ether1 10.155.101.235 D4:CA:6D:8E:A8:1F MikroTik 6.42 (s...
...
For this: "0 ether1 2.2.2.2 08:00:27:8B:66:7F MikroTik 7.0beta..."

Do you mean that version 7 will be available soon?

Regards.

Re: CHR neighbour discovery problem

Posted: Thu Nov 01, 2018 5:03 pm
by Steveocee
I too have this problem. Winbox finds all RB & CRS devices in my network but my CHR takes about 4 tries to discover if at all.

Re: CHR neighbour discovery problem

Posted: Mon Nov 05, 2018 1:12 pm
by jmginer
My CHR also takes around 1 minute to become discovered by Winbox.

Re: CHR neighbour discovery problem

Posted: Mon Nov 05, 2018 4:16 pm
by jarda
Me too. Discovery of chr takes ages usually.

Re: CHR neighbour discovery problem

Posted: Tue Nov 06, 2018 1:07 am
by sid5632
I suggest you all write to Mikrotik support, seeing as they clearly don't believe me - based on the fact that they have done NOTHING about this bug in the last 9 months.
Posting here is essentially pointless.

Re: CHR neighbour discovery problem

Posted: Tue Nov 06, 2018 10:45 am
by Steveocee
I suggest you all write to Mikrotik support, seeing as they clearly don't believe me - based on the fact that they have done NOTHING about this bug in the last 9 months.
Posting here is essentially pointless.
Done.

Re: CHR neighbour discovery problem

Posted: Fri Nov 16, 2018 5:09 pm
by Steveocee
So quick follow up.

MikroTik support have so far been very responsive however the implication is currently that the issue is with my computers L2 connectivity.
My desktop and 2 laptops can't discover it (cabled and 2 wireless) however the 'Tik App on my phone on the same wireless AP as the laptops CAN discover the CHR.

This leads me (personally) to think the problem MUST simply be with how Winbox is written? Why would the 'Tik App get the CHR and not Winbox from the same AP? It can't be L2.

Re: CHR neighbour discovery problem

Posted: Fri Nov 23, 2018 7:49 am
by filipelias
And I thought my chr is just slow

Send from my Moto Z Play using Tapatalk.