6.33.1 version is released!

Hi,

with RB951G-2HnD the same. Just terminating and no connection…

Carrier: Deutsche Telekom 6000RAM DSL.

(Remote site - will checkout tomorrow).

Greetz…Detlef

I have a RB2011.
Since version 6.32.3, MTU 1492 in PPPoE has malfunctioned. Any later version has solved.
V6.32.3 work fine.

imagen

V6.34rc6 Don’t work.

share image

If you did use RouterOS + RouterOS for PPPoE tunnel, then it should work correctly since 6.34rc3. Now also problem with RouterOS + other vendor device is fixed if RFC4638 is supported in both ends. Upgrade your RouterOS device to 6.34rc6.

If you still have some problems about which we are not aware of, then please generate supout file with PPPoE debug logs and send it to support@mikrotik.com

It is good that we have many new users joining into forum to report the same issue and it is completely unsuspicious. :slight_smile:

Do you have any information about what is PPPoE server in your case?
Have you same issues with MTU/MRU 1480?

I just checked my pppoe-clients, and i was not able to repeat the issue with regular MTU.

*) fastpath - fixed wireless interface fastpath (broken in 6.33);


What was the result of this in 6.33?

in greece pppoe client is using 1492 mru mtu
i have to downgrade back to 6.33 to keep using that number
with 6.33.1 it was in a connection loop and never connected.

I upgraded my office CRS125 before doing any client units (our usual procedure) and 6.33.1 broke my PPPoE connection (MTU=1480) - not even creating a new PPPoE client would allow me to connect. I downgraded back to 6.33 and connected again immediately using the original PPPoE Client profile.

I’m hanging back on further upgrades until this PPPoE bug is fixed.

In my case, the connection is with the ISP. I have no way of knowing if it supports RFC4638.
It worked well before, not now.

Could someone who downloaded the Grand Unified Torrent™ for 6.33.1, please seed? It’s stuck at 81.88%.

Same Problem here with PPPoE-Client Connection.
ROS 6.33.1 do MTU 1480
Possible ist 1492 but the Connection is always done in 1480.

mistry7

Simple queue not working v6.33.1, Could this be an RB750 r2 mipsbe firmware issue? http://forum.mikrotik.com/t/rb750r2-mipsbe-simple-queue-not-working-v6-33-1/93154/1

Although I was saying that 6.33 provided its version number to Dude 4b3, now I have to say that 6.33.1 definitely does not. All devices in device list with 6.33.1 lost their version value.

Mikrotik, did you any undocumented change on snmp oids or what?

Hello, can someone give some example how to use the vlan-mode and vlan id on the virutal ap ?
i cant figure out how do make work

thanks

I found the same issue of KVM in x86 not functioning. It just showed starting but not running.
I have to restore back to 6.32.3

Attempting to use Webfig gives “Error: Not Found” at the login screen for some source addresses (I can’t quite figure the pattern out: I was at one point trying 0.0.0.0/0 and ::0/0 as permitted and still have the problem when accessing remotely). Works reliably when connected via L2TP+IPSec VPN. Worked OK with 6.33.

I hade the same issue when connecting through https after upgrade but fixed it by clearing all local cache in my browser (firefox). Give it a try and see if it helps.

*) fastpath - fixed wireless interface fastpath (broken in 6.33);

Doesn’t seem to be the case, at least with NetMetals (wireless-cm2 package used, Nv2, wireless interface queue set to only-hardware-queue) performance worsens with it enabled.

I upgraded my RB951G-2HnD from v6.30.1 to v6.33.1 and immediately after doing so the PPPoE connection stops working to my ADSL bridged modem.

I had to downgrade back to get PPPoE working again..

Looks like we might have some issues with PPPoE in the release.

My pppoe-out1 is configured the same. It stops working and never connects upon upgrading to 6.33.1 and I had to downgrade back to the version that was working.

Really disappointed, especially since when I tweeted about it and got no reply from mikrotik on twitter.

purana - In 6.34rc11 it is fixed. At least all of our clients who had these problems reported back that now it is fixed.