Netinstall 6.43rc19 does not work. I think for routeros 6.43rc17 need netinstall 6.43rc17.That version has been withdrawn. You would not want to install that! Get the 6.43rc19
Netinstall 6.43rc19 does not work. I think for routeros 6.43rc17 need netinstall 6.43rc17.That version has been withdrawn. You would not want to install that! Get the 6.43rc19
Wait, the first step in the post-v6.43 login method is to send the password in plain text? Who the hell thought that was a good idea?API authentication method have changed, see API manual:
https://wiki.mikrotik.com/wiki/Manual:API#Initial_login
Winbox 3.14RC work fine.... What's wrong with me?Login by Winbox does not work but SSH and Telnet works
download last winbox 3.14RC and "login great again".I reset my cfg with no default settings how do I get back in? It's over 300ft on a tower. I can mac telnet, but it tells me password is wrong.
I was experiencing very low download speeds. Been tying several rc versions. But now i have one AP and i cant get on it. Is there anything i can do???? Netinstall recognizes my AP but does not install.Why those who cannot login even installed the rc version?
What a mess.
First I connected via serial. Then I reformatted my NAND. So I Netinstalled 6.41.4 as to me that seems like the only stable version. I then updated firmware to the 6.41.4.. I formatted NAND again to be sure once I was sure of my firmware. I netinstalled 6.41.4 again and used a backup from months ago. This resulted in a clean install using a truly stable version of RouterOS. I dont consider 6.42.x or 6.43.x stable.
Once I had that up and going. I repartitioned to 2. I copied my known good clean install into the second partition. Copied the config. i then made it active and rebooted to change to it and verified it was good.
I then switched back and upgraded 6.41.4 to 6.43.19. Of course I lost Winbox access, however, Winbox 2.x works great as it does not use authentication.
So ive been running 6.43.19 for 3 days on a SOHO setup and its working fine. No issues in my simple test setup other then no 3.x Winbox and NO NETWATCH.
I do have a production older PPC based router which is stuck on 6.42.1 and only has 6MB of disc space left and so I cant update it. This sudden irreversible loss of discspace making it impossible to upgrade/downgrade is a unpatched issue that so far is kinda random. But it also occurs with 43RC so watch your system/resources/diskspace. The only way to fix this is NAND format and Netinstall.
Yea at this point these should not be considered Release Candidates, they should be considered engineering daily builds that could brick your device and require physical access with a serial cable to recover. I now consider ANYTHING that comes from Mikrotik in this category. Look at how bad the "stable" release of 42.1 was.
So for me 6.41.4, all services disabled except Winbox and that set to LAN side only with a custom port.
MIKROTIK - PLEASE REVIEW AND CORRECT ALL KNOWN ISSUES BEFORE ADDING ANY NEW FEATURES. FOCUS YOUR STAFF ON GETTING THINGS STABLE AND RESTORING LOST FEATURES LIKE NETWATCH. 43RC19 is close. Fix authentication and add Netwatch.
The forum users here are awesome. So is Mikrotik. Ive been using ONLY mikrotik products for 8 years. Im confident things will get resolved. BUT. Im concerned by all these missteps in a row over the last 2 months.@Xymox,
what have we (forum users) done to you?
Please stop flooding forum with useless texts. if you have to say something ugly to mikrotik staff, please write directly to support, not here.
If you have been following these topics on the forum for some time, you shold know, they are exactly that.Yea at this point these should not be considered Release Candidates, they should be considered engineering daily builds that could brick your device and require physical access with a serial cable to recover. I now consider ANYTHING that comes from Mikrotik in this category. Look at how bad the "stable" release of 42.1 was.
Note that release candidate versions are published strictly for testing purposes and should not be used on production routers.
Unfortunately some people can't read it if they don't visit the forum There's no such warning in WinBox, for example.That warning is perfectly clear. Unfortunately some people don't read.
So rc!=rc that makes no sense!If you have been following these topics on the forum for some time, you shold know, they are exactly that.Yea at this point these should not be considered Release Candidates, they should be considered engineering daily builds that could brick your device and require physical access with a serial cable to recover. I now consider ANYTHING that comes from Mikrotik in this category. Look at how bad the "stable" release of 42.1 was.
Unofficially "rc" = "beta" or "nightly build". "current" = "rc". "bugfix" ="stable"
And why should people have to read these things, just make RC a real RC and not a nightly.Unfortunately some people can't read it if they don't visit the forum There's no such warning in WinBox, for example.That warning is perfectly clear. Unfortunately some people don't read.
... or call it "Recently Compiled" instead of "Release Candidate"...And why should people have to read these things, just make RC a real RC and not a nightly.
Naming of releases should be self explanatory
Or call it "Ridiculous Count"... Once Linus Torvalds stated:... or call it "Recently Compiled" instead of "Release Candidate"...And why should people have to read these things, just make RC a real RC and not a nightly.
Naming of releases should be self explanatory
However, for some reason four numbers just looks visually too obnoxious to me, so as I don't care that much, I'll just use "-rc", and we can all agree that it stands for "Ridiculous Count" rather than "Release Candidate".
As I have said. I love Mikrotik. I literally use nothing else. For 8+ years. I have great respect for Normis here on the forum. I NEVER intended any disrespect to anyone or to Mikrotik. In fact, I have great respect that they have allowed me to post these posts.If you have been following these topics on the forum for some time, you shold know, they are exactly that.Yea at this point these should not be considered Release Candidates, they should be considered engineering daily builds that could brick your device and require physical access with a serial cable to recover. I now consider ANYTHING that comes from Mikrotik in this category. Look at how bad the "stable" release of 42.1 was.
Unofficially "rc" = "beta" or "nightly build". "current" = "rc". "bugfix" ="stable"
Regarding the travel cost to many sites from the same reason... It looks like you are not testing the new versions before productive implementation. Otherwise I cannot explain to myself how you could break many remote sites at once. I always deploy newer versions in vawes starting on the closest sites and continue with the further if nothing bad happens during a week or so. But never at once.
Technically, 6.42 topic is locked, so they continue hereAnd again - this is not 6.43rc version related discussion.
Things, just got interesting!!Version 6.43rc21 has been released.
*) dhcp - added dynamic IPv4/IPv6 "dual-stack" simple queue support, based on client's MAC address;
*) dhcpv4-server - added "allow-dual-stack-queue" implementation (CLI only);
*) dhcpv6-server - added "allow-dual-stack-queue" implementation (CLI only);
!) radius - use MS-CHAPv2 for "login" service authentication;
Could you please explain how to enable this function?*) dhcp - added dynamic IPv4/IPv6 "dual-stack" simple queue support, based on client's MAC address;
*) dhcp - fixed DHCP server stuck in invalid state;
*) dhcpv4-server - added "allow-dual-stack-queue" implementation (CLI only);
*) dhcpv6-server - added "allow-dual-stack-queue" implementation (CLI only);
So... Where's my health?*) winbox - show "System/Health" only on boards that have health monitoring;
I wish Mikrotik would just move to a compressed root image thats decompressed to a Read-Only RAM disk on boot, with a seperate R/W partition for persistent data (configuration files), accross all platforms. RAM is cheap, and a lot of existing platforms already have enough RAM to do this.I lost 10MB of disc space when I upgraded from RC19 to RC21 on a CCR. Ive seen this same thing on PPC and MIPSBE.. MT Support replicated it and is working on it. After a few upgrades or downgrades you can run out of space and then the only thing you can do is Netinstall as your stuck on whatever version your at. This effects 6.42.x thru 6.43RC21. So careful upgrading as you might be loosing space with each time you do it, this is kinda critical on devices with low disc space.. MT support has seen it, so, its getting worked on.
IMHO always use partitions when you upgrade so its easy to go back.
Netwatch problem persistXymox - for example, your Netwatch includes this command "/system script run IPSMTP". So are policies write,read,reboot,test or only some of them, only ones that are enabled on this script? For example, no romon policy, no dude policy, etc. And again - this is not 6.43rc version related discussion.
MT has said this thread is not the place for Netwatch discussion. So I started a separate thread. viewtopic.php?f=2&t=134538Netwatch problem persistXymox - for example, your Netwatch includes this command "/system script run IPSMTP". So are policies write,read,reboot,test or only some of them, only ones that are enabled on this script? For example, no romon policy, no dude policy, etc. And again - this is not 6.43rc version related discussion.
tested on rb750UP with routeros 6.43RC21
No log error, only log the netwatch up or down, script dont run, no error messages
User owner of the script permissions full
Captura.JPG
The wiki has been updated with examples:Could you please explain how to enable this function?*) dhcp - added dynamic IPv4/IPv6 "dual-stack" simple queue support, based on client's MAC address;
*) dhcp - fixed DHCP server stuck in invalid state;
*) dhcpv4-server - added "allow-dual-stack-queue" implementation (CLI only);
*) dhcpv6-server - added "allow-dual-stack-queue" implementation (CLI only);
I've looked at wiki, but there are details only about leases and bindings.
Cheers
Thanks for that, artz!The wiki has been updated with examples:
https://wiki.mikrotik.com/wiki/Manual:I ... e_limiting
https://wiki.mikrotik.com/wiki/Manual:I ... e_limiting
I only have suggestions for improvement:Everyone who complained about the Netwatch issue - Please see this topic viewtopic.php?f=2&t=134538
https://wiki.mikrotik.com/wiki/Manual:API#Initial_loginCould anyone give an example of how to connect in the api PHP in the new version of mikrotik v3.43rc21
I modified the php file for now this way and it works... it is not detecting prior version... I hope 6.43 comes out soon to keep it like thathttps://wiki.mikrotik.com/wiki/Manual:API#Initial_loginCould anyone give an example of how to connect in the api PHP in the new version of mikrotik v3.43rc21
check version one would need if he has to manage multiple devices prior the change and after like me.You don't have to check version.
* Send /login with username and password in plain text
* if response is with challenge then fall back to old login method
* otherwise check status if login is successful
As an example see how it is done on python example in the wiki
if ($this->socket) {
socket_set_timeout($this->socket, $this->timeout);
// RouterOS >= 6.43
$this->write('/login', false);
$this->write('=name=' . $login, false);
$this->write('=password=' . $password);
$RESPONSE = $this->read(false);
if (isset($RESPONSE[0]) && $RESPONSE[0] == '!done') {
//RouterOs < 6.43
if (isset($RESPONSE[1])) {
$MATCHES = array();
if (preg_match_all('/[^=]+/i', $RESPONSE[1], $MATCHES)) {
if ($MATCHES[0][0] == 'ret' && strlen($MATCHES[0][1]) == 32) {
$this->write('/login', false);
$this->write('=name=' . $login, false);
$this->write('=response=00' . md5(chr(0) . $password . pack('H*', $MATCHES[0][1])));
$RESPONSE = $this->read(false);
if (isset($RESPONSE[0]) && $RESPONSE[0] == '!done') {
$this->connected = true;
break;
}
}
}
}
else
{
$this->connected = true;
break;
}
}
fclose($this->socket);
}
Nothing worked for me either when I upgraded from v5.26 straight to 6.42.3 and I tested it in different platforms with the same exact boot problem. Everything stopped working after the upgrade and you had to use netinstall to recover. However everything worked good when upgrading to bugfix first and then to current. I had no boot problems whatsoever. However I could not get a clean backup when upgrading from bugfix to current. I get always an error so after both upgrades are done you have to do a final step and reset to factory defaults and then copy paste the original rsc file.I did test upgrade from 5.26 to this version. Just for testing. Everything went well. Upgrade failed for you due to configuration or something like thta. In general it works just fine.
Security risk is really not as important as functionality and speed to me in some installations as those old versions are not accessible. I was actually forced to downgrade from current as there is lack of MT support and broken code in later versions of ROS for the dual nstream, besides a few other problems, like the backup error current ROS almost always has. Those old versions have been working rock solid for many years. Sometimes upgrading is not a very wise choice.And, keep "current" a bit more regularly. Running such old versions is a security risk, that is widely known in all of the software world.
So where is new Windows Bandwidth Test app?!) btest - requires at least v6.43 Bandwidth Test client when connecting to v6.43 or later version server except when authentication is not required;
Version 6.43rc21 has been released.
MAJOR CHANGES IN v6.43:
----------------------
!) winbox - improved authentication process excluding man-in-the-middle possibility (Winbox v3.14 required);
----------------------
Thanks. It's working for Winbox, but Dude is still complainingVersion 6.43rc21 has been released.
MAJOR CHANGES IN v6.43:
----------------------
!) winbox - improved authentication process excluding man-in-the-middle possibility (Winbox v3.14 required);
----------------------
You can find Winbox here: https://mikrotik.com/download
As I wrote in the 6.42.3 thread, the check-installation function does not seem to have the claimed new functionality/System check-installation reports everything ok and the old system check-disk is no longer there.
What are those bindstr and bindstr2?*) chr - provide part of network interface GUID at the beginning of "bindstr2" value when running CHR on Hyper-V;
is it for SXT LTE?*) lte - improved modem event processing;
Hello @mrz ,You don't have to check version.
* Send /login with username and password in plain text
* if response is with challenge then fall back to old login method
* otherwise check status if login is successful
As an example see how it is done on python example in the wiki
def login(self, username, pwd):
for repl, attrs in self.talk(["/login"]):
chal = binascii.unhexlify((attrs['=ret']).encode('UTF-8'))
md = hashlib.md5()
md.update(b'\x00')
md.update(pwd.encode('UTF-8'))
md.update(chal)
self.talk(["/login", "=name=" + username,
"=response=00" + binascii.hexlify(md.digest()).decode('UTF-8') ])
seems, not. rc23 even worse for LHG. alot disconnects (~50/hour). after roll back to 6.42.3 - rockstable.Does rc23 fix the w60g issues seen in rc19 and rc21?
It was last edited a year ago. It's not compatible with 6.43 changes.Reading https://wiki.mikrotik.com/wiki/Manual:API_Python3
Can you please tell me if the function login is compatible with v 6.42 and v 6.43 ?
Hello strods!*) dhcpv6-server - added initial dynamic simple queue support;
Do you have reported this to Mikrotik and if, what is your support ticket id?Bug in 6.43rc23:Is this bug fixed in 6.43rc27?
- Upgrade from previous version to 6.43rc23 when you have /ip ipsec peer proposal with hash-algorithm=sha512
- Open this proposal in Winbox. You will see that in Winbox it have checked md5 and sha1, but in the export it have sha512
- Set hash algorithm to sha512 through Winbox, now autosup file starts generating
Reported just now. Ticket id is 2018061322004299Do you have reported this to Mikrotik and if, what is your support ticket id?
Try to recover with MAC telnet if possible. I had the same issue and I was lucky.I have upgrade my SXT LTE (band 3,7), from ROS 6.42.3 to 6.43RC27.
But after upgrading... I can't get access to my SXT LTE.
Wrong username or password message.
Device is on tower so, difficult to reset device.
What is the problem?
But that does not yet work with RouterOS 6.43rc. I opened an issue already.
Can anyone already quantify this in some way?*) w60g - improved link stability;
*) w60g - improved maximum link distance;
I think no.How could you think that 60g will work without clear line of sight?
Which RADIUS server did you use? Can you post a configuration example?tested winbox auth. with radius (mschapv2) interworking. works like a charm!
I running lastest version Winbox 3.14.He simply needs new WinBox
I have read many many time changelog and nothing explicit about solution or notice about this problemPlease read the changelog.
1) distance mesurement in CLI is here since rc19. Has it been improved somehow? Or what is the difference?
*) w60g - added distance measurement (CLI only);
*) w60g - improved link stability;
*) w60g - improved maximum link distance;
You need Winbox 3.14Big problem...
Updated Mys CCR (to 6,43rc27) an now stucked outside! All is running but cant connect - wrong username or password??? A bit of PANIC!!!
------------------
Sorry! Had two winbox on my pc!! Just need new winbox! Sorry!
1) Yes, there are some improvements - mostly stability
1) distance mesurement in CLI is here since rc19. Has it been improved somehow? Or what is the difference?
3) what is the new maximum link distance for WAP60 and LHG60?
2) I have a 10 meters long test link between 2 LHG60s (YES, I know it too little for LHG60 and can be clearly solved by wireless wire, but unfortunately I do not have possibility for longer distance for testing at the moment and it will be used for 500m "production" link in the near future) and I have to say that link flaps approximately 5 times per day (no rain, no wind, nothing breaking the clear line of sight, no birds flying, no obvious reason for link flap). Can be caused just by the fact it too close to each other? Or is it something what should be checked by MikroTik (maybe a kind of bug)? The link is under continuous iperf3 bi-directional test, where two servers with 1Gbit/s NICs at the end. Result is somewhere between 800-870 Mbit/s for bi-directional TCP connection and PING is somewhere between 5 to 15 ms.
MIKROTIK please how can we solve this problem?Big problem...
Updated Mys CCR (to 6,43rc27) an now stucked outside! All is running but cant connect - wrong username or password??? A bit of PANIC!!!
------------------
Sorry! Had two winbox on my pc!! Just need new winbox! Sorry!
Please provide more details to support@mikrotik.comCan somebody please recommend stable SW for wireless wire wAP60G ? I have tried many but all are unstable ? (jam after couple of days = hard reset is necessary). It is probably linked with hot weather ... Thank you.
Do You have level4 license on Bridge device?I am still experiencing a problem with the WAP60 on this firmware.
Both client & AP running latest release.
Client connects when ap set to bridge. However when AP set to ap-bridge same client will not connect. No matter which frequency is selected (even the new 64800)
what is the new maximum distance for wAP60g and LHG60G?*) w60g - improved maximal achievable distance;
That's just wireless PHY basics. The smaller the wavelength gets, the penetrative wave properties decrease rapidly but the reflective ones increase. Think low/medium frequency ≈ broadcast radio (goes literally straight through the ground), very high frequency ≈ visible light (is reflected almost 100% on mirrors or white objects). This is basically the point for having beamforming, too.How could you think that 60g will work without clear line of sight?
look for problem on your network, for me works fine.I upgraded to 6.43rc32 and even using winbox 3.15 login fails!
look problem on your network, for me works fine.I upgraded to 6.43rc32 and even using winbox 3.15 login fails!
i have observed this weird issue with password in earlier rc. i just changed password before upgrade and not logged in after upgrade with new one, just with old.I reset it and now it works...
weird because the password is saved as a favorite in winbox so I wasn't typing anything wrong earlier... and right before the update I used the same favorite to login to it and update it!
still need to upgrade dude client manually. Client crashes after each upgrade via client uiVersion 6.43rc32 has been released.
*) dude - fixed client auto upgrade (broken since 6.43rc17);
Thank you for a report, but can you please confirm that your Dude client (executed with the administrator rights) auto upgrade was working before 6.43rc17, and does not work in 6.43rc32 ?still need to upgrade dude client manually. Client crashes after each upgrade via client uiVersion 6.43rc32 has been released.
*) dude - fixed client auto upgrade (broken since 6.43rc17);
So thats the trick Yes, with "launch as administrator" dude client updates as expected. But is this "feature" documented somewhere? Because if i load exe "as administrator" i need to enter credentials like first time.Thank you for a report, but can you please confirm that your Dude client (executed with the administrator rights) auto upgrade was working before 6.43rc17, and does not work in 6.43rc32 ?still need to upgrade dude client manually. Client crashes after each upgrade via client uiVersion 6.43rc32 has been released.
*) dude - fixed client auto upgrade (broken since 6.43rc17);
It is a CHR. Apparently it does not have IP Cloud, but I noticed that only because I wanted to have a look at it after reading change notes.pe1chl - Can you provide supout file from RouterBOARD that does not show IP/Cloud menu on GUI?
There is other topic with problems ARM and NV2 - viewtopic.php?f=7&t=128916&p=670546#p669811What kind of issue are you referring to? Have you contacted support directly to see if problem is not caused by configuration or something that can be adjusted in order to resolve the issue?
*) tile - fixed Ethernet interfaces becoming unresponsive;
I have a very strange problem with a CCR1072. Suddenly there are IP addresses that stop responding, some work and others do not... within the same broadcast (L2) -no routing apply-. There is no problem of firewall or similar, by ARP the MAC is seen, but communication is simply lost... until a reboot is made and everything works again. It has happened to me twice in the last week. With the 6.42.1. Does this changelog correct this problem or similar?
The problem happens in an 802.3ad bonding interface with vlans on it. At the other end there is a CRS317-1G-16S switch. Even if I restart the switch, it does not recover the communication... I must restart the CCR1072.
We have about 30 x CCR's installed in exactly this fashion, Bonding interface with LACP to a switch (Extreme x620/x670 and Juniper EX4550) and have not experienced this problem, we have been running this configuration successfully for over 5 years now from 6.0rc5 to 6.40.8So my big question is: Is it the problem in CRS317 or in CCR1072, or maybe the mix of both? I think it has some relationship with bonding...
This fix has a problem, it ruins the installation. When you have only one partition, it means netinstall.Thank you very much for the reports about issues with space, next RouterOS version will fix the issue.
Meanwhile this package can be used to clear space on your router,
The current Beta version does match the 6.43rc changes for my device.Do you guys have an ETA for an updated Android TikApp (or beta version), to match the 6.43rc series authentication / login changes?
I'm successfully upgraded a hAp ac2.WARNING!!! This version 6.43rc40 just bricked two RBSXTsq5HPnD units I was testing it with. Software upgrade went fine from the factory installed 6.40.4 but then the firmware upgrade bricked the units. Netinstall currently underway.
hAp ac2 is not a RBSXTsq5HPnD - also this may depend on what ROS version is being upgraded from. I am happy that you have not had a problem. However I can recreate this bricking process by taking another unit off the shelfI'm successfully upgraded a hAp ac2.WARNING!!! This version 6.43rc40 just bricked two RBSXTsq5HPnD units I was testing it with. Software upgrade went fine from the factory installed 6.40.4 but then the firmware upgrade bricked the units. Netinstall currently underway.
This also may depend on the configuration of the device.hAp ac2 is not a RBSXTsq5HPnD - also this may depend on what ROS version is being upgraded from. I am happy that you have not had a problem. However I can recreate this bricking process by taking another unit off the shelfI'm successfully upgraded a hAp ac2.WARNING!!! This version 6.43rc40 just bricked two RBSXTsq5HPnD units I was testing it with. Software upgrade went fine from the factory installed 6.40.4 but then the firmware upgrade bricked the units. Netinstall currently underway.
Netinstall does recover the unit and even allowed v6.43rc40 to be loaded - so this is a fault of the upgrade process.
That was a valid point - however I just tested another fresh unit from the same batch which was fully reset with no defaults and I can confirm it is also bricked.This also may depend on the configuration of the device.
Yeah well that doesn't change the value of the warning that I am giving - especially as the units in question came factory shipped with 6.40.4. Also saying that you cannot upgrade from an older version because of problems in the older version is kinda crazyIt has been stated multiple times here that most of the upgrade process is performed by the old version from which you upgrade. So if you in all cases upgraded from 6.40.4., the issue may also be that one, not the 6.43rc40.
Well, saying it is not crazy, the fact that it happens for some versions is a different question But this warning has been published by Mikrotik staff in earlier topics here, the only thing I'm far from sure is whether 6.40.4 is affected by that issue or not.saying that you cannot upgrade from an older version because of problems in the older version is kinda crazy
I did - and that does workTry to upgrade the 6.40.4 first to the current version (6.42.5) and then upgrade to 6.43rc from there.
That comment made me smileWell, saying it is not crazy, the fact that it happens for some versions is a different question
Same for me, but on a CRS328, upgrade is fine, but when i upgraded the routerboot and rebooted the system not load anymore, i do it a netinstall and recovered the board.WARNING!!! This version 6.43rc40 just bricked two RBSXTsq5HPnD units I was testing it with. Software upgrade went fine from the factory installed 6.40.4 but then the firmware upgrade bricked the units. Netinstall currently underway.
How to see it in action?...
!) cloud - added IPv6 support;
...
Fixes for connecting issues will be included in next RC versionwAP60G 240m link updated from rc32 to rc42, client not connecting any more in scan see signal but not connecting, back to 6.42.5 it is working again, but seem to me it is not stable as has been in 6.42.1.
Also please check scan for frequency 64800 seems to me it is not scanning that frequency when click scan button.
Had the same with my HAP AC2. Had no time to look for a fix, did you need netinstall?WARNING!!! This version 6.43rc40 just bricked two RBSXTsq5HPnD units I was testing it with. Software upgrade went fine from the factory installed 6.40.4 but then the firmware upgrade bricked the units. Netinstall currently underway.
In RC34; *) winbox - show "System/Health" only on boards that have health monitoring. I don't know if the cAP AC does support health.A little bug, When running 6.43rc42 on a cAP AC running "/system health print" outputs nothing, and the health menu is gone from WinBox.
17:26:49 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3
17:27:17 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3
17:27:17 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3
17:27:41 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3
17:27:41 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3
17:28:08 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3
17:28:08 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3
17:28:35 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3
17:28:35 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3
17:29:03 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3
17:29:03 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3
17:29:30 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3
17:29:30 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3
17:29:57 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3
17:29:57 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3
17:30:24 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3
17:30:24 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3
17:30:49 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3
17:30:49 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3
17:31:16 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3
17:31:16 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3
17:31:46 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3
17:31:46 dhcp,info dhcp-server assigned 192.168.1.4 to 74:5E:1C:32:14:C3
17:32:12 dhcp,info dhcp-server deassigned 192.168.1.4 from 74:5E:1C:32:14:C3
[admin@MikroTik] /ip cloud> print
ddns-enabled: yes
update-time: no
status: connecting...
I can confirm, LHG60 does not connect for more than few seconds, still disconnecting and reconnecting. Back on 6.42.5 - works again OK.Fixes for connecting issues will be included in next RC versionwAP60G 240m link updated from rc32 to rc42, client not connecting any more in scan see signal but not connecting, back to 6.42.5 it is working again, but seem to me it is not stable as has been in 6.42.1.
Also please check scan for frequency 64800 seems to me it is not scanning that frequency when click scan button.
same hereI can confirm, LHG60 does not connect for more than few seconds, still disconnecting and reconnecting. Back on 6.42.5 - works again OK.Fixes for connecting issues will be included in next RC versionwAP60G 240m link updated from rc32 to rc42, client not connecting any more in scan see signal but not connecting, back to 6.42.5 it is working again, but seem to me it is not stable as has been in 6.42.1.
Also please check scan for frequency 64800 seems to me it is not scanning that frequency when click scan button.
Does it resolve to IPv6 address exclusively then? That would be a real issue for be, because I have devices connected via dual stack, but connect to them from IPv4-only networks.amokkatmt - If your router can reach cloud server over IPv6, then Cloud should resolve to IPv6 address instead of IPv4. That happens automatically;
6.42.5 (latest current till now) works OK for me.I wonder if the same limitations and/or problems apply to LHGG-60ad. Anyone installed them? We are expecting a pair of those and I was wondering what would be the best stable ROS for it. It will be a production link so stability is a must.
Why do you think two DNS names (one with A record and one with AAAA record) is better than having one DNS name with both A and AAAA records?Even better, have two automatically generated FQDNs, one with a "-ip4" and one with "-ip6" suffixes after the serial number and associate each with the respective address.
Because if for example you have a network with different restrictions for IPv4 and IPv6, you can explicity choose which protocol to use to manage the devices, instead of the device deciding for you.Why do you think two DNS names (one with A record and one with AAAA record) is better than having one DNS name with both A and AAAA records?Even better, have two automatically generated FQDNs, one with a "-ip4" and one with "-ip6" suffixes after the serial number and associate each with the respective address.
Please do not post change notes like that!*) dhcpv6 - improved reliability on IPv6 DHCP services;
Could this, by any remote chance, be related to the issue described here?For example, DHCPv6 issue could lead to DHCPv6 service crash (can be seen only by MikroTik staff) and IPv6 services could not work or work incorrectly.
Yes, it has certainly improved! good to see that warnings like that are now also visible when doing the one-click-upgrade from the router itself. Lots of people never look here so they do not see the warnings about winbox versions when they are not in the changelog.As you can see in 6.43rc release - we are improving changelog so important notes would be more noticeable. Also, for example, Winbox vulnerability issue was mentioned in changelog and special topics were made.
So encryption=rc4 is the old behaviour, encryption=aes-sha256 is the new one? What is the default if I do not specify the option?*) backup - added support for new backup file encryption (AES128-CTR) with signatures (SHA256);
What type of laptop do you have, do you know the WiFi chip and number of antennas it has? There are no known issues with the mentioned model, it works fine for most peopleAre you still working on hAP ac2's WiFi performance? I use laptop with Intel 7260 and WiFi performance is very poor (it fluctuates a lot within a huge range between 20 KB/s and 9 MB/s with average around 500 KB/s. The same laptop achieves 250 Mbit (which is what I pay for) when I use router provided by ISP (both stay almost in the same place).
Do you have updated wifi card drivers? Use the Intel® Driver & Support Assistant, or manually locate it.Are you still working on hAP ac2's WiFi performance? I use laptop with Intel 7260 and WiFi performance is very poor (it fluctuates a lot within a huge range between 20 KB/s and 9 MB/s with average around 500 KB/s. The same laptop achieves 250 Mbit (which is what I pay for) when I use router provided by ISP (both stay almost in the same place).
It's Sony Vaio Pro 13 (https://www.trustedreviews.com/reviews/sony-vaio-pro-13).What type of laptop do you have, do you know the WiFi chip and number of antennas it has? There are no known issues with the mentioned model, it works fine for most peopleAre you still working on hAP ac2's WiFi performance? I use laptop with Intel 7260 and WiFi performance is very poor (it fluctuates a lot within a huge range between 20 KB/s and 9 MB/s with average around 500 KB/s. The same laptop achieves 250 Mbit (which is what I pay for) when I use router provided by ISP (both stay almost in the same place).
# uname -a
Linux vp 4.17.5-1-ARCH #1 SMP PREEMPT Sun Jul 8 17:27:31 UTC 2018 x86_64 GNU/Linux
# lspci
01:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b)
Subsystem: Intel Corporation Dual Band Wireless-N 7260
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 44
Region 0: Memory at f7c00000 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee08004 Data: 4023
Capabilities: [40] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr+ NoSnoop+ FLReset-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <4us, L1 <32us
ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp-
LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Range B, TimeoutDis+, LTR+, OBFF Via WAKE#
AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 16ms to 55ms, TimeoutDis-, LTR+, OBFF Disabled
AtomicOpsCtl: ReqEn-
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
HeaderLog: 00000000 00000000 00000000 00000000
Capabilities: [140 v1] Device Serial Number 5c-51-4f-xx-xx-xx-xx-xx
Capabilities: [14c v1] Latency Tolerance Reporting
Max snoop latency: 3145728ns
Max no snoop latency: 3145728ns
Capabilities: [154 v1] Vendor Specific Information: ID=cafe Rev=1 Len=014 <?>
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
# systool -vm iwlwifi
Module = "iwlwifi"
Attributes:
coresize = "327680"
initsize = "0"
initstate = "live"
refcnt = "1"
srcversion = "A082116DEC439F44B0AAD63"
taint = ""
uevent = <store method only>
Parameters:
11n_disable = "0"
amsdu_size = "0"
antenna_coupling = "0"
bt_coex_active = "Y"
d0i3_disable = "Y"
d0i3_timeout = "1000"
debug = "0"
disable_11ac = "N"
fw_monitor = "N"
fw_restart = "Y"
lar_disable = "N"
led_mode = "0"
nvm_file = "(null)"
power_level = "0"
power_save = "N"
swcrypto = "0"
uapsd_disable = "3"
Sections:
.altinstr_replacement= "0xffffffffc0a9da3d"
.altinstructions = "0xffffffffc0ab9f10"
.bss = "0xffffffffc0abeec0"
.data.once = "0xffffffffc0abd8f0"
.data = "0xffffffffc0abb300"
.exit.text = "0xffffffffc0a9da2c"
.gnu.linkonce.this_module= "0xffffffffc0abeb80"
.init.text = "0xffffffffc0acd000"
.note.gnu.build-id = "0xffffffffc0a9e000"
.orc_unwind = "0xffffffffc0ab35dd"
.orc_unwind_ip = "0xffffffffc0aaf6c5"
.parainstructions = "0xffffffffc0aba090"
.ref.data = "0xffffffffc0abdd00"
.rodata = "0xffffffffc0a9e5c0"
.rodata.str1.1 = "0xffffffffc0aa9bbb"
.rodata.str1.8 = "0xffffffffc0aab858"
.smp_locks = "0xffffffffc0ab9f2c"
.strtab = "0xffffffffc0adab40"
.symtab = "0xffffffffc0ace000"
.text = "0xffffffffc0a7c000"
.text.unlikely = "0xffffffffc0a9da45"
__bpf_raw_tp_map = "0xffffffffc0abd900"
__bug_table = "0xffffffffc0abd0b0"
__jump_table = "0xffffffffc0abb000"
__kcrctab = "0xffffffffc0a9e490"
__kcrctab_gpl = "0xffffffffc0a9e4a0"
__ksymtab = "0xffffffffc0a9e030"
__ksymtab_gpl = "0xffffffffc0a9e070"
__ksymtab_strings = "0xffffffffc0aaf130"
__mcount_loc = "0xffffffffc0ab9488"
__param = "0xffffffffc0ab9c68"
__tracepoints_ptrs = "0xffffffffc0aba1b0"
__tracepoints_strings= "0xffffffffc0aba280"
__tracepoints = "0xffffffffc0abe540"
_ftrace_events = "0xffffffffc0abdc20"
# dmesg | grep -i iwl
[ 3.119352] iwlwifi 0000:01:00.0: enabling device (0000 -> 0002)
[ 3.124355] iwlwifi 0000:01:00.0: loaded firmware version 17.948900127.0 op_mode iwlmvm
[ 3.288512] iwlwifi 0000:01:00.0: Detected Intel(R) Dual Band Wireless N 7260, REV=0x144
[ 3.314884] iwlwifi 0000:01:00.0: base HW address: 5c:51:4f:xx:xx:xx
[ 3.516017] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[ 3.518324] iwlwifi 0000:01:00.0 wlp1s0: renamed from wlan0
I don't use Windows, I don't have it installed. I use latest Linux kernel so yes, the driver is in latest version I use this latptop with many APs all over the world and it has no issues. As I said before, I get 250 Mbit in my house using router provided by my ISP where Mikrotik is not even close. Both routers are next to each other.Do you have updated wifi card drivers? Use the Intel® Driver & Support Assistant, or manually locate it.Are you still working on hAP ac2's WiFi performance? I use laptop with Intel 7260 and WiFi performance is very poor (it fluctuates a lot within a huge range between 20 KB/s and 9 MB/s with average around 500 KB/s. The same laptop achieves 250 Mbit (which is what I pay for) when I use router provided by ISP (both stay almost in the same place).
He had the same problem and the update helped.
I hope it's not off topic, but when should we expect this to hit the current branch? I have a production userman router that seems to be having some recent Paypal issues lately.Version 6.43rc40 has been released.
*) userman - fixed compatibility with PayPal TLS 1.2;
This is weekly graph on my hAP ac²Anyone else getting this?
GET /routeros/LATEST.6rc HTTP/1.1
Host: upgrade.mikrotik.com
HTTP/1.1 200 OK
Date: Mon, 23 Jul 2018 08:01:34 GMT
Content-Type: application/octet-stream
Content-Length: 20
Last-Modified: Thu, 12 Jul 2018 11:05:13 GMT
Connection: keep-alive
ETag: "5b4735e9-14"
Server: ThirdWorldFileDaemon
Access-Control-Allow-Origin: *
Accept-Ranges: bytes
6.43rc44 1531295119
it`s not that the idea? i use this usb stick only for sms netwatch(internet it`s not include it), but i don`t understand why evyrything work normaly before with this gsm option and now did`t not.As a workaround worth trying if this issue complicates your life, it might be possible to send the SMSes using /interface lte at-chat and the AT command used to send SMSes on your modem model.
*) wireless - improved Nv2 reliability on ARM devices;
The first point-to-point tests with nv2 on arm are not satisfactory. We will perform more tests
can you show some results? i was experiencing performance varying between 250-430Mbps using SXTsq ACs with early 6.43rc builds even under excellent conditions.Little bit better but the issue still present
Just a question without intention of doubting what you say: why use NV2 on PtP?*) wireless - improved Nv2 reliability on ARM devices;
The first point-to-point tests with nv2 on arm are not satisfactory. We will perform more tests
yeah, that's funnyOk so now I test the RC45 Build. My setup scripts fail can't rename user admin anymore? WHY?
[admin@internal] > user set admin name=adminn
failure: user name can't be changed
Changing name of logged in user is not good idea. What if you are logged as different user?
[sergey@router.home] > /user set admin name adminn
failure: user name can't be changed
I always use nv2 with mikrotik. There are some noise in my city.Just a question without intention of doubting what you say: why use NV2 on PtP?*) wireless - improved Nv2 reliability on ARM devices;
The first point-to-point tests with nv2 on arm are not satisfactory. We will perform more tests
I agree.Drop of RADIUS PAP support for ssh logins is a big problem for us too.
We're using a one-time password implementation which is impossible to integrate with MS-CHAPv2 - the security appliance only stores the hash of the PIN (fixed part of the password) and because of this cannot support MS-CHAPv2 since it would require to store PIN as clear-text. 6.43rc is forcing us to drop the OTP, actually decreasing security of the network.
Please allow us to make decisions on how to secure our network ourselves and make a setting allowing to select PAP for "login" service authentication. In any case RADIUS requests can always be sent via encrypted tunnels, while MS-CHAPv2 security strength has been watered down to level of a long obsolete single DES56 - one can find online services that will crack it in a day.
This is definitely the wrong thread for your request. There are separate threads and parts of the forum for those kind of questions. This thread is solely for issues with this particular release version and it's update.Hi, need some help to configure a paypal payment option with hotspot and usermanager. Just found this and update it to the RC version, but still need help on this.
Thank you, I will test it soon and report.Version 6.43rc51 has been released.
*) ike1 - zero out reserved bytes in NAT-OA payload;
Please clarify:*) filesystem - fixed NAND memory going into read-only mode (requires "factory-firmware" >= 3.41.1 and "current-firmware" >= 6.43);
routerboard: yes
model: RouterBOARD 3011UiAS
serial-number: 689A05572F46
firmware-type: ipq8060
factory-firmware: 3.27
current-firmware: 3.41
upgrade-firmware: 3.41
Is it stable enough for LtAP device at least?*) usb - fixed modem initialisation on LtAP mini;
Unfortunately it is the same - report sent to support.Thank you, I will test it soon and report.Version 6.43rc51 has been released.
*) ike1 - zero out reserved bytes in NAT-OA payload;
I think factory routerboard firmware = backup bootloader.Will the fix be included only in later production runs?
I was under the assumption that the factory-firmware identifies the firmware ver# the device initially shipped with,
and it can't be somehow upgraded.
Or we are talking about bakup routerboot code... (in which case I still think it is not user-upgradeable?).
Nothing relevant on the wiki.
I usually assumed the factory/backup version to be completely irrelevant unless you force it by a RESET button sequence (or possibly some other means).The backup RouterBOOT version can not be older than v3.24 version. A special package is provided to upgrade the backup RouterBOOT (DANGEROUS). Newer devices will have this new backup loader already installed at the factory. Download the package for:
All valid considerations.I think factory routerboard firmware = backup bootloader.Will the fix be included only in later production runs?
I was under the assumption that the factory-firmware identifies the firmware ver# the device initially shipped with,
and it can't be somehow upgraded.
Or we are talking about bakup routerboot code... (in which case I still think it is not user-upgradeable?).
Nothing relevant on the wiki.
It's normally not allowed but seems possible to upgrade the factory version: https://wiki.mikrotik.com/wiki/Manual:R ... D_settingsI usually assumed the factory/backup version to be completely irrelevant unless you force it by a RESET button sequence (or possibly some other means).The backup RouterBOOT version can not be older than v3.24 version. A special package is provided to upgrade the backup RouterBOOT (DANGEROUS). Newer devices will have this new backup loader already installed at the factory. Download the package for:
I still think this is the case here. The new feature will probably be available when using the normal boot loader (of a high enough version) but be absent when using the backup bootloader (either manually forced or may be automatically triggered if the "main" one is too corrupted to do anything).
I never tried but thought the secondary (factory) version can be upgraded too, either via Netinstall or even just by using the "force backup booter" and initiating an upgrade from ROS. But I never felt the need, so never tried... I just tried to latter (force backup and upgrade from ROS) but it's not that easy. I wonder if Netinstall could do it.
Edit:
Oh! And I think even though we now have a matching ROS and bootloader version (even for every incremental, let alone RC version), that firmware still has some internal version number (probably still somewhere around 3.4x for ROS 6.4x). So this change only complicates this question (it's probably possible to have basically the same factory backup and "main" booloader on a device even though the visible version number is seemingly much higher on the normally-upgradeable "main" firmware).
I think they just rebuild the source code of the bootloader for every ROS release, so it has a matching version number but this no longer indicates they made any change to the source. But this seems to be impractical because now we don't know when the code actually changes.
In my opinion the best solution would be to always auto-upgrade the main bootloader along every ROS upgrade (without the need to issue manual reboot twice) and allow the user to manually upgrade the backup bootloader once the new ROS successfully booted with an upgraded main bootloader (which is a fair enough confirmation that the device is stable enough with the new bootloader to use ROS for bootloader changes, thus it's probably possible to downgrade if some small error occurs later on).in witch case they should provide a "special" package for the users who would want to upgrade the backup loader.
"sfp-connector-type" is still falsely displayed as "LC" for S-RJ01 modules in Winbox and CLI*) sfp - hide "sfp-wavelength" parameter for RJ45 transceivers;
Would also like this explained*) bridge - added per-port based "tag-stacking" feature
Can this also be explained. Similar to selective q-in-q?
Wiki has been updated with an example:*) bridge - added per-port based "tag-stacking" feature
Can this also be explained. Similar to selective q-in-q?
*) bridge - added support for DHCP Option 82 (disables hardware offloading, CLI only);
*) bridge - added support for DHCP Snooping (disables hardware offloading, CLI only);
All my everyday devices still connects just fine.*) wireless - added option to disable PMKID for WPA2 (CLI only);
Did you specify which ports are trusted ports under /interface bridge port?Could we please get some examples of how to use these features on the Wiki ?Code: Select all*) bridge - added support for DHCP Option 82 (disables hardware offloading, CLI only); *) bridge - added support for DHCP Snooping (disables hardware offloading, CLI only);
I cannot see any of the options I would expect, e.g. being able to set the contents of the Option-82 injection string with variables for the first feature, or being able to specify the valid DHCP server for the second.
I second that!Could we please get some examples of how to use these features on the Wiki ?Code: Select all*) bridge - added support for DHCP Option 82 (disables hardware offloading, CLI only); *) bridge - added support for DHCP Snooping (disables hardware offloading, CLI only);
I cannot see any of the options I would expect, e.g. being able to set the contents of the Option-82 injection string with variables for the first feature, or being able to specify the valid DHCP server for the second.
I tested it again with Draytek router behind NAT and now it works OK!*) ike1 - zero out reserved bytes in NAT-OA payload;
How does this one work? Any specific commands that it works with?*) console - added "dont-require-permissions" parameter for scripts;
Where I can change this settings via CLI?*) bridge - added support for BPDU Guard (CLI only);
Funny thing after Version 6.43rc56 , my DHCPv6 client is showing in red in winbox, even though everything is working, and my ipv6 connectivity is ok. Still after after re-creating it from scratch... Not a big deal, but...
[admin@migo] /ipv6 route> check
status: ok
interface: pppoe-out1
nexthop: ::
[admin@migo] /ipv6 route> print
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, o - ospf, b - bgp, U - unreachable
# DST-ADDRESS GATEWAY DISTANCE
0 ADS ::/0 pppoe-out1 1
1 DS ::/0 fe80::90:1a00:2a3:47c... 1
2 ADSU 2001:4dd2:8986::/48 1
3 ADC 2001:4dd2:8986::/64 bridge-local 0
[admin@migo] /ipv6 dhcp-client> print
Flags: D - dynamic, X - disabled, I - invalid
# INTERFACE STATUS REQUEST PREFIX ADDRESS
0 I pppoe-out1 bound prefix 2001:4dd2:8986::/48, 22h28m17s
I have to report, that distance measurement does not work correctly. On AP side it reports 706.54m while on client side just 374.28m (374.28 is the correct distance)Version 6.43rc56 has been released.
*) w60g - stop doing distance measurements after first successful measurement;