Anything changed regarding dhcpv6 server? anyone noticed a problem?

Dear MikroTik, I’d like to request a feature that would greatly benefit many FTTH deployments: PPPoE Offloading/Multithreading. Currently, PPPoE is processed on a single CPU core, which can become a _bottleneck_ . Offloading PPPoE or leveraging multiple cores would boost performance and by eliminate...

PPPOE-client is a single thread on MikroTik, and it is handled by CPU, no hardware offloading.

why don't you use IPv6? router should be reachable.

/56 can be split into 256 networks with /64 , minimum you may use for any interface is /64 Starting 2a00:1234:0567:0b00: to 2a00:1234:0567:0bff: Assign any of these /64 addresses to an interface and let SLAAC do the rest, 'advertise', and route ::/0 to pppoe-out1 and you may use 2a00:1234:5678:11::/...

CCR2116 is connected to 3810m, bonded connection LACP, OSPFv3 state is stuck on LOADING' 7.14rc1 CCR2116 /routing/ospf/neighbor> print Flags: V - virtual; D - dynamic 0 D instance=ospf-instance-ipv4 area=ospf-area-ipv4 address=10.255.1.2 router-id=10.255.255.2 state="Full" state-changes=5 ...

I think it is called 'pppoe relay' which is not available on RouterOS, here are other methods you may try, - Keep pppoe and NAT on mikrotik and change watchguard to bridge mode 'transparent mode' https://www.watchguard.com/help/docs/help-center/en-US/Content/en-US/Fireware/networksetup/net_config_br...

CCR2116, OSPFv3 has a problem on 7.14rc, downgrading to 7.13.4 solved the issue.

Tried to netinstall into a version not know to have the issue?

Confirmed, WireGuard is blocked by ISP. Unlikely, but try changing the port number. Btw, this is OT thus please create a new thread to continue troubleshooting. Just noticed multiple reports about WireGuard failing to connect on the same ISP; you can disregard my previous comments about any possibl...

Confirmed, WireGuard is blocked by ISP.

/ip firewall filter add action=accept chain=input comment="allow WireGuard" dst-port=13231 in-interface=pppoe-out1 protocol=udp add action=accept chain=input comment="allow WireGuard traffic" src-address=10.100.100.0/24 add action=accept chain=input connection-state=established,...

/interface bridge add name=loopback port-cost-mode=short /interface wireguard add listen-port=13231 mtu=1420 name=wireguard1 /interface vlan add interface=sfp-sfpplus4 name=GPON vlan-id=10 /interface bonding add mode=802.3ad name=bonding1 slaves=sfp-sfpplus1,sfp-sfpplus2,sfp-sfpplus3 transmit-hash-...

CCR2116, WireGuard isn't working, replaced it with ZeroTier, in details: - delete and re-add the peer may solve the problem but once you disconnect you can't connect back. - It shows 94bytes received, 'Handshake did not complete after 5 seconds' - Same behavior on iPhone, iPad, Windows and MacOS - T...

Any reported wireguard problems?

CCR2116 has AL73400 16 cores @ 2000 MHz, Switch chip 98DX3255
CCR2004 has AL32400 4 cores @ 1700 MHz, no switch chip, PIPE 98PX1012 "Passive Intelligent Port Extender"

Theoretically CCR2116 >>> CCR2004

Try 7.12rc4 ,
*) system - fixed process multithreading (introduced in v7.9);

must be firewall, ?forgot to change address list or allowed list etc..

it's just a simple interface pppoe client

/interface pppoe-client

Hi, due to PPPOE being single threaded CCR2116 can't do more than >2gbps as PPPOE client, is there a way to make this process multi threaded or hardware offloaded?

It is very very quiet recently - in both beta and stable threads.
Not sure - it might be a good sign?
Maybe even a v7 long-term on the way?

it's not as frequent as before, maybe vacation time?

CCR2116, problem with IPv6 routing with OSPFv3, going back to the stable version fixed the issue.

Feature: ability to interact with Ansible, and script running capabilities e.g Python/Netmiko for network automation.

interestingly CCR2116 has better temps after 7.11 upgrade, with 20% min fan speed.

Hi, I just noticed that only one core hitting >50% when the CCR2116 ~ 1gbps on PPPOE, is this expected behavior? PPPOE is a single thread process?

+1 maybe v7.10? v8?

Not sure if this is related to the mentioned IPv6 malfunction, nevertheless, IPv6 wasn't working well on 7.9 /CCR2116 after upgrade, a little investigation showed removing IPv6 firewall filters fixed the issue, further digging showed interfaces list was messed up, particularly LAN list with 'unknown...

Confirmed 7.9rc2. ccr2116