EDIT: Found the problem. I added default routes for each VLAN to use with marked routing, but had removed the “default” default route for Eth1, and that, for whatever reason, killed all incoming traffic.
There’s probably a simple answer to this, but I’ve spent the last few hours trying to get remote access from winbox to work on my 493AH. Is it a NAT or Filter rule that has to be added/modified? Right now, it’s taking traffic from ports 2-8 and mangling it to different VLANs on Eth1. Outgoing seems to work fine, but I need to be able to connect to the router via Winbox from outside, and to enable WAN ping as well.
You’re going to have to post your firewall rules at a minimum for anyone to help. The 400 series don’t have any firewall filter rules on them by default, so if you can’t access it remotely, or ping it, then you have a firewall rule on input that is blocking it, or you are forwarding more than what you want to with a NAT rule.
Here is my current firewall config; I have tried disabling all the rules at once, but I still cannot get to the WAN interface via WinBox, nor can I ping it.
Ok, it looks like you don’t have any rules to force the router to remember what interface connections came in on. I’m assuming based off of your mangle rules that you have 6 WAN connections and each is going out using a different VLAN?
If my assumptions are right (no way to tell without you providing the necessary information) then the problem comes into play because without making mangle rules for the router to remember what interface a connection came in on and to make it reply back over it, then it falls through to the main routing table.
From the PCC Wiki, adjust the rules to fit your needs.