IPv6 is not dead, it is growing. IPv4 is dying. IPv4 NAT cannot handle what is coming in the future. Companies don't feel under any pressure to move, but cell providers are moving and home customers are getting IPv6 at an increasing rate.never seen anyone using ipv6
They still have to implement MPLS - I think that is the one major feature still missing from the current beta. Otherwise, there are probably many small fixes needed here and there.Any time frame to move off development phase and make it ready for production / stable?
Yes, now you should find that if you try logging in as the user a second time, the first one actually gets disconnected instead of simply passing no traffic.Okay, thanks. I found that option. It was disabled. So now in Splynx, both POD + clean and COA & POD is enabled. Should be fine right?
They gave me this same response a year ago.I Know they have not given any ETA, but atleast it gives all of us a hope.
I had ticket 2018070222004763 for this, but it was in the older OTRS system they used before they moved to JIRA.Do you have a ticket number?
It hides the columns on the right if your terminal window is not wide enough to show them. Make your terminal window wider before running traceroute, or use the graphical traceroute in Winbox.In my environment I just get 8 columns
This is because they only added support for DHCPv6 RADIUS accounting in that version where PPPoE is not used. If PPPoE is used, it is still not supported.
It is Still Not Working Normis.
We are getting only Remote Prefix but Not the Delegated IPv6 Prefix
This is already in RouterOS as of 6.47 (FWD records in IP->DNS->Static).My features wish list:
- dns: action redirect requests to external DNS (regex or domain filtering)
OSPF is completely rewritten in v7 so I would be surprised if this bug still affects v7. There probably will be some all-new bugs to contend with, though (fun fun).I have experienced this multiple times. I logged a ticket with Mikrotik and got the usual "Fixed in v7" answer.
You need to give your router's bridge interface an IP from the prefix pool:I found several discussions about IPv6 within this forum but still I'm unable to figure out how to properly configure it and make it work.
/ipv6 address add address=::1 from-pool=my-ipv6-pool-1 interface=bridge
Check /ipv6/settings in CLI to see if disable-ipv6 is set to "yes".I cannot find ipv6 link local address in any ipv6 interface. Rebooting doesn't help too.
I can reproduce the tcp/564 connection on my own RouterOS 7 device here. I agree with the OP that RouterOS 7 devices do appear to be listening on that port.2000 is the btest server.
are you testing using nmap on the same the same subnet, or traversing another device?
I was actually replying to networkmonkey - I'm afraid I don't know anything about Huawei equipment, never used it, so I have no idea what you want to do.Will try Thanks!
Are you sure three tries is enough to properly test it? When I see your screenshots above, I see that you had problems resolving facebook on the fourth try but the first three were OK. But you are sure the CCR is OK after three tries?I got as like below image
This answer makes no sense. Do you mean you are only using PCs on that VLAN? I don’t know what you mean by “on DHCP”.On DHCP im using direct PC's only.
You’ll need to also check “other configuration” box if you want Windows to get DNS server addresses from DHCPV6 server on MikroTik. If they don’t get DNS v6 after that then you have not added DHCPv6 server for that specific network.This what i did in the IPv6->ND
Have you added DHCPV6 server on that vlan? What neighbor discovery settings are configured on the mikrotik under ipv6-> ND?I have getting Valid IPv6 IP and getting Fe80::... gateway, But not able to get IPv6 DNS,
Can’t you just replace the TPlink devices? Or upgrade them to fix it? Disabling DHCPV6 is not a good solution, IPV6 with manual config is too much work.That issue got TP-LINK routers DUID new each time ...
I've disable DHCPv6 becouse of that ...
I wonder if this might work?Has anyone tried some sort of shielding for these AP's yet?
Seems like with 60GHz it would be more effectively shielded given the beam width?
FYI we have tested this on our devices - DHCP relay is working fine for us on 6.44.5.I got problem with dhcp-relay , after upgrade my client cannot get address.
Now I downgrade to version 6.43.16 it work fine.