Page 1 of 1

v6.39.1 [current]

Posted: Wed May 03, 2017 1:46 pm
by strods
To upgrade, click "Check for updates" at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

What's new in 6.39.1 (2017-Apr-27 10:06):

*) defconf - discard default configuration startup query with RouterOS upgrade;
*) defconf - discard default configuration startup query with configuration change from Webfig;
*) smb - fixed external drive folder sharing when "/flash" folder existed;
*) smb - fixed invalid default share after reboot when "/flash" folder existed;
*) upnp - fixed firewall nat rule update when external IP address changes;
*) dns - made loading thousands of static entries faster;

Re: v6.39.1 [current]

Posted: Wed May 03, 2017 3:52 pm
by cgabriel
Reading about the 6.39 problems, I have just made a backup before upgrading (via Winbox / Files), directly in root.
However, the backup file disappeared after upgrade; is it normal??
Fortunately the configuration was kept...

Regards,
Gabriel

Re: v6.39.1 [current]

Posted: Wed May 03, 2017 3:53 pm
by Ansy
What's new in 6.39.1 (2017-Apr-27 10:06):
*) dns - made loading thousands of static entries faster;
Wonder how many that "thousands of static entries" can I load (faster or not) into DNS server?
dnsmasq manage about 50K eating 30MB RAM on x86... works well... wont the same in MT.

Re: v6.39.1 [current]

Posted: Wed May 03, 2017 3:58 pm
by pe1chl
Reading about the 6.39 problems, I have just made a backup before upgrading (via Winbox / Files), directly in root.
However, the backup file disappeared after upgrade; is it normal??
It depends on what device you have. But certainly the only useful backup is the backup that you have downloaded to another system.
Keeping your backup on the router is not useful as it will be gone when you need to factory-reset it, the time you need the backup.

Re: v6.39.1 [current]

Posted: Wed May 03, 2017 5:09 pm
by Kindis
I'm having very strange fasttrack issues with this release (did not test 6.39).
Had no issues on 6.38.5.

The issue is that suft from Windows to internet and so on work as expected BUT an RDP connection to a Windows server does not and a connection from an other Mikrotik device going to internet does not work either. As soon as I disable the Fatstrack rule in firewall everything started working as expected.
Anybody else have issues using fasttrack?

Re: v6.39.1 [current]

Posted: Wed May 03, 2017 5:22 pm
by cgabriel
It depends on what device you have. But certainly the only useful backup is the backup that you have downloaded to another system.
Keeping your backup on the router is not useful as it will be gone when you need to factory-reset it, the time you need the backup.
I saved the backup when reading about update issues (config lost). If the config would have been lost, I could simply load the backup (when no reset is necessary, I understand).
But I had no problem, the config was properly kept; I just saw that the backup wasn't there anymore (I had no other file)...
I am still interested, is it normal?
The device is RouterBOARD 962UiGS-5HacT2HnT
Thanks,
Gabriel

Re: v6.39.1 [current]

Posted: Wed May 03, 2017 5:31 pm
by tandrot8
Hi !
I downloaded and installed the 6.39.1 of ROS on a RB951G-2Hnd. After rebooting, the router stopped to work properly. I wasn't able to gain access to the router via Winbox or Webfig using IP or MAC addresses.
I tried to do factory reset, but for some reason I wasn't able to connect via Winbox(IP and MAC). In the end I performed a netinstall. It was the only way to regain access to the router.

Re: v6.39.1 [current]

Posted: Wed May 03, 2017 5:54 pm
by pe1chl
It depends on what device you have. But certainly the only useful backup is the backup that you have downloaded to another system.
Keeping your backup on the router is not useful as it will be gone when you need to factory-reset it, the time you need the backup.
I saved the backup when reading about update issues (config lost). If the config would have been lost, I could simply load the backup (when no reset is necessary, I understand).
But I had no problem, the config was properly kept; I just saw that the backup wasn't there anymore (I had no other file)...
I am still interested, is it normal?
The device is RouterBOARD 962UiGS-5HacT2HnT
Thanks,
Gabriel
On that device and all other "new" devices with 16MB flash it is normal, yes. The root directory that you see is a RAMdisk,
it is lost on reboot. There is a flash subdirectory on those devices that is the flash memory.
On older devices that have 128MB flash (I think there are also some with 64MB) the root directory is the flash and the
files are kept on reboot and update.
But still, when you would have been affected by this error there would have been a big risk of losing your backup as you
probably would have had to netinstall.
Always download the backup after making it!
It is also better to erase it afterwards.

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 2:28 am
by dadoremix
Well done
Sxt lite 2
For p2p link... killed with 6.39.1
Upgrade from 6.39
I hear beep, but no mac, ip or calling netinstall for help
So, again travel to roof



Sent from my iPhone using Tapatalk Pro

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 7:17 am
by Andre81
+1 lost configuration and access to router at all.

The only way is to use a direct short and shielded cable between pc and roterboard (RB951G-2NnD).
I've test Netinstall about 50 times, and then after I decided to use shielded and short cable the router appears in Neinstall.

All configuration is gone, no backup at all...

Damn!!

A.

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 9:29 am
by obscurus
The same issue after upgrade RB951G-2Hnd - lost configuration and access to router at all.
I can repair it only with netinstall on win7 32bit (netintstall does not see router on windows 10 64bit).

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 9:59 am
by pe1chl
Upgrade from 6.39
So, again travel to roof
Why did you upgrade a roofmounted p2p link from 6.39 to 6.39.1 ???
There appears to be no change in the changelogs that would affect you...

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 10:06 am
by sawireless
Hi Guys

also downloaded and installed the 6.39.1
upgrades from 6.38.5
The problems that we have found.

1: lost all our port forwarding.
2: Radius clients on PPPoE take a hell of a long time to reconnect.

will give a update if we find something else.

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 10:29 am
by pe1chl
also downloaded and installed the 6.39.1
Useless information without indicating what was your previous version and how your router is configured...

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 10:41 am
by 4RESTER
RB951G-2Hnd, upgraded from 6.39 to 6.39.1
After updating the router does not work normally.
When it turn on, one BEEP is heard. Double BEEP is absent.
The router is not detected by the MAC in Winbox Neighbors.
Resetting the router does not help, neither through the button nor through the closure of the RESET-pads (reseting sound audibly) on the board.

HOW TO RECOVERY RB951G-2Hnd ?!

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 10:49 am
by jarda
Use the backup partition before any update. When update fails, use netinstall.

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 11:10 am
by Shadeofspirit
solved
(6.39 to 6.39.1 on CHR
dude stoped to see any devices
"connection to agent CHRDUDE not ready (not connected, next attempt at 08:09:18), next attempt at 08:10:20")

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 11:29 am
by Mikegyver42
i lost my RB951G-2Hnd after upgrading from 6.39 to 6.39.1 !!!
After updating the router does not work.
I tried a reset without success :-(
I tried a netinstall but the router is nether seen in the netinstall interface :-(

How to repair my RB951G-2Hnd ?

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 11:35 am
by 4RESTER
Use the backup partition before any update. When update fails, use netinstall.
[SOLVED]
With the Netinstall the RB951G-2Hnd (6.39.1) is recovered (downgraded to 6.39) successfully! 10x a lot!

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 1:23 pm
by colinardo
For information:
RB951G-2Hnd was OK after upgrading to 6.39. But when you try installing the "multicast" 6.39-mipsbe package after installing 6.39, you get stuck in a boot loop with constant beeps. Netinstall was needed to recover.

Better wait upgrading this device.

Best regards

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 1:26 pm
by Andre81
i lost my RB951G-2Hnd after upgrading from 6.39 to 6.39.1 !!!
After updating the router does not work.
I tried a reset without success :-(
I tried a netinstall but the router is nether seen in the netinstall interface :-(

How to repair my RB951G-2Hnd ?

Have you tried a shielded cable max lenght of 2mt (direct connection) for net install?

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 1:46 pm
by ndbjorne
Upgraded a bunch of RB750, 1*mAP, 1*RB100AH2x, 1*RB2011, 1*x86 from 6.38.5 and I lost only a few comments.

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 1:48 pm
by tandrot9
Hi to all!
For those who have RB951G-2HnD and can't access the router using either IP or MAC addresses, use netinstall.

Warning!
Before performing a netinstall or an upgrade download your backup config files on your PC(Winbox or Webfig)!!!!
A netinstall will format the internal storage!!! You won't be able to recover your backup config files!!!
Do not forget to select Keep Old configuration. After successful recovery, login with your username and password that you had before.

Follow the instruction described here: https://wiki.mikrotik.com/wiki/Manual:Netinstall. I followed the steps described here and I was able to gain access to the router.

Good luck!

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 1:54 pm
by expert
Some people here are complaining about serious issues with 3011 after upgrade.
However I haven't seen any reaction of MK confirming or rejecting that. So I'm asking whether is it safe to upgrade 3011 and wish to hear clear answer.

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 2:04 pm
by JohnTRIVOLTA
"RB951G-2Hnd, upgraded from 6.39 to 6.39.1
After updating the router does not work normally.
When it turn on, one BEEP is heard. Double BEEP is absent.
The router is not detected by the MAC in Winbox Neighbors.
Resetting the router does not help, neither through the button nor through the closure of the RESET-pads (reseting sound audibly) on the board."

The same issue with my RB433AH ! I was lucky I had a backup on the sd card,because I lost everything on the flash after reinstaling ROS with Netinstall !

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 2:50 pm
by Mikegyver42
i lost my RB951G-2Hnd after upgrading from 6.39 to 6.39.1 !!!
After updating the router does not work.
I tried a reset without success :-(
I tried a netinstall but the router is nether seen in the netinstall interface :-(

How to repair my RB951G-2Hnd ?
Have you tried a shielded cable max lenght of 2mt (direct connection) for net install?
I used the MikroTik wiki to use netinstall and it don't work (they says to put 10.0.1.10/24 IP to the ethernet interface on the PC and to put 192.168.1.2 to the network booting server configuration in netinstall)
I found an internet site who says to use 192.168.1.2/24 to the PC and the 192.168.1.3 to netinstall booting server and it works !
I reload an old routerboard and the router works, i update it with 6.39.1 and it always works.

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 3:14 pm
by JohnTRIVOLTA
Try this :
First put the power, after 2-3 seconds press the reset button and after 5 seconds release it and see if you will initialize the flash!
I use 10.0.0.1/24 for PC lan adapter and 10.0.0.2 for PXE .

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 3:18 pm
by Mikegyver42
Try this :
First put the power, after 2-3 seconds press the reset button and after 5 seconds release it and see if you will initialize the flash!
I use 10.0.0.1/24 for PC lan adapter and 10.0.0.2 for PXE .
I said in my post that my router was running now.

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 3:20 pm
by tandrot9
@mikegyver42: You have to put on your computer an IP address from the same network.(eg: on PC: 10.10.10.10/24, on netinstall server: 10.10.10.20/24.
It doesn't work if you put on PC 192.168.10.10 and on netinstall server 10.10.10.20 because you don't have a route from 192.x.x.x to 10.x.x.x.)
Then you should be able to access through netinstall interface the router to install the ROS.

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 3:22 pm
by JohnTRIVOLTA
Try this :
First put the power, after 2-3 seconds press the reset button and after 5 seconds release it and see if you will initialize the flash!
I use 10.0.0.1/24 for PC lan adapter and 10.0.0.2 for PXE .
I said in my post that my router was running now.
Glad it works

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 3:29 pm
by Mikegyver42
@mikegyver42: You have to put on your computer an IP address from the same network.(eg: on PC: 10.10.10.10/24, on netinstall server: 10.10.10.20/24.
It doesn't work if you put on PC 192.168.10.10 and on netinstall server 10.10.10.20 because you don't have a route from 192.x.x.x to 10.x.x.x.)
Then you should be able to access through netinstall interface the router to install the ROS.
exact, i don't read the MikroTik wiki correctly :-(
now all is working fine.

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 3:41 pm
by tandrot9
@mikegyver42: Glad that everything is working fine for you, now.

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 4:51 pm
by Kindis
Some people here are complaining about serious issues with 3011 after upgrade.
However I haven't seen any reaction of MK confirming or rejecting that. So I'm asking whether is it safe to upgrade 3011 and wish to hear clear answer.
I have upgraded my 3011 without issues. The only problem I have now is fasttrack issues but those are related to connections using fasttrack then passing a CHR (on Hyper-V 2012 R2).
Except for that I have upgraded CHR, RB750Gr3, RB493G, 3011 and a wAP ac without issues (if you overlook the fasttrack issue).

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 6:49 pm
by Ansy
I finally managed to recover hEX off the bootloop (some tryes & tricks used), but...

MT, why, Why, WHY do you make undocumented changes breaking our scripts???
/ip proxy access remove numbers=[find action=deny]
Works in 6.38.5, doesn't work in 6.39.1
/ip proxy access remove numbers=[find action="deny"]
Works in 6.39.1, doesn't work in 6.38.5

As result, I've a mess of updated devices and not updated ones... and I have to make another scripts to change my old scripts before upload them to routers according to their actual ROS versions.
Yes, I know sed and other great utilities... but some of my devices crashed due to memory overload just because of not purged old proxy records before loading new ones.

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 8:04 pm
by mavink
I had a very annoying issue when upgrading an RB3011 today. This was probably because I've tried repartitioning it in previous RouterOS versions (unsuccesfully of course, since this is only officially supported since 6.39.1).

I upgraded from RouterOS 6.38.5 to 6.39.1. This caused it to get stuck in a boot loop, with the console giving an error about not being able to find the kernel. The RouterBoot debug menu showed two partitions; I fixed the problem by repartitioning it to 1 partition from within RouterBoot. After that the RB3011 booted succesfully, with RouterOS 6.39.1 and the correct configuration.

Re: v6.39.1 [current]

Posted: Thu May 04, 2017 10:58 pm
by ErfanDL
I upgrade from 6.38.5 to 6.39.1 on RB2011 the router bricked and I lost my configuration :| :|

Please test updates on all products before publishing

Re: v6.39.1 [current]

Posted: Fri May 05, 2017 1:27 am
by chuspy
I installed it on 951Ui-2HnD and I am going to make it CapsMAn v2 over the weekend. Is new wireless combinig wireless and wireless-cm2 package or I am missing cm2 and if so how to add it?

Re: v6.39.1 [current]

Posted: Fri May 05, 2017 1:37 am
by Kevo
There is a single wireless package now.

Re: v6.39.1 [current]

Posted: Fri May 05, 2017 2:45 am
by MayestroPW
There is still a problem within hotspot directory.
If I set it to:
/disk1/hotspot/hotspot1
It will be automatically changed to:
/flash/disk1/hotspot/hotspot1

Re: v6.39.1 [current]

Posted: Fri May 05, 2017 3:51 am
by eduardomazolini
Mu backup was missing to!

Enviado de meu SM-G800H usando Tapatalk

Re: v6.39.1 [current]

Posted: Fri May 05, 2017 8:58 am
by makstex
My router broken to....

RouterBOOT booter 2.30

RouterBoard 1000

CPU frequency: 1333 MHz
Memory size: 512 MB

Press any key within 2 seconds to enter setup..
loading kernel from nand... OK
setting up elf image... OK
jumping to kernel code
Starting...
chmod: /flash/nova/run: No such file or directory
chmod: /flash/etc/ssh_host_key: No such file or directory
chmod: /flash/etc/ssh_host_key.pub: No such file or directory
chmod: /flash/etc/ssh_host_rsa_key.pub: No such file or directory
chmod: /flash/rw/run/netns: No such file or directory
chmod: /flash/lost+found/: Too many open files
chmod: /flash/lost+found/: Too many open files
chmod: /flash/lost+found/: Too many open files
chmod: /flash/lost+found/: Too many open files
chmod: /flash/lost+found/: Too many open files
chmod: /flash/lost+found/: Too ma.....................................................


trying to restore via netinstall

Re: v6.39.1 [current]

Posted: Fri May 05, 2017 9:37 am
by makstex
Netinstall not finding router
http://joxi.ru/1A5L5oytgEQ62E
I tried the version of netinstall 6.39.1 .... 6.38.5 ..... 6.30 - Microtik sees - netinstall it is not.

Yes !!! I won it!
It was in the network address.
Put local 10.0.0.1, in netinstall 10.0.0.2 and he found it.

Re: v6.39.1 [current]

Posted: Fri May 05, 2017 10:16 am
by heydude
Big Thank to MikroTik developpers!
capsman and 25 caps updated in no time and without any problems (different devicec)!

Specially for the new capsman features.
-extension channel auto matching-mode
-possibility to specify channel list
-save last channel option
-background scan / rescan interval

After some testing arount, the new features seem to work great

@Mikrotik -> Please update the capsman wiki. some new options need explanation.

Re: v6.39.1 [current]

Posted: Fri May 05, 2017 10:35 am
by dash
Some people here are complaining about serious issues with 3011 after upgrade.
However I haven't seen any reaction of MK confirming or rejecting that. So I'm asking whether is it safe to upgrade 3011 and wish to hear clear answer.
From my point of view, the only working upgrade for a RB3011 is to use netinstall. I had the exactly same issue (bootloop) on 3 different 3011 devices after updating them. I would NOT recommend you to update. unless its ok for you to use netinstall :)

Re: v6.39.1 [current]

Posted: Fri May 05, 2017 12:57 pm
by nz_monkey
After some testing arount, the new features seem to work great

@Mikrotik -> Please update the capsman wiki. some new options need explanation.
+1 on the Thanks, and on the Wiki update suggestion.

Now we just need Band Steering :)

Re: v6.39.1 [current]

Posted: Fri May 05, 2017 1:00 pm
by RN3QTB
Hi friends! Today updated the firmware on the base station RouterBoard433 Wireless (Atheros AR5413) to v6.39.1 (stable) After the updates have dramatically decreased the signal strength. No settings changed, just updated and rebooted. Help, please!
Image

Re: v6.39.1 [current]

Posted: Fri May 05, 2017 1:47 pm
by cgabriel
Channel list seems to work properly, but I would like to see the current channel/frequency in the CAP interface list, similar to SSID, Band, etc.
The columns are there but empty.

Re: v6.39.1 [current]

Posted: Fri May 05, 2017 1:55 pm
by RN3QTB
Channel list seems to work properly, but I would like to see the current channel/frequency in the CAP interface list, similar to SSID, Band, etc.
The columns are there but empty.
they are present, I just erased them.

Re: v6.39.1 [current]

Posted: Fri May 05, 2017 2:11 pm
by heydude
To view current channel of the interface in <cap interface list, you have to enable the hidden column "current channel". The fields in column "channel" only have entries, if channel is set manually.

Re: v6.39.1 [current]

Posted: Fri May 05, 2017 2:14 pm
by moep
still having DFS problems with hAP ac on 6.39.1
on 6.38.5 everything was fine.
every day there is radar detected and the AP switches channels until it gets to a non DFS channel (5180).
it makes no difference if I change antenna gain or the "start channel" to another one (usally 5500 ist default, tested with 5580, 5640).
the problem only seems to occur, if the device is triple chain 5GHz.
this problem seems to also be present on netmetal 5.
one connected device is sufficient to trigger the DFS problem.

Re: v6.39.1 [current]

Posted: Fri May 05, 2017 2:43 pm
by gavinsaxby
Has anyone seen trouble with DHCP after upgrading to 6.39 or 6.39.1? I upgraded a 951Ui-2HnD router to 6.39 at a customer on Tuesday morning because I was onsite to add new equipment and thought I'd try the upgrade (yeah, silly idea I know) and now our Debian Linux server isn't accepting DHCP offers from it (the Linux box hasn't been touched and no software has been upgraded on it). The Linux box syslog reports that no DHCP offers were received, the router log says the offer wasn't accepted. Windows 7 doesn't seem to have a problem and gets a lease without problem. I've tried 6.39.1 and that doesn't seem to have fixed it.

Re: v6.39.1 [current]

Posted: Fri May 05, 2017 3:00 pm
by Marino
I'm having very strange fasttrack issues with this release (did not test 6.39).
Had no issues on 6.38.5.

The issue is that suft from Windows to internet and so on work as expected BUT an RDP connection to a Windows server does not and a connection from an other Mikrotik device going to internet does not work either. As soon as I disable the Fatstrack rule in firewall everything started working as expected.
Anybody else have issues using fasttrack?
Yes, I have on a rb750g3 with two wireless caps and local break out instead of capsman forward. The rb750 uses eth2 as LAN-interface and fasttrack firewall rules are on top. Websites load slow and local media streamers are not visible sometimes (chromecast). Disable fasttrack solves the problem.

With capsman forward and break out on a bridge on the rb750 seems to work ok. Might be a config issue.

Re: v6.39.1 [current]

Posted: Fri May 05, 2017 11:34 pm
by idorotic
Hi, I have problem with 6.39 and 6.39.1 on rb951g & rb750gl, it is not possible to edit ports in firewall, they are greyed. Ports can be edited only after switching protocol. On 6.38.5 everything worked normally.
Image
Image

Re: v6.39.1 [current]

Posted: Sat May 06, 2017 12:00 am
by zoltix
Hi all,
My RB2011 has been bricked and I lost my configuration after upgrading from 6.39 to 6.39.1. and more netinstall could not see the router.
I had to use my serial cable,change the boot option to boot on ethernet and finally upgrade via netinstall.
All these steps succeed to get back my rb2011

More details when I connect with my terminal:

Press any key within 2 seconds to enter setup..
loading kernel from nand... OK
setting up elf image... OK
jumping to kernel code
Starting...
chmod: /flash/nova/run: No such file or directory
chmod: /flash/etc/ssh_host_key: No such file or directory
chmod: /flash/etc/ssh_host_key.pub: No such file or directory
chmod: /flash/etc/ssh_host_rsa_key.pub: No such file or directory
chmod: /flash/rw/run/netns: No such file or directory
chmod: /flash/lost+found/: Too many open files
chmod: /flash/lost+found/: Too many open files
chmod: /flash/lost+found/: Too many open files
chmod: /flash/lost+found/: Too many open files
chmod: /flash/lost+found/: Too many open files
chmod: /flash/lost+found/: Too ma.....................................................


and repeating infinitely the same line "chmod: /flash/lost+found/: Too many open files"

Re: v6.39.1 [current]

Posted: Sat May 06, 2017 1:58 pm
by Kindis
I'm having very strange fasttrack issues with this release (did not test 6.39).
Had no issues on 6.38.5.

The issue is that suft from Windows to internet and so on work as expected BUT an RDP connection to a Windows server does not and a connection from an other Mikrotik device going to internet does not work either. As soon as I disable the Fatstrack rule in firewall everything started working as expected.
Anybody else have issues using fasttrack?
Yes, I have on a rb750g3 with two wireless caps and local break out instead of capsman forward. The rb750 uses eth2 as LAN-interface and fasttrack firewall rules are on top. Websites load slow and local media streamers are not visible sometimes (chromecast). Disable fasttrack solves the problem.

With capsman forward and break out on a bridge on the rb750 seems to work ok. Might be a config issue.
My 750 Gr3 is my WAN router and the 3011 hold my user network but this issue appears to if the traffic passes my CHR router (DMZ). Don't know why this is and it's not all traffic but I think it's related to some typ of encryption as RDP does not work.

Re: v6.39.1 [current]

Posted: Sat May 06, 2017 3:17 pm
by Senux
Hi !
I downloaded and installed the 6.39.1 of ROS on a RB951G-2Hnd. After rebooting, the router stopped to work properly. I wasn't able to gain access to the router via Winbox or Webfig using IP or MAC addresses.
I tried to do factory reset, but for some reason I wasn't able to connect via Winbox(IP and MAC). In the end I performed a netinstall. It was the only way to regain access to the router.
The same problem with this model.
AND IT IS 4 DAYS after this epic FAIL and NO ANY SOLUTION OR ADVISE FROM MIKROTIK!!! THEY DO NOT CANCELED THIS DANGEROUS BUGGY UPDATE!!!

You have Mikrotik? - it is yours problem. I think they are coding with mistakes to break routers to cause You buy a new router. It is not first or second and I am sure not the last epic fail from Mikrotik coders

Re: v6.39.1 [current]

Posted: Sat May 06, 2017 3:34 pm
by jarda
I have heard about no one who bought a new router because the previous was bricked by update. They are rather sent to rma instead which is for sure profitable for mikrotik...

Re: v6.39.1 [current]

Posted: Sat May 06, 2017 3:40 pm
by Senux
I have heard about no one who bought a new router because the previous was bricked by update. They are rather sent to rma instead which is for sure profitable for mikrotik...
And if You must work instead of waiting 2-3 weaks for paid rma - routers are out of warranty? You and other company workers goes to vacation for this reason?

Re: v6.39.1 [current]

Posted: Sat May 06, 2017 4:02 pm
by jarda
I do not blindly hurry with updates. I read the forum. When I know why to do the update, I firstly test in the lab. And yes, I needed to use a serial cable and netinstall few times in the history in the lab. But never in the field so far.
I also use backup partitions to be able easily revert the routers back when necessary so I am very unhappy of those new routers with 16MB of flash that are not able to carry two partitions.

Re: v6.39.1 [current]

Posted: Sat May 06, 2017 10:57 pm
by Marino
I'm having very strange fasttrack issues with this release (did not test 6.39).
Had no issues on 6.38.5.

The issue is that suft from Windows to internet and so on work as expected BUT an RDP connection to a Windows server does not and a connection from an other Mikrotik device going to internet does not work either. As soon as I disable the Fatstrack rule in firewall everything started working as expected.
Anybody else have issues using fasttrack?
Yes, I have on a rb750g3 with two wireless caps and local break out instead of capsman forward. The rb750 uses eth2 as LAN-interface and fasttrack firewall rules are on top. Websites load slow and local media streamers are not visible sometimes (chromecast). Disable fasttrack solves the problem.

With capsman forward and break out on a bridge on the rb750 seems to work ok. Might be a config issue.
My 750 Gr3 is my WAN router and the 3011 hold my user network but this issue appears to if the traffic passes my CHR router (DMZ). Don't know why this is and it's not all traffic but I think it's related to some typ of encryption as RDP does not work.
It seems mainly https sites on my 750gr3, so you might have a good point.

Re: v6.39.1 [current]

Posted: Sun May 07, 2017 10:03 am
by Thomeless
I also having problem with DFS on AP in this version. One of my AP still detecting for radar and never switch back to normal mode. I don't have this issue on clients. AP si RB411.

Re: v6.39.1 [current]

Posted: Sun May 07, 2017 10:44 am
by MartijnVdS
I also having problem with DFS on AP in this version. One of my AP still detecting for radar and never switch back to normal mode. I don't have this issue on clients. AP si RB411.
Which country and frequency did you set it to? Some frequencies require a very long radar search (10 minutes)

Re: v6.39.1 [current]

Posted: Sun May 07, 2017 2:00 pm
by dapilori90
Updated a bunch of devices from v6.38.5 to v6.39.1:
  • hAP AC lite: MAC address of the bridge changed without any reason. Everything else was OK.
  • RB2011UiAS, CCR1009-8G-1S, RB911G-5HPnD: everything OK.

Re: v6.39.1 [current]

Posted: Sun May 07, 2017 2:04 pm
by jarda
Use administrative mac address on bridges to prevent its changing.

Re: v6.39.1 [current]

Posted: Sun May 07, 2017 3:01 pm
by erebusodora
After update RB 750 v.6.38 to 6.39.1 is died. Nothig help .......reset or hardware reset. Netinstall not help too. Blink only power light. :(

Re: v6.39.1 [current]

Posted: Sun May 07, 2017 5:42 pm
by dadoremix
Netinstall work always
Read wiki
Push and hold reset buton all time, then power up


Sent from my iPhone using Tapatalk Pro

Re: v6.39.1 [current]

Posted: Sun May 07, 2017 6:35 pm
by biatche
does capsman work better in any way compared to 6.37?

i am seeing a lot of rejected, forbidden by access list, and group key timeout, sending station leaving

anybody else?

Re: v6.39.1 [current]

Posted: Mon May 08, 2017 10:29 am
by momen44994
38.1 x86 pc

without real ip i can access remotely by winbox or other way

Re: v6.39.1 [current]

Posted: Mon May 08, 2017 10:48 am
by kangarie
upgrade RB751U-2HnD v.6.39 to 6.39.1 not boot, netinstall fixed

Re: v6.39.1 [current]

Posted: Mon May 08, 2017 2:49 pm
by lublupospat
Здравствуйте
Пишу о проблеме появившейся после очередного обновления до 6.39 с версии 6.38.X но устройстве RB751G-2HnD.
Упала скорость передачи до 5-6Mb/s на 802.11 B/G/N
Устройство включено коммутатором с VLAN
VLAN1 -- WLAN и ETH2
VLAN2 -- ETH3-ETH5
ETH1 Оба VLAN


Hi
Writes about the problem after the next appeared before 6.39 Update with version 6.38.X but RB751G-device 2HnD.
The transmission rate fell to 5-6M/s on 802.11B/G/N
The device is switched on with a VLAN
VLAN1 - WLAN and ETH2
VLAN2 - eth3-ETH5
ETH1 VLAN Both

Re: v6.39.1 [current]

Posted: Mon May 08, 2017 3:40 pm
by Siona
English please...

Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka

Re: v6.39.1 [current]

Posted: Mon May 08, 2017 5:19 pm
by strods
About RB3011 bootloop after upgrade. Problem is caused by Partitions. In past it was possible to access Partitions menu and make partitions, but it did not work. However if it was done in the past, then after upgrade (to this version where partitions do work) you will run into bootloop issues.

Solution - before an upgrade set partition count to 1:
"/partitions repartition partitions=1"

Those who already did experience this problem - connect serial cable to device, go into RouterBOOT menu and re-partition device to single partition from there.

Re: v6.39.1 [current]

Posted: Mon May 08, 2017 6:21 pm
by jarda
Very bad message. I am using multiple partitions where possible to prevent such problems during updates. And now it is opposed? Now I must say like others: you are breaking things and not testing enough before public release to current branch.

Re: v6.39.1 [current]

Posted: Mon May 08, 2017 6:53 pm
by brwainer
Very bad message. I am using multiple partitions where possible to prevent such problems during updates. And now it is opposed? Now I must say like others: you are breaking things and not testing enough before public release to current branch.
I think the issue here isn't that they are breaking things - its that they actually fixed partitions, but didn't test what happens if you upgrade a device that already had the broken partitions in place.

EDIT: And, partitions aren't being opposed - you just can't have any broken partitions in place before the upgrade to 6.39.1 on a 3011. After upgrading, then you can set up partitions and it will work properly as well, which it wasn't before.

Re: v6.39.1 [current]

Posted: Mon May 08, 2017 7:09 pm
by jarda
Question is if this reason is valid to 3011 only or if it affects the other devices mentioned here with the same symptoms.

Re: v6.39.1 [current]

Posted: Tue May 09, 2017 12:53 am
by moep
As I already posted in here viewtopic.php?f=7&t=121431 LTE USB Stick rebooting is broken in v6.39.x
In v6.38.5 rebooting with LTE USB Stick is possible and the ppp interface is reconnecting as expected.

Please fix it :)

Re: RE: Re: v6.39.1 [current]

Posted: Tue May 09, 2017 2:50 am
by eduardomazolini
After update RB 750 v.6.38 to 6.39.1 is di. Nothig help .......reset or hardware reset. Netinstall not help too. Blink only power light. :(
My mAP broken too

Enviado de meu SM-G800H usando Tapatalk

Re: v6.39.1 [current]

Posted: Tue May 09, 2017 10:20 am
by PeterO
Same problem here.
Last weekend tried to upgrade my CCR1009 from 6.38.5 to 6.39.1
It was a disaster. Luckily i could connect it anyway over my VPN and did a downgrade to 6.38.5 and reinstalled dude-server. Working fine now.
This morning tried to upgrade wAP from 6.38.5 to 6.39.1 and that's totally bricked now!
Wil try netinstall later today and see if that will solve it.

When is 6.39.1 removed from the site?

Re: v6.39.1 [current]

Posted: Tue May 09, 2017 11:22 am
by rextended
Please add this feature:

on user-manager:
display "last-seen" data (already present on terminal/database) on /userman graphics interface on "statistics" in username details

Re: v6.39.1 [current]

Posted: Tue May 09, 2017 11:43 am
by rextended
Same problem here.
Last weekend tried to upgrade my CCR1009 from 6.38.5 to 6.39.1
It was a disaster. Luckily i could connect it anyway over my VPN and did a downgrade to 6.38.5 and reinstalled dude-server. Working fine now.
This morning tried to upgrade wAP from 6.38.5 to 6.39.1 and that's totally bricked now!
Wil try netinstall later today and see if that will solve it.

When is 6.39.1 removed from the site?
I use 6.39.1 live on production (CCR1009-7G-1C, netmetal 5, hex poe, etc.), actually the only problem I have is when I use old winbox 2 for disable/enable something. But if I use 3.11 I have no problem.
On bridge I use new fast-forward=yes and I notice decreased latency, but not more bandwidth.

Re: v6.39.1 [current]

Posted: Tue May 09, 2017 12:07 pm
by erebusodora
Netinstall work always
Read wiki
Push and hold reset buton all time, then power up


Sent from my iPhone using Tapatalk Pro
Netinstall not workin i try 50 times. I read wiki manual but nothig hapen.

Re: v6.39.1 [current]

Posted: Tue May 09, 2017 12:09 pm
by pe1chl
Same problem here.
This is a useless remark in a topic where several issues are discussed.
Apparently your "same problem" is not the most active issue: configuration lost on update.
So what it is instead, can only be guessed.

Re: v6.39.1 [current]

Posted: Tue May 09, 2017 12:12 pm
by PeterO
I use 6.39.1 live on production (CCR1009-7G-1C, netmetal 5, hex poe, etc.), [...]
I'm using CCR1009-8G-1S-1S+ also with Winbox 3.11

Re: v6.39.1 [current]

Posted: Tue May 09, 2017 1:47 pm
by amt
On bridge I use new fast-forward=yes and I notice decreased latency, but not more bandwidth.
Hi,
what is change on you but ? what is the differences betwen before and later after fast-forwad=yes. is there too much differences with bandwith ?

Thanks.

Re: v6.39.1 [current]

Posted: Tue May 09, 2017 1:50 pm
by techmngr
Hi Everyone.

It's my first time posting in this forum and just a little over 3 months using Mikrotik routers, having worked in mostly Cisco network environments. Just would like to ask what the most stable RouterOS there is for a Mikrotik1036? If it helps, I'll be running BGP on the router.

I have so much questions about Mikrotik, would this be the best forum for Mikrotik? :-)

Thanks in advance.

Re: v6.39.1 [current]

Posted: Tue May 09, 2017 2:19 pm
by amt
Hi Everyone.

It's my first time posting in this forum and just a little over 3 months using Mikrotik routers, having worked in mostly Cisco network environments. Just would like to ask what the most stable RouterOS there is for a Mikrotik1036? If it helps, I'll be running BGP on the router.

I have so much questions about Mikrotik, would this be the best forum for Mikrotik? :-)

Thanks in advance.
Hi,

Im using version 6.38.5 on CCR1036-12G-4S and using bgp without any problem.

Re: v6.39.1 [current]

Posted: Tue May 09, 2017 5:49 pm
by alexcherry
Ok, I'm writing it again here, because on 6.39 I didn't get any answer on my comment:

In the 6.39 is broken Accounting STOP packet. 6.39.1 the same thing. Guys, you touched the accounting packets, please fix the stop packet framed IP address.

Description :
In case when Mikrotik stops the PPP session, it sends wrong Framed-IP address (10.0.0.0).
We work with the Framed-IP address as part of session identification and our Radius cannot close the session correctly. I'm pretty sure all Radius based software are affected by this.

Here is a correct START packet, where Framed-IP is the IP address of customer (192.168.102.5) :

START:
Service-Type = Framed-User
Framed-Protocol = PPP
Framed-IP-Address = 192.168.102.5
Acct-Authentic = RADIUS

And here is a STOP packet with broken Framed-IP address :

Service-Type = Framed-User
Framed-Protocol = PPP
Framed-IP-Address = 10.0.0.0
Acct-Authentic = RADIUS
Event-Timestamp = "May 2 2017 18:16:38 CEST"
NAS-IP-Address = 10.0.1.36

Re: v6.39.1 [current]

Posted: Tue May 09, 2017 8:12 pm
by jspool
Hello,

On 6.39.1 on routers that are using mangle to set the desired default route I have been having issues where traffic stops routing out the mangle route and it requires connections to be cleared to resume normal operation.

Router 1 default route is over EOIP tunnel that is connected to Router 2. Been working great in this setup until 6.39.1 In fact upgrading from bugfix to current I saw the same issue immediately after it booted the current. With the 6.39.1 I have to clear connections almost weekly. Aside from that it seems to be working fine for normal non mangled setups.

Re: v6.39.1 [current]

Posted: Tue May 09, 2017 8:32 pm
by pe1chl
Been working great in this setup until 6.39.1 In fact upgrading from bugfix to current I saw the same issue immediately after it booted the current.
This kind of problem is often caused by having "FastTrack" in the configuration in a situation where it is not possible to do it, and being rescued by
the fact that FastTrack was not yet supported for some specific interface type. When a new version extends FastTrack support to that interface
type, the configuration that always was incorrect suddenly starts failing.
This can be confirmed by disabling FastTrack to see if it fixes it, and if so: study the matter and maybe put some rules before the FastTrack rule.

Re: v6.39.1 [current]

Posted: Tue May 09, 2017 8:38 pm
by jspool
Been working great in this setup until 6.39.1 In fact upgrading from bugfix to current I saw the same issue immediately after it booted the current.
This kind of problem is often caused by having "FastTrack" in the configuration in a situation where it is not possible to do it, and being rescued by
the fact that FastTrack was not yet supported for some specific interface type. When a new version extends FastTrack support to that interface
type, the configuration that always was incorrect suddenly starts failing.
This can be confirmed by disabling FastTrack to see if it fixes it, and if so: study the matter and maybe put some rules before the FastTrack rule.
Thanks for the info. I currently do not use FastTrack as historically it doesn't play nice with queuing. Both routers do not have a FastTrack rule in /ip firewall filter.

Re: v6.39.1 [current]

Posted: Tue May 09, 2017 11:30 pm
by pe1chl
Maybe it could be FastPath as well...

Re: v6.39.1 [current]

Posted: Wed May 10, 2017 12:55 am
by sport80
Hi,

i've tried to upgrade a CCR1009-8G-1S of my customer from 6.37.5 to 6.39.1. The upgrade works without problem. But the reason of upgrade is that my customer need a IKEV2 IPSEC for your business necessity. The IPSEC stop to working when i've enabled the new IKEV2 configuration. The same configuration also stop to working with the 6.38.5. I must to downgrade to 6.37.5 bugfix, restored a backup configuration and used a classic IKEV1 configuration.

The IKEV2 requested are this:

Phase 1
Version: IKEV2
Chiper: AES256
Hash: SHA512
DH: modp2048
Authentication: Pre-Shared Key
Lifetime 1440

Phase 2
Chiper: AES256
Hash: SHA512
IPSEC Compression: none
PFS DH: modp2048
Lifetime 1440

With the CCR1009 all the IPSEC parameters disappears, in winbox interface and also using terminal interrogation. The reboot does not solve the problem. The System -> Profile are not accessible and the CPU usage increase

I've tried also the same configuration in a old RB750 with only this IPSEC configuration configured

The results are the same as the CCR1009 but now i've the possibility to see more details. The IPSEC never try to connect or to contact the IPSEC EndPoint. The System -> Profile show the IPSEC package that goes to 98% of cpu utilization.

Hope this could be usefull to the newest releases (when the bugfix 6.38.6?)

Sorry for my bad english

Thank you very much

Re: v6.39.1 [current]

Posted: Wed May 10, 2017 2:01 am
by pe1chl
The IKEV2 requested are this:

Authentication: Pre-Shared Key
Really??

Re: v6.39.1 [current]

Posted: Wed May 10, 2017 8:25 am
by strods
Please everyone who is experiencing issues with this version and can see that after disabling FastTrack/FastPath issues goes away - generate supout file on device while problem is actual and send this file to support@mikrotik.com

We have not received yet such file from anyone and are not being able to notice any issues in common configurations where FastTrack/FastPath is being used.

Re: v6.39.1 [current]

Posted: Wed May 10, 2017 9:18 am
by amt
Hi, I have problem with 6.39 and 6.39.1 on rb951g & rb750gl, it is not possible to edit ports in firewall, they are greyed. Ports can be edited only after switching protocol. On 6.38.5 everything worked normally.
Image
Image

upgrade your winbox... use V3.11

Re: v6.39.1 [current]

Posted: Wed May 10, 2017 10:53 am
by Kindis
Please everyone who is experiencing issues with this version and can see that after disabling FastTrack/FastPath issues goes away - generate supout file on device while problem is actual and send this file to support@mikrotik.com

We have not received yet such file from anyone and are not being able to notice any issues in common configurations where FastTrack/FastPath is being used.
I have sent in supout but has not gotten any feedback from you. I can reproduce the issue so I can create new files if you like or give you remote access.
[Ticket#2017050322000985]

Re: v6.39.1 [current]

Posted: Wed May 10, 2017 11:13 am
by RN3QTB
Hi friends! Today updated the firmware on the base station RouterBoard433 Wireless (Atheros AR5413) to v6.39.1 (stable) After the updates have dramatically decreased the signal strength. No settings changed, just updated and rebooted. Help, please!
Image
UP!!!!

Re: v6.39.1 [current]

Posted: Wed May 10, 2017 11:47 am
by pe1chl
Hi friends! Today updated the firmware on the base station RouterBoard433 Wireless (Atheros AR5413) to v6.39.1 (stable) After the updates have dramatically decreased the signal strength. No settings changed, just updated and rebooted. Help, please!
Image
UP!!!!
I heard the same thing from a local user!
It was fixed when the other side was rebooted as well...
Maybe a second reboot of the updated 433 might have fixed it as well.

Re: v6.39.1 [current]

Posted: Wed May 10, 2017 1:52 pm
by pukkita
Description :
In case when Mikrotik stops the PPP session, it sends wrong Framed-IP address (10.0.0.0).
We work with the Framed-IP address as part of session identification and our Radius cannot close the session correctly. I'm pretty sure all Radius based software are affected by this.

Here is a correct START packet, where Framed-IP is the IP address of customer (192.168.102.5) :

START:
Service-Type = Framed-User
Framed-Protocol = PPP
Framed-IP-Address = 192.168.102.5
Acct-Authentic = RADIUS

And here is a STOP packet with broken Framed-IP address :

Service-Type = Framed-User
Framed-Protocol = PPP
Framed-IP-Address = 10.0.0.0
Acct-Authentic = RADIUS
Event-Timestamp = "May 2 2017 18:16:38 CEST"
NAS-IP-Address = 10.0.1.36
Have several routers (CCRs) with 6.39 and 6.39.1, accounting enabled, working with freeradius 3, framedipaddress is sent correctly. Have you inspected a packet capture?

Re: v6.39.1 [current]

Posted: Wed May 10, 2017 2:41 pm
by RN3QTB
Hi friends! Today updated the firmware on the base station RouterBoard433 Wireless (Atheros AR5413) to v6.39.1 (stable) After the updates have dramatically decreased the signal strength. No settings changed, just updated and rebooted. Help, please!
Image
UP!!!!
I heard the same thing from a local user!
It was fixed when the other side was rebooted as well...
Maybe a second reboot of the updated 433 might have fixed it as well.
thank you very much, indeed, after flashing the second router and after restarting the signal is recovered. watching the work on

Re: v6.39.1 [current]

Posted: Wed May 10, 2017 2:48 pm
by Ansy
What's new in 6.39.1 (2017-Apr-27 10:06):
*) dns - made loading thousands of static entries faster;
Wonder how many that "thousands of static entries" can I load (faster or not) into DNS server?
dnsmasq manage about 50K eating 30MB RAM on x86... works well... wont the same in MT.
Tested on hEX (RB750Gr3) -- 4020 items only. No one more, any DNS cache settings, 150+MB RAM free.
Sad.

Re: v6.39.1 [current]

Posted: Wed May 10, 2017 2:49 pm
by strods
Ansy - This fix has nothing to do with RAM.
*) dns - made loading thousands of static entries faster;

Entries are loaded into memory after reboot much faster.

If you want to make cache bigger, then you have to change "cache-size" on DNS server configuration.

Re: v6.39.1 [current]

Posted: Wed May 10, 2017 6:53 pm
by owsugde
Not sure if this has been fixed yet in RC, but anyway, I need to report a (somewhat) critical bug with 6.39(.1):

My Netmetal 5 (921UAGS-5SHPacT, the three chainer without PCIe) isn't able to use two transmit antennas anymore (say, chain 1 and 2, and not 0). All three is ok, only one is ok. With two, however, the AP seems to be running when I check in Netmetal using Winbox, but the counterpart (an SXT SA5 ac) doesn't pick up anything. When I have it scan for the AP, nothing comes up. If I go back to one or three transmit chains without changing anything else at all, the SXT can log in just fine immediately. I use an NV2-only setting with all rx antennas active, which worked just fine until and including 6.38.5.

To me, it seems to be something wrong with a driver somewhere, in either the Netmetal or the SXT (probably Netmetal). Because, wireless signal tab as well as registration details on both ends give me weirdly "empty" figures for the by-chain rx strengths:

Image

Before, and even now on 6.93.1 with other devices (e.g., wAP ac), I get figures for each of the NxM receive antennas.

Re: v6.39.1 [current]

Posted: Thu May 11, 2017 9:23 am
by zm0m
951G-2HnD
Starting from v6.39, when connecting to a device from WinBox version 2 (Winbox v2.2.16),
a problem is detected in NAT Firewall rules: dstnat is inactive with Src.Port; Dst.Port; AnyPort,
accordingly, if you change these rules, the values in these fields are lost. This causes the device to malfunction.
In Winbox 3, everything works correctly.

Re: v6.39.1 [current]

Posted: Thu May 11, 2017 10:02 am
by andriys
Starting from v6.39, when connecting to a device from WinBox version 2 (Winbox v2.2.16),
a problem is detected...
Isn't it something to be expected?
Check this out:
What's new in 6.39 (2017-Apr-27 10:06):
...
!) winbox - minimal required version is v3.11;
...

Re: v6.39.1 [current]

Posted: Thu May 11, 2017 11:25 am
by zm0m
andriys

Thanks for the info. I use some versions of Winbox, it happened historically, and now it does not work very well with the new 6.39.

Re: v6.39.1 [current]

Posted: Thu May 11, 2017 12:07 pm
by pe1chl
Why do you use winbox when you don't want to or cannot upgrade it? use Webfig instead.

Re: v6.39.1 [current]

Posted: Thu May 11, 2017 1:27 pm
by zm0m
pe1chl

I have a some workstation with Win2k it has for develop and debug purposes. So on it i use winbox v2. IMHO, Webfig is not very comfortable for me.

Re: v6.39.1 [current]

Posted: Thu May 11, 2017 1:56 pm
by pe1chl
pe1chl

I have a some workstation with Win2k it has for develop and debug purposes. So on it i use winbox v2. IMHO, Webfig is not very comfortable for me.
Do you really think that MikroTik should spend development and debug effort, effort that cannot then be spent on other tasks, for supporting your ancient computer and special request?
Man, Windows 2000 has been out of support for ages. Even the TWO releases after that, XP and Vista, are out of support.

Re: v6.39.1 [current]

Posted: Thu May 11, 2017 3:05 pm
by zm0m
pe1chl

I know about this, and I have no claims to Mikrotik developers. I shared this information for others. I am a developer and I need this oldest OS for my tests.

Re: v6.39.1 [current]

Posted: Thu May 11, 2017 3:21 pm
by Ansy
What's new in 6.39.1 (2017-Apr-27 10:06):
*) dns - made loading thousands of static entries faster;
Wonder how many that "thousands of static entries" can I load (faster or not) into DNS server?
dnsmasq manage about 50K eating 30MB RAM on x86... works well... wont the same in MT.
Tested on hEX (RB750Gr3) -- 4020 items only. No one more, any DNS cache settings, 150+MB RAM free.
Sad.
Sorry, some records failed to add because of more than 63 chars length (I've specially tested this limit).
For now I've managed to add 20K static DNS records (regexps!) and gonna test it in work.
THANX, MT!

Re: v6.39.1 [current]

Posted: Thu May 11, 2017 3:53 pm
by pe1chl
Sorry, some records failed to add because of more than 63 chars length (I've specially tested this limit).
A DNS name cannot be longer than 255 chars in total and no more than 63 chars in each "label" (part between dots).
That is described in the standard, so when you expected to use longer labels the error is on your side.

Re: v6.39.1 [current]

Posted: Thu May 11, 2017 8:46 pm
by alexcherry
Have several routers (CCRs) with 6.39 and 6.39.1, accounting enabled, working with freeradius 3, framedipaddress is sent correctly. Have you inspected a packet capture?
Are you talking about Stop accounting packet ? I'm telling that Framed-IP is OK in Accounting-start, regular accounting and access packets. It's broken only in accounting-stop packet.
How to generate accounting stop packet - close the existing PPPoE session and Mikrotik will send this packet to Radius.

I'm quite sure in this, we use Framed-IP in our software for session identification and now our clients who upgraded RouterOS are facing the issue.

Re: v6.39.1 [current]

Posted: Fri May 12, 2017 5:09 am
by DaveBrowning
Has anyone seen trouble with DHCP after upgrading to 6.39 or 6.39.1? I upgraded a 951Ui-2HnD router to 6.39 at a customer on Tuesday morning because I was onsite to add new equipment and thought I'd try the upgrade (yeah, silly idea I know) and now our Debian Linux server isn't accepting DHCP offers from it (the Linux box hasn't been touched and no software has been upgraded on it). The Linux box syslog reports that no DHCP offers were received, the router log says the offer wasn't accepted. Windows 7 doesn't seem to have a problem and gets a lease without problem. I've tried 6.39.1 and that doesn't seem to have fixed it.
I'm having this issue. driving me bonkers! Support advised downgrade to bugfix version however I'm sure a downgrade would go horribly wrong given I also have 30 odd CAPS connecting to the problem router for CAPsMAN.. Eagerly awaiting a later version with a fix.

Re: v6.39.1 [current]

Posted: Fri May 12, 2017 8:53 am
by Ansy
Sorry, some records failed to add because of more than 63 chars length (I've specially tested this limit).
A DNS name cannot be longer than 255 chars in total and no more than 63 chars in each "label" (part between dots).
That is described in the standard, so when you expected to use longer labels the error is on your side.
All domain names are real ones (russian gov. block list), but IMHO that limits are for name field, not for REGEXP field in MT ROS DNS static records. & yes, I've tested dot delimited regexps each shorter than 63 chars too, without success. Any case, I need more static records than huge their lengths.

P.S. Top length record, for example, 214 chars (lightly changed, of course ;)
legalrc.biz.magazin-v-doverennyx-account-legpills.prinimayet-zakazy-pishite-v-kontakty.kuritelnyye-smesi-miksy-marki-sol-dzhiv-jwh-skorost-zakladki.reagenty-kuritelniye-smesi-geroin-efedrin-metadon-lsd-mdma-jwh.biz

Re: v6.39.1 [current]

Posted: Fri May 12, 2017 10:10 am
by strods
gavinsaxby - Please write to support@mikrotik.com and send supout file which would be generated on DHCP server while you can not receive address from it.
DaveBrowning - Please provide ticket number of that ticket within which support has advised you to downgrade to bugfix version. We will look into it.

Before you generate supout file please:
1) Run this command - "/system logging add topics=dhcp,debug";
2) After that reproduce problem and only then generate supout file.

Re: v6.39.1 [current]

Posted: Fri May 12, 2017 4:10 pm
by pukkita
Have several routers (CCRs) with 6.39 and 6.39.1, accounting enabled, working with freeradius 3, framedipaddress is sent correctly. Have you inspected a packet capture?
Are you talking about Stop accounting packet ? I'm telling that Framed-IP is OK in Accounting-start, regular accounting and access packets. It's broken only in accounting-stop packet.
How to generate accounting stop packet - close the existing PPPoE session and Mikrotik will send this packet to Radius.

I'm quite sure in this, we use Framed-IP in our software for session identification and now our clients who upgraded RouterOS are facing the issue.
I was referring to the stop records in radacct (guess you use a SQL backend).

Had the chance to setup debugging and you're right, definitely Framed-IP-Address = 10.0.0.0 on the stop accounting packets... didn't notice this as radacct stop record correctly reflects the Framed-IP-Address of the user and I don't use the values directly from the packets but from the SQL backend.

I think it will be better to write directly to support along with a supout etc.

Re: v6.39.1 [current]

Posted: Sat May 13, 2017 3:53 pm
by peo
Serial port forwarding don’t work on mmips architecture. The same configuration works on mipsbe device.

Re: v6.39.1 [current]

Posted: Sun May 14, 2017 12:53 am
by gyropilot
Updated the following devices today to ROS v6.39.1 with no difficulties:

hAP ac Lite
Metal 52 ac

Re: v6.39.1 [current]

Posted: Sun May 14, 2017 10:36 am
by Hakeel
Anyone experience any issues with with P2P filters after this upgrade? i had configured torrent filters but after the upgrade am now told p2p filters is obsolete i match with layer7. how do i go about fixing this problem?

Re: v6.39.1 [current]

Posted: Sun May 14, 2017 11:27 am
by gramels
still having DFS problems with hAP ac on 6.39.1
on 6.38.5 everything was fine.
every day there is radar detected and the AP switches channels until it gets to a non DFS channel (5180).
it makes no difference if I change antenna gain or the "start channel" to another one (usally 5500 ist default, tested with 5580, 5640).
the problem only seems to occur, if the device is triple chain 5GHz.
this problem seems to also be present on netmetal 5.
one connected device is sufficient to trigger the DFS problem.
same here, I upgraded to 6.39.1 yesterday but do not get stable connection on DFS channels (using CAPSMAN), downgraded the APs to 6.38.5 and it is fine again. CAPSMAN still on 6.39.1

Re: v6.39.1 [current]

Posted: Sun May 14, 2017 11:46 am
by msatter
Anyone experience any issues with with P2P filters after this upgrade? i had configured torrent filters but after the upgrade am now told p2p filters is obsolete i match with layer7. how do i go about fixing this problem?
Follow the postings: viewtopic.php?p=596706#p596706

Re: v6.39.1 [current]

Posted: Mon May 15, 2017 12:29 pm
by SiB
Upgrade 3x CCR1016-12G and my tunnels base on IPSec are down... from v6.4 or v6.20 to current.
ARPings works but I haven't L3 communication.

logs:
ipsec, debug ... Expecting IP address type in main mode when using preshared key for authorization (see RFC 2409 section 5.4), but User_FQDN ...
ipsec, error ... phase1 negotiation failed due to time up ...

IPSec Peer - I open one tunel and ONLY PRESS APPLY and get error like "failure: address ID must be used in main mode, use my-id=auto!"

WorkARound or maybe a sollution is to change into "My ID Type: auto" because all my peers use old default value "user fqdn" without any fqdn inserted - current have got problem with old default value.

@Mikrotik:
1) Why I have tree column with ~"My ID"
2) I cannot use a loop to change this option for all entry :( .
Any find is with my-id, not my-id-type and the user-fqdn: is strange. e.g. "put [/ip ipsec peer find where my-id=user-fqdn:]" and others
Maybe sollution shouldbe: /ip ipsec peer set my-id=auto [find ] ;

http://prntscr.com/f7zd73
Image

Re: v6.39.1 [current]

Posted: Mon May 15, 2017 5:40 pm
by complex1
Just updated my RB2011UiAS from v6.38.5 to v6.39.1 and everything is OK so far.

Re: v6.39.1 [current]

Posted: Mon May 15, 2017 6:30 pm
by Thomeless
I also having problem with DFS on AP in this version. One of my AP still detecting for radar and never switch back to normal mode. I don't have this issue on clients. AP si RB411.
Which country and frequency did you set it to? Some frequencies require a very long radar search (10 minutes)
Czech Republic and frequency 5600 I think...

Re: v6.39.1 [current]

Posted: Tue May 16, 2017 11:01 am
by Deantwo
Upgrade 3x CCR1016-12G and my tunnels base on IPSec are down...
I also upgraded a CCR1016-12G to RouterOS v6.39.1, and the IPsec tunnel stopped working.
From what I could see in the Installed SAs, it was not receiving anything even though the other end was transmitting.
Upgrading the router in the other end yielded the same result, it stopped receiving.

I ended up downgrading again, not sure what was going and I haven't had the time to test it.

Re: v6.39.1 [current]

Posted: Tue May 16, 2017 11:55 am
by pe1chl
it must be specific to your configuration as I have also upgraded a CCR to 6.39.1 and the IPsec tunnels work fine.
maybe some error in the firewall config.

Re: v6.39.1 [current]

Posted: Tue May 16, 2017 7:52 pm
by marcin21
damn!, upgraded few RB2011, CRS125 and 3011 to from ros36.4 to ros39.1,
rb3011 is functional but unable to login due to "invalid password" error.
Is there eny solution to such problem or do I have to go there and do factory reset?

Re: v6.39.1 [current]

Posted: Wed May 17, 2017 10:10 am
by Bossman
Some people here are complaining about serious issues with 3011 after upgrade.
However I haven't seen any reaction of MK confirming or rejecting that. So I'm asking whether is it safe to upgrade 3011 and wish to hear clear answer.
Our routers are set to auto Update.

We have ONE 3011.5 ports in use. All routing is OSPF. No Firewall rules. NO Queues.

After 8 days, things seem to be fine.

Re: v6.39.1 [current]

Posted: Wed May 17, 2017 6:49 pm
by miketk
removed

Re: v6.39.1 [current]

Posted: Wed May 17, 2017 6:51 pm
by miketk
Have several routers (CCRs) with 6.39 and 6.39.1, accounting enabled, working with freeradius 3, framedipaddress is sent correctly. Have you inspected a packet capture?
Are you talking about Stop accounting packet ? I'm telling that Framed-IP is OK in Accounting-start, regular accounting and access packets. It's broken only in accounting-stop packet.
How to generate accounting stop packet - close the existing PPPoE session and Mikrotik will send this packet to Radius.
I'm quite sure in this, we use Framed-IP in our software for session identification and now our clients who upgraded RouterOS are facing the issue.
I can confirm the issue with 3011 and radius accounting Stop on 6.39.1,
have to use mix of data for session ID because mikrotik acct-session-id is not unique and sometimes have collision.

Re: v6.39.1 [current]

Posted: Thu May 18, 2017 10:47 am
by techmngr
Hi Everyone.

It's my first time posting in this forum and just a little over 3 months using Mikrotik routers, having worked in mostly Cisco network environments. Just would like to ask what the most stable RouterOS there is for a Mikrotik1036? If it helps, I'll be running BGP on the router.

I have so much questions about Mikrotik, would this be the best forum for Mikrotik? :-)

Thanks in advance.
Hi,

Im using version 6.38.5 on CCR1036-12G-4S and using bgp without any problem.
Hi Sir..

Thanks for the response..I'll try using it then..appreciate it.

Re: v6.39.1 [current]

Posted: Sat May 20, 2017 12:45 pm
by kraks
Hi,
I have problem send trap at 2 IP address.
Trap is sending only 1 IP address

RB1000 FW 6.39.1

Settings

Image
Image

when i change sequence then the problem is same

Image
Image

Is it possible fix it ?

Re: v6.39.1 [current]

Posted: Mon May 22, 2017 1:34 am
by Ishtiaque
I do not blindly hurry with updates. I read the forum. When I know why to do the update, I firstly test in the lab. And yes, I needed to use a serial cable and netinstall few times in the history in the lab. But never in the field so far.
I also use backup partitions to be able easily revert the routers back when necessary so I am very unhappy of those new routers with 16MB of flash that are not able to carry two partitions.
Dear
Which is the best version for CCR-1016-12G ...

Please ?

Thanks In advance .

Re: v6.39.1 [current]

Posted: Mon May 22, 2017 6:46 am
by jarda
The one you are running now if you do not suffer by any problem or do not need any of new features.

Re: v6.39.1 [current]

Posted: Mon May 22, 2017 2:04 pm
by andreadg88
Hi,
i've upgraded my pair of CCR1072 that i use as PPPoE Server and i've the same issue of alexcherry about radius accounting stop packet.
The Framed-IP-Address value that RouterOS send to Freeradius was totally incorrect.
The Framed-IP-Address value for the Interim-Update of same connected user works fine.


INTERIM-UPDATE
May/22/2017 12:30:16 radius,debug,packet sending Accounting-Request with id 86 to 185.129.91.248:1646
May/22/2017 12:30:16 radius,debug,packet Signature = 0x66b016e8ba441d18c7ed03c01a7d14e5
May/22/2017 12:30:16 radius,debug,packet Service-Type = 2
May/22/2017 12:30:16 radius,debug,packet Framed-Protocol = 1
May/22/2017 12:30:16 radius,debug,packet NAS-Port = 15765320
May/22/2017 12:30:16 radius,debug,packet NAS-Port-Type = 15
May/22/2017 12:30:16 radius,debug,packet
User-Name = "209_mi_voce@optimabs"
May/22/2017 12:30:16 radius,debug,packet Calling-Station-Id = "C8:0E:14:46:6D:37"
May/22/2017 12:30:16 radius,debug,packet Called-Station-Id = "Optima4014"
May/22/2017 12:30:16 radius,debug,packet NAS-Port-Id = "bridgeVlan4014"
May/22/2017 12:30:16 radius,debug,packet MS-CHAP-Domain = "optimabs"
May/22/2017 12:30:16 radius,debug,packet Acct-Session-Id = "81908eef"
May/22/2017 12:30:16 radius,debug,packet
Framed-IP-Address = 10.101.7.52
May/22/2017 12:30:16 radius,debug,packet Acct-Authentic = 1
May/22/2017 12:30:16 radius,debug,packet Event-Timestamp = 1495449016
May/22/2017 12:30:16 radius,debug,packet Acct-Session-Time = 780
May/22/2017 12:30:16 radius,debug,packet Idle-Timeout = 3600
May/22/2017 12:30:16 radius,debug,packet Session-Timeout = 0
May/22/2017 12:30:16 radius,debug,packet MT-Address-List = "ngavoce"
May/22/2017 12:30:16 radius,debug,packet Acct-Input-Octets = 54
May/22/2017 12:30:16 radius,debug,packet Acct-Input-Gigawords = 0
May/22/2017 12:30:16 radius,debug,packet Acct-Input-Packets = 3
May/22/2017 12:30:16 radius,debug,packet Acct-Output-Octets = 46
May/22/2017 12:30:16 radius,debug,packet Acct-Output-Gigawords = 0
May/22/2017 12:30:16 radius,debug,packet Acct-Output-Packets = 4
May/22/2017 12:30:16 radius,debug,packet Acct-Status-Type = 3
May/22/2017 12:30:16 radius,debug,packet NAS-Identifier = "PPPoE-2"
May/22/2017 12:30:16 radius,debug,packet Acct-Delay-Time = 0
May/22/2017 12:30:16 radius,debug,packet MT-Realm = 0x6f7074696d616273
May/22/2017 12:30:16 radius,debug,packet NAS-IP-Address = 185.129.88.5




RELEASE
May/22/2017 12:30:29 radius,debug,packet sending Accounting-Request with id 98 to 185.129.91.248:1646
May/22/2017 12:30:29 radius,debug,packet Signature = 0xcd439aab48a306e004dc6280de6f2fc8
May/22/2017 12:30:29 radius,debug,packet Service-Type = 2
May/22/2017 12:30:29 radius,debug,packet Framed-Protocol = 1
May/22/2017 12:30:29 radius,debug,packet NAS-Port = 15765320
May/22/2017 12:30:29 radius,debug,packet NAS-Port-Type = 15
May/22/2017 12:30:29 radius,debug,packet
User-Name = "209_mi_voce@optimabs"
May/22/2017 12:30:29 radius,debug,packet Calling-Station-Id = "C8:0E:14:46:6D:37"
May/22/2017 12:30:29 radius,debug,packet Called-Station-Id = "Optima4014"
May/22/2017 12:30:29 radius,debug,packet NAS-Port-Id = "bridgeVlan4014"
May/22/2017 12:30:29 radius,debug,packet MS-CHAP-Domain = "optimabs"
May/22/2017 12:30:29 radius,debug,packet Acct-Session-Id = "81908eef"
May/22/2017 12:30:29 radius,debug,packet
Framed-IP-Address = 10.0.0.0
May/22/2017 12:30:29 radius,debug,packet Acct-Authentic = 1
May/22/2017 12:30:29 radius,debug,packet Event-Timestamp = 1495449029
May/22/2017 12:30:29 radius,debug,packet Acct-Session-Time = 794
May/22/2017 12:30:29 radius,debug,packet Idle-Timeout = 3600
May/22/2017 12:30:29 radius,debug,packet Session-Timeout = 0
May/22/2017 12:30:29 radius,debug,packet MT-Address-List = "ngavoce"
May/22/2017 12:30:29 radius,debug,packet Acct-Input-Octets = 54
May/22/2017 12:30:29 radius,debug,packet Acct-Input-Gigawords = 0
May/22/2017 12:30:29 radius,debug,packet Acct-Input-Packets = 3
May/22/2017 12:30:29 radius,debug,packet Acct-Output-Octets = 46
May/22/2017 12:30:29 radius,debug,packet Acct-Output-Gigawords = 0
May/22/2017 12:30:29 radius,debug,packet Acct-Output-Packets = 4
May/22/2017 12:30:29 radius,debug,packet Acct-Status-Type = 2
May/22/2017 12:30:29 radius,debug,packet Acct-Terminate-Cause = 10
May/22/2017 12:30:29 radius,debug,packet NAS-Identifier = "PPPoE-2"
May/22/2017 12:30:29 radius,debug,packet Acct-Delay-Time = 0
May/22/2017 12:30:29 radius,debug,packet MT-Realm = 0x6f7074696d616273
May/22/2017 12:30:29 radius,debug,packet NAS-IP-Address = 185.129.88.5



FreeRadius LOG
Mon May 22 12:32:11 2017 : Info: Released IP 10.0.0.0 (did Optima4014 cli C8:0E:14:46:6D:37 user 209_mi_voce@optimabs)
Mon May 22 12:32:11 2017 : Auth: Login OK: [209_mi_voce@optimabs] (from client MIKROTIK PPPoE-2 port 15765441 cli C8:0E:14:46:6D:37)
Mon May 22 12:32:11 2017 : Info: Allocated IP: 10.101.5.119 from voce_nga   (did Optima4014 cli C8:0E:14:46:6D:37 port 15765441 user 209_mi_voce@optimabs)


I cannot downgrade to previous version because i create a service disruption...please fix it....

Re: v6.39.1 [current]

Posted: Tue May 23, 2017 12:29 am
by Ishtiaque
The one you are running now if you do not suffer by any problem or do not need any of new features.
Dear ,
Yes problem in current version , please just suggest me which is the best version.
and which version you are working with ..... Please Don't mind .

Re: v6.39.1 [current]

Posted: Tue May 23, 2017 1:05 pm
by andriys
please just suggest me which is the best version.
and which version you are working with
When in doubt, just stick to the latest version in the bugfix update channel, which is 6.37.5 as of now.

Re: v6.39.1 [current]

Posted: Tue May 23, 2017 2:50 pm
by jarda
I am mostly running at 6.39.1 now. Just few remote devices where I was not brave enough to upgrade are running with older versions.

Re: v6.39.1 [current]

Posted: Tue May 23, 2017 6:11 pm
by anuser
i am seeing a lot of rejected, forbidden by access list, and group key timeout, sending station leaving
anybody else?
I am seeing to many "group key timeouts" aswell with CAPSMAN forwarding (mainly on 2.4Ghz.)

Re: v6.39.1 [current]

Posted: Tue May 23, 2017 8:34 pm
by nilodgarry
hi guy i need a help please i want to add dude-6.39.1.npk on my mikrotik os but it doesn't work after multiple try.
my os is at the last version 6.39.1 but the dude is refuse to instal on package contents.

Re: v6.39.1 [current]

Posted: Tue May 23, 2017 10:27 pm
by jarda
Don't duplicate the posts.
viewtopic.php?p=599572#p599572

Re: v6.39.1 [current]

Posted: Tue May 23, 2017 11:27 pm
by acidvenom
My cAP bricked too. Was upgrading from 6.39 to 6.39.1. Just to let you know.

Re: v6.39.1 [current]

Posted: Wed May 24, 2017 11:49 am
by amt
I upgrade 6.39.1 many device like 3011,OmniTiK,CCR1036,CCR1072,SXT,LHG... and there is no any problem....

Re: v6.39.1 [current]

Posted: Thu May 25, 2017 12:36 am
by andreadg88
Hey,
have you any news regarding the issue that i have described below?
It's very difficult to work in this bugged scenario


Regards
Andrea

Hi,
i've upgraded my pair of CCR1072 that i use as PPPoE Server and i've the same issue of alexcherry about radius accounting stop packet.
The Framed-IP-Address value that RouterOS send to Freeradius was totally incorrect.
The Framed-IP-Address value for the Interim-Update of same connected user works fine.


INTERIM-UPDATE
May/22/2017 12:30:16 radius,debug,packet sending Accounting-Request with id 86 to 185.129.91.248:1646
May/22/2017 12:30:16 radius,debug,packet Signature = 0x66b016e8ba441d18c7ed03c01a7d14e5
May/22/2017 12:30:16 radius,debug,packet Service-Type = 2
May/22/2017 12:30:16 radius,debug,packet Framed-Protocol = 1
May/22/2017 12:30:16 radius,debug,packet NAS-Port = 15765320
May/22/2017 12:30:16 radius,debug,packet NAS-Port-Type = 15
May/22/2017 12:30:16 radius,debug,packet
User-Name = "209_mi_voce@optimabs"
May/22/2017 12:30:16 radius,debug,packet Calling-Station-Id = "C8:0E:14:46:6D:37"
May/22/2017 12:30:16 radius,debug,packet Called-Station-Id = "Optima4014"
May/22/2017 12:30:16 radius,debug,packet NAS-Port-Id = "bridgeVlan4014"
May/22/2017 12:30:16 radius,debug,packet MS-CHAP-Domain = "optimabs"
May/22/2017 12:30:16 radius,debug,packet Acct-Session-Id = "81908eef"
May/22/2017 12:30:16 radius,debug,packet
Framed-IP-Address = 10.101.7.52
May/22/2017 12:30:16 radius,debug,packet Acct-Authentic = 1
May/22/2017 12:30:16 radius,debug,packet Event-Timestamp = 1495449016
May/22/2017 12:30:16 radius,debug,packet Acct-Session-Time = 780
May/22/2017 12:30:16 radius,debug,packet Idle-Timeout = 3600
May/22/2017 12:30:16 radius,debug,packet Session-Timeout = 0
May/22/2017 12:30:16 radius,debug,packet MT-Address-List = "ngavoce"
May/22/2017 12:30:16 radius,debug,packet Acct-Input-Octets = 54
May/22/2017 12:30:16 radius,debug,packet Acct-Input-Gigawords = 0
May/22/2017 12:30:16 radius,debug,packet Acct-Input-Packets = 3
May/22/2017 12:30:16 radius,debug,packet Acct-Output-Octets = 46
May/22/2017 12:30:16 radius,debug,packet Acct-Output-Gigawords = 0
May/22/2017 12:30:16 radius,debug,packet Acct-Output-Packets = 4
May/22/2017 12:30:16 radius,debug,packet Acct-Status-Type = 3
May/22/2017 12:30:16 radius,debug,packet NAS-Identifier = "PPPoE-2"
May/22/2017 12:30:16 radius,debug,packet Acct-Delay-Time = 0
May/22/2017 12:30:16 radius,debug,packet MT-Realm = 0x6f7074696d616273
May/22/2017 12:30:16 radius,debug,packet NAS-IP-Address = 185.129.88.5




RELEASE
May/22/2017 12:30:29 radius,debug,packet sending Accounting-Request with id 98 to 185.129.91.248:1646
May/22/2017 12:30:29 radius,debug,packet Signature = 0xcd439aab48a306e004dc6280de6f2fc8
May/22/2017 12:30:29 radius,debug,packet Service-Type = 2
May/22/2017 12:30:29 radius,debug,packet Framed-Protocol = 1
May/22/2017 12:30:29 radius,debug,packet NAS-Port = 15765320
May/22/2017 12:30:29 radius,debug,packet NAS-Port-Type = 15
May/22/2017 12:30:29 radius,debug,packet
User-Name = "209_mi_voce@optimabs"
May/22/2017 12:30:29 radius,debug,packet Calling-Station-Id = "C8:0E:14:46:6D:37"
May/22/2017 12:30:29 radius,debug,packet Called-Station-Id = "Optima4014"
May/22/2017 12:30:29 radius,debug,packet NAS-Port-Id = "bridgeVlan4014"
May/22/2017 12:30:29 radius,debug,packet MS-CHAP-Domain = "optimabs"
May/22/2017 12:30:29 radius,debug,packet Acct-Session-Id = "81908eef"
May/22/2017 12:30:29 radius,debug,packet
Framed-IP-Address = 10.0.0.0
May/22/2017 12:30:29 radius,debug,packet Acct-Authentic = 1
May/22/2017 12:30:29 radius,debug,packet Event-Timestamp = 1495449029
May/22/2017 12:30:29 radius,debug,packet Acct-Session-Time = 794
May/22/2017 12:30:29 radius,debug,packet Idle-Timeout = 3600
May/22/2017 12:30:29 radius,debug,packet Session-Timeout = 0
May/22/2017 12:30:29 radius,debug,packet MT-Address-List = "ngavoce"
May/22/2017 12:30:29 radius,debug,packet Acct-Input-Octets = 54
May/22/2017 12:30:29 radius,debug,packet Acct-Input-Gigawords = 0
May/22/2017 12:30:29 radius,debug,packet Acct-Input-Packets = 3
May/22/2017 12:30:29 radius,debug,packet Acct-Output-Octets = 46
May/22/2017 12:30:29 radius,debug,packet Acct-Output-Gigawords = 0
May/22/2017 12:30:29 radius,debug,packet Acct-Output-Packets = 4
May/22/2017 12:30:29 radius,debug,packet Acct-Status-Type = 2
May/22/2017 12:30:29 radius,debug,packet Acct-Terminate-Cause = 10
May/22/2017 12:30:29 radius,debug,packet NAS-Identifier = "PPPoE-2"
May/22/2017 12:30:29 radius,debug,packet Acct-Delay-Time = 0
May/22/2017 12:30:29 radius,debug,packet MT-Realm = 0x6f7074696d616273
May/22/2017 12:30:29 radius,debug,packet NAS-IP-Address = 185.129.88.5



FreeRadius LOG
Mon May 22 12:32:11 2017 : Info: Released IP 10.0.0.0 (did Optima4014 cli C8:0E:14:46:6D:37 user 209_mi_voce@optimabs)
Mon May 22 12:32:11 2017 : Auth: Login OK: [209_mi_voce@optimabs] (from client MIKROTIK PPPoE-2 port 15765441 cli C8:0E:14:46:6D:37)
Mon May 22 12:32:11 2017 : Info: Allocated IP: 10.101.5.119 from voce_nga   (did Optima4014 cli C8:0E:14:46:6D:37 port 15765441 user 209_mi_voce@optimabs)


I cannot downgrade to previous version because i create a service disruption...please fix it....

Re: v6.39.1 [current]

Posted: Thu May 25, 2017 7:24 am
by Ishtiaque
please just suggest me which is the best version.
and which version you are working with
When in doubt, just stick to the latest version in the bugfix update channel, which is 6.37.5 as of now.
Thank you so Much Dear .
Nicely Answered.

Re: v6.39.1 [current]

Posted: Thu May 25, 2017 7:29 am
by Ishtiaque
I am mostly running at 6.39.1 now. Just few remote devices where I was not brave enough to upgrade are running with older versions.
Thank you Dear For your Answer .
It is Helpful for me and cleared many Hesitation .

Re: v6.39.1 [current]

Posted: Thu May 25, 2017 6:06 pm
by Yakko
We use mikrotiks for are customers and seem to be having issues on PS4 at the moment
I seem to be having an issue on PS4's with the dns.
The error code that pops up is
Cannot connect to playstation network. Dns error (NW-31253-4).
They suggest many things all of which i have tried. Just for reference though the the web browser on the ps4 works just fine.
port forwards
dns switched to google or open dns
updating ps4
static the ip
upnp... nothing works
I'm left at possibly the latest update to 3.39.1
"dns - made loading thousands of static entries faster;"
May be breaking something and preventing connection to it.
I'm kind of at a loss I even attempted to call Mikrotik experts from LinkTechs to review settings and find out what the problem is.

Re: v6.39.1 [current]

Posted: Thu May 25, 2017 7:05 pm
by pe1chl
Disable external access to the DNS and setup a dst-nat from 192.168.88.1:53 to 8.8.8.8:53 and see if that solves the issue.

Re: v6.39.1 [current]

Posted: Fri May 26, 2017 11:28 am
by strods
Radius accounting messages and other fixes are available in 6.40rc version:
viewtopic.php?f=21&t=121198

Re: v6.39.1 [current]

Posted: Fri May 26, 2017 12:46 pm
by MarkoB
We use mikrotiks for are customers and seem to be having issues on PS4 at the moment
I seem to be having an issue on PS4's with the dns.
The error code that pops up is
Cannot connect to playstation network. Dns error (NW-31253-4).
They suggest many things all of which i have tried. Just for reference though the the web browser on the ps4 works just fine.
port forwards
dns switched to google or open dns
updating ps4
static the ip
upnp... nothing works
I'm left at possibly the latest update to 3.39.1
"dns - made loading thousands of static entries faster;"
May be breaking something and preventing connection to it.
I'm kind of at a loss I even attempted to call Mikrotik experts from LinkTechs to review settings and find out what the problem is.
PS4 does not support EDNS
change Max UDP Packet Size in DNS options from 4096 to 512

Re: v6.39.1 [current]

Posted: Mon May 29, 2017 11:59 pm
by voytec
Updated CCR1009-7G-1C-1S+ from v6.38.5 to v6.39.1 - everything OK.

Re: v6.39.1 [current]

Posted: Tue May 30, 2017 4:03 am
by ploquets
I'm still trying to figure it out this changelog from 6.39
!) ppp - implemented internal algorithm for "change-mss", no mangle rules necessary;

viewtopic.php?t=122019

Please help

Re: v6.39.1 [current]

Posted: Wed May 31, 2017 11:58 pm
by jmay
Anyone seeing problems with ping timeouts? Every MT I have is losing about 5% of pings. I can even ping a MT from a computer with a direct cable plugged into it and lose packets.

Re: v6.39.1 [current]

Posted: Fri Jun 02, 2017 5:25 pm
by idlemind
I just bought a pair of cap lite's and I un-boxed them but found the default configuration to be buggy at best.

They came with 6.37.4 and the default configuration came with the standard 192.168.88.1 on a bridge interface and a default SSID broadcasted. Sadly no DHCP server or pool are setup so you can't configure the device without setting a static IP on your device and then connect to either Ethernet or wireless. Not the worst but it did prevent me from using the TikApp to try and configure these little units. In summary, the default configuration for these units in 6.37.4 provides a very poor customer experience and doesn't match the documentation provided with the product.

After some mucking around with them I got them online and updated them to 6.39.1 to see if their were improvements in the default configuration. There definitely was but still not enough to get the unit setup in a fashion suggested by the documentation, connect to the SSID and type http://192.168.88.1 into the browser.

The difference comes down to a DHCP client being placed on the bridge interface. A WLAN is still configured and broadcast that you won't be able to connect to unless you have plugged the device into an Ethernet segment running one. Arguably better but still doesn't match the documentation.

Suggestion

Either adapt the products documentation to match the configuration supplied in 6.39.1 or alter the default configuration. The alteration would simply be to make it function as the documentation says it would. Plug it into power, connect to the default SSID and use the TikApp, WebFig, WinBox or SSH to configure the device at 192.168.88.1.

To play devils advocate, a device like the cap lite is probably not going to be used like a typical router so I could see some proponents of the cap lite's default behavior in 6.39.1. You could match the MAC to an IP and login into it after plugging it into a network device. For some and especially in larger deployments I could see the benefit of this. It definitely matches other products in the access point market. If that's the case and the intention from MikroTik it should be noted in the documentation of the product and displayed prominently on the devices information page. An example could be bold print indicating this device has received an update to how it is configured.

Reference

6.37.4 Default Configuration
  script: :global ssid;
          #| WISP Bridge:
          #|  * wireless and LAN interfaces are bridged;
          #|  * IP address 192.168.88.1/24 is set on bridge
          #| wlan1 Configuration:
          #|     mode:          ap-bridge;
          #|     band:          2ghz-b/g/n;
          #|     ht-chains:     0,1;
          #|     ht-extension:  20/40mhz-Ce;
          #| LAN Configuration:


          :log info Starting_defconf_script_;
          :global action;
          #-------------------------------------------------------------------------------
          # Apply configuration.
          # these commands are executed after installation or configuration reset
          #-------------------------------------------------------------------------------
          :if ($action = "apply") do={
          # wait for interfaces
          :local count 0;
          :while ([/interface ethernet find] = "") do={
          :if ($count = 30) do={
          :log warning "DefConf: Unable to find ethernet interfaces";
          /quit;
          }
          :delay 1s; :set count ($count +1);
          };

            :local count 0;
            :while ([/interface wireless print count-only] < 1) do={
              :set count ($count +1);
              :if ($count = 30) do={
                :log warning "DefConf: Unable to find wireless interface(s)";
                /ip address add address=192.168.88.1/24 interface=ether1 comment="defconf";
                /quit
              }
              :delay 1s;
            };
            /interface wireless {
              set wlan1 mode=ap-bridge band=2ghz-b/g/n tx-chains=0,1 rx-chains=0,1 \
                disabled=no wireless-protocol=802.11 distance=indoors
              :local wlanMac  [/interface wireless get wlan1 mac-address];
              :set ssid "MikroTik-$[:pick $wlanMac 9 11]$[:pick $wlanMac 12 14]$[:pick $wlanMac 15 17]"
              set wlan1 ssid=$ssid
              set wlan1 frequency=auto
              set wlan1 channel-width=20/40mhz-Ce ;
            }
           /interface bridge
             add name=bridge disabled=no auto-mac=yes protocol-mode=rstp comment=defconf;
           :local bMACIsSet 0;
           :foreach k in=[/interface find where !(slave=yes  || name~"bridge")] do={
             :log info "k: $k"
             :local tmpPortName [/interface get $k name];
             :log info "port: $tmpPortName"
             :if ($bMACIsSet = 0) do={
               :if ([/interface get $k type] = "ether") do={
                 /interface bridge set "bridge" auto-mac=no admin-mac=[/interface ethernet get $tmpPortName mac-address];
                 :set bMACIsSet 1;
               }
             }
             /interface bridge port
               add bridge=bridge interface=$tmpPortName comment=defconf;
           }
            /ip address add address=192.168.88.1/24 interface=bridge comment="defconf";
          }
          #-------------------------------------------------------------------------------
          # Revert configuration.
          # these commands are executed if user requests to remove default configuration
          #-------------------------------------------------------------------------------
          :if ($action = "revert") do={
          # remove wan port protection
           /ip firewall filter remove [find comment~"defconf"]
           /ip firewall nat remove [find comment~"defconf"]
           /tool mac-server remove [find interface!=all]
           /tool mac-server set [find] disabled=no
           /tool mac-server mac-winbox remove [find interface!=all]
           /tool mac-server mac-winbox set [find] disabled=no
           /ip neighbor discovery set [find ] discover=yes
             :local o [/ip dhcp-server network find comment="defconf"]
             :if ([:len $o] != 0) do={ /ip dhcp-server network remove $o }
             :local o [/ip dhcp-server find name="defconf" !disabled]
             :if ([:len $o] != 0) do={ /ip dhcp-server remove $o }
             /ip pool {
               :local o [find name="default-dhcp" ranges=192.168.88.10-192.168.88.254]
               :if ([:len $o] != 0) do={ remove $o }
             }
             :local o [/ip dhcp-client find comment="defconf"]
             :if ([:len $o] != 0) do={ /ip dhcp-client remove $o }
           /ip dns {
             set allow-remote-requests=no
             :local o [static find name=router address=192.168.88.1]
             :if ([:len $o] != 0) do={ static remove $o }
           }
           /ip address {
             :local o [find comment="defconf"]
             :if ([:len $o] != 0) do={ remove $o }
           }
           :foreach iface in=[/interface ethernet find] do={
             /interface ethernet set $iface name=[get $iface default-name]
           }
           /interface bridge port remove [find comment="defconf"]
           /interface bridge remove [find comment="defconf"]
           /interface wireless reset-configuration wlan1
          }
          :log info Defconf_script_finished;
6.39.1 Default Configuration
  script: :global ssid;
          #| WISP Bridge:
          #|  * wireless and LAN interfaces are bridged;

          #| wlan1 Configuration:
          #|     mode:          ap-bridge;
          #|     band:          2ghz-b/g/n;
          #|     ht-chains:     0,1;
          #|     ht-extension:  20/40mhz-Ce;
          #| LAN Configuration:
          #|     DHCP Client: enabled on LAN port;

          :log info Starting_defconf_script_;
          :global action;
          #-------------------------------------------------------------------------------
          # Apply configuration.
          # these commands are executed after installation or configuration reset
          #-------------------------------------------------------------------------------
          :if ($action = "apply") do={
          # wait for interfaces
          :local count 0;
          :while ([/interface ethernet find] = "") do={
          :if ($count = 30) do={
          :log warning "DefConf: Unable to find ethernet interfaces";
          /quit;
          }
          :delay 1s; :set count ($count +1);
          };

            :local count 0;
            :while ([/interface wireless print count-only] < 1) do={
              :set count ($count +1);
              :if ($count = 30) do={
                :log warning "DefConf: Unable to find wireless interface(s)";
                /ip address add address=192.168.88.1/24 interface=ether1 comment="defconf";
                /quit
              }
              :delay 1s;
            };
            /interface wireless {
              set wlan1 mode=ap-bridge band=2ghz-b/g/n tx-chains=0,1 rx-chains=0,1 \
                disabled=no wireless-protocol=802.11 distance=indoors
              :local wlanMac  [/interface wireless get wlan1 mac-address];
              :set ssid "MikroTik-$[:pick $wlanMac 9 11]$[:pick $wlanMac 12 14]$[:pick $wlanMac 15 17]"
              set wlan1 ssid=$ssid
              set wlan1 frequency=auto
              set wlan1 channel-width=20/40mhz-Ce ;
            }
           /interface bridge
             add name=bridge disabled=no auto-mac=yes protocol-mode=rstp comment=defconf;
           :local bMACIsSet 0;
           :foreach k in=[/interface find where !(slave=yes  || name~"bridge")] do={
             :log info "k: $k"
             :local tmpPortName [/interface get $k name];
             :log info "port: $tmpPortName"
             :if ($bMACIsSet = 0) do={
               :if ([/interface get $k type] = "ether") do={
                 /interface bridge set "bridge" auto-mac=no admin-mac=[/interface ethernet get $tmpPortName mac-address];
                 :set bMACIsSet 1;
               }
             }
             /interface bridge port
               add bridge=bridge interface=$tmpPortName comment=defconf;
           }
            /ip dhcp-client add interface=bridge disabled=no comment="defconf";
          }
          #-------------------------------------------------------------------------------
          # Revert configuration.
          # these commands are executed if user requests to remove default configuration
          #-------------------------------------------------------------------------------
          :if ($action = "revert") do={
          # remove wan port protection
           /ip firewall filter remove [find comment~"defconf"]
           /ip firewall nat remove [find comment~"defconf"]
           /tool mac-server remove [find interface!=all]
           /tool mac-server set [find] disabled=no
           /tool mac-server mac-winbox remove [find interface!=all]
           /tool mac-server mac-winbox set [find] disabled=no
           /ip neighbor discovery set [find ] discover=yes
             :local o [/ip dhcp-server network find comment="defconf"]
             :if ([:len $o] != 0) do={ /ip dhcp-server network remove $o }
             :local o [/ip dhcp-server find name="defconf" !disabled]
             :if ([:len $o] != 0) do={ /ip dhcp-server remove $o }
             /ip pool {
               :local o [find name="default-dhcp" ranges=192.168.88.10-192.168.88.254]
               :if ([:len $o] != 0) do={ remove $o }
             }
             :local o [/ip dhcp-client find comment="defconf"]
             :if ([:len $o] != 0) do={ /ip dhcp-client remove $o }
           /ip dns {
             set allow-remote-requests=no
             :local o [static find name=router address=192.168.88.1]
             :if ([:len $o] != 0) do={ static remove $o }
           }
           /ip address {
             :local o [find comment="defconf"]
             :if ([:len $o] != 0) do={ remove $o }
           }
           :foreach iface in=[/interface ethernet find] do={
             /interface ethernet set $iface name=[get $iface default-name]
           }
           /interface bridge port remove [find comment="defconf"]
           /interface bridge remove [find comment="defconf"]
           /interface wireless reset-configuration wlan1
          }
          :log info Defconf_script_finished;

Re: v6.39.1 [current]

Posted: Sat Jun 03, 2017 7:42 pm
by jarda
You do not need to care about the out of the box config. Just plug the wire, connect with winbox by mac, wipe out the config and enjoy clear device prepaired for whatever configuration you can imagine.

Re: v6.39.1 [current]

Posted: Mon Jun 05, 2017 11:12 am
by HeadCraft
Upgraded from 6.38.5 to 6.39.1
Wireless clients (Honeywell Dolphin 6000) can't connect to wi-fi, while all other devices can (included dolphin 6500, notebooks, smartphones, etc)
I have CAPsMAN configured on mikrotik 1100AHx2 and CAP clients on mikrotik hAP ac lite and RB912UAG-2HPnD.
Log on CAPsMAN writes:
...disconnected, extensive data loss
...disconnected, 4-way handshake timeout
...connected
...disconnected, extensive data loss
...connected
...disconnected, received deauth: class 3 frame received (7)
...disconnected, registered to other interface
and so on.

It seems like wireless clients can't even authenticate on wi-fi. Downgraded to 6.38.5 on CAP clients, while CAPsMAN is still 6.39.1, and all start working again.

Re: v6.39.1 [current]

Posted: Mon Jun 05, 2017 11:22 am
by mariro
Upgrade RB 1100 AH and RB 1100 AHX4 to version 6.39, 10 % loss packet on the any ports in RB. When dowgrade on system version 6.38, los packet is correct.

Re: v6.39.1 [current]

Posted: Tue Jun 06, 2017 2:05 pm
by strods
Version 6.39.2 has been released:
viewtopic.php?f=21&t=122322