With ROS v6.2 or v6.1 router crash (reboots) when insert YOTA usb-modem.
With ROS v5.25 router and modem works fine.
I know that and i already did that before. I have changed all ether6 to sfp1 but it didn’t help.
For example if i ping 8.8.8.8 interface=ether6 from CCR it`s working but when i change all ethr6 to sfp1 and do same ping 8.8.8.8 interface=sfp1 i get timeouts.
please contact support@mikrotik.com and also tell us exactly which of two Yota modems you use? What routerboard you are using?
Does this feature - running a .rsc file automatically after a /system reset-configuration
work in the latest 6.xx revisions?
i have placed a file in the files window (x.rsc) and executed the command:
/system reset-configuration run-after-reset=x.rsc
The configuration is executed, the router reboots, but the x.rsc file is not executed.
What am i missing?
thanks in advance
Be sure not to have duplicate commands. Best is to create a full config file and reset with no-defaults=yes option.
I have tried each combination of the additional parameters:
no-defaults=yes and no-defaults=yes
skip-backup=yes and skip-backup=no
but without success.
i have also tried with a very simple, one line .rsc script file:
/system identity set name=xyz123
to see if i can get this very simple script to run, but without success.
I am sure i am doing something wrong, but have run out of ideas of what additional to try.
i have not configured this system with netinstall, but have used the 951G out of the box (i have a number of them, and so i know this is not specific to the specific router. Are there any additional requirements that need to be configured to allow this feature to work?
Hello!
I have a RouterBoard 1100 which was recently upgraded from 5.25 to 6.2. Since then the computers from various internal subnets can’t see each other. I’ve attached the config file. Any help would be appreciated.
Thanks,
cereno
mikrotik_config.rsc (7.96 KB)
Check to see if “IP → Settings → IP Forward” is enabled.
It was enabled by default. Any other guess?
traceroute =)
error: hold timer expired, subcode=0
this happened since I have the v6.x. probe and with all
I am writing to you in order to let them get that error. few days ago, I’m having problems in my ccr1036, with version 6.2. This problem causes all BGP connections frequently disconnect, making it impossible to operate in this way. I need a solution urgently. no more.
I need an answer, it is urgent. attachment autosupout.rif
I’m sorry but can You provide a link to the archive with packages? For PPC architecture… I already downloaded the routeros-ppc-6.3rc1.npk.
I think I found a bug in version 6.2
I added a NAT rule in the dst-nat chain to port forward to an internal device.
When I did that I immediately got disconnected via Winbox (winbox crashed).
Lucky for me I still could get connection via ssh.
By connecting to ssh I found out that the order of the firewall filter has changed.
The rule allowing me to access the device by winbox was set below the implicit drop rule I have.
Is this a known issue or something to do with winbox.
I’m using winbox on Windows 7 ultimate x64
This will be fixed in RouterOS v6.3.
Any news on when the src-address issue in web-proxy will be fixed?
Hy guys, i’m a new guy here
and i need your help because i meet a problem how i can create user-manager in mikrotik version 5.4
if i use mikrotik version 4.17
i use this command and working
/tool/user-manager/user/add=subscriber=subscriber=name= user_m=password=pass_m=uptime-limit=1d=add-credit=1d
but if i user in mikrotik version 5.4 is not working
/tool/user-manager/user/add=customer=mikrotik1=username=test1=password=t1=copy-from=user1d
i already create the profile but still not working
please help me
@ widarta
You should post it in one (!) thread where it belongs or - if there is no suitable existing thread - open a new one in a suitable sub-forum. Your post has nothing to do with Mikrotik news or RouterOS 6.2 
For those using 6.3RC1, new release out 28/8/2013 12:32:24
change since the 22/08:
*) console - added ‘/console clear-history’ command that clears command-line
history for all users, requires ‘policy’ policy;
*) sstp - limit packet queue for each device;
*) RB2011L - fixed occasional gigabit switch-chip lockup;
*) user manager - will warn on 1MB and stop before reaching minimum of 500KB disk space;
Ah great!
The only thing I don’t get is why this is not called RC2 as it is clearly a new iteration.
6.3RC1, new release out 28/8/2013 12:32:24
still not working netwatch,scheduler