NOP*) rb2011 - fixed possible LCD blinking along with ethernet LED (introduced in 6.40);
same as beforeirghost - Are you talking about blinking LCD during Netinstall process? This fix solved problem when LCD was blinking while device is booted on RouterOS. Next rc release will fix also blinking LCD during Netinstall process (latest Netinstall will be required).
2017-08-04T15:52:43.042+02:00 38d0 W:Network gsync32!LogPotentialProxyNetworkFailure [Reason: Warning:Potential proxy failure] @ 306 (**email_address**)> WinHttpGetProxyForUrl auto-detect failed with 0x80072f94 [color=#FF0000][Reason: Warning:Network timeouts][/color] . 0/(null). IsNetworkActive is 1, flags 1, IsNetworkActive GetLastError 0x80004005
2017-08-04T15:52:43.497+02:00 38d0 W:Sync gsync32!GLookSyncHelper::GetSyncPermit @ 513 (**email_address**)> SyncEngine '4'; SyncPermit is SYNC_PERMIT_UNKNOWN (0)
2017-08-04T15:52:43.499+02:00 38d0 W:Sync gsync32!GLookSyncHelper::GetSyncPermit @ 513 (**email_address**)> SyncEngine '4'; SyncPermit is SYNC_PERMIT_UNKNOWN (0)
2017-08-04T15:52:43.499+02:00 38d0 A:Sync gsync32!GLookSyncHelper::SetSyncPermit @ 537 (**email_address**)> SyncEngine '4'; SyncPermit is now: SYNC_PERMIT_GRANTED (2).
2017-08-04T15:52:43.499+02:00 38d0 A:Sync gsync32!GLookSyncer::GoOnline @ 1315 (**email_address**)> Going Online.
2017-08-04T15:52:43.500+02:00 38d0 A:Sync gsync32!GLookSyncer::ScheduleAllSyncTasks @ 1549 (**email_address**)> Scheduling calendar sync task: init delay 5 sec, interval 600 sec
2017-08-04T15:52:43.500+02:00 38d0 A:Sync gsync32!GLookSyncer::ScheduleAllSyncTasks @ 1566 (**email_address**)> Scheduling contacts sync task: init delay 5 sec, interval 1200 sec
2017-08-04T15:52:43.500+02:00 38d0 A:Sync gsync32!GLookSyncer::ScheduleAllSyncTasks @ 1583 (**email_address**)> Scheduling email sync task: init delay 5 sec, interval 60 sec
2017-08-04T15:52:43.500+02:00 38d0 A:Sync gsync32!GLookSyncer::ScheduleAllSyncTasks @ 1604 (**email_address**)> Scheduling AB sync task: init delay 30 sec, interval 21600 sec
2017-08-04T15:52:43.500+02:00 38d0 A:Sync gsync32!GLookSyncer::ScheduleAllSyncTasks @ 1621 (**email_address**)> Scheduling notes sync task: init delay 5 sec, interval 3600 sec
2017-08-04T15:52:43.500+02:00 3618 W:Network gsync32!LogPotentialProxyNetworkFailure [Reason: Warning:Potential proxy failure] @ 306 (**email_address**)> WinHttpGetProxyForUrl auto-detect failed with 0x80072f94 [Reason: Warning:Network timeouts]. 0/(null). IsNetworkActive is 1, flags 1, IsNetworkActive GetLastError 0x80004005
#error exporting /system routerboard mode-button
i noticed the same thingAnyone have problem with ethernet link down and up? i see that after i upgrade 6.40 from 6.39.
Can you see if the connections are marked as fasttrack?Fasttrack does not work in 6.40.1
SXT LTE
There is no fasttrack support for SXT LTE units yet!Can you see if the connections are marked as fasttrack?Fasttrack does not work in 6.40.1
SXT LTE
What's new in v6.40 (2017-Jul-21 08:45):
!) lte - added initial fastpath support (except SXT LTE and Sierra modems);
!) lte - added initial support for passthrough mode for lte modems that supports fastpath;
now what?There is no fasttrack support for SXT LTE units yet!Can you see if the connections are marked as fasttrack?Fasttrack does not work in 6.40.1
SXT LTE
What's new in v6.40 (2017-Jul-21 08:45):
!) lte - added initial fastpath support (except SXT LTE and Sierra modems);
!) lte - added initial support for passthrough mode for lte modems that supports fastpath;
Hello,
Update from 6.39.2...aaand problem with dhcp:
Mikrotik(ap bridge,dhcp server)<----wireless--->ap_client[F8:D1:11:52:xx:xx](bridged wlan & eth, no other services)<----wired--->PC[B8:27:EB:8C:xx:xx]
aug/07 01:37:07 dhcp,warning dhcp1 offering lease 10.10.20.20 for B8:27:EB:8C:xx:xx to F8:D1:11:52:xx:xx without success
Reverted back to 6.39.2, problem disappears.
I am seeing the same thing, scenario is: a rb POE Hex Lite, that is powering another POE Hex Lite (that is about 140ft away, with good cat6 cable), on the far end POE hex Lite, i had to set eth1-poe-in (settings = long-cable = yes a while back, and have never had issues). after upgrade from 6.37.1 to 6.40.1 today, the 1st Hex LIte is showing Short-circut on the eth2 powering the far end hex Lite.After the upgrade to version 6.40.1 from 6.39.2, problems with PoE ports:
00:10:11 poe-out,warning ether4 detected poe-out status: short_circuit
00:10:13 poe-out,info ether4 detected poe-out status: wait_for_load
00:10:14 poe-out,warning ether4 detected poe-out status: short_circuit
00:10:14 poe-out,info ether4 detected poe-out status: wait_for_load
RouterBoard 960PGS.
After returning to 6.39.2, the problem disappeared.
So I have a HEX and about 45.000 blacklisted addresses and if I make the none-static they will be be still there after a reboot? They have to be saved somewhere during the reboot and the Flash is to small for that if I am correct.In the past if you had rule which adds IP address to address list, then you could either specify timeout or do not specify anything which is equal to none-dynamic behavior. None-static is introduced for those users who create blacklists for, for example, attackers and want to save them into address list still also after reboot.
in my post (in regards to passive POE issues introduced only in 6.40.1) , im not referring to log messages, these are poe SHORT errors/messages, which appear in the interface list, and thus cut POE to the affected port/device. (while on AUTO, which worked if i downgrade to any pre 6.40.1).Everyone who sees log messages about PoE but did not see them in previous versions - There was no PoE-OUT logging topic in past RouterOS versions. It was just now introduced in 6.40 version.
Latest RC (6.41) fixes the issue.I'm to lazy to read all the posts, but seen one with the same issue I have in 6.40.1
LCD screen flashes after a power cycle, if I make a change to anything like, " read only mode on or off, the screen stops flashing. It will flash on and off after a power up if read only was left check or unchecked. don't believe that the read only mode check box has anything to do with this, it just when Anything is changed about the screen settings it stops, until the power cycle.
The settings I have for the screen are off, disable - I see no reason to have this screen
on RB 2011UiAS-2Hnd
system routerboard upgrade
Updated from 6.39.2 to 6.40.1 on a hEX (RouterBOOT 3.35 before and after)
...
Was there any NIC firmware update incorporated in 6.40.1 that broke things possibly?
> /system routerboard print
routerboard: yes
model: RouterBOARD 750G r3
serial-number: ###
firmware-type: mt7621L
factory-firmware: 3.34
current-firmware: 3.35
upgrade-firmware: 3.35
I now tried four other Cat6 cables of various length, to no avail.Updated from 6.39.2 to 6.40.1 on a hEX (RouterBOOT 3.35 before and after)
Cable modem only seen as 100 Mbps link now. It's being negotiated as 1 Gbps, stays up for a second, and after some tries falls back to 100 Mbps.
Old RouterOS logs confirm that previously it was 1 Gbps (I'm on a 200 Mbps line, so 100 Mbps isn't enough).
Setting fixed to 1 Gbps establishes link for a second, then goes down again. Playing with various autosensing settings didn't help either.
Maybe false alert, seems to be NOT related to 6.40.1.Cable modem only seen as 100 Mbps link now. It's being negotiated as 1 Gbps, stays up for a second, and after some tries falls back to 100 Mbps.
Pretty much same behavior on our CCR-1036 routers.after upgrade i see some Strange behavior
i have hex r3
i use graphing for interfaces
after upgrade to 6.40.1 when you go to graphing via http, hex r3 stop responding, you musto go from interface to interface.. 5-6 and then block
winbox is working, but for 3-4 hours he block and only power off help
I have the same problem with the SXT LTE. Moreover also the RSRQ and RSSI graphs on the "Quick Set" page show wrong values, something around 65000.The modem-signal LED display has broken from 6.39.2 > 6.40(.1) with the RB912 (BaseBox 5) + Sierra Wireless MC8705. Once downgraded back to 6.39.2 the LEDs light up again where as on 6.40 and 6.40.1 they do not light up.
Thanks for the update ... I was too reluctant to go for 6.40.1 after your post ... now I may reconsiderMaybe false alert, seems to be NOT related to 6.40.1.
I had a chance to test with a friend's hEX. Worked reliably with 6.40, likewise with 6.40.1, both RouterBOOT 3.35.
I more and more think it's hardware-related.Thanks for the update ... I was too reluctant to go for 6.40.1 after your post ... now I may reconsiderMaybe false alert, seems to be NOT related to 6.40.1.
I had a chance to test with a friend's hEX. Worked reliably with 6.40, likewise with 6.40.1, both RouterBOOT 3.35.
Anyways seems to me that Mikrotik should document changes to RouterBOOT firmware ...
Putting off power from the device for an hour seems to have helped, having a sync with 1 Gbps again now.I more and more think it's hardware-related.
I just put a switch in between the heX and the cable modem, and voilà, full sync with 1 Gbps
Support ticket has been created, just attached a supout file as well.If you experience ethernet interface link speed issues with this RouterOS version, then please reboot router, reproduce the problem and generate supout file. Send this file to support@mikrotik.com and also give description of the problem - involved devices, cable description and what do you do in order to reproduce the same problem.
Yes, I have exactly the same issue. What can I provide to help this issue to be resolved?Anyone have problem with ethernet link down and up? i see that after i upgrade 6.40 from 6.39.
I tried adding :local mikrotikexport "$sub1 mt_export_backup" but handling error still occurs!6.40.1: error handling file while sending mikrotik backup file via GMAIL smtp.
Fixed it by
:local backupfile "$sub1 mt_config_backup.backup"
/interface bridge filter
add chain=input mac-protocol=pppoe-discovery
add chain=forward mac-protocol=pppoe-discovery
add chain=forward mac-protocol=pppoe
add chain=input mac-protocol=pppoe
add action=drop chain=forward in-interface=wlan1
add action=drop chain=forward out-interface=wlan1
add action=drop chain=input in-interface=wlan1
add action=drop chain=output out-interface=wlan1
If an interface is part of a bridge, then the IP address and the DHCP server need to be on the bridge itself, not on any of the interfaces that are a member of that bridge.Has anyone tried running DHCP server on wlan1 interface? mine goes red after running dhcp server
wlan1 interface is on ap bridge and has an ip of 192.168.3.1
I used the wizard to run DHCP server on the wlan1 interface