General bug, I see it in every platforms that we have.IP----> Web Proxy---------> General-------> Port show :0from ROS 6.34, x86, (not solve this problem)
I wonder if you are using Apple devices and have not dealt much with WPA setups??After update to this version, and some changing of wifi channels for testing, my mobile phone and tablet cannot connect automatically to wireless.
Hardware rb2011uias-2hnd-in.
Ros problem or something else?
No issues here. Also tested on SXT G-5HnD.RB2011UiAS-2HnD is reporting Voltage as 0.0 V and no temperature too.
No issues here, I verify on RB2011UiAS-2HnD, RB2011UiAS, RB3011UiASRB2011UiAS-2HnD is reporting Voltage as 0.0 V and no temperature too.
there is no such thing as simple L7 rule, all is same complexity for computing. Only question is how much traffic get to this rule - your task is to make it as few packets as possible. and WHY use L7 for website block - it is like killing flies with shotgun (overkill), yes, it works, but why use it? you need to use Static DNS entries or web proxy.I have upgraded a router CCR, and today the CPU went 98 - 100% and when looking at profile it was caused by L7 rule. its a very simple rule to block website. Anybody else with same issue ?
thanks.
Do you have a non 'i' (POE out) RB2011 to check?No issues here, I verify on RB2011UiAS-2HnD, RB2011UiAS, RB3011UiASRB2011UiAS-2HnD is reporting Voltage as 0.0 V and no temperature too.
Everything. CLI, Winbox, SNMP.Is this problem with voltage actual only though Winbox or also in CLI?
What does this command show?
"/system health print"
> /system health print voltage: 285.6V
Yes.Backup incomplete ?
RoS 6.34.1, Winbox 3.1:
I backed up a map2n and restored the backup on a 2nd map2n.
After restore,
all Wireless - Settings ( except the SSID ) were gone,
even the wlan - Interface was disabled !
这真的是正常的吗?
Thanks
Manfred
Just readHello
On 6.34.1:
[admin@e] /ip service> print
Flags: X - disabled, I - invalid
# NAME PORT ADDRESS CERTIFICATE
0 telnet 23
1 XI ftp 21
2 XI www 80
3 ssh 22
4 XI www-ssl 443 none
5 XI api 8728
6 winbox 8291
7 XI api-ssl 8729 none
So there is a I like Invalid after the X. What does invalid mean?
It happened to me too, at a first glance I thought it was damaged (one of the first CCR1036 I bought when they have been released). But disconnecting the ethernet cables make the router boot again normally.Upgraded one CCR1036-8G-2S+ from 6.32.3 to 6.34.1 no problem. Upgraded the next CCR1036-8G-2S+ from 6.32.3 to 6.34.1, and the router is constantly rebooting not coming up.
Well I can't "disconnect" the Ethernet cables, but I did shut the ports on the remote switch (Cisco 6500), and it's still not coming up. If I have to shut the SFP ports too, then I'll have to involve my service provider I suppose.It happened to me too, at a first glance I thought it was damaged (one of the first CCR1036 I bought when they have been released). But disconnecting the ethernet cables make the router boot again normally.Upgraded one CCR1036-8G-2S+ from 6.32.3 to 6.34.1 no problem. Upgraded the next CCR1036-8G-2S+ from 6.32.3 to 6.34.1, and the router is constantly rebooting not coming up.
我不知道三ggers it, I upgraded about 40 CCR and it happened only to that one. I also net-installed it with 6.34.1 and the result is the same. I didn't have the time to try previous releases, I just replaced it.
old variables show the same behaviour. you have to use quotes with them:e.g. :log warning "Hotspot login of User: $user with MAC: $mac-address" results in a log entry "Hotspot login of User: Test with MAC: -address"
The new variables with the dash "-" seem not to work... Can someone confirm this?
:log warning "Hotspot login of User: $user with MAC: $"mac-address""
Ethernet ports down, SFP+ ports down, router still screwed....Well I can't "disconnect" the Ethernet cables, but I did shut the ports on the remote switch (Cisco 6500), and it's still not coming up. If I have to shut the SFP ports too, then I'll have to involve my service provider I suppose.It happened to me too, at a first glance I thought it was damaged (one of the first CCR1036 I bought when they have been released). But disconnecting the ethernet cables make the router boot again normally.Upgraded one CCR1036-8G-2S+ from 6.32.3 to 6.34.1 no problem. Upgraded the next CCR1036-8G-2S+ from 6.32.3 to 6.34.1, and the router is constantly rebooting not coming up.
我不知道三ggers it, I upgraded about 40 CCR and it happened only to that one. I also net-installed it with 6.34.1 and the result is the same. I didn't have the time to try previous releases, I just replaced it.
problem in arp entry ip and mac on cero 00:00:00:00:00:00 i put the bug fix and is the same and teh version v6.35rc and is the same
What's new in 6.33.5 (2015-Dec-28 09:13):
*) arp - show incomplete ARP entries;
++For all people who blames MT for failing updates....test this update first on your testing gear, not on the production. Common sense, but still...
Ethernet ports down, SFP+ ports down, router still screwed....It happened to me too, at a first glance I thought it was damaged (one of the first CCR1036 I bought when they have been released). But disconnecting the ethernet cables make the router boot again normally.Upgraded one CCR1036-8G-2S+ from 6.32.3 to 6.34.1 no problem. Upgraded the next CCR1036-8G-2S+ from 6.32.3 to 6.34.1, and the router is constantly rebooting not coming up.
我不知道三ggers it, I upgraded about 40 CCR and it happened only to that one. I also net-installed it with 6.34.1 and the result is the same. I didn't have the time to try previous releases, I just replaced it
Well I can't "disconnect" the Ethernet cables, but I did shut the ports on the remote switch (Cisco 6500), and it's still not coming up. If I have to shut the SFP ports too, then I'll have to involve my service provider I suppose.
Thanks Mikrotik, appreciate it!
/ip firewall filter add chain=input comment="Allow limited pings" limit=50/5s,2 protocol=icmp
/ip firewall filter add chain=input comment="Allow limited pings" limit=50/5s,2:packet protocol=icmp
/system clock set time-zone-name=US/Pacific-New
Maybe cosmetic but I have just wasted an hour on it migrating a router and wondering why my scripts dont work.It appeared in v6.34 and is already fixed in v6.35rc. It is just a cosmetic bug that aes-256 is displayed as aes-128
Same here the other dayMaybe cosmetic but I have just wasted an hour on it migrating a router and wondering why my scripts dont work.It appeared in v6.34 and is already fixed in v6.35rc. It is just a cosmetic bug that aes-256 is displayed as aes-128
I have reply from MT: "The problem will be resolved in next RouterOS verions, starting from 6.35rc11"I've noticed an issue running 6.34.1 and Winbox 3.1. If I set the email server in Winbox > Tools > Email > Server to either the fqdn or ip of my mail server then try send an email I get an error connecting entry in the logs.
"/tool e-mail print" didn't show a server address entry. "/tool e-mail set" had an address setting option which I set to my mail servers fqdn. This updated the Winbox email server setting and I was able to send emails.
So setting "/tool e-mail set address=fqdn/ip will set Winbox > Tools > Email > Server but not vice versa.
Good to know - we reported it as affecting RoS 6.33.5 onwards......I have reply from MT: "The problem will be resolved in next RouterOS verions, starting from 6.35rc11"I've noticed an issue running 6.34.1 and Winbox 3.1. If I set the email server in Winbox > Tools > Email > Server to either the fqdn or ip of my mail server then try send an email I get an error connecting entry in the logs.
"/tool e-mail print" didn't show a server address entry. "/tool e-mail set" had an address setting option which I set to my mail servers fqdn. This updated the Winbox email server setting and I was able to send emails.
So setting "/tool e-mail set address=fqdn/ip will set Winbox > Tools > Email > Server but not vice versa.