have you tried defining default gateway within wg for u1 & u2, as respectively c1 & c2?
hence routes that get pushed to the wg peers:
https://help.mikrotik.com/docs/spaces/R ... uard-Peers
Sure it does, that's what the _core_ role of routing is...Just by setting up routes, the traffic does not get forced trough the IPSec/GRE tunnel.
and the Chinese copy of this TP-link https://www.cudy.com/products/gs108e-1-0 is only $27 and that's sad.
If the tests are not representative of real-world use-cases, how should I have used these as devices are not being compared in tests that matter?off course, is a common misconception, there are to compare devices, not to be representative of some scenario
the possible scenarios are infinite
did indeed, it's doing its thing, but with little to no headroom, hence the question. Would like some (more) peace of mind, that if anything ...Did you already test if the device as-is performs according to your needs ?
I love ityou say it like you've never worked for support, translating from human to techspeakeverybody is lazy and writes/tells minimum-minimorum of information, expecting others sharing same context and common sense... which is not that common.
These seem to contradict each other?Now the router responds correctly even on the secondary WAN, with the exception of Wireguard.
Furthermore, I would like to make the firewall reachable from the secondary WAN, regardless of whether the primary WAN was Up or not.
not quite true, see previous linkCorrect, but once a packet matches the fasttrack rule, no other rules are processed
it effectively works as "accept all"
Just for posteriority, this is NOT the case: Mikrotik always reports full bandwidth over all directions -> that 1Gb/s is shared for both directions!The 1Gb/s links are full duplex.
Don't believe that to be the case: I think the port attribution of all independent links is fixed, (but I haven't tested it...)1) If we are talking about 5 independent ports: the two 1Gbps links will be used, as needed. There is no hard assignment of a link to a group os ports.
Thx for reaction. Disabled routing was mentioned with beta1, so that was a given / known. But what about the rest? Once bugs are ironed out and routing added, will that be v7.0?No, BGP and MPLS are not even enabled.is the current beta functionality-wise complete
I was thinking LACP between Hyper-V & SW3.I'm not sure, but as I know, LACP cannot be set when there is only 1 connection between switches (sw1->sw3 and sw2->sw3). How to set LACP in this scenario?
add action=accept chain=forward in-interface= bridge out-interface="eht1 Internet"
you're out of context, read last few posts. hint: i've commented on the src-nat!You can force any DNS request to use your DNS by using dst-natthese are not needed as dns is on another network
will a wireless bridge pass the xSTP related frames?Can also add a device each side of the wireless devices then use RSTP
which is exactly what the script does...You can always log in via FTP to create a folder and/or copy/move files.I am some shocked.
A script on 200+ lines is needed just to create a folder in RouterOS.
This is some MT should add a built in function.
/ip firewall nat set [find where action="masquerade"] !src-address out-interface-list=WAN
To access global variables, "policy" right is neededSince RouterOS v6.42 Netwatch is limited to read,write,test,reboot script policies.
If you enable "vlan-filtering=yes" on 4011, all vlans will need to pass over cpu. On CSS3xx it's in hardware.what do you mean by "Note that the 4011 doesn't doe vlan filtering in hardware."? It could make this any trouble? Or it's just for info?
This is NOT the case, switch chip are different and with different capabilities: nand, ram, cpu...to have an identical hardware...
lolYou don't seem to be very good at hiding addresses.![]()