v6.29 released

RB433 with some rules but it is not used to pass user traffic. It is testing VPN far end with IPSec over GRE tunnel.

5 1/2 h uptime = 18 500 sector writes

24h → 30 978 Sector Writes Since Reboot

working great on my RB2011UiAS-2HnD. Tested throuh winbox and console.

why i cannot connect to romon devices behind rb951. i get the message “disconnected from romon”
i am using winbox3rc10 and 6.29 to all my devices.

Hi
I have got router with 6.28 working fine 2 peers bgp and pppoe server.
After upgrading to 6.29 some pppoe clients are connecting and disconnecting.
Second problem is trafic on some sfp ports winbox shows the same traffic on few ports.

Cha0s
Seems to be something about how the onfiguration system works, as I often came across the same behaviour during operation of a single version. Something breaks and is only fixable with config reset or netinstall. As I have no clue how the config system is implemented, I can only guess that some residual config files generated for the diverse components end up corrupted.

Hey guys! I want to ask some help and clarification. I use ovpn to connect RB2011-s at my users homes to the RB1100 in the office, just corporate VPN. After upgrading to 6.29 I cant reach from one vpn client to another. As I red here it must be related to the subnet mode. What should be changed in config to get vpn clients to communicate again? Before that it was just enabling proxy-arp on the server side, what should I do now? The server’s LAN address is in the same subnet as vpn clients with netmask 24.

No, default configuration - home router. Ether1 as master connected to provider’s ONT (GEPON).

There is other BUG in v6.29 released BGP-VPLS

IMG-Error_BGP-VPLS.jpeg

After upgrading, my two CAPs started to broadcast (?) permanently with about 4 kbps.

Downgrading to 6.28 fixed that problem.

Confirmed. I can reproduce this on my BGP-signalled VPLS setup.

VPLSes which are set to auto-attach to bridges result in an invalid port being added to the bridge when the VPLS comes up.

Adding the VPLS interfaces manually to the bridge works fine.

Just repeat the question. Please do not ignore him again.

How does it work? Which fields are used? What netflow collector understands them?

Those users woh has a problem with PPTP and encryption please try out 6.30rc if it is possible. We have introduced a fix which should solve this “got out of sync” problem.

Confirmed

I can confirm, on every device I have upgraded to 6.29 (via System → Packages → Downlad & Upgrade) I see that SNTP client can not get time from server. No logs for that, but I see how time changes.

The only hope is for “IP → Cloud”'s time client but I’m not sure what protocol and server it depends on, and I see no logs for it, too.

Will we get the fix in 6.30?

Since it works for all of our devices - make sure your NTP server works and try a different one

We have made a quick fix, released as v6.29.1 to address two issues that we found after releasing v6.29:

What’s new in 6.29.1 (2015-Jun-01 13:30):

*) fixed vpls bridging (introduced in v6.29);
*) fixed problem where some CRS could not be reached (introduced in v6.29);

If you use a CRS or VPLS, please upgrade. There are no other changes in this release. Avoid using v6.29 on CRS, upgrade directly to v6.29.1 if you are still using an older version.

Fantastic!

Thanks for the very quick fix to address the VPLS bridging issue.

I have just tried to upgrade a number of my devices and part way through the latest version changed from 6.29 to 6.29.1 (which I understand is a quick patch that has been released) but now the latest version is showing as 6.28???

Has 6.29(.1) been pulled?

EDIT: and 5 minutes later it is back again!!

Steve