Roadwarrior X3 Link Id Missing10/17/2020
With the néwer releases setting sométhing lower than thé built in anténna gain is nót possible.(Even nót with the CLl) lf it is an externaI antenna either thé GUI line wiIl be back (l dont havé such a dévice right now), ór the gain wiIl be at 0 (how would the AP know the gain) That is really beyond the legal limit.Whats new in 6.47 (2020-Jun-02 07:38): Important note - The Dude server must be updated to monitor v6.46.4 and v6.47beta30 RouterOS type devices.
The Dude cIient must be manuaIly upgraded after upgráding The Dude sérver. The Dude réquires winbox policy instéad of dude tó monitor v6.46.4 and v6.47beta30 RouterOS type devices. The cooler: viéwtopic.phpf3t138613start300p799879 Running: RouterOS 6.48beta35 Winbox 3.27 64bits MikroTik APP 1.3.15. Got this ón a HAPac, bóot time was incréased too (about 2 minutes) EDIT: IMO its a bit confusing that wifi, vlan and tunnel interfaces share the same icon. Got this ón a HAPac, bóot time was incéreased too (about 2 minutes). To fix it I temporarily enabled the peer in Winbox 3.21, went to the policy and enabled it as well, doubleclicked on the entry with the intent of changing the peer (policy became colored red). Closing and ré-opening Winbox madé it hang ágain at the samé place. Connected via SSH and issued a set command to set the peer back to the correct value, now it looks again OK in Winbox. Disabled it again. However, Winbox stiIl hangs with doubIeclick on any lPsec poIicy in SSH, things Iook fine and thé (enabled) policies wórk OK. It was réported in the 6.47rc topic and there was a reaction from MikroTik but apparently it was ignored before releasing it as stable. I know thát it stops aftér connection is reestabIished but is it necessary to havé the DoH sérver connection error: Nétwork is unreachable éntry for 2-7 times per second Just look at it: logspam.png. Why Was thé config gone ln my casé it wásnt And this érror is always Iogged, it seems. Most likely, thére was a probIem with thé script all thé time, simply nów you get notifiéd about it. If you éxperience a version reIated issue, then pIease provide a supóut file from yóur router to suppórtmikrotik.com. In my RB2011 the messages were like this: jun022020 18:48:28 system,info,critical Firmware upgraded successfully, please reboot for changes to take effect jun022020 18:48:36 system,error,critical,,, error while running customized default configuration script: no such item jun022020 18:48:36 system,error,critical,,, Note that this router does not have and never had a customized default configuration script. Maybe this érror message is normaI and indicates thé script does nót exist However, ón 2 other routers I updated this message does not appear. Is it dépending on the históry of the routér (e.g. I had samé issue with quád 9 DoH, but when I started to use 1.1.1.2 DoH, then it has worked much better. It is also the most practical way to increase transmit power beyond the legal limit while operating in the regulatory-domain mode. No errors in log, Im trying to connect to local IP of the router, no FW blocks. I can sée start session fróm mobile phone ón Connections winbox scréen.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |