It has to be like that, i dont need it because i have wireless client added to access list.You set default-forwarding=no on wireless interface.
The default is yes on all version of RouterOS, is your fault.
But for simple router is ok?What bugs do you mean for the CRS?
Also what should be noted that the CRS is mainly a switch, with routing capability. if you intend to use it as a router only, it is not very powerful. For just routing purposes we have other devices.
and it works, thanks.3 chain=srcnat action=masquerade dst-address=192.168.69.1 out-interface=ether2-master-local
You can do this remotly - http://ip_address/rebootThat cryptic output is a cosmetic problem which can be observed during changing between old and new Web GUI design. Power cycle fixes it.
Sadly I confirm that.http://forum.mikrotik.com/viewtopic.php?f=17&t=44971 bug still present.
Sorry but I dont understood, please explain.Use 0.0.0.0/0:low-high format in IP Src and IP Dst fields, to apply UDP or TCP port conditions.
Ok but how to block certain tcp/udp port?Have you tried the ACLs ?
I think it should be doable with the ACLs, but hav not tried this myself
OK, I know, but what this have to do with SwOS?
I did that and now I have Tx/Rx signal -55/-56 dBm and CCQ 90/95%, transmission is 100Mb/s full duplex.each chain has to be a different polarization
Try another method: power off switch, press reset and then power on (slightly diffrent than previously).Update:
1. The ACT light is quickly flashing even no device is connected to the switch ...
Windos XP SP3, firefox 3.6.12 and IE 7.reverged and others.
Which OS are you using and browsers?
I'm able to reproduce problem on MACOS with any browser, however it is fine on Windows/Linux.
Anyway we are working on the issue.
I disagree with you, port numbers are ok (i checked fw version 1.0 and 1.2).And I also dislike that port numbers written on the switch case are opposite order with port numbers on web interface (port 5 is port 1 etc.)