Community discussions

MikroTik App
 
btang
just joined
Topic Author
Posts: 2
Joined: Tue Sep 13, 2016 5:57 am

possible regulatory info mismatch with CAP

Mon Dec 19, 2016 4:41 am

router board use one router as CAPsMAN , and a 951-n as AP .
CAP can connect to CAPsMAN and everything shows fine .
wireless device can not be connected though .
in the CAPsWAN wireless log , it shows
.................disconnected, received disassoc: unspecified (1)

In the CAPsWAN interface menu , it shows this ,
---possible regulatory info mismatch with CAP

what does this mean ?

thanks a lot !
 
btang
just joined
Topic Author
Posts: 2
Joined: Tue Sep 13, 2016 5:57 am

Re: possible regulatory info mismatch with CAP

Mon Dec 19, 2016 10:54 pm

Mikrotik support , please provide some info here please .
thanks !
 
MartijnVdS
Frequent Visitor
Frequent Visitor
Posts: 93
Joined: Wed Aug 13, 2014 9:36 am

Re: possible regulatory info mismatch with CAP

Tue Dec 20, 2016 8:51 am

Mikrotik support , please provide some info here please .
thanks !
If you want support to answer, you should probably email them. This isn't a support forum.
 
MartijnVdS
Frequent Visitor
Frequent Visitor
Posts: 93
Joined: Wed Aug 13, 2014 9:36 am

Re: possible regulatory info mismatch with CAP

Tue Dec 20, 2016 8:53 am

router board use one router as CAPsMAN , and a 951-n as AP .
CAP can connect to CAPsMAN and everything shows fine .
wireless device can not be connected though .
in the CAPsWAN wireless log , it shows
.................disconnected, received disassoc: unspecified (1)

In the CAPsWAN interface menu , it shows this ,
---possible regulatory info mismatch with CAP

what does this mean ?

thanks a lot !
I'd say the database of regulatory information on the CAP is different from the one on the manager.

Does it go away if you run the same RouterOS version on both ends?
 
User avatar
mrmut
Member Candidate
Member Candidate
Posts: 199
Joined: Mon May 18, 2009 2:10 pm

Re: possible regulatory info mismatch with CAP

Thu Sep 05, 2019 11:45 pm

I have had this several times. Usually fixed by restarting CAPsMan.

Don't know what causes it.

Who is online

Users browsing this forum: Kipk, Matta, Snooops and 31 guests