CRS210 still does not route correctly using 6.34rc3. Reverting to 6.33 resolves it. This is using a SFP fiber connection to a CRS112 which is successfully running 6.34rc3.6.34rc3 version will be released today:
Changes since 6.34rc1:
*) smb - fixed SMB share crash when connection was cancelled;
*) lcd - fixed LCD crash on fast disable/enable;
*) fastpath - fixed wireless interface fastpath (broken in 6.33);
*) pppoe - fixed compliance to RFC4638 (MTU larger than 1488);
*) webfig - show correctly SFP Tx/Rx;
*) winbox - renamed power-cycle-ping-interval to power-cycle-ping-timeout;
*) CCR1072 - added support for S-RJ01 SFP modules;
*) trafficgen - fixed issue that traffic-generator could not be started twice without reboot;
*) dhcpv4-client - support /32 address assignment;
*) licensing - fix unneeded connection attempts to 169.254.x.x (must be CHR only);
*) dhcpv6-server - replace delay option with preference option;
*) dhcpv6-client - added address acquisition support;
*) dhcpv6 - implement and enable rapid commit by default.
we are working on DHCPv6-client, so you might experience some problems with the DHCP-PD client as they are in the same place. If that is important feature you are using for day to day configuration wait at least till rc5 release or newer.Upgraded from 6.33 to 6.34rc3 and lost my ipv6 dhcp-client config. (no entry)
Reverted to 6.33, but still had to add back the client entry.
Can't seem to find it..6.34rc5 will be released today.
Changes since 6.34rc3:
*) dns - fix for situation when dynamic dns servers could disappear;
*) packages - show version tag when no bundle is installed;
*) vrrp - fix enabling disabled vrrp interface when vrrp program has exited;
*) winbox - do not send any changes on OK button press if nothing has been changed;
*) sfp - fix 10g ports in 1g mode (introduced in 6.34rc1);
*) dhcpv6-client - added DHCPv6-client functionality for current DHCP-PD client;
"Today" have another sense from today6.34rc5 will be released today.
...
We can't add drivers. RouterOS drivers come from the used Linux Kernel. We only change kernel in big releases, next change will come in RouterOS v7Hi Guys
Can we please get driver support for the the following Broadcom 4 ports SFP+ card. It uses the Broadcom BCM57840S controller. I have 1 of these cards based on the http://wiki.mikrotik.com/wiki/Supported ... t_chipsets page I thought it would be supported.
http://www.supermicro.com/products/acce ... tg-b4s.cfm
Support promised to me ros7 (public alpha) in this year. month and a half left. With interest expect.Hi Normis
This does not really help as we have been hearing about ROSv7 for a long time but not even seen a alpha or beta version, so this could be another 2 years before we see any ROSv7, and in the meantime all new network interfaces is unusable because of old kernel being used. Broadcom have back ported their drivers to even kernel 2.6.x so I cant see how this can not be injected into the v3 kernel used by ROSv6.
Can you please explain? I'm sure we have other users with similar issues.
Version 6.34rc6 has been released.
Changes since previous rc version:
*) pppoe - fixed compliance to RFC4638 (MTU larger than 1488) again;
Anyone else seeing this?ipv6 dhcp-c add interface=ether8 add-default-route=yes request=prefix pool-name=IPv6
[admin@MikroTik] /ipv6 address> printCan't seem to get IPv6 DHCPv6 to work right. Keeps asking me for an "IA". The only way to get it to work is from the command line using the following string:Anyone else seeing this?ipv6 dhcp-c add interface=ether8 add-default-route=yes request=prefix pool-name=IPv6
-tp
http://wiki.mikrotik.com/wiki/Manual:In ... _referenceDear Strods,
Is there any possibilty that you will be more elaborate on what particulary fix fixed ?
What " fixed on-backup script;" fixed ? Any example ? Description ? Link to forum discussion on that error ? Anything ?
Question should be - is it working for you? If yes, do not worry, keep using it. If you notice some problem then it is good time to upgrade. Time of global bugs in RouterOS is almost over, most of bugs now are very specific to particular configuration and particular installation. This forum is getting boring, and that is already saying something - that everything mostly worksI know that VRRP could execute scripts.
I am asking what was buggy ? Should I be worry if I use it ? Maybe I am "fighting" similar problem which is the ROS error but not mine ?
"Apparently it was buggy" is not the expected answer.
Version 6.34rc9 has been released.
Changes since previous version:
*) ppp - fixed dynamic filter rule adding on some firewall filter configurations;
*) vrrp - fixed on-backup script;
*) ethernet - fixed link resetting on power-cycle-ping value change;
*) pppoe - improved MTU discovery compatibility with other vendors;
*) hotspot - fixed login by mac-cookie when roaming among hotspot servers.
Hi strods. Can you clarify, please, which SIP features/headers are now additionally supported?*) firewall - SIP helper update for newer Cisco phones.
This problem still exists with v6.34rc14.Still having the same IPv6 DHCP issue with ROS 6.34rc9, when requesting a prefix:
Almost same thing with "Stable" version"RB2011UiAS-2HnD upgrade from 6.34rc12 to 6.34rc16 resulted in endless reboot.
RB951G-2HnD upgrade from 6.34rc12 to 6.34rc16 worked correctly
?
6.34rc3 added the ability to request a IPv6 address via the DHCPv6-client.This problem still exists with v6.34rc14.Still having the same IPv6 DHCP issue with ROS 6.34rc9, when requesting a prefix:
Works fine with v6.33.2
-tp
Current situation seems to be able to support only at the command.I install 6.34rc and Ipv6 per pppoe as dhcpv6 client has broken.
I update to 6.34rc18 but status DHCPv6 Client is stoped.
How run IPv6 ?
[admin@Mikrotik] /ipv6 dhcp-client> add interface=ether5 request=prefix add-default-route=no pool-name=ipoe pool-prefix-length=56 use-peer-dns=no
IPv6 dont workVersion 6.34rc19 has been released.
Changes since previous version:
*) CHR - implemented trial support for different CHR speed tiers;
*) dhcpv6-client - fix add route/address;
at 6.34rc19 dont workCurrent situation seems to be able to support only at the command.Code: Select all[admin@Mikrotik] /ipv6 dhcp-client> add interface=ether5 request=prefix add-default-route=no pool-name=ipoe pool-prefix-length=56 use-peer-dns=no
What are profile-defined routes? Where exactly have you managed to define them?Profile-defined Routes in PPTP/L2TP/OVPN connections aren't being sent to the correct tunnels
Could you please provide the CLI command to login user manually? I couldnt find it anywhere on the latest RC firmware6.34rc8 version has been released
Changes since 6.34rc6:
*) usermanager - fixed usermanager webpage crash;
*) ipsec - fixed active SAs flushing;
*) bridge - fixed power-cycle-ping for bridge ports (was affecting all bridge);
*) ethernet - fixed link resetting on power-cycle-ping value change;
*) pppoe - made MTU discovery more robust;
*) hotspot - added option to login user manually from cli.
I push it out via RADIUS, but there's a field under PPP Secrets for you to define what to route to the far end of a tunnel once it is established.What are profile-defined routes? Where exactly have you managed to define them?Profile-defined Routes in PPTP/L2TP/OVPN connections aren't being sent to the correct tunnels
Hello.
After upgrade to 6.34rc20 I can't login on my router, x86 based - Winbox (both versions): login timeout, telnet/ssh: connection closed (after about one minute waiting). Without this behaviour, other jobs are OK. Router is far away from me.
Any help?
Regards,
RafGan
Same here, except routeros also reboots randomly.Hello.
After upgrade to 6.34rc20 I can't login on my router, x86 based - Winbox (both versions): login timeout, telnet/ssh: connection closed (after about one minute waiting). Without this behaviour, other jobs are OK. Router is far away from me.
Any help?
Regards,
RafGan
I am having the same issues on x86. Can't login at the console as well. Dude updated and the Windows client updated and can login to dude.
Hello.
After upgrade to 6.34rc20 I can't login on my router, x86 based - Winbox (both versions): login timeout, telnet/ssh: connection closed (after about one minute waiting). Without this behaviour, other jobs are OK. Router is far away from me.
Any help?
Regards,
RafGan
I wonder still again and again why so much people install rc or whatever new versions of ros on productive and or distant devices. These versions are for testing purposes only. Everyone should carefully select what wersion he will deploy and make his own tests on lab devices to be at least somehow confident that it is not harmful.
If you cannot access remote device you have to go there and check what happened. Most probably none on the forum can help you with this. For critical devices it is smart to have another rb nearby connected by serial cable to each other so you can try to see serial console remotely. Remote resetator could be helpful too.
Hello.
After upgrade to 6.34rc20 I can't login on my router, x86 based - Winbox (both versions): login timeout, telnet/ssh: connection closed (after about one minute waiting). Without this behaviour, other jobs are OK. Router is far away from me.
Any help?
Regards,
RafGan
I am having the same issues on x86. Can't login at the console as well. Dude updated and the Windows client updated and can login to dude.
The only way to get access again, that i found, is netinstalling RouterOS on that x86 with problem, check "keep old configuration" checkbox, and select the packages (6.33.3) everything works fine.Hello.
After upgrade to 6.34rc20 I can't login on my router, x86 based - Winbox (both versions): login timeout, telnet/ssh: connection closed (after about one minute waiting). Without this behaviour, other jobs are OK. Router is far away from me.
Any help?
Regards,
RafGan
I am having the same issues on x86. Can't login at the console as well. Dude updated and the Windows client updated and can login to dude.
Same situation here, on x86. Can't login ssh, winbox, telnet, mactelnet, web. None work.
It looks like only TILE is missing the Client. You can download it from x86 section, it is the same for all architectures.Hi,
Thanks for bringing the Dude development back to life
I cant find the dude client download though??
Check "Tools -> Profile" to see what specifically is causing it.After upgrading to rc21, I see a constantly higher cpu load on all my devices than before. My devices are not very busy, so the increase is not causing any problems. CPU in the graph has gone from about 1-2% to 4-5%. I am just wondering whether is it normal.
I cannot be sure, because I do not have knowledge of the respective percentages before the upgrade. Also it is not easy to derive any conclusions from instantaneous readings. It would be useful to have some historical data in profiling (like accumulative cpu time of each process etc). Also, what is this "unclassified" category? It seems to have a higher cpu share in older devices (such as an Omnitik).Check "Tools -> Profile" to see what specifically is causing it.After upgrading to rc21, I see a constantly higher cpu load on all my devices than before. My devices are not very busy, so the increase is not causing any problems. CPU in the graph has gone from about 1-2% to 4-5%. I am just wondering whether is it normal.
Normally Unclassified should be 0. If you have something there above a few percent, you should make a supout.rif file and email support.I cannot be sure, because I do not have knowledge of the respective percentages before the upgrade. Also it is not easy to derive any conclusions from instantaneous readings. It would be useful to have some historical data in profiling (like accumulative cpu time of each process etc). Also, what is this "unclassified" category? It seems to have a higher cpu share in older devices (such as an Omnitik).Check "Tools -> Profile" to see what specifically is causing it.After upgrading to rc21, I see a constantly higher cpu load on all my devices than before. My devices are not very busy, so the increase is not causing any problems. CPU in the graph has gone from about 1-2% to 4-5%. I am just wondering whether is it normal.
thats would be perhaps some Tile arch improvements, leading to *mindblowing* performance boost and scalability, lol*) kernel - general improvement for core process scheduling
Elaborate please? Effects?
I really like your optimism!but R7 MIPS was still 1 year away ~ or so, yet .
So how to upgrade if all connections will be lost without upgrading all devices at once ?*) ipsec - fix phase2 hmac-sha-256-128 truncation len from 96 to 128
This will break compatibility with all previous versions and any other currently compatible software using sha256 hmac for phase2;
Want to know more details about this.*) ipsec - fix phase2 hmac-sha-256-128 truncation len from 96 to 128
This will break compatibility with all previous versions and any other
currently compatible software using sha256 hmac for phase2;
I try to update on RB951G-2HnD test echipament from 6.34rc20 but with no success.
I find "System rebooted because of kernel failure" message on log.
New packages: routeros-mipsbe-6.34rc22.npk and ntp-6.34rc22-mipsbe.npk is on router file system.
judging from recent shift to 6.05 and from r7 timeline - its more likely to be within 10 months. so "one year" was reasonable/safe approximation, i think.I really like your optimism!but R7 MIPS was still 1 year away ~ or so, yet .
hardly its something specific, new and thus worthy to discuss and/or relevant to topic thing, thus.This thread is to discuss about this candidate software version or to collect speculations and personal opinions about the stars in the sky ?!
Mikrotik does not like to share, only when "willing" to launch something new ....of course always late and incomplete but to improve definitelly over the time: always the same pattern.
The Zorro's reply is about "kernel - general improvement for core process scheduling" in the changelog from v6.34. From there he extrapolates to other issues that I found valid (and accurate).This thread is to discuss about this candidate software version or to collect speculations and personal opinions about the stars in the sky ?!
Mikrotik does not like to share, only when "willing" to launch something new ....of course always late and incomplete but to improve definitelly over the time: always the same pattern.
What is this?6.34rc23 version is released.
*) wireless - regular “wireless” package is now retired and replaced by "wireless-fp" and "wireless-cm2";
resolve www.google.com
failure: dns server failure
11:13:06 system,info dns changed by Vaselli
11:13:08 dns,packet --- sending udp query to 8.8.8.8:53:
11:13:08 dns,packet id:e1d2 rd:1 tc:0 aa:0 qr:0 ra:0 QUERY 'no error'
11:13:08 dns,packet question: www.google.com:A:IN
11:13:17 dns,packet --- sending udp query to 8.8.8.8:53:
11:13:17 dns,packet id:84a6 rd:1 tc:0 aa:0 qr:0 ra:0 QUERY 'no error'
11:13:17 dns,packet question: cloud.mikrotik.com:A:IN
11:14:17 dns,packet --- sending udp query to 8.8.8.8:53:
11:14:17 dns,packet id:90e8 rd:1 tc:0 aa:0 qr:0 ra:0 QUERY 'no error'
11:14:17 dns,packet question: cloud.mikrotik.com:A:IN
console and Winbox use different DNS settings. Using the GUI you use the DNS Server configured in your Windows computer. Using the command line, you use "ip dns" settings.
So in this case I guess your Windows PC has another DNS configured, but the 192.168.99.1 DNS is not responding. Try to enter 8.8.8.8 in your "ip dns" menu
[Vaselli@CRS] > resolve www.google.com
failure: dns server failure
[Vaselli@CRS] > ip dns print
servers: 8.8.8.8
dynamic-servers:
allow-remote-requests: yes
max-udp-packet-size: 4096
query-server-timeout: 0ms
query-total-timeout: 0ms
cache-size: 2048KiB
cache-max-ttl: 2d
cache-used: 11KiB
[Vaselli@CRS] > ip dns cache print
Flags: S - static
# NAME ADDRESS TTL
0 S google 8.8.8.8 2d
1 S google 8.8.4.4 2d
[Vaselli@CRS] > ip dns static print
Flags: D - dynamic, X - disabled, R - regexp
# NAME ADDRESS TTL
0 google 8.8.8.8 2d
1 google 8.8.4.4 2d
[Vaselli@Raffa's MK] > resolve www.google.com
[Vaselli@Raffa's MK] > ip dns print
servers: 8.8.8.8
dynamic-servers:
allow-remote-requests: yes
max-udp-packet-size: 512
query-server-timeout: 2s
query-total-timeout: 10s
cache-size: 2048KiB
cache-max-ttl: 1w
cache-used: 16KiB
[Vaselli@Raffa's MK] > ip dns cache print
Flags: S - static
# NAME ADDRESS TTL
0 S google 8.8.8.8 1d
1 S google 8.8.4.4 1d
2 S oi 200.222.122.132 1d
3 S oi 200.222.123.100 1d
4 therich... 192.237.140.116 23h30m36s
5 cloud.m... 91.188.51.139 1h26m10s
6 cloud.m... 81.198.87.240 1h26m10s
7 costco.ca 170.167.8.7 4h8m53s
8 wikimap... 192.69.192.210 20m33s
[Vaselli@Raffa's MK] > ip dns static print
Flags: D - dynamic, X - disabled, R - regexp
# NAME ADDRESS TTL
0 Google 8.8.8.8 1d
1 Google 8.8.4.4 1d
2 OI 200.222.122.132 1d
3 OI 200.222.123.100 1d
[Vaselli@Raffa's MK] >
ok, what part of the conf do you whant ?How can I know what to ignore? Please post full and correct config so we can find the issue.
/interface ethernet
set [ find default-name=ether23 ] comment=\
"TRUNK TO 433UAH -eth2 (old-TRUNK TO CCR)"
/ip neighbor discovery
set ether23 comment="TRUNK TO 433UAH -eth2 (old-TRUNK TO CCR)"
/interface vlan
add interface=ether23 l2mtu=1584 name=vlan99_MGT vlan-id=99
/interface ethernet
set [ find default-name=ether2 ] master-port=ether23
set [ find default-name=ether3 ] master-port=ether23
set [ find default-name=ether4 ] master-port=ether23
set [ find default-name=ether5 ] master-port=ether23
set [ find default-name=ether6 ] master-port=ether23
set [ find default-name=ether7 ] master-port=ether23
set [ find default-name=ether8 ] disabled=yes master-port=ether23
set [ find default-name=ether9 ] master-port=ether23
set [ find default-name=ether10 ] master-port=ether23
set [ find default-name=ether11 ] master-port=ether23
set [ find default-name=ether12 ] master-port=ether23
set [ find default-name=ether13 ] master-port=ether23
set [ find default-name=ether14 ] master-port=ether23
set [ find default-name=ether15 ] master-port=ether23
set [ find default-name=ether16 ] master-port=ether23
set [ find default-name=ether17 ] master-port=ether23
set [ find default-name=ether18 ] master-port=ether23
set [ find default-name=ether19 ] master-port=ether23
set [ find default-name=ether20 ] comment="DECODER TV OI" master-port=ether23
set [ find default-name=ether21 ] comment="TRUNK TO 433UAH -eth3" \
master-port=ether23
set [ find default-name=ether22 ] comment="TRUNK TO OI FIBRA" master-port=\
ether23
/ip neighbor discovery
set ether20 comment="DECODER TV OI"
set ether21 comment="TRUNK TO 433UAH -eth3"
set ether22 comment="TRUNK TO OI FIBRA"
/interface ethernet switch
set forward-unknown-vlan=no
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip ipsec proposal
set [ find default=yes ] enc-algorithms=aes-128-cbc
/system logging action
set 0 memory-lines=10000
set 1 disk-file-name=""
/tool user-manager customer
set admin access=\
own-routers,own-users,own-profiles,own-limits,config-payment-gw
/interface ethernet switch egress-vlan-tag
add tagged-ports=ether23 vlan-id=2
add tagged-ports=ether23 vlan-id=3
add tagged-ports=ether23 vlan-id=4
add tagged-ports=ether23 vlan-id=5
add tagged-ports=ether23 vlan-id=6
add tagged-ports=ether22,ether23 vlan-id=210
add tagged-ports=ether22,ether23 vlan-id=220
add tagged-ports=ether19,ether23 vlan-id=7
add tagged-ports=ether19,ether23,switch1-cpu vlan-id=99
/interface ethernet switch ingress-vlan-translation
add customer-vid=0 new-customer-vid=2 ports=\
ether2,ether3,ether4,ether5,ether6,ether7,ether8 sa-learning=yes
add customer-vid=0 new-customer-vid=4 ports=ether14 sa-learning=yes
add customer-vid=0 new-customer-vid=5 ports=ether15 sa-learning=yes
add customer-vid=0 new-customer-vid=6 ports=ether16 sa-learning=yes
add customer-vid=0 new-customer-vid=3 ports=\
ether9,ether10,ether11,ether12,ether13 sa-learning=yes
add customer-vid=0 new-customer-vid=220 ports=ether20 sa-learning=yes
add customer-vid=0 new-customer-vid=7 ports=ether17,ether18 sa-learning=yes
/interface ethernet switch vlan
add ports=ether2,ether3,ether4,ether5,ether6,ether7,ether8,ether23 vlan-id=2
add ports=ether9,ether10,ether11,ether12,ether13,ether23 vlan-id=3
add ports=ether14,ether23 vlan-id=4
add ports=ether15,ether23 vlan-id=5
add ports=ether16,ether23 vlan-id=6
add ports=ether22,ether23 vlan-id=210
add ports=ether20,ether22,ether23 vlan-id=220
add ports=ether19,ether23 vlan-id=7
add ports=ether19,ether23,switch1-cpu vlan-id=99
/interface wireless cap
set caps-man-addresses=192.168.99.1 certificate=request discovery-interfaces=\
ether23 interfaces=*1 lock-to-caps-man=yes
/ip address
add address=192.168.88.2/24 interface=ether1 network=192.168.88.0
add address=192.168.99.2/24 interface=vlan99_MGT network=192.168.99.0
/ip cloud
set ddns-enabled=yes
/ip dns
set allow-remote-requests=yes cache-max-ttl=2d query-server-timeout=0ms \
query-total-timeout=0ms servers=8.8.8.8
/ip dns static
add address=8.8.8.8 name=google ttl=2d
add address=8.8.4.4 name=google ttl=2d
/ip route
add distance=1 gateway=192.168.99.1
/ip service
set telnet address=\
192.168.2.0/24,192.168.3.0/24,192.168.99.0/24,172.16.4.0/24
set ftp disabled=yes
set www port=8787
set ssh port=222
set api port=8730
set winbox port=8292
set api-ssl port=8731
/lcd
set backlight-timeout=15m
/lcd pin
set pin-number=8723
/routing igmp-proxy
set quick-leave=yes
/routing igmp-proxy interface
add
/system clock
set time-zone-autodetect=no time-zone-name=America/Sao_Paulo
/system identity
set name=CRS
/system lcd
set contrast=0 enabled=no port=parallel type=24x4
/system lcd page
set time disabled=yes display-time=5s
set resources disabled=yes display-time=5s
set uptime disabled=yes display-time=5s
set packets disabled=yes display-time=5s
set bits disabled=yes display-time=5s
set version disabled=yes display-time=5s
set identity disabled=yes display-time=5s
set vlan99_MGT disabled=yes display-time=5s
set wlan1 disabled=yes display-time=5s
set ether1 disabled=yes display-time=5s
set ether2 disabled=yes display-time=5s
set ether3 disabled=yes display-time=5s
set ether4 disabled=yes display-time=5s
set ether5 disabled=yes display-time=5s
set ether6 disabled=yes display-time=5s
set ether7 disabled=yes display-time=5s
set ether8 disabled=yes display-time=5s
set ether9 disabled=yes display-time=5s
set ether10 disabled=yes display-time=5s
set ether11 disabled=yes display-time=5s
set ether12 disabled=yes display-time=5s
set ether13 disabled=yes display-time=5s
set ether14 disabled=yes display-time=5s
set ether15 disabled=yes display-time=5s
set ether16 disabled=yes display-time=5s
set ether17 disabled=yes display-time=5s
set ether18 disabled=yes display-time=5s
set ether19 disabled=yes display-time=5s
set ether20 disabled=yes display-time=5s
set ether21 disabled=yes display-time=5s
set ether22 disabled=yes display-time=5s
set ether23 disabled=yes display-time=5s
set ether24 disabled=yes display-time=5s
set sfp1 disabled=yes display-time=5s
/system logging
add topics=dns,packet
/system ntp client
set enabled=yes primary-ntp=200.192.232.8 secondary-ntp=200.160.0.8
/tool romon
set enabled=yes
/tool romon port
add
/tool user-manager database
set db-path=user-manager
Vaselli@CRS] > ping 8.8.8.8
SEQ HOST SIZE TTL TIME STATUS
0 8.8.8.8 56 52 4ms
1 8.8.8.8 56 52 5ms
2 8.8.8.8 56 52 6ms
3 8.8.8.8 56 52 6ms
4 8.8.8.8 56 52 6ms
5 8.8.8.8 56 52 6ms
6 8.8.8.8 56 52 5ms
7 8.8.8.8 56 52 6ms
sent=8 received=8 packet-loss=0% min-rtt=4ms avg-rtt=5ms max-rtt=6ms
Your server query timeout values are 0.
Use:
/ip dns set query-server-timeout=2s query-total-timeout=10s
:log info "Log Backup Sended to email...";
:local sysname [/system identity get name];
:local sysver [/system package get system version];
#read log
:local logcontent
:foreach int in=[/log find ] do={
:set logcontent ("$logcontent\r\n" .[/log get $int time]. " - " .[/log get $int message])
}
#send email
/tool e-mail send to=**@*** subject=([/system identity get name] . " Log " . [/system clock get date]) body=("Log of $sysname\nRouterOS version: \
$sysver\nTime and Date stamp: " . [/system clock get time] . " " . [/system clock get date] . "\n " . \
$logcontent);
#delete old log
/system logging action set memory memory-lines=1
/system logging action set memory memory-lines=1000
:log info "System log cleared by email-log-backup script...";
still errorExact same script works for me perfectly on same version.
Try to print body instead of sending message. Maybe you can notice something there:
:put ("Log of $sysname\nRouterOS version: \
$sysver\nTime and Date stamp: " . [/system clock get time] . " " . [/system clock get date] . "\n " . \
$logcontent)
/tool e-mail send to=**@*** subject=([/system identity get name] . " Log " . [/system clock get date]) body=(" ");
MikroTik RouterOS 6.34rc30 (c) 1999-2015 http://www.mikrotik.com/
[?] Gives the list of available commands
command [?] Gives help on the command and list of arguments
[Tab] Completes the command/word. If the input is ambiguous,
a second [Tab] gives possible options
/ Move up to base level
.. Move up one level
/command Use command at the base level
[admin@MikroTik2] > interface ethernet monitor 25
name: sfpplus2-slave-local
status: link-ok
auto-negotiation: done
rate: 10Gbps
full-duplex: yes
tx-flow-control: no
rx-flow-control: no
advertising:
link-partner-advertising:
sfp-module-present: yes
sfp-rx-lose: no
sfp-tx-fault: no
sfp-type: SFP-or-SFP+
sfp-connector-type: LC
sfp-link-length-9um: 10000m
sfp-vendor-name: Mikrotik
sfp-vendor-part-number: S+32LC10D
sfp-vendor-revision: 1.0
sfp-vendor-serial: MT50420H7983
sfp-manufacturing-date: 15-05-10
sfp-wavelength: 1330nm
sfp-temperature: 43C
sfp-supply-voltage: 3.181V
sfp-tx-bias-current: 34mA
sfp-tx-power: -40dBm
sfp-rx-power: -5.613dBm
[admin@MikroTik2] > system routerboard print
routerboard: yes
model: CRS226-24G-2S+
serial-number: 4C7E045BC537
firmware-type: qca8513
current-firmware: 3.22
upgrade-firmware: 3.22
[admin@MikroTik2] >
[admin@MikroTik] > interface ethernet monitor 9
name: sfpplus2-slave-local
status: link-ok
auto-negotiation: done
rate: 10Gbps
full-duplex: yes
tx-flow-control: no
rx-flow-control: no
advertising:
link-partner-advertising:
sfp-module-present: yes
sfp-rx-lose: no
sfp-tx-fault: no
sfp-type: SFP-or-SFP+
sfp-connector-type: LC
sfp-link-length-9um: 10000m
sfp-vendor-name: Mikrotik
sfp-vendor-part-number: S+23LC10D
sfp-vendor-revision: 1.0
sfp-vendor-serial: MT50420H7097
sfp-manufacturing-date: 15-04-21
sfp-wavelength: 1270nm
sfp-temperature: 49C
sfp-supply-voltage: 3.211V
sfp-tx-bias-current: 37mA
sfp-tx-power: -40dBm
sfp-rx-power: -5.081dBm
[admin@MikroTik] > system routerboard print
routerboard: yes
model: CRS210-8G-2S+
serial-number: 583A05910292
firmware-type: qca8513
current-firmware: 3.22
upgrade-firmware: 3.22
Do you have any details on this? I reported an issue with kernel failures on tile when using AES GCM (back on 11/19) and I'm wondering if this is related. I never heard back from support other than saying they would try to fix it.6.34rc23 version is released.
Changes since previous version:
*) crypto - fixed kernel failure in talitos HW encryption;
It appears so, I was able to move all of my VPNs back to GCM without any crashes.Do you have any details on this? I reported an issue with kernel failures on tile when using AES GCM (back on 11/19) and I'm wondering if this is related. I never heard back from support other than saying they would try to fix it.6.34rc23 version is released.
Changes since previous version:
*) crypto - fixed kernel failure in talitos HW encryption;
You have the default identity for all your routers. Change it, and the Identity will change in RoMON.
/system identity set name=Router_Name
If the name is long, RMON only displays mikrotik.Qper - This is not version related issue so please create another topic. What is the problem here? If router identity is default MikroTik then it will be shown also here. If you connect to router and change identity then you will see it also in RoMON neighbours list.
On ARM devices UserManager will not work within RouterOS v6. That is why packet is not available for download.
http://wiki.mikrotik.com/wiki/User_Mana ... er_Manager
"The MikroTik User Manager works on x86, MIPS, PowerPC and TILE processor based routers."
Nice enhancement!*) upnp - fixed missing in-interface option for dynamic dst-nat rules;
*) upnp - added comment for dynamic dst-nat rules to inform what host/program required it;
Nice.6.34rc32 version is released.
Changes since previous version:
*) net - fix bridge firewall chain check (broken since 6.33.2);
This enhancement got me in to "Teredo disabling spree" on all office PCs with Win10 this weekend... why it is enabled by default?Nice enhancement!*) upnp - fixed missing in-interface option for dynamic dst-nat rules;
*) upnp - added comment for dynamic dst-nat rules to inform what host/program required it;
its funny, cuz its my favorite defaults (not only for Win10 machines).This enhancement got me in to "Teredo disabling spree" on all office PCs with Win10 this weekend... why it is enabled by default?Nice enhancement!*) upnp - fixed missing in-interface option for dynamic dst-nat rules;
*) upnp - added comment for dynamic dst-nat rules to inform what host/program required it;
Yes, thanks for the feature it makes it much easier to manage dst-nat now.
Can you explain it? How it works?*) ipsec - prioritize proposals;
*) ipsec - support multiple DH groups for phase 1;
Thanks a lot, it looks that currently this option is supported only from command-line, not from Winbox.Now you can choose multiple DH groups in phase1
and all the chosen protcols are sorted from strongest to weakest protocol before sending proposals to remote peer.
all the chosen protocols are sorted from strongest to weakest protocol before sending proposals to remote peer.
Nice enhancement!*) upnp - added comment for dynamic dst-nat rules to inform what host/program required it;
Now all views are saved, so you can select it yourself and use it. Each configuration have it's unique important fields, you can't keep everyone happy.Why is to-adresses column not enabled by default? No need to write to-addresses in comment field...!
Is there anything else I can send you to be able to track this down?
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.
It looks like it - same thing happened to 6.33.5 also - check download page.Oh no. Mipsle support drop during subminor version development? What happened? Is it for always?
how it suppose to work?*) address-list - properly remove unused address-lists from drop-downs;
hum...raffav - This change is for situation like this but after you have disabled address-list of firewall rule in past you could see this list still in drop down menu but now you can not.
Of course it will still exist in such case. You can type anything under address list fields in firewall rules. You do not have to have actual entries in address list.
some obsoleted mips branches - already deprecated by linux kernel and toolchain long agoOh no. Mipsle support drop during subminor version development? What happened? Is it for always?
MIPS-LE was removed. Not SMIPS.Removing? SMIPS is a relatively recent beast, RouterOS v5.x for SMIPS has never existed.but removing "legacy" 5.xx ROS from download for SMIPS - make no sense
sorry, that MY mistake, obviously.Removing? SMIPS is a relatively recent beast, RouterOS v5.x for SMIPS has never existed.but removing "legacy" 5.xx ROS from download for SMIPS - make no sense
MIPS-LE is not only RB112, but for example RB133 or RB532 which are still well supported by 6.32.3. Maybe also by 6.33.x, but I dont have such experience as I do not use this version in production. Your statement that thay never worked good with v6 is obviously not true. I still do not understand why the support for MIPS-LE was dropped so suddenly.MIPS-LE was removed. Not SMIPS.Removing? SMIPS is a relatively recent beast, RouterOS v5.x for SMIPS has never existed.but removing "legacy" 5.xx ROS from download for SMIPS - make no sense
MIPS-LE were really old devices, like the RB112. They never worked good with v6.
SMIPS never existed for v5.
I would like to see there also all PPP servers and other services like UPNP, DNS, DHCP, NTP, SNMP and all others (even not manageably) to have one place where all active ports on the device are shown at once giving full overview to the administrator to know what ports are currently opened. Well, this part is more a "feature request" for aligning the reality with documentation than question. I admit.This document lists protocols and ports used by various MikroTik RouterOS services. It helps you to determine why your MikroTik router listens to certain ports, and what you need to block/allow in case you want to prevent or grant access to the certain services. Please see the relevant sections of the Manual for more explanations.
Does this mean you switched to a newer openssl library in this version?*) sstp - allow ECDHE when pfs enabled;
Do I check correct menu ?*) routerboard - print factory-firmware version in routerboard menu;
Try this URL http://download2.mikrotik.com/routeros/ ... 34rc45.npkI have a 404 error on the Dude package URL : http://download.mikrotik.com/dude-6.34rc45-tile.npk
Normal ?
Br
Perfect ! Have you a changelog for this package ? Any fix since dude-6.34rc41.npk ?Try this URL http://download2.mikrotik.com/routeros/ ... 34rc45.npkI have a 404 error on the Dude package URL :
http://download.mikrotik.com/dude-6.34rc45-tile.npk
Normal ?
Br
Special topic for that http://forum.mikrotik.com/viewtopic.php ... 82#p517782Perfect ! Have you a changelog for this package ? Any fix since dude-6.34rc41.npk ?
We have had the same problem.We have an issue that has been reported to support and wanted to see how many others are having the same issue.
When using MPLS Traffic Engineering tunnels and MP-BGP with VRFs, if the BGP peering goes down and back up, traffic stops forwarding until the Traffic Engineering interface is disabled and re-enabled.
When looking at a packet capture, it appears the outer label is missing in the MPLS label stack. Once the TE interface is bounced, the label shows back up in the capture.
Has anyone else run into this or similar issues with deploying Traffic Engineering tunnels?
Glad to know someone else is having this issue, in working with MikroTik on the ticket we have open, it appears they have found the bug and fixed it and the fix will be included in 6.34.We have had the same problem.We have an issue that has been reported to support and wanted to see how many others are having the same issue.
When using MPLS Traffic Engineering tunnels and MP-BGP with VRFs, if the BGP peering goes down and back up, traffic stops forwarding until the Traffic Engineering interface is disabled and re-enabled.
When looking at a packet capture, it appears the outer label is missing in the MPLS label stack. Once the TE interface is bounced, the label shows back up in the capture.
Has anyone else run into this or similar issues with deploying Traffic Engineering tunnels?