Stop this debate and enjoy RC releases! Feel proud yourselves because you're helping Mikrotik in making best networking products ever seen! They let us be a part of the developement with the RC channel! As the others do?
I need to echo macgaiver: go to the right topic (or create a new) and post your complains in there. No offenses, just to don't mess up this topic.The problem is not that it is RC, but that it is NOT.
It is not even beta, because Current is beta-level, IMHO.
Too many branches encumber the devs. I think that actual situation is far better than before, we should just understand the naming convention used by MT or maybe they can just change it:Nightly -> Beta -> RC -> Feature -> Bugfix
I threw my router in the trash, 2011UiAS-2HnDI also had the problem that the router couldnt reboot after the update (2011UiAS-2HnD)
Unplugged power and after replug the router startet.
I know it was my fault that i didnt checked the forum before installation but i dont understand why mikrotik still deliver this update when there are much more problems then normal.
It would be enough to disable the update and wait for next release.
LOL haven't heard about Netinstall?I threw my router in the trash, 2011UiAS-2HnDI also had the problem that the router couldnt reboot after the update (2011UiAS-2HnD)
Unplugged power and after replug the router startet.
I know it was my fault that i didnt checked the forum before installation but i dont understand why mikrotik still deliver this update when there are much more problems then normal.
It would be enough to disable the update and wait for next release.
The v6.35rc45 was especially bugged...I have 2x 951Ui-2HnD that are non-responsive after updating to v6.35rc45. One of them came back up partially, it had the the entire RoS Package disabled in it. I made a supout.rif and re-enabled the package and now it is completely non-responsive.
So if we are in rc43-45, we have to downgrade first ?Everyone who is still experiencing issues with upgrade/downgrade. In version 6.35rc46 we introduced fix:
*) nand - fixed reboot loop after upgrade to >v6.35rc43;
This fixed reboot loop, but you have to remember that within upgrade you can not have rc43-rc45 version involved. For example, upgrade from rc45 to rc46 could still crash because you try to upgrade from problematic version which does not have this fix included.
So if we are in rc43-45, we have to downgrade first ?Everyone who is still experiencing issues with upgrade/downgrade. In version 6.35rc46 we introduced fix:
*) nand - fixed reboot loop after upgrade to >v6.35rc43;
This fixed reboot loop, but you have to remember that within upgrade you can not have rc43-rc45 version involved. For example, upgrade from rc45 to rc46 could still crash because you try to upgrade from problematic version which does not have this fix included.
Well I just upgraded the normal way from rc43, no problem on my ccr1009.So if we are in rc43-45, we have to downgrade first ?Everyone who is still experiencing issues with upgrade/downgrade. In version 6.35rc46 we introduced fix:
*) nand - fixed reboot loop after upgrade to >v6.35rc43;
This fixed reboot loop, but you have to remember that within upgrade you can not have rc43-rc45 version involved. For example, upgrade from rc45 to rc46 could still crash because you try to upgrade from problematic version which does not have this fix included.
no, best way is to use netinstall
I hope that they pay no cent for sending in a device which is bricked because you installed a nightly build.When everyone who bricked a device by update would send it to mikrotik back for warranty repair, it would make mikrotik to think and test twice before releasing harmful versions to public.
Stay there until [stable] releaseThanks to all, that mikrotik made from 6.2 to 6.32 & 6.34.4 . There is some great impruvements of stability was made.
I also has problem with 6.35 rc44 or rc45 on my 951G with boot loop.
It was fixed with netinstall & some PXE server.
Now I am on 6.34.4 and do not shure to go back to RC.
Can be PXE server be integrated to netintall for easy recover? Or write some more in manual? For idiots.
It IS supported on all RB7xxDear engineers of Mikrotik, it is possible to hope that you implement the work of "FastTrack" on RB750G
It works on our RB750GL but not on our RB750GIt IS supported on all RB7xxDear engineers of Mikrotik, it is possible to hope that you implement the work of "FastTrack" on RB750G
Yes, exactly so, 750 works 750G noIt works on our RB750GL but not on our RB750GIt IS supported on all RB7xxDear engineers of Mikrotik, it is possible to hope that you implement the work of "FastTrack" on RB750G
It turns out that it is possible not to hope that fasttrack will work at RB750G ? ЭХ Mikrotik... and I had hoped and believed...I found one on old board shelf, just betweer RB230 and RB532. , Yes you are right, this board is using same CPU as RB4xx series, so fastpath is not supported. you need ar72xx CPU at least ar71xx doesn't have the support.
Hi mccreigh. Sorry for the long wait, but I have finally completed the config and have it ready to share. Feel free to use and modify as-needed. Comments are written in the config that most should be able to understand with basic RouterOS and networking experience.I'd really appreciate a working config that I can dig through to understand.
My other problem is finding a sequence of steps to get from the factory-default RBmAPL-n2D WISP AP configuration to one where the (only) Ethernet interface is on the LAN without losing Winbox connectability. (I can always use the magic button to restore the factory-default configuration, but then I'm right back where I started.) Once I'm controlling the router firmly through its Ethernet interface, I should be able to reconfigure the wlan interface without losing control.
# RouterOS Hotel Setup
# Created 2016-04-10 by Jacob McDonald
# Revised n/a
# This config was built using a model RouterBOARD 962UiGS-5HacT2HnT (“hAP ac”).
# This router has 1x 2.4 GHz radio and 1x 5 GHz radio, but this configuration does not depend on two radios.
# This config uses the 2.4 GHz radio base interface in Station-Pseudobridge mode to connect to another Wi-Fi AP,
# and creates a Virtual AP virtual interface on top to serve 2.4 GHz stations. A 5 GHz AP is also configured, and
# the 5 GHz AP would provide better performance since the 2.4 GHz radio wouldn’t have to share air-time serving
# stations in AP mode and forwarding the traffic to the other AP in station mode.
# The split-mode radio configuration only works with RouterOS 6.35 (rc and higher), using the testing radio
# package “wireless-rep”. This package is not included in the main software package, but can be extracted from
# the extras package and installed a la carte.
# RotuerOS Software: http://www.mikrotik.com/download
# 1. Install the base package from System -> Packages, or by uploading the .npk to the root filesystem and reboot.
# 2. Extract the wireless-rep.npk package from the extras .zip archive, upload to the root filesystem, and reboot.
# 3. Third, upgrade the RouterBOARD firmware: System -> RouterBOARD -> Upgrade, and reboot.
# Change the wireless security profiles in “/interface wireless security-profiles” below:
# default: set for your desired AP password (LAN)
# wlan-WAN: set to the AP password for the Wi-Fi network you wish to use as WAN
# none: this is a profile for using a Wi-Fi network as WAN with no authentication, typical in hotels
# Change between “wlan-WAN” and “none” security-profile as-needed by changing the setting in the
# “/interface wireless wlan1-WAN” config.
# Using the WebUI, Winbox, or CLI, perform Scan on the wlan-WAN interface, and select Connect to the AP you wish
# to use as WAN. This will adopt the frequency, bandwidth, and protocol settings automatically.
# This config will use the DHCP-supplied DNS servers from the WAN interface, which will be necessary to pass
# through the captive portal.
# apr/10/2016 20:31:47 by RouterOS 6.35rc48
# software id = XZFF-04CI
#
/interface bridge
add name=bridge1
/interface ethernet
set [ find default-name=ether1 ] name=ether1-WAN
/interface wireless
set [ find default-name=wlan2 ] band=5ghz-a/n/ac disabled=no mode=ap-bridge name=wlan2-5G-LAN ssid="Magrathea 5G" wireless-protocol=802.11
/ip neighbor discovery
set ether1-WAN discover=no
/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa2-psk eap-methods="" mode=dynamic-keys supplicant-identity=MikroTik wpa2-pre-shared-key=h2g2h2g2
add authentication-types=wpa2-psk eap-methods="" mode=dynamic-keys name=wlan-WAN supplicant-identity="" wpa-pre-shared-key=hdyfrc4la1 wpa2-pre-shared-key=hdyfrc4la1
add name=none
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-b/g/n disabled=no distance=indoors frequency=2442 mode=station-pseudobridge name=wlan1-2G-WAN security-profile=wlan-WAN \
ssid=skyconway_com-2231 wireless-protocol=802.11
add disabled=no keepalive-frames=disabled mac-address=E6:8D:8C:49:23:FA master-interface=wlan1-2G-WAN mode=ap-bridge multicast-buffering=disabled name=wlan3-2G-LAN ssid=Magrathea \
wds-cost-range=0 wds-default-cost=0 wps-mode=disabled
/ip neighbor discovery
set wlan1-2G-WAN discover=no
/ip hotspot profile
set [ find default=yes ] html-directory=flash/hotspot
/ip pool
add name=dhcp ranges=192.168.88.3-192.168.88.254
/ip dhcp-server
add address-pool=dhcp authoritative=yes disabled=no interface=bridge1 name=dhcp1
/interface bridge port
add bridge=bridge1 interface=ether2
add bridge=bridge1 interface=ether3
add bridge=bridge1 interface=ether4
add bridge=bridge1 interface=ether5
add bridge=bridge1 interface=sfp1
add bridge=bridge1 interface=wlan2-5G-LAN
add bridge=bridge1 interface=wlan3-2G-LAN
/ip address
add address=192.168.88.1/24 interface=ether2 network=192.168.88.0
/ip dhcp-client
add default-route-distance=0 dhcp-options=hostname,clientid disabled=no interface=ether1-WAN
add default-route-distance=2 dhcp-options=hostname,clientid disabled=no interface=wlan1-2G-WAN
/ip dhcp-server network
add address=192.168.88.0/24 gateway=192.168.88.1 netmask=24
/ip dns
set allow-remote-requests=yes
/ip firewall filter
add chain=input protocol=icmp
add chain=input connection-state=established
add chain=input connection-state=related
add action=drop chain=input in-interface=ether1-WAN
add action=drop chain=input in-interface=wlan1-2G-WAN
/ip firewall nat
add action=masquerade chain=srcnat out-interface=ether1-WAN
add action=masquerade chain=srcnat out-interface=wlan1-2G-WAN
/ip upnp
set enabled=yes
/ip upnp interfaces
add interface=bridge1 type=internal
add interface=ether1-WAN type=external
add interface=wlan1-2G-WAN type=external
/system clock
set time-zone-name=UTC
/system identity
set name=rbtest
/system leds
set 1 interface=wlan2-5G-LAN
/system ntp client
# These are from us.pool.ntp.org
set enabled=yes primary-ntp=108.61.73.243 secondary-ntp=216.229.4.69
/tool mac-server
set [ find default=yes ] disabled=yes
add interface=ether2
add interface=ether3
add interface=ether4
add interface=ether5
add interface=sfp1
add interface=wlan2-5G-LAN
add interface=wlan3-2G-LAN
/tool mac-server mac-winbox
set [ find default=yes ] disabled=yes
add interface=ether2
add interface=ether3
add interface=ether4
add interface=ether5
add interface=sfp1
add interface=wlan2-5G-LAN
add interface=wlan3-2G-LAN
Requests for CAPsMAN bug fixes and new features, based on my experience with the current RC version:
6. {Annoying} Stop CAPsMAN from creating virtual interfaces on CAPs with name "wlanXXX" where XXX is a number which is incremented every time the interface is disabled and re-enabled.
Why not use the existing wireless "connect list" feature ?Did someone try to this new feature?
>> wireless background scan
I wanted to script a background scan for known Wifi-APs and if found, connect to it automatically.
The Microtik is in a car, and I know several Wifi along the road (while stopping the car!).
The Idea was: Scan for known ssid's (or MAC..) and if found one, set wlan2 to the known credentials.
simply didn't understand this function! Thanks a lot for pointing me there, i will try it!!!Why not use the existing wireless "connect list" feature ?
Hi uldisVersion 6.35rc49 has been released.
...
*) tunnels - fixed performance slowdown on any other tunnel disable/enable;
...
Version 6.35rc49 has been released.
Changes since previous version:
*) dhcpv6 client - fix ia expiration and lifetime validation;
*) dhcpv6 server - acquire binding on renew if it does not exist;
I'm also interested in this new feature.I see a lot of works on dhcpv6 in recents RCs, which is a good thing.
Any timeline about adding options on the dhcpv6 client ? (like asked here : http://forum.mikrotik.com/viewtopic.php ... 81#p517695 ) ?
Thx.
This problem is already fixed in the latest rc wireless-rep package.Any news about fixing AC mode and Intel 7260 ?
No, you need to switch the RouterOS to Release Candidate channel and upgrade to the latest RC which currently is rc49. And then install the wireless-rep package.Can I use latest current release and latest rc wireless rep package ?
So it means there is an error in the script that expects some wlan adapter but it is not present... You should correct the default script then.Each time you upgrade, new defautl configuration file is generated, it doesn't matter if you wipe defconf or not.
currently it is not possible and it will not be added in the near future as it isn't just simple settings, there are lot of things needed for supporting that feature. And for the regular indoor APs you don't need this function.Hi,
how to open then "bridge-mode" for capsman mode? thanks.
"nv2-ptp", "nv2-ptmp"? I never heard of that. Only "NV2" then parameters are set for different type of link?6.35rc49
NV2 qos works very good, ping in low, ap control capacity of the client well. Could u add a second Wieless Protocol nv2 (ex nv2-ptp, old named nv2-ptmp) for ptp only, with some special features to improove it? Ex lower the ping and more overhead control to stable the links? It could be the option in wireless-rep, we will test it.
regards
Mateusz
Nv2 gives time space, and other things, it is in the code, for ptmp it is working now very well as i wrote (in auto period size one station overhead ap much before, now it isn`t). I think for ptp the code could be rewrite and aded as a second choise in menu. In lte no matter what rate and speed u have, ping is always the same, this is for me good qos. It is work for a coders, i am a customer, they must do the job to beat airmax, not me For me i rather be pleased to have 90mb and ping 0-1-2 ms on 240/240 802.11N than 130-140mb and ping 2-7-20ms, this is example. When noise apears radio should do the job and lower the speed to do 0-1-2ms, now u understand?"nv2-ptp", "nv2-ptmp"? I never heard of that. Only "NV2" then parameters are set for different type of link?6.35rc49
NV2 qos works very good, ping in low, ap control capacity of the client well. Could u add a second Wieless Protocol nv2 (ex nv2-ptp, old named nv2-ptmp) for ptp only, with some special features to improove it? Ex lower the ping and more overhead control to stable the links? It could be the option in wireless-rep, we will test it.
regards
Mateusz
How did you measure the NV2 qos? Examples?
No, not a lot. Your english is a bit hard to understand.Nv2 gives time space, and other things, it is in the code, for ptmp it is working now very well as i wrote (in auto period size one station overhead ap much before, now it isn`t). I think for ptp the code could be rewrite and aded as a second choise in menu. In lte no matter what rate and speed u have, ping is always the same, this is for me good qos. It is work for a coders, i am a customer, they must do the job to beat airmax, not me For me i rather be pleased to have 90mb and ping 0-1-2 ms on 240/240 802.11N than 130-140mb and ping 2-7-20ms, this is example. When noise apears radio should do the job and lower the speed to do 0-1-2ms, now u understand?"nv2-ptp", "nv2-ptmp"? I never heard of that. Only "NV2" then parameters are set for different type of link?6.35rc49
NV2 qos works very good, ping in low, ap control capacity of the client well. Could u add a second Wieless Protocol nv2 (ex nv2-ptp, old named nv2-ptmp) for ptp only, with some special features to improove it? Ex lower the ping and more overhead control to stable the links? It could be the option in wireless-rep, we will test it.
regards
Mateusz
How did you measure the NV2 qos? Examples?
regards
Mateusz
regarding options for DHCPv6-client, DHCP-PD client (and also DHCP--PD server) as it currently stands - options will be available only with RouterOS 7.x release due to technical limitations for backporting the feature.
If your were to create access lists based on the OUI info in this table http://standards-oui.ieee.org/oui.txt then each registration would have manufacturer listed next to it.Is it possible to add more information about connected user to CAPSMAN view with wireless-rep package?
e.g. user name being used, auto-translation of vendor part of MAC (well it´s a gimmick)
It is not, perhaps, supposed to work. My understanding is CAPsMAN currently mainly targets indoors setups with only the standard 802.11 features supported.on CapsMan channel width=10mhz not work