add action=drop chain=forward connection-state=invalid
Ok, I hope you don't release 6.32 before this is fixed, because RouterOS without working firewall filters is nearly uselessdadaniel - Issue is not fixed yet. It is reported to developers.
This could be very hard, because you have to be lucky to catch the moment when it is uploading to some other client. I cannot find any information about protocols and ports used anywhere.You will have to sniff the traffic to see what protocol is used.
No, it will kill my bandwidth. Default setting in non-VL editions of Windows 10 is to upload to other users on the internet.but why? it will save your bandwidth
Is this fasttrack rule replacing the default "accept connection-state=established,related"-rule or do I still need it?best is to fasttrack connection-state=established,related
It does only make sense to use FastTrack on specific (known) connections before they enter filter/other routing chains. Using it afterwards makes no sense at all...Why not to mark packet at mangle postrouting?
Is there any SXT shield kit available?Got my first batch of SXT AC and SXT AC SA.
802.11af works fine. The non SA Version does not have a shield painting inside.
So for ptp on a loaded tower some additional shielding might be neccesary.
Try this: http://aacable.wordpress.com/tag/mikrot ... detection/is it possible???
This field is empty, only local address is visible.(I suppose default Gateway: "remote-address"):
I will try this, thank you.as this is tunnel interface you can use interface name as default gateway. And you can assign static name for PPTP-out tunnel.
Will this VLAN processing run at hardware level and is capable of wire-speed?That VLAN rule table does not apply to CRS125, the features which will allow similar functionality are currently being developed.
Your e-mail-support is very good, but getting an answer takes way to long. I do not have the time to wait 1 week for each reply of the same case number. Sorry...In support emails, 90% of bugs are not bugs, but mistakes.
sorry, I forgot to add "wirespeed VLAN capable (via switch chipset)"Every single one, because RouterOS implements 802.1q
Hello,has anybody written to support@?Doesn't appear to be even acknowledged by MT as yet, even though there is more than one report of the issue mentioned on this topic.