*) fixed bug - PPPoE server could crash when running on multiple cores;
*) fixed bug - bridging over PPP interfaces with encryption enabled did not work;
*) fixed dhcp server - arp entries were not added after reboot;
*) fixed problem in pppoe, pptp & l2tp - server could restart;
*) fixed bug in console - bridge and ip filter “print static” and “print
dynamic” commands had the opposite effect;
*) fixed bug - DHCP server did not parse Relay-Agent-Info option 82;
*) fixed bug - hotspot login could fail with “ippool acquire failed”;
*) graphing - ip address formatting bugfix;
*) ospf - added support for Opaque LSA;
*) ospf - fixed routes changing type from Intra Area to AS External;
*) ospf - fixed multicast group membership in case there are
multiple IP networks configured on a single interface;
*) routing - now iBGP routes are resolved through IGP and static by default;
*) user manager - fixed ampersand bug;
*) updated regulatory information for Australia;
*) updated drivers;
This has not been fixed… I had this same problem in 3.2 even without encryption. Hotspot on a bridged interface with l2tp tunnels still isn’t working for some reason. I am almost 100% positive it has to do with MTU issues. I will take some pcaps and explain better with a supout coming soon.
Hello,
please could anybody tell me what does it exactly means “Drivers update”, I’m very interested in support f.e. P35 chipset with ICH9, is RouterOS improving the support for the new chipsets from Intel, we are using computers as routers and last working chipset is 945, it is today quiet an old chipset ???
Seems everyone miss out the major fix of the release!
*) fixed bug - PPPoE server could crash when running on multiple cores;
a.k.a. multicore support finally fixed!
About the
*) drivers updated
It is update - so affects only existing drivers, so no new drivers are supported. and it looks like particularly it is nForce related updates, maybe some other. One way or another if you have popular Ethernet adapter that had issues (but was recognized in RouterOS) you should upgrade and try it out - then write standard mail to support.
Ive found two bugs so far on ROS 3.3, but one of them wont let myself sleep:
/interface wireless access-list print where interface = wlan1
Does not do any filter… just dump the entire access-list;
IP Pool facility get stuck with PPPOE server
People disconnect from PPPOE server but their IP address still in the “used addresses” forever til a reboot.
Supouts sent already but got no answer back nothing since last week. I would like to say that a feed-back would be nice for such things… its depressive downgrading 50+ devices ya know?
As I had several stability problems with previous v3.x releases on rb333 and finally found v3.2 as working version and v3.3 doesn’t have any more features I need I’m little bit affraid of new bugs that can make my links unstable. Where it is possible to download the 3.2 version? Can’t find it anywhere..
/interface wireless access-list print where interface = “wlan1”
NOPE, this is still broken and not working on v3.3! Nothing you can do to filter a specific data on access-list. Also, I hope they bring up a new release as soon as possible due to the IP Pool stuck bug. After upgrading all our devices to v3.3 it happens very often, but happens and it is very disturbing cuz detections are made when customers do complain. Only reboot solve.
MT said it will be fixed in the next release, but this next one is taking too long to come. Please, hurry til I get forced to downgrade 50+ devices. It is depressing.
try putting a space after that last quote - right before you hit enter… something i ran into on another cli command that they said would be fixed in 3.4 when it comes out.
