I don’t know if that module is the same, but if it is, then you’ll create a vlan 8 interface on the SFP interface, and add your pppoe dialler to the vlan8 interface

Whoa, and speaking of VRRP bugs, you can't have more than one IPv6 address on a VRRP interface, or they both stop communicating.. Same with having an IPv6 address on the VRRP interface, and on the parent interface. What the?!? Actually, after some testing, when you set the V3 Protocol to IPv6, it t...

Appears to be just cosmetic. 8000 byte ping packet works when sourced from vrrp IP address with do-not-fragment set. It's more than cosmetic. It appears like a bug. Try pinging TO the vrrp IP address, FROM the non-VRRP IP on the same router.. It enforces the 'cosmetic' MTU :( i.e. vlan39 - mtu 9100...

Ok, so I borrowed an RB951-2n, and an RB2011-2HnD-IN from work for the holidays to do some more in-depth testing, alongside a spare CRS-109-8G-1S-2HnD-IN. Rolled all three back to 6.40.9 and defaulted configuration. Some interesting notes.. 1) CRS* looks to be the only platform which supports vlan-e...

Thanks tdw, I'm thinking there's an actual problem hardware-wise on the CRS109 then :( I've just replicated your config onto one of my spare CRS109's, and still have the issue where packets from the wlan are still tagged vlan100 when passed out the ether interfaces. So tempted to just buy a bunch of...

Hey Anav, Thanks for your reply :) Unfortunately, that didn't work - couple of reasons 1) As I mentioned, the new RouterOS bridge code doesn't support hw offload on the crs1xx platform, so max throughput available would be about 50mbps. But besides that 2) that would be pushing all traffic out the e...

Hi All, This has been driving me nuts for weeks. Our local Mikrotik mail list hasn't been a huge amount of help - seems like it's just broken behaviour in RouterOS, and no amount of workarounds will fix it permanently. Hoping someone here has a solution :) I have a bunch of CRS109's both at home and...

O that is interesting, that must be some bug/feature introduced in RouterOS recently! When I first received my SFP, it worked fine with auto-negotiate off. I had 1500 byte MTU all working (same as how you wrote above) and the only problem was I did not get my expected line speed and there is no way...

Couple of thoughts.. 1) Re the TG589: make sure you have also increased the MTU on the TG589, or you're simply not going to be able to use packets larger than 1500 with it. You can't JUST increase packet size on the Mikrotik side.. :) 2) Whoever said turning off autonegotiate was the way to go with ...

I’m on 6.41.1 on a CRS-109

It's funny, the VDSL link itself comes up fine no matter what. It seems to be the bridge between the VDSL interface and the SFP interface that just doesn't come up. Whatever it is that makes the interface show as 'Running' in RouterOS basically. I haven't been able to make the SFP go into 'Running' ...

As far as I understand to get stats I'd need to send an ethernet frame with an command/query to the SFP (with the SFP MAC as destination) and would get an response with the requested data back. Would be nice to get this working even if not directly on RouterOS but from an host connected to an route...

Sooo, you've had them three days... Do they work for VDSL? I can't imagine having these things for more than an hour without having tried to get my VDSL up and running with them C'mon man, you're killing me with the suspense!

Hi Folks, I emailed Mikrotik support about this almost a month ago, but haven't had a reply, so hoping someone on the forum here can help! We bought a CCR-1009 just over a month ago, to try to drop our power usage (we've been using an old HP DL360G3!), when we moved into a new datacenter. Our config...