Yes.So ether 5 is a TRUNK port and not an access port?????
This one solved it, thanks! I know the PVIDs are redundant but they do practically nothing in this setup, so it doesn't hurt either. ROS defaults to PVID 1 and I tend to change it from 1 to one of my VLAN IDs.Code: Select all
/interface bridge vlan add bridge=bridge-lan tagged=bridge-lan,ether5 vlan-ids=20
No idea, but possible.Is he trying to use Winbox to connect
I assume that's a rhetorical question.how would you route a Winbox connection through a socks proxy?
Good! Thanks for the feedback. Your attacker was a particularly malicious one, almost locking you out completely. Almost.Now I can remote login to the infected router with user "sys" via SOCK
It would be really useful to bump that post with today's date and tag with (UPDATED) or something.We have added more details, so that it is more clear:
https://blog.mikrotik.com/security/winb ... ility.html
Maybe this helps a bit.Does anyone have the depth of the new CRS354-48P-4S+2Q+?
I am curious if it will fit into some customer wall mount racks.
I would highly doubt that the existing name servers would be having degradation from legitimate updates or queries.
The installable x86 version does include virtio drivers, I use virtualised ROS instances at multiple places (on KVM, not Xen) with virtio, without problems.For example x86 don't have virtio drivers, so you can't install RouterOS on a public cloud like Amazon EC2, Azure, or like it.