Interesting info. A bit early, as you only got it, but I would like to hear your findings on link / connection stability.
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
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.
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.
/ip settings set rp-filter=strict
/interface bridge port add bridge=bridge1 interface=ether2-LAN-OFFICE /ip traffic-flow set active-flow-timeout=1m cache-entries=16k enabled=yes interfaces=ether2-LAN-OFFICE