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.
Possibly, but that would be a really strange setup. It is very unusual to establish OSPF neighbor with another ISP. You would typically use BGP in this role.Can you run two instances of OSPF between the same two routers (with multiple loopback addresses, etc) and make this work?
You might be able to do this with BGP, depending on your topology.Any other option? Another routing protocol? multiple OSPF instances perhaps?
Yes, exactly. Also as an ISP it makes sense to allow most (if not all) ICMP - it makes troubleshooting much easier.So, other 'regular' traffic should pass then, correct? Unless it's specifically blocked in the firewall of one of the routers. Correct?
Add two firewall rules to allow all ICMP on input and forward chains and move them to the top of the list on all three routers, then try the ping again.I've typed /24 too many times. Yes, it's 0.0.0.0/0 on all routers.
Yes it does - why would it not?Really? Will this work without intetnet? Cos i've tried a few hotspot guides from here but most requires internet connection to work properly.
What radios are you using?I don't find any good document about it, if is possible get some help that how can I configure it.
I don't have any QOS or priority configuration on routers / links.
I think what you want is PCQ - please see: https://wiki.mikrotik.com/wiki/Manual:Q ... Q_Examplesit will effect only connection limit?? then what will i do for bandwidth limit???
This is excellent news - does this also work with DHCPv6 servers over PPP (ex. PPPoE)?*) dhcpv6-server - added RADIUS accounting support;
can you run /ip route export and paste the results? And the same for /ip route print?I will try a config reset later on Router 1. For the time being it's working in the opposite traffic flow.
That doesn't look like the right connection, port 443 is not BGP. You'll need to share more config than just that one screenshot to allow for troubleshooting.Does anyone have a hint on what i could start looking? It's appreciated.
Confirmed that Google DNS is resolving the 6.43.x new IP cloud names but not Cloudflare DNS from here as well.There is a difference between DNS resolvers:
Firmware is 6.43.2 on CCR1036-8G-2S+ for example. This looks like connectivity problems, and nothing to do with old/new.
Through what feature - DHCP? Hotspot? PPP? Can you execute "/queue simple print" and show the output? Printing the list will include all dynamic queues as separate items.The Child Q's are created dynamically
Then how many OSPF routers and how many routes?160 device but ospf not working all of them, for example p2p links connected with /29 , AP's with connected to powerbox with /30. Only power box or Rb1100 works with ospf if AP attached on it or if any p2p link
I think the address-family="" in your reject rule is probably causing it to not match anything.Why are the /32 routes installed and active? Seems like the prefix-length=16-24 filter attribute is handled incorrectly.
Already contacted MT support two days ago, no reply yet.
At this point I would probably recommend a netinstall to a 6.36 or 6.37 release and restore the config on that version, then upgrade to a newer release./tool fetch url=https://download.mikrotik.com/routeros/ ... c-6.37.npk
If you have two bridges on one chip it will only be able to hardware accelerate one of those two bridges (this was also the case before, where you could only have one master port per switch chip).I have one bridge on the gigabit chip and 2 bridges on the fast chip.
*) dhcpv6-server - recreate DHCPv6 server binding if it is no longer within prefix pool when rebinding/renewing;
Can you clarify what you meant by deactivated bridges - did you have a bridge created but it was disabled? Maybe this is why the conversion failed, if it wasn't expecting this.I changed the L2 MTU to 1500. I think because of the Airport Extreme.
Excellent! Glad that helped. It is not always unusual for there to be a delay when making major routing changes.Sorry for delayed edit! The problem is now solved. I don't know why now, but in some cases I have seen delayed reactions on some lower level Mikrotik routers (like RB750).
Then, the most likely problem is that your other routers are probably missing a route to the 192.168.134.0/24 subnet, and can't get the reply packet back to the PC as a result.It can ping ONLY IPs bound to that router, and nothing else.