I’ll start this topic and put my beta 3 bug reports here - as far as I can free some time for testing.
First one:
Doing a
/export file=test
Will create a file “test.rsc” as expected, but then the console is crashing. Not sure if the export file is complete…
Best regards,
Christian Meis
RB532+RB564+2xCM9
Window Frequency select don’t work!
I see only 2437Mhz… or manually rewrite this.
dude package? 
Shutting down be (/system shutdown) gave this error:
failed to stop dudes: std failure: broken path (2)
I’m still looking where to find the dude from the dude-package 
Any hints from MikroTik, perhaps?
Best regards,
Christian Meis
file looks complete to me!
you shouldn’t have received the package. anyway, we will fix the error. a working package will be released in one of the upcoming betas
Nice
Best regards,
Christian Meis
Just noticed today,
No support yet for RTL8111B Gigabit Ethernet chipset in Beta 3
"Realtek RTL8111B PCI-E Gigabit LAN "
Please can we have this added? Would be great.
Drivers for Linux2.4 and 2.6 are here:
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false#2
Regards
hmm, didn’t see this thread at first, I just made a bug post on the other beta 3 thread… I’ll just post the link as to not double post 
http://forum.mikrotik.com/t/new-routeros-beta-is-out-v3-0beta3/9913/18
narrowed down the wireless button causing winbox to crash to a virtual AP that was upgraded from 2.9.x removed it and everything is fine now.
when mode=ap-bridge, noisefloor is showing at 5555dBm, works fine in station mode
what’s the trick getting station-psudobridge to work? I can’t seem to get PPPoE to work across it…
it would be nice to have the frequency selection drop down back, easier then typing…
in station mode, where can I verify that the Polling and CSMA options correctly are pulling from the AP? wireless registration → registration properties (AP Client window) shows if NStream is turned on or not, but doesn’t list Polling or CSMA status.
winbox → files: deleting the hotspot folders causes winbox to crash
that’s all for the moment. time for some NStream / CSMA testing now
Hi guys
I’m having a problem. I upgraded a routerboard 112 (Level 4) to the new beta3. The CPU sits at 100%. It defaults with no IP address, and winbox won’t connect to it. I login to it through another Routerboard (running 2.9.35) through MAC Telnet. anytime I reboot the beta3 board it resets everything - no ip addresses, no passwords saved, all packages enabled as default.
Any recommendations?
Thanks
Do you have the same resets issues with 2.9 version ?
Check if 2.9 version works correctly, report back with the results.
I didn’t when it was loaded with 2.9. 2.9 worked flawlessly. I can’t get it to downgrade now… upload the packages and issue the “downgrade” command, correct?
To downgrade upload 2.9 packages and ‘system package downgrade’, or you can use netinstall to install 2.9.
3.0rc3 on a RB112 with NL-2511MP+ radio card running pseudo-bridge station mode talking to a SmartBridges AP.
Works fine from the ethernet side. Excellent connection and throughput.
When I try to access it from the wireless side with either WinBox or telnet session, I lose connectivity right after or while I try to log in.
The router seems to either reboot or stay crashed which requires a power cycle to get working again.
Tom
I’ve just come up against this having put together a router and finding that only my PCI ether adapters work, and not the onboard gigE!
Help? Can we have RTL8111B driver in 2.9 or 3.0b please?
Any news from Mikrotik on support for GigE chipsets?
Select large amount of VLAN Interfaces (32 tested with RC2) and remove the interfaces in WinBox… WinBox stops responding, when closing and reconnecting to the router with WinBox, WinBox is still screwed and does not respond…
Tested on RC2 inside VMWare, so far it happened every time (3 times in a row)… Not sure if it’s a ROS thing, or perhaps a VMWare thing…
Also, /ip neighbor discovery sees VRRP Interfaces… Considering CDP is multicast in any case, any use in sending the multicast on the actual interface, as well as the VRRP interface, which theoretically is the same media? Same story for interface graphs as well… Not too sure at this stage if /interface vrrp was such a good idea in all honesty… VRRP really isn’t a virtual interface as such…
DO we have any documentation for version 3.0 ???