Yup, but a default route in main is sufficient to meet this requirement.the main routing table should be able to resolve the destination too.
Have you tried the procedure I have suggested in my previous post?I would appreciate any help or workaround.
Indeed.Would the following mask allow 44:61:32:xx:xx:xx
FF:FF:FF:00:00:00
ip-addressHow it's written correctly?
OK, no firewall filter rules at all so VRRP packets from the other router can definitely get in if they make it through the LAN.Here are the two test routers I have set up.
We finally made it work. What's your current issue with that setup, and what do you need to achieve besides the basic load distribution?How did it end up going?
I forgot again that you cannot set MSS in prerouting or input, so yes, might make sense to set it in output on the CHR as well. The most likely bottleneck is the ISP end of the PPPoE tunnel so it should not be necessary to do that, but who knows.I'm not using any mangling on CHR side tho
The thing is that the choice between R10 and R11 is random, so the fact that your certificate is signed using R10 doesn't mean that @josephny's one will be too; actually, it even doesn't mean that your next one will be signed using R10.I try it on my Mikrotik router using your script:
Look at viewtopic.php?p=980927#p980927Have supout bug reports been sent to MT, on these issues??