You're mentioning dynamic rules ... those obviously don't survive reboots. If you want those higher than static rules, you have to push them up when creating them.they should not yes, but i have this issue and also they will be upper of dynamic rules in raw tab
You can't get that data, it's confidential.i want to know million packets per seconds.
So check firewall on the "problematic" device. Windows firewall by default blocks pings for example.i cantCan you ping wired device from another wired device? The wired device's firewall might interfer ...
I'd upgrade firmware and then check things again. Firmware version 3.33 is pretty old.Current Firmware 3.33
Upgrade Firmware 6.43.4
/system routerboard upgrade
Sure they will fix it ... in ROS V7They can only ignore us for so long eventually they will have to own up to it and fix it.@Normis I 'll post here untill we 'll have an answer
I apologize for my inistence but I need an answer
As OP is running DHCP client on bridge, default route should be dynamically configured by that ... and will not be seen in export (only in /ip route print). Other routes are not needed.Your export is not complete, I see no routes printed for instance
Before loading exported configuration do inspect it in case it contains something suspicious.Ok! that is cool. I have a backup copy of /export file, I will reload script from scratch for security measure.
This.And also you need to specify out-interface=ether1 for your masquerade rule.
Thanks for the link. The example is false, IMO proxy-arp there is abused to fix mistake in L3 config. So I'm still eager to find out why would I want to have proxy-arp on bridge.@mkx
This is just an example.
https://networklessons.com/cisco/ccie-r ... explained/
... and the same goes for DHCP client on sfp1.Other than that, when an interface is a slave of another interface, it cannot have its own IP configuration. So in your case, the dhcp-client on ether1 should not be there ...
Can you post output of command /interface bridge export? Just to check if there's something weird.I found a strange behavior about bridges - might be only WinBox issue but still...
route add -net 192.168.101.0 netmask 255.255.255.0 gw 192.168.100.1
See how your own position is skewing your point of view?So, us, professional users of ROS, ...
> /system package update check-for-updates channel: current installed-version: 6.43.1 latest-version: 6.43.1 status: System is already up to date
... and don't use binary backup to restore configuration ... as you can never be sure when your router was actually compromised. Rather use ASCII configuration exports and check it thoroughly before applying.- if unsure, perform a netinstall to wipe all and start over
You mean changing identity name as inChanging the identity on hAp ac² crashes the router with an error: "kernel failure in previous boot".
/system identity set name="some other name"