It allows to use mac address both as user-name and password. Old one allowed it be used just as user-name. In some situations it might make things easier for various devices to login if mac login is enabled."hotspot - add mac-auth-mode setting for mac-as-passwd option"
so what exactly does this?
/ip hotspot profile set mac-auth-mode=
MacAuthMode ::= mac-as-username | mac-as-username-and-password
Did it try to reboot? Reboot manually and see the LOGI am running 6.33rc14 on a RB711GA-5HnD. I try to to winbox autoupdate on the "Current" channel. I'm told that the latest version is 6.33 as expected. I click on either download or download & install. In either case nothing gets downloaded and the message at the bottom of the winbox "check for updates" window says: "New version is available". Why does it not download and update?
It did not try to reboot. Nothing was in the log. I updated my original post to indicate that I could (and did) manually download and manually upgraded successfully.Did it try to reboot? Reboot manually and see the LOGI am running 6.33rc14 on a RB711GA-5HnD. I try to to winbox autoupdate on the "Current" channel. I'm told that the latest version is 6.33 as expected. I click on either download or download & install. In either case nothing gets downloaded and the message at the bottom of the winbox "check for updates" window says: "New version is available". Why does it not download and update?
That's actually mentioned in ChangeLog...Looks like WInBox 3.0 is not a release candidate anymore Was able to get in after downloading Winbox 3.0.
I would want to know that as well! Probably it is not what i need but still it would be interesting to have new features explained. Manual is not updated with info as far as i can see.hotspot - add login-timeout setting to force login for unauth hosts
and what is this doing exactly...
What was broken?*) quickset - fixed HomeAP mode;
Speaking about that, if I would make my users to use wireless-cm2 on their CPEs, is this package mature enough also on point to multipoint?Given the single stream TCP/IP speed up is in wireless-cm2, if we are not using Capsman v1 should we all start using wireless-cm2 instead of wireless-fp by default?
Thanks!I found out, Add login-timeout is the timeout a device stays in hosts tab list . After that time it is deleted.
Yes, definitely.the final 6.33 still has the IPv6 addresses going missing bug... should I open a support case?
An update: openwrt x86 images work as before but debian i386 images does not. Logging shows kvm error. VNC does not allow me to connect.My KVM image does not start. When click enable and start, it just briefly indicates start and then stopped.
Please add the possibility of using an arbitrary username and password.It allows to use mac address both as user-name and password. Old one allowed it be used just as user-name."hotspot - add mac-auth-mode setting for mac-as-passwd option"
so what exactly does this?
Have you contacted MikroTik support and sent them a supout file?DNS fully broken for me.
/ip dns> print
action timed out - try again, if error continues contact MikroTik support and send a supout file (13)
/ip dns> set servers=8.8.8.8
action timed out - try again, if error continues contact MikroTik support and send a supout file (13)
I confirm this KVM behavior with i386 Debian image on x86My KVM image does not start. When click enable and start, it just briefly indicates start and then stopped.
The same still appears in the 6.34 release candidate. After downgrade back to 6.32.3, it is back to normalI confirm this KVM behavior with i386 Debian image on x86My KVM image does not start. When click enable and start, it just briefly indicates start and then stopped.
I just submitted the supout from one of the devices. Please note that I'm seeing this on regular units (RB-SXTs, RB75x, RB95x, etc), not a CHR image. This behaviour is not limited to the device from which I gathered the supout, it's common for all units that were updated to 6.33.bjornr and ckleea would be nice if you sent support output files to the support. Create the file after your attempt to start your image file.
Also, while at it, check if you have kernel and initrd files supplied for the configuration.
+1*) l2tp: implemented PPPoE over L2TP in LNS mode, RFC3817;
example configuration please.
Not so good idea. It is preventing to download compatible winbox from ros device when no access to Internet from any reason. It is big step back.chg123 - Have you used Branding maker to modify this router? Winbox is not saved on router any more. It is on our server and you should be directed to http://www.mikrotik.com/download/winbox.exe
winbox.exe went from 125KB to 1620KB so I can understand that.It is preventing to download compatible winbox from ros device when no access to Internet from any reason. It is big step back.
+1*) l2tp: implemented PPPoE over L2TP in LNS mode, RFC3817;
example configuration please.
Make sure your inner-tunnel IPsec traffic is exempt from Fasttrack.In 6.33 my configured IPSec RoadWarrior tunnel stopped working... Interestingly everything is working when I enable packet sniffing or torch on the interface.
Indeed, thanks. Removing the FastTrack rules solved the issue. Will have to find a solution how to properly exempt the IPSec traffic from these rules now.Make sure your inner-tunnel IPsec traffic is exempt from Fasttrack.In 6.33 my configured IPSec RoadWarrior tunnel stopped working... Interestingly everything is working when I enable packet sniffing or torch on the interface.
I guess they changes the core of WinBox architechture. WinBox used to download (and cache) a set of DLLs from the router on connect, one DLL per RouterOS package (i.e. system, wireless, security, etc.). Those DLLs is what actually implements UI for a particular package. WinBox 3 does not appear to be doing that any longer. Mikrotik devs, I guess, moved all the logic into the WinBox itself. That means they also introduced a new way for WinBox and the router to communicate which configuration options are available in the RouterOS version you are connected to at the moment. The main advantage of this approach is it will allow (sooner or later) Mikrotik guys to make WinBox truly portable without the need in Wine or similar crutches.winbox.exe went from 125KB to 1620KB so I can understand that.
not so easy to understand why it increased so much in size...
You can use a recently introduced 'ipsec-policy' firewall rule matcher. It should easily solve your task, provided you do not NAT your inner-tunnel traffic.Will have to find a solution how to properly exempt the IPSec traffic from these rules now.
I was trying to add a simple FastTrack rule for the related / established connections in the forward chain for inbound as well as outbound traffic.You can use a recently introduced 'ipsec-policy' firewall rule matcher. It should easily solve your task, provided you do not NAT your inner-tunnel traffic.Will have to find a solution how to properly exempt the IPSec traffic from these rules now.
Nope, I did not apply any branding maker. The Winbox link on the routers site still goes to the dead local winbox.exe link.chg123 - Have you used Branding maker to modify this router? Winbox is not saved on router any more. It is on our server and you should be directed to http://www.mikrotik.com/download/winbox.exe
I guess they changes the core of WinBox architechture. WinBox used to download (and cache) a set of DLLs from the router on connect, one DLL per RouterOS package (i.e. system, wireless, security, etc.). Those DLLs is what actually implements UI for a particular package. WinBox 3 does not appear to be doing that any longer. Mikrotik devs, I guess, moved all the logic into the WinBox itself. That means they also introduced a new way for WinBox and the router to communicate which configuration options are available in the RouterOS version you are connected to at the moment. The main advantage of this approach is it will allow (sooner or later) Mikrotik guys to make WinBox truly portable without the need in Wine or similar crutches.winbox.exe went from 125KB to 1620KB so I can understand that.
not so easy to understand why it increased so much in size...
What has changed regarding MTU sizes on PPPoE interfaces?*) pppoe - added support for MTU > 1492 on PPPoE;
Same problem here.What has changed regarding MTU sizes on PPPoE interfaces?*) pppoe - added support for MTU > 1492 on PPPoE;
I have been using 6.30.2 on a RB2011UAS-2HnD-IN and was able to use an MTU of 1500 bytes when connecting to my ISP's PPPoE server.
After upgrading to 6.33 I am no longer able to connect with an MTU of 1500 bytes. RouterOS keeps reverting back to 1480 bytes after connecting.
1488 was the max MTU I was able to set without it reverting back to 1480.
I have downgraded back to 6.30.2 for now where an MTU of 1500 bytes still seems to be working for me.
I'm not sure if I'm doing something wrong or if this is a bug. I have not yet been able to test out the versions between 6.30.2 and 6.33.
Please post a screenshot of the problem. Which Winbox link specifically is not workingNope, I did not apply any branding maker. The Winbox link on the routers site still goes to the dead local winbox.exe link.chg123 - Have you used Branding maker to modify this router? Winbox is not saved on router any more. It is on our server and you should be directed to http://www.mikrotik.com/download/winbox.exe
Really sad.
I use Debian Wheezy and Jessie to install the KVM. After successful installation, I take out the reference to the netinstall iso image, then I can boot into the debian directly without the need of kernel or initrd files in the setting. It is different from that of the image prepared from openwrt x86.bjornr and ckleea would be nice if you sent support output files to the support. Create the file after your attempt to start your image file.
Also, while at it, check if you have kernel and initrd files supplied for the configuration.
Hmm that is not good... I will have to stick with 6.32.3 until this is fixed!I have been using 6.30.2 on a RB2011UAS-2HnD-IN and was able to use an MTU of 1500 bytes when connecting to my ISP's PPPoE server.
After upgrading to 6.33 I am no longer able to connect with an MTU of 1500 bytes. RouterOS keeps reverting back to 1480 bytes after connecting.
1488 was the max MTU I was able to set without it reverting back to 1480.
Not so good idea. It is preventing to download compatible winbox from ros device when no access to Internet from any reason. It is big step back.chg123 - Have you used Branding maker to modify this router? Winbox is not saved on router any more. It is on our server and you should be directed to http://www.mikrotik.com/download/winbox.exe
This frees up a lot of space in the router, and ensures you always get newest Winbox. When you have no access to internet, you still have Webfig, which is 1:1 in layout and features.+1Not so good idea. It is preventing to download compatible winbox from ros device when no access to Internet from any reason. It is big step back.chg123 - Have you used Branding maker to modify this router? Winbox is not saved on router any more. It is on our server and you should be directed to http://www.mikrotik.com/download/winbox.exe
This frees up a lot of space in the router, and ensures you always get newest Winbox. When you have no access to internet, you still have Webfig, which is 1:1 in layout and features.
Uplink runs from the RouterBOARD to a TP-Link SG3210 switch which then goes out over a VLAN to an ethernet to fiber media converter to my ISP.Is your PPPoE link running over plain ethernet or on top of a VLAN? What modem do you use?
some SPI based products have 16 and 8MB of storage, so yes, that is a lot.Yeap. It frees a whole 1.5 mbyte of data! HUGE savings!
We can now use our routers as fileservers with so many data free!
Open "Tool -> Profile" and see what is causing it.I have a weird issue that , my CPU keep spam up to 50% and then it will start over.
Even router in IDLE mode it is still spamming up to 50%.
Anyone facing this issue before? I have no clue what is happening on this.
Thanks for your reply. The trouble is that I don't know about a security vulnerability (that is, if it is "broken"). I have a working system and would rather not update it unless it addresses a security vulnerability. Hence the request.Rule of thumb: If it is not broken, then do not fix it.
If your network is working why do you want to change/fix it ?
I opened a ticket and included supout.rif and packet capture files for both 6.30.2 and 6.33.Same problem here.
I opened a ticket to support!
If you can do the same, maybe they can look at the issue with more situations!
My ISP does have support for RFC4638 and reports a max payload of 1500 bytes.This can mean two things: either the RFC4638 support is broken and thus the router falls back to a lower MTU, or your ISP does not support RFC4638 and there is no longer a way to still override the MTU as before.
No. Time Source Destination Protocol Length Info
15 3.054014 Routerbo_xx:xx:xx Broadcast PPPoED 42 Active Discovery Initiation (PADI)
Frame 15: 42 bytes on wire (336 bits), 42 bytes captured (336 bits)
Ethernet II, Src: Routerbo_xx:xx:xx (d4:ca:6d:xx:xx:xx), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
802.1Q Virtual LAN, PRI: 0, CFI: 0, ID: 6
PPP-over-Ethernet Discovery
0001 .... = Version: 1
.... 0001 = Type: 1
Code: Active Discovery Initiation (PADI) (0x09)
Session ID: 0x0000
Payload Length: 18
PPPoE Tags
Host-Uniq: 00dc0001
PPP-Max-Payload: 05dc
No. Time Source Destination Protocol Length Info
16 3.057052 HuaweiTe_xx:xx:xx Routerbo_xx:xx:xx PPPoED 65 Active Discovery Offer (PADO) AC-Name='195.xxx.xxx.xxx'
Frame 16: 65 bytes on wire (520 bits), 65 bytes captured (520 bits)
Ethernet II, Src: HuaweiTe_xx:xx:xx (e0:97:96:xx:xx:xx), Dst: Routerbo_xx:xx:xx (d4:ca:6d:xx:xx:xx)
802.1Q Virtual LAN, PRI: 7, CFI: 0, ID: 6
PPP-over-Ethernet Discovery
0001 .... = Version: 1
.... 0001 = Type: 1
Code: Active Discovery Offer (PADO) (0x07)
Session ID: 0x0000
Payload Length: 41
PPPoE Tags
Host-Uniq: 00dc0001
PPP-Max-Payload: 05dc
AC-Name: 195.xxx.xxx.xxx
I can understand that. I also have the winbox on my computer for such reason. But I liked the possibility to grab the winbox directly from any ros device (excluding smips due to low disk space). There is no need to spare 1,5MB on devices having 64MB or more flash.jarda - Winbox is too large to store it on router. Since there are flash directories on routers for a while now and HDD space is limited we decided to store Winbox on our download site. Any way Winbox is portable tool and even if you do not have internet access and you want to use router, then there is always Webfig, CLI and you can carry Winbox on your USB drive.
I do not see this behaviour on my laboratory devices. It looks correctly like with previous versions.The Dude is loosing interest in RouterOS devices. The package information was lost before in the device list (tab RouterOS) - now also the RouterOS version is gone. This view was a great help for updates.
Are there such changes in some API or is it gone by mistake?
on my CCR the link is correct, but on x86 and mipsbe the link refer to router itself:Please post a screenshot of the problem. Which Winbox link specifically is not workingNope, I did not apply any branding maker. The Winbox link on the routers site still goes to the dead local winbox.exe link.chg123 - Have you used Branding maker to modify this router? Winbox is not saved on router any more. It is on our server and you should be directed to http://www.mikrotik.com/download/winbox.exe
Really sad.
NoI guess they changes the core of WinBox architechture. WinBox used to download (and cache) a set of DLLs from the router on connect, one DLL per RouterOS package (i.e. system, wireless, security, etc.). Those DLLs is what actually implements UI for a particular package. WinBox 3 does not appear to be doing that any longer. Mikrotik devs, I guess, moved all the logic into the WinBox itself. That means they also introduced a new way for WinBox and the router to communicate which configuration options are available in the RouterOS version you are connected to at the moment. The main advantage of this approach is it will allow (sooner or later) Mikrotik guys to make WinBox truly portable without the need in Wine or similar crutches.winbox.exe went from 125KB to 1620KB so I can understand that.
not so easy to understand why it increased so much in size...
If there is a chance for a really portable winbox please launch a natively looking mac version soon!
In my screenshot the "white labeled versions" have been updated to 6.33 and the last column lost it's content I think about half a year ago.I do not see this behaviour on my laboratory devices. It looks correctly like with previous versions.The Dude is loosing interest in RouterOS devices. The package information was lost before in the device list (tab RouterOS) - now also the RouterOS version is gone. This view was a great help for updates.
Are there such changes in some API or is it gone by mistake?
It is management that causing it.Open "Tool -> Profile" and see what is causing it.I have a weird issue that , my CPU keep spam up to 50% and then it will start over.
Even router in IDLE mode it is still spamming up to 50%.
Anyone facing this issue before? I have no clue what is happening on this.
indeed before posting here, i did that. in IE, Firefox and also google chrome. sure it's not cached.shinobi - Can you test with another browser or clear cache? At this point it seems that cache might be causing this issue.
As I said, not a problem in my case: Maybe some other problem you have than general problem of v 6.33...In my screenshot the "white labeled versions" have been updated to 6.33 and the last column lost it's content I think about half a year ago.I do not see this behaviour on my laboratory devices. It looks correctly like with previous versions.The Dude is loosing interest in RouterOS devices. The package information was lost before in the device list (tab RouterOS) - now also the RouterOS version is gone. This view was a great help for updates.
Are there such changes in some API or is it gone by mistake?
checked my x86 installation - the link points to mikrotik.com...indeed before posting here, i did that. in IE, Firefox and also google chrome. sure it's not cached.
yahooo!!!We plan to make a new Dude release this year
Man ...We plan to make a new Dude release this year, it should fix this, and many other bugs that have been gathered over the last years. Please post about RouterOS v6.33 and make new Dude posts in a separate thread.
This year? Does it mean year 2015 as usually counted on this planet - after the born of Jesus Christ?We plan to make a new Dude release this year...
So it looks like its implementation is broken in the routerMy ISP does have support for RFC4638 and reports a max payload of 1500 bytes.
So how do you move firewall / other rules in webfig? There is no re-ordering capability as far as I can tell so I have to keep using winbox.This frees up a lot of space in the router, and ensures you always get newest Winbox. When you have no access to internet, you still have Webfig, which is 1:1 in layout and features.
well, I drag it - and it moves just like in WinBox...So how do you move firewall / other rules in webfig? There is no re-ordering capability as far as I can tell so I have to keep using winbox.
New Dude - ahWe plan to make a new Dude release this year, it should fix this, and many other bugs that have been gathered over the last years. Please post about RouterOS v6.33 and make new Dude posts in a separate thread.
I hope in the new release will be finalized multicast and IGMP, I'm tired to use routers from other manufacturers for normal viewing of IPTV wi-fi, 'cause when I start viewing HD IPTV via wi-fi picture fray and computers from the local network do not meet , and in the log File, pops up a message that the loop can be as soon as I switch off all IPTV continues to operate normally , I ask you to correct this problem please:We plan to make a new Dude release this year, it should fix this, and many other bugs that have been gathered over the last years. Please post about RouterOS v6.33 and make new Dude posts in a separate thread.
As far as my testing goes (I'm not an expert in this all LNS/LAC stuff), configuration looks straight forward*) l2tp: implemented PPPoE over L2TP in LNS mode, RFC3817;
example configuration please.
/ppp l2tp-secret
I have the same situation on my RB951G-2HnD. The link points to the local winbox storage on the router and is actually dead (404). Tried different browsers, for sure this is not cache issue.on my CCR the link is correct, but on x86 and mipsbe the link refer to router itself:
echo "User-Name=test" | /usr/bin/radclient -d /etc/freeradius/ -r 2 -x 10.55.1.54:3799 coa "mikrotik-rate-limit=10M/10M 20M/30M 950k/9500k 2000/20000" "secret"
Try enabling multicast helper in your wireless interface settings. Please note that 'default' means 'disabled' currently.when I start viewing HD IPTV via wi-fi picture fray and computers from the local network do not meet
You probably need to supply RADIUS attributes (like 'Acct-Session-Id') to identify a particular user session, not just the user itself. Haven't tried it myself, just guessing.Routerboard after sending this command:just writes bad request the counter icoming.Code: Select allecho "User-Name=test" | /usr/bin/radclient -d /etc/freeradius/ -r 2 -x 10.55.1.54:3799 coa "mikrotik-rate-limit=10M/10M 20M/30M 950k/9500k 2000/20000" "secret"
It was also an item for user Xyl.pe1chl - It is already fixed in 6.34rc:
http://forum.mikrotik.com/viewtopic.php ... 05#p507126
http://www.mikrotik.com/download
did you include the NTP server package when you updated? is it enabled?updated yesterday
ntp server disappeared in 6.33
[...@MikroTik] > /system ntp
client export
no announcement in a change log
Here's the Screenshot. What you cannot see is my mouse pointer hovering over the winbox icon. On the left bottom you see the URL behing this icon which is http://{routerip}/winbox/winbox.exePlease post a screenshot of the problem. Which Winbox link specifically is not workingNope, I did not apply any branding maker. The Winbox link on the routers site still goes to the dead local winbox.exe link.chg123 - Have you used Branding maker to modify this router? Winbox is not saved on router any more. It is on our server and you should be directed to http://www.mikrotik.com/download/winbox.exe
Really sad.
NTP package are missing from smips only.did you include the NTP server package when you updated? is it enabled?updated yesterday
ntp server disappeared in 6.33
[...@MikroTik] > /system ntp
client export
no announcement in a change log
My CRS125-24G-1S-2HnD (mipsbe) is currently running RouterOS v6.30.1. When I try to use the "Check For Upgrades" option it returns "Could not resolve address upgrade.mikrotik.com". The DNS servers are configured to 8.8.8.8 and 8.8.8.4. What should I do to solve this?
I send commands from the server to the NAS mikrotikHello, it is not working on the latest version 6.33 radius requirement Coa. I do not know if I have something of a special turned on routerboard except incoming. Routerboard after sending this command:just writes bad request the counter icoming.Code: Select allecho "User-Name=test" | /usr/bin/radclient -d /etc/freeradius/ -r 2 -x 10.55.1.54:3799 coa "mikrotik-rate-limit=10M/10M 20M/30M 950k/9500k 2000/20000" "secret"
echo "User-Name=pppoeuser-1, NAS-IP-Address=123.17.8.34,Mikrotik-Rate-Limit = '1M 1536k 768k 8 8 1M'," | radclient -r 2 123.17.8.34:3799 coa drowssap
Received response ID 198, code 44, length = 45
NAS-Identifier = "KGD-123-17-8-34"
NAS-IP-Address = 123.17.8.34
I'm attaching memory map for my modules - maybe you can add support for them. (should be quite easy)Transceiver type: SFP or SFP+
Transceiver: 1000BASE-LX
Length: 3 Km [ Single Mode ]
550 m (OM1) / 550 m (OM2) / 0 m (OM3) [ Multi Mode ]
Speed: 1250 Mb/s
Wavelength: 1310 nm
Connector Type: SC
Vendor name: OEM
Vendor part number: AOPB-3524S-R03
Vendor revision: A0
Vendor serial number: S1235041040266
Product date: 141022
DDM Temperature: 36.5352 C (Warn :-128.0000 / -128.0000) DEFAULT
(Alarm:-128.0000 / -128.0000) DEFAULT
DDM Vcc: 3.3384 V (Warn : 0.0000 / 0.0000) DEFAULT
(Alarm: 0.0000 / 0.0000) DEFAULT
DDM TX bias: 12.8860 mA (Warn : 0.0000 / 0.0000) DEFAULT
(Alarm: 0.0000 / 0.0000) DEFAULT
DDM TX power: -10.0130 dBm (Warn : -40.0000 / -40.0000) DEFAULT
(Alarm: -40.0000 / -40.0000) DEFAULT
DDM RX power: -13.0364 dBm (Warn : -15.0000 / -8.0000) ADMIN
(Alarm: -19.0000 / -6.0000) ADMIN
DDM power state: TX ON RX ON
I get the same error and the reason I get it is because I have a drop rule for all traffic in input chain last in my firewall. If I disable this rule check for updates work.My CRS125-24G-1S-2HnD (mipsbe) is currently running RouterOS v6.30.1. When I try to use the "Check For Upgrades" option it returns "Could not resolve address upgrade.mikrotik.com". The DNS servers are configured to 8.8.8.8 and 8.8.8.4. What should I do to solve this?
updated packages from separate download file, no luck.did you include the NTP server package when you updated? is it enabled?