I have same problem on CCR1036.Vlans over bonding interface are broken (no Rx packets) after upgrade from 6.7 to 6.10. Downgrading the RB951G-2HnD back to 6.7 resolved the issue. Please fix.
After your decision, I see the data just a second, then again is lost. I think this is a problem of Firefox in Ubuntu Linux, in windows 7 & IE all work good. =\
/interface pppoe-server server
add default-profile=default-encryption disabled=no interface=ether1 mrru=1600 service-name=service1
/ppp secret
add local-address=10.0.0.1 name=test password=test profile=default-encryption remote-address=10.0.0.2
/system identity
set name="Test Gateway"
/interface pppoe-client
add add-default-route=yes allow=pap,chap,mschap1,mschap2 default-route-distance=1 dial-on-demand=no disabled=no interface=ether2 keepalive-timeout=60 max-mru=1480 max-mtu=1480 mrru=1600 name=pppoe-out1 password=test profile=default-encryption use-peer-dns=no user=test
/system identity
set name="Test CPE"
Route table is correct and is not the main table.
Anyhow it indicates a problem.
It is absurd to the implementation of the IPSEC tunnel mode
Why in this case served the ends of the tunnel on the left and right quickly and so the package is not addressed properly.
By the way, I do not know if I understand the diagram, but for me, the diagram shows that it should be able to ping the IP of the router, eg the inside of the IPSEC police as the input and determine the policy is directed to forward?
I beg for the correct diagram for the implementation of IPSEC
I am able to send a bottle of vodka a person who confirms the correctness of the current diagram:
http://wiki.mikrotik.com/images/thumb/3 ... ple_5c.png
Maybe vodke help him understand that the diagram is not correct.
I've finally managed to flash 6.10 via netinstall. It seems like it does not work right away after booting. It started to work after I plugged out the ethernet cable and put it back. About a minute or so also passed. So, if it does not work with you - wait a minute and try to re-plug the cable.I can't install any other routeros version via Netinstall: I see a router, choose package, press install and nothing happens.
where exactly ?It looks like 6.11 beta so far doesn't fix any of these issues ... at least according to the changelog
What's new in 6.11rc1 (2014-Feb-24 10:54):
*) dhcp - added support for DHCP option 138 - list of CAPWAP IPv4 servers;
*) quickset - added Guest Network setup to Home AP mode;
*) console - no longer required to supply value of '/routing bgp instance vrf'
property 'instance' for 'add' command;
By the way, this was copied from a publically available mikrotik.com page, not the beta website.
Mikrotik a lot of people including me have been reporting issues like the above recently. Are Mikrotik working actively working to resolve these issues?MT #1 and #2 - 951G-2HnD 6.10 + 3.12
Link speed/Duplex problems at least with 3 devices.
- Fiber media converter STELS (maybe IC+ 1xx) 100Mbps connected with 1m A-A (direct) cable to MT #1 ether2-master-local with default config.
- HP NC360T PCIe DP Gigabit Server Adapter (Intel) connected with 15m A-B (cross) cable to MT #2 ether2-master-local with default config.
- Realtek 8168 integrated PCIe GBE controller connected with 5m cable to MT #2 ether4-slave-local with default config.
MT #2 (Auto + FD) -> Intel (10 + H) - OK
MT #2 (Auto + FD) -> Intel (10 + FD) - MT status 10H with warning excessive or late collision, link duplex mismatch ?
MT #2 (Auto + H/FD) or (100 + H/FD) -> Intel (100 + H/FD) - MT status 100H, Intel connection status - Not available
MT #2 (Auto + FD) -> D-Link DES-1008 (Gigabit router) -> Intel (100 + H/FD) - OK
MT #2 (Auto + H/FD) -> RTL8168 (Auto) - OK
MT #2 (1000 + H/FD) -> RTL8168 (Auto) - MT status 1000FD, RTL connection status - Not available
MT #1 (Auto + FD) -> STELS (Auto) - FDX led on STELS is ON
MT #1 (100 + FD) -> STELS (Auto) - FDX led on STELS is OFF
And sometimes warnings "excessive or late collision, link duplex mismatch ?" with EN28J60 10Mbps H device.
to normis:
Now the error occurred in the hotspot. Account in hotspot not authorize because address list were dynamic entry with the IP addresses. Not removed! Why?
It happened so that accounts can not be logged because remained dynamic IP addresses in the address list.
I had to manually delete the dynamic (d) address.
In this case results mostly are as they should be.MT #1 and #2 - 951G-2HnD 6.10 + 3.12
Link speed/Duplex problems at least with 3 devices.
- Fiber media converter STELS (maybe IC+ 1xx) 100Mbps connected with 1m A-A (direct) cable to MT #1 ether2-master-local with default config.
- HP NC360T PCIe DP Gigabit Server Adapter (Intel) connected with 15m A-B (cross) cable to MT #2 ether2-master-local with default config.
- Realtek 8168 integrated PCIe GBE controller connected with 5m cable to MT #2 ether4-slave-local with default config.
MT #2 (Auto + FD) -> Intel (10 + H) - OK
MT #2 (Auto + FD) -> Intel (10 + FD) - MT status 10H with warning excessive or late collision, link duplex mismatch ?
MT #2 (Auto + H/FD) or (100 + H/FD) -> Intel (100 + H/FD) - MT status 100H, Intel connection status - Not available
MT #2 (Auto + FD) -> D-Link DES-1008 (Gigabit router) -> Intel (100 + H/FD) - OK
MT #2 (Auto + H/FD) -> RTL8168 (Auto) - OK
MT #2 (1000 + H/FD) -> RTL8168 (Auto) - MT status 1000FD, RTL connection status - Not available
MT #1 (Auto + FD) -> STELS (Auto) - FDX led on STELS is ON, SPD - ON (100Mbps Full Duplex)
MT #1 (100 + FD) -> STELS (Auto) - FDX led on STELS is OFF, SPD - ON (100Mbps Half)
And sometimes warnings "excessive or late collision, link duplex mismatch ?" with EN28J60 10Mbps H device.
Works fine for me on v6.10 RB2011UAS-2HnDfirewall filter dont check address lists, all rules drop connections with this features.
What's New in 6.11 rc1? No description available.
The problem is in encryption.any confirmations that 6.10 fixed all the sstp client issues with win 7 clients, that got broke in 6.8 and 6.9, how about pptp and winbox disconnects?
looking for confirmation. i dropped a production network big time on 6.8, going to cool off for a while
This is the configuration that we, and others seem to be having issues with.In this case results mostly are as they should be.MT #1 and #2 - 951G-2HnD 6.10 + 3.12
Link speed/Duplex problems at least with 3 devices.
- Fiber media converter STELS (maybe IC+ 1xx) 100Mbps connected with 1m A-A (direct) cable to MT #1 ether2-master-local with default config.
- HP NC360T PCIe DP Gigabit Server Adapter (Intel) connected with 15m A-B (cross) cable to MT #2 ether2-master-local with default config.
- Realtek 8168 integrated PCIe GBE controller connected with 5m cable to MT #2 ether4-slave-local with default config.
MT #2 (Auto + FD) -> Intel (10 + H) - OK
MT #2 (Auto + FD) -> Intel (10 + FD) - MT status 10H with warning excessive or late collision, link duplex mismatch ?
MT #2 (Auto + H/FD) or (100 + H/FD) -> Intel (100 + H/FD) - MT status 100H, Intel connection status - Not available
MT #2 (Auto + FD) -> D-Link DES-1008 (Gigabit router) -> Intel (100 + H/FD) - OK
MT #2 (Auto + H/FD) -> RTL8168 (Auto) - OK
MT #2 (1000 + H/FD) -> RTL8168 (Auto) - MT status 1000FD, RTL connection status - Not available
MT #1 (Auto + FD) -> STELS (Auto) - FDX led on STELS is ON, SPD - ON (100Mbps Full Duplex)
MT #1 (100 + FD) -> STELS (Auto) - FDX led on STELS is OFF, SPD - ON (100Mbps Half)
And sometimes warnings "excessive or late collision, link duplex mismatch ?" with EN28J60 10Mbps H device.
Autonegotiation on the one end and forced speed on the other end makes duplex mismatch.
And autonegotiation is obligatory for 1000BASE-T gigabit Ethernet over twisted pair.
More info: en.wikipedia.org/wiki/Autonegotiation
Only this setup may be in question:
MT #2 (Auto + H/FD) or (100 + H/FD) -> Intel (100 + H/FD) - MT status 100H, Intel connection status - Not available
Yup, SSTP is still confirmed broken in certain scenarios by several people. It should work from mikrotik 6.10 to mikrotik 6.10, but other than that, it could be unstable or not connect at all.The problem is in encryption.any confirmations that 6.10 fixed all the sstp client issues with win 7 clients, that got broke in 6.8 and 6.9, how about pptp and winbox disconnects?
looking for confirmation. i dropped a production network big time on 6.8, going to cool off for a while
Read my very very detailed and repeatable (with any hardware) post on page 3....
http://forum.mikrotik.com/viewtopic.php ... 64#p411334
Try to use SSTP without encryption on both end.
Just a try...
Try another NTP server, like one from "pool.ntp.org". We had some people in support with similar issues, and they all said that changing the server has fixed the issue.- NTP (from NTP package) client struggles at best, and refuses to synchronize in other cases, to our Windows 7 NTP server after reboots
Route table is correct and is not the main table.
Anyhow it indicates a problem.
It is absurd to the implementation of the IPSEC tunnel mode
Why in this case served the ends of the tunnel on the left and right quickly and so the package is not addressed properly.
By the way, I do not know if I understand the diagram, but for me, the diagram shows that it should be able to ping the IP of the router, eg the inside of the IPSEC police as the input and determine the policy is directed to forward?
I beg for the correct diagram for the implementation of IPSEC
I am able to send a bottle of vodka a person who confirms the correctness of the current diagram:
http://wiki.mikrotik.com/images/thumb/3 ... ple_5c.png
Maybe vodke help him understand that the diagram is not correct.
Please look at diagram again
in interface -> prerouting chain -> routing decision (here you need the route to actually forward)-> forward chain -> post routing -> ipsec policy -> ipsec encryption -> local-in process -> routing decision again (now for encrypted packet) -> output chain -> out interface.
Wrong. In case you have correct configuration, the actual flow should look like this:and according to the diagram instructed to do so:
Input interface -> In Interface Bridge ->Prerouting -> Routing Decision -> Input -> Ipsec Policy -> IPSec Dectyption -> Forward
f**k and hear he go to forward but the ip is in local IP shud be placed to routing Routing Decision
so the flow shuld be directed to local proces IN
Is it on x86 machine? Please send supout.rif to MikroTik support.There is a bug with dhcp-server on vlan. After update from 5.25 to 6.10 some devolo dlan pro modems cant get their IPs. Had to downgrade.
No. It's a RB411 in production. Cant play/debug at this site.Is it on x86 machine? Please send supout.rif to MikroTik support.There is a bug with dhcp-server on vlan. After update from 5.25 to 6.10 some devolo dlan pro modems cant get their IPs. Had to downgrade.
which forum is that? more info please. email supportA whole forum with thousands of users with Mikrotik routers (different models) are having an issue with the 6.10 version with the IP TV from Movistar Spain (ADSLZone).
Image freezes and sometimes it isn't received.
Back to 6.9 and it perfectly works.
In the decryption is bad scheme.Wrong. In case you have correct configuration, the actual flow should look like this:and according to the diagram instructed to do so:
Input interface -> In Interface Bridge ->Prerouting -> Routing Decision -> Input -> Ipsec Policy -> IPSec Dectyption -> Forward
f**k and hear he go to forward but the ip is in local IP shud be placed to routing Routing Decision
so the flow shuld be directed to local proces IN
Input Interface -> Prerouting -> Routing Decision -> Forward -> Postrouting -> IPsec Policy -> IPsec Encryption -> Routing Decision -> Output -> IPsec Policy -> Output Interface.
They seem to have mixed up "IPsec Encryption" and "IPsec Decryption" on the Routing diagram on this page in the wiki. So, the diagram in its current state sucks indeed.
This is really a BIG problem for us also.. we use the NASPORT value to make a lot of tests using snmp.[Ticket#2014022566000158]
new pppoe BUG introduced with the new pppoe package.
The NASPORT value reported in radius by MT is completely wrong.
In regular package it is the snmp index of the pppoe-client interface
Now it is completely not useful.
We need it to be reported correctly.
regards
Ros
I do not understand what you are talking about. In your initial post above you were talking about transit (i.e. FORWARD) packet not being forwarded to your IPsec tunnel. Encryption is NOT implemented in Routing Decision block. It's just that the Routing Decision takes place BEFORE IPsec Policy block. If you do not have a corresponding route in your routing table your packet will be dropped in Routing Decision before it even reaches IPsec policy block. It could be fake route or whatever. That's how it works in RouterOS (as well as in Linux, FreeBSD and possibly other places as well). Just take it for granted. The fact that Cisco works differently does NOT mean RouterOS is doing something wrong.In the decryption is bad scheme.
Well unless you are on a forward input filtering.
Take a look that speaks of packets addressed to the device and not forward to the network.
The device has its own IP address and the traffic going to the device is INPUT and not FORWARD
As for the fact that encryption is implemented in the routing decision for tunnel mode does not utter.
This is the forum and the thread:which forum is that? more info please. email supportA whole forum with thousands of users with Mikrotik routers (different models) are having an issue with the 6.10 version with the IP TV from Movistar Spain (ADSLZone).
Image freezes and sometimes it isn't received.
Back to 6.9 and it perfectly works.
Me neither.I do not understand what you are talking about.In the decryption is bad scheme.
Well unless you are on a forward input filtering.
Take a look that speaks of packets addressed to the device and not forward to the network.
The device has its own IP address and the traffic going to the device is INPUT and not FORWARD
As for the fact that encryption is implemented in the routing decision for tunnel mode does not utter.
I have described the pppoe encryption bug exactly here:Please send us supout.rif file from problematic v6.10 installation and steps to repeat the issue. Let's get all these issues fixed. Thank you for all the help.
Fri Feb 28 15:09:40 2014 TCP connection established with x.x.x.x:1194
Fri Feb 28 15:09:40 2014 TCPv4_CLIENT link local: [undef]
Fri Feb 28 15:09:40 2014 TCPv4_CLIENT link remote: x.x.x.x:1194
Fri Feb 28 15:10:40 2014 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Fri Feb 28 15:10:40 2014 TLS Error: TLS handshake failed
Fri Feb 28 15:10:40 2014 Fatal TLS error (check_tls_errors_co), restarting
Fri Feb 28 15:10:40 2014 TCP/UDP: Closing socket
Fri Feb 28 15:10:40 2014 SIGUSR1[soft,tls-error] received, process restarting
please tell me your ticket number, I will check status of this issue. Did you also send supout.rif to support?I have described the pppoe encryption bug exactly here:Please send us supout.rif file from problematic v6.10 installation and steps to repeat the issue. Let's get all these issues fixed. Thank you for all the help.
http://forum.mikrotik.com/viewtopic.php ... 00#p411334
But not are in your list.
Please read that post.
Is all EXTREMELY detailed how to reproduce the tremendous bug.
Thanks
please tell me your ticket number, I will check status of this issue. Did you also send supout.rif to support?I have described the pppoe encryption bug exactly here:Please send us supout.rif file from problematic v6.10 installation and steps to repeat the issue. Let's get all these issues fixed. Thank you for all the help.
http://forum.mikrotik.com/viewtopic.php ... 00#p411334
But not are in your list.
Please read that post.
Is all EXTREMELY detailed how to reproduce the tremendous bug.
Thanks
This is the correct way to submit problems, you did everything correctly! When you send an email to support, you receive an auto response, with ticket number in subject. what is your ticket number?I have sended EMAIL at support@mikrotik.com 2014/02/14 16:24 (CET)
I re-submit the email and this is the ticket:This is the correct way to submit problems, you did everything correctly! When you send an email to support, you receive an auto response, with ticket number in subject. what is your ticket number?I have sended EMAIL at support@mikrotik.com 2014/02/14 16:24 (CET)
We have tested and progressively went back through prior ROS versions until we found one where certificate management worked. You have to go back to 6.3. I think someone else mentioned this.
Any release after 6.3 certificate authority certs and keys cannot be properly imported, particularly from self signing in OpenSSL.
Funny thing is that if you install certs in 6.3 and then upgrade the certs remain functional.
I would guess that most of this issues with SSTP, OVPN, SSL etc are related to this issue. We did not notice until now because we were not installing new certificates, just upgrading systems with already installed certificates.
The certificates work, CAs don't get imported as CAs.i started with 6.7 on a 2011. self signed. no issues with sstp both in a ptp, and with windows clients
Be more specific what do you mean by "not imported as CA".The certificates work, CAs don't get imported as CAs.i started with 6.7 on a 2011. self signed. no issues with sstp both in a ptp, and with windows clients
This is a SSTP configuration error, not a bug. Please check your config. I see several people with this config mistake. For the PPP profile that you use in SSTP, turn off encryption, this setting is only used for PPTP. If you have enabled encryption in the PPP profile and use it for SSTP, you will get this error."Encryption negotiation rejected”
If I import a self signed certificate, it works.Be more specific what do you mean by "not imported as CA".The certificates work, CAs don't get imported as CAs.i started with 6.7 on a 2011. self signed. no issues with sstp both in a ptp, and with windows clients
Yes I used it on RB750 basic configuration no problem. For now up time is 15 days.May i use ROS 6.10 in RB750 ?
We use a RB750G at the office.Yes I used it on RB750 basic configuration no problem. For now up time is 15 days.May i use ROS 6.10 in RB750 ?
What is auto frequency feature? As I can see on my test router it changes frequency but there isWhat's new in 6.11rc1 (2014-Mar-06 15:05):
*) wireless - add auto frequency feature;
installing the new package automatically improves the wireless forwarding for Nv2 and 802.11.Nice
How to use - Wireless Fast Path for 802.11? It is in changelog for New “Wireless-FP” package
such number of obscene words is clearly against the rules of this forum, I'm sorry but that's how it works: http://forum.mikrotik.com/faq.phpGood to see you delete my posts.
Pretty much confirms it all.
I can't find it in:You can temporary get rid of this TLS error by setting reneg-sec 0 on ovpn server.
Problem will be fixed in next release.
/interface ovpn-server> server print
write to support@mikrotik.com with your MikroTik.com account name - they will give you access to development releasesWhere I can download "officially" beta / release candidate version without use Google?
I would partecipate as tester.
Very thanks!write to support --- mikrotik.com with your MikroTik.com account name - they will give you access to development releasesWhere I can download "officially" beta / release candidate version without use Google?
I would partecipate as tester.
This is a SSTP configuration error, not a bug. Please check your config. I see several people with this config mistake. For the PPP profile that you use in SSTP, turn off encryption, this setting is only used for PPTP. If you have enabled encryption in the PPP profile and use it for SSTP, you will get this error."Encryption negotiation rejected”
On wireshark in the local network.Where you see that? That's normal if ports are in master/slave relationship.
No it doesn't mean that, the SSTP tunnel will be encrypted with it's own algorythm. The ppp setting is only for PPTP, and if you enable it, it will attempt to use this too, which is not made for SSTP and will result in the above error. We will clarify the manual and will re-label this checkbox.This is a SSTP configuration error, not a bug. Please check your config. I see several people with this config mistake. For the PPP profile that you use in SSTP, turn off encryption, this setting is only used for PPTP. If you have enabled encryption in the PPP profile and use it for SSTP, you will get this error."Encryption negotiation rejected”
Could you elaborate more on that, I couldn't find anything about not setting encryption to 'required' for the sstp profile in the wiki.
If you set encryption to no for sstp, does that mean that the tunnel won't be encrypted?
If it's not a bug but a configuration error, then it's a major flaw in the ROS interface and OS to let use this setting for sstp.
sorry but we are currently not working on Dude problems, maybe later in the yearhello
still ip/route table in snmp (dude) problem not solved!
hellosorry but we are currently not working on Dude problems, maybe later in the yearhello
still ip/route table in snmp (dude) problem not solved!
Same problem on x86 . Dhcp servers on Vlans not working correctly. Clients get Ip but after the lease expired cannot renew lease. Router shows "Server offering lease without success" After the reboot everything fine until next renew. Clear installation, no other configuration , no bridges . 3 vlans under the ethernet interface. The same issue on 6.0 and 6.10. On 5.26 everything works fine.There is a bug with dhcp-server on vlan. After update from 5.25 to 6.10 some devolo dlan pro modems cant get their IPs. Had to downgrade.
Same problem on x86 . Dhcp servers on Vlans not working correctly. Clients get Ip but after the lease expired cannot renew lease. Router shows "Server offering lease without success" After the reboot everything fine until next renew. Clear installation, no other configuration , no bridges . 3 vlans under the ethernet interface. The same issue on 6.0 and 6.10. On 5.26 everything works fine.There is a bug with dhcp-server on vlan. After update from 5.25 to 6.10 some devolo dlan pro modems cant get their IPs. Had to downgrade.
/interface ethernet switch port set [find] learn-restricted-unknown-sa=yes
Yay !!michaelcarey,
Enter this command to fix it on CRS125:Code: Select all/interface ethernet switch port set [find] learn-restricted-unknown-sa=yes
You can get more information on bug fixes. Under what conditions does it arise?build (2014-03-12 14:58:04)
*) fixed 100% cpu usage on CCRs;
+1 to that.You can get more information on bug fixes. Under what conditions does it arise?build (2014-03-12 14:58:04)
*) fixed 100% cpu usage on CCRs;
Bug fixing doesn't work like that. We can fix the source of the problem, but it will be very hard to list all situations where this bug was showing itself.You can get more information on bug fixes. Under what conditions does it arise?build (2014-03-12 14:58:04)
*) fixed 100% cpu usage on CCRs;
Please upgrade to newest test release of v6.11 and check agin if you still see the kernel panics. If yes, then send that new support output files to support@mikrotik.comdunno if anyone else is having the same problem but...
upgraded an rb435g to the 6.11rc1 with the fp wireless driver and its getting
"system rebooted because of kernel failure"
"router was rebooted without proper shutdown!!
file attached!!!
now at 11/03/14 was my rb800 that crashed :X
same error as the 435g
i'm using the 10/03/14 13:36 release....
Ответ от 192.168.192.10: число байт=32 время=5мс TTL=62
Ответ от 192.168.192.10: число байт=32 время=4мс TTL=62
Ответ от 192.168.192.10: число байт=32 время=4мс TTL=62
Ответ от 192.168.192.10: число байт=32 время=4мс TTL=62
Ответ от 192.168.192.10: число байт=32 время=5мс TTL=62
Ответ от 192.168.192.10: число байт=32 время=4мс TTL=62
Ответ от 192.168.192.10: число байт=32 время=5мс TTL=62
Ответ от 192.168.192.10: число байт=32 время=244мс TTL=62
Ответ от 192.168.192.10: число байт=32 время=4мс TTL=62
Ответ от 192.168.192.10: число байт=32 время=4мс TTL=62
Ответ от 192.168.192.10: число байт=32 время=4мс TTL=62
Ответ от 192.168.192.10: число байт=32 время=4мс TTL=62
Ответ от 192.168.192.10: число байт=32 время=4мс TTL=62
Ответ от 192.168.192.10: число байт=32 время=241мс TTL=62
Ответ от 192.168.192.10: число байт=32 время=4мс TTL=62
Ответ от 192.168.192.10: число байт=32 время=4мс TTL=62
Ответ от 192.168.192.10: число байт=32 время=242мс TTL=62
It's strange that two RB751U-2HnD devices have been upgraded to 6.10 successfully and work OK for now.unfortunately no, this model does not support it [RS-232]. It may have serial port pads on
pcd, but they won't work without special software on router which we do not share
with public.
...
whole picture looks awflly like problem with nand flash on router, it could have
died of old age so to speek or just hardware failure of this specific chip. In
this case router hardware replacement will be required.
/system routerboard updateDO NOT REBOOT
/system routerboard settings set baud-rate=115200 set boot-delay=2s set boot-device=try-ethernet-once-then-nand set boot-protocol=bootp set cpu-mode=regular set enable-jumper-reset=yes set enter-setup-on=delete-key set force-backup-booter=no set silent-boot=nonow reboot and use netinstall without keeping old configuration
I'm glad to do it, but:if the rb start, open winbox and update BIOS:
Simply I can not see device with WinBox (MAC or IP) at all. Only Netinstall sees it somehow.My RB/750 turns all LEDs ON (despite of real state of Ethernet ports) and no reaction in WinBox, no traffic at all (after normal reboot) -- I've sniffed any packets with WireShark software.
If I reset device to defaults (short circuit contact hole with screwdriver or 1-2 sec RESET while powering on) hardware lights Ethernet LEDs right according to real port connections -- but no any Ethernet packets too.
I am a dumb. Advanced tools package is missing... sorry everyone for disturbing.I have just netinstalled 6.10 on RB2011UAS-2HnD and upgraded FW from 3.10 to 3.12. I was not able to run config script downloaded from v.6.9. so I did it by copy-paste thru terminal.
Reason: The Netwatch is missing in Tools.
How to get Netwatch back? I need it.
rextended, made all your checklist exactly (thanks for trick #4) twice with netinstall6.10+routeros6.10 & netinstall5.26+routeros5.26, but thats' doesn't help to repair my device.Forget the hole with the screwdriver.
1) before power the rb, press reset button and leave pressed, insert power plug, and wait until devices are visible in netinstall (15~20sec) [assuming the pc is working], now release reset button.
2) If you can see correctly the device on netinstall 6.10, try to install the package 6.10.
3) If netinstall fail, repeat the steps 1-2 with netisntall 5.26 AND RouterOS 5.26.
4) When devices show "waiting reboot" on netisntall, fast remove the power,
5) before power the rb, press reset button and still with reset button pressed, insert power plug, and when any led display up, release reset button [load backup bios].
6) Wait if rb start and follow the previous instruction to upgrade the bios.
Yes, I have the same problem long time. Mostly on the bridge interface or on the VRRP interface. After rebooting the IPv6 do not works on the interface.Does anybody here also have the problem that IPv6 addresses sometimes aren't working until disable and re-enable (new added address or after a reboot)? Had that on 4 MikroTiks (RB750GL, RB2011UAS-RM, RB2011UiAS-2HnD-IN, RB951G-2HnD) but unfortunately MikroTik cannot confirm this bug. Very annoying if after a reboot nothing is working.
I'm mostly using IPv6 addresses on bridges.
Edit: Not working means, sometimes I can ping the IPv6 from the local MikroTik cli. But if I try to reach another host in that subnet, traffic goes through the default gateway.
/ipv6 address print where address="fe80::ff:fe00:12/64"
Flags: X - disabled, I - invalid, D - dynamic, G - global, L - link-local
# ADDRESS FROM-POOL INTERFACE ADVERTISE
20 DL fe80::ff:fe00:12/64 (unknown) no
21 DL fe80::ff:fe00:12/64 bridge-wan no
Done. But after reboot (fast power off when "Waiting...", then power on with RESET button pressed till LEDs on, then power off/on reboot) I see no my device RB/750 in WinBox So I can't do next part of firmware/bios upgrade procedure. All LEDs on, no any network activity/visibilityMade one last try with [use SAME version of Netinstall and RouterOS!]
http://download.mikrotikindonesia.com/i ... l-5.11.zip
http://download.mikrotikindonesia.com/i ... e-5.11.npk
Yes, that version!...
I'm very glad if your receipt helps you or somebody else in same trouble... but not me, sorry.I have the same problem, when I forget to upgrade BIOS [firmware] before upgrading some SXT to version 5.26 or 6.x
But after I successfully boot RB with old software [or backup BIOS] I can fix with the method described before.
If you reach to reboot properly the board, first do bios upgrade as I explain on previous post.
Yes, I agree. I see this from ROS6.7 days (at least on the RB800). A profile show that a dhcp task consumes my CPU.Hi, I have a problem using option DHCPv6-PD to send ipv6 prefixes via pppoe, the option send the prefix and create the route, works well and hangs dhcp when pppoe conection drop.
If I disconect normaly them dhcpv6 release the prefix but when hangs suddenly it simply stay conected and dhcpv4 stop too, cant get new prefixes or release the one with pppoe. When that happens one core of my cpu goes 100% and only a reboot normalize it.
probably, it's already fixed in pre-release:v6.10 every hour disconnect openvpn.
What's new in 6.11 (2014-Mar-18 11:14):
*) ovpn - fixed TLS renegotiation;
NTP client works fine after upgrade. Please check if the NTP server IP isn't changed.951 and 751, after upgrade on 6.10 don't work ntp client.
IP of NTP server didn't changed, and after i found problem, i tried change IP to new. In 6.07 work fine.NTP client works fine after upgrade. Please check if the NTP server IP isn't changed.
Another user has the same problems like me.Im having issues with ntp client.
2 rb433 and 2rb951 doesnt sync the clock time with ntp servers.
anyone else having this problem?
This problem with full IPv4 route cache I see for whole ROS6 line. With the ROS 6.10 is only more fastelly cache filled.I believe this issue is somehow v6.10 related .. I did not experience this kind of problems with older versions of routeros.
http://forum.mikrotik.com/viewtopic.php?f=3&t=83030
On few RB912 I had this problem directly after upgrade too. But after second reboot SNTP client opetares OK.951 and 751, after upgrade on 6.10 don't work ntp client.
Tomorrow exit 6.11Just downgrade to 6.07 two of devices, ntp client working fine.
I'm using 6.10 on RB951, no NTP problem...IP of NTP server didn't changed, and after i found problem, i tried change IP to new. In 6.07 work fine.NTP client works fine after upgrade. Please check if the NTP server IP isn't changed.
We have 2 of 751 and 3 of 951, every have problem with NTP Client.