It seems that v7.12 stable will not generate OSPF LSA type3 - “inter-area-prefix“ while v7.11.2 stable is ok. Here are configs: https://z1.ax1x.com/2023/11/16/pitmIfK.png [admin@ROS7.11.2A] >export /ip address add address=10.0.0.1/24 interface=ether1 network=10.0.0.0 add address=192.168.1.1/25 inter...

It seems that v7.12 stable will not generate OSPF LSA type3 - “inter-area-prefix“ while v7.11.2 stable is ok. Here are configs: https://z1.ax1x.com/2023/11/16/pitmIfK.png [admin@ROS7.11.2A] >export /ip address add address=10.0.0.1/24 interface=ether1 network=10.0.0.0 add address=192.168.1.1/25 inter...

ROS v7.4. what’s the problem with ipv6 routing table? if I add an ipv6 address on bridge2 , some addresses will be unroutable , even if I didn’t change anything on /ipv6 route. [admin@MT] > ipv6 route pri Flags: D - DYNAMIC; A - ACTIVE; c, d, v, y - COPY Columns: DST-ADDRESS, GATEWAY, DISTANCE DST-A...

Plus "-t" after dig , "dig -t aaaa ntp.6now.cf" , you can find 13 AAAA records.
So i think it doesn't send AAAA query by default in ROSv7.1RC6, like the dig command.
On my device with ROSv6.49, ntp.6now.cf works ok

debug info:

09:18:05 ntp,debug Start resolving name: ntp.6now.cf
09:18:05 ntp,debug Couldn't resolve host name: ntp.6now.cf (dns name exists, but no appropriate record) Try again after 60 seconds.

7.1RC5.

[admin@ROS] > sys ntp client pri
enabled: yes
mode: unicast
servers: ntp.6now.cf
freq-drift: 0 PPM
status: waiting

/ip dns cache print, only SOA record there.

I'm using 7.1RC4.
when "/tool sniffer start", wireguard Rx speed can be up to 100Mbps. But if "/tool sniffer stop", the speed drops to kbps.

An ipipv6 tunnel problem remains in 6.47.4. When pppoe client disconnect and then reconnect, ipv6 address of device is changed , but local address of ipipv6 tunnel is not changed (ipv6 firewall connection print), and the tunnel is down actually. I didn't configure "local-address" value. I ...

An ipipv6 tunnel problem in 6.47.2. When pppoe client disconnect and then reconnect, ipv6 address of device is changed , but local address of ipipv6 tunnel is not changed (ipv6 firewall connection print), and the tunnel is down actually. I didn't configure "local-address" value. I think i...

An ipipv6 tunnel problem in 6.47.2. When pppoe client disconnect and then reconnect, ipv6 address of device is changed , but local address of ipipv6 tunnel is not changed (ipv6 firewall connection print), and the tunnel is down actually. I didn't configure "local-address" value. I think it...

update: First problem, I change it with option "unset keepalive", there is no ipv6encap connection anymore, but I think it's a bug anyway. Second problem, when ipv6 address of device changes for pppoe redialing, the local address of ipipv6 tunnel has no change, and tunnel is down actually....

You can print your configuration first.
/ipv6 export

two pppoe access points , you mean two Access Concentrator ? one main,one backup

If you get internet access with PPPOE, ipv6 dhcp-client interface should be PPPOE interface. Ipv6 address setting is also needed ,it will be addressed from the pool of your prefix requested by dhcp-client. /ipv6 address add address=::1 from-pool=v6-PD interface=bridge /ipv6 dhcp-client add interface...

I think you can try this way:
Just have a try , i didn't test it.

Nothing in your example addresses his public IP issue.

Can you explain why ?

I think you can try this way: /interface bridge add name=LAN-bridge add name=WAN-bridge /interface bridge port add bridge=WAN-bridge interface=ether1 add bridge=WAN-bridge interface=ether2 add bridge=WAN-bridge interface=ether3 add bridge=WAN-bridge interface=ether4 add bridge=LAN-bridge interface=e...

/ipv6 dhcp-client add add-default-route=yes interface=ether1 pool-name=rogers-ipv6 request=prefix use-peer-dns=no
You can try to request prefix only ."address" here means WAN side address I think, it's not necessary.

I think, DHCPv6 server should be stateful and providing a shorter than /64 block, such as /60 , then your DHCPv6 client device can get a /64 with DHCP prefix delegation.

If you ISP gives you a private address through PPPoE yes it is, but if the ISP assigns you a Public IP through PPPoE no it is not...

Why not be a choice there? I can choose v4 or v6 updating by myself.

Ipv4 address of pppoe is always behind a NAT of ISP. Updating IP Cloud ipv4 address is meaningless.

Does anyone have any opinions ?

I configured an ipipv6 tunnel between two MT devices, all with v6.46.4. When checking ipv6 firewall connections, I found a protocol=ipv6-encap connection, just like this: [admin@MT] > ipv fi co pri de Flags: S - seen reply, A - assured 0 S protocol=ipv6-encap src-address=2409:8a20:abcd:ef00::1 dst-a...

RouterOS version 6.45.7 has been released in public "stable" channel! Before an upgrade: 1) Remember to make backup/export files before an upgrade and save them on another storage device; 2) Make sure the device will not lose power during upgrade process; 3) Device has enough free storage...