SSH not working to WAN IP

Me again:) with a semi-bizarre issue.

I’ve gotten my entire configuration working (with quite some help :slight_smile: ) so I thought it might be useful to be able to manage the router when I’m not home.
SSH, WINBOX, … - you name it - all work as long as I’m in the LAN. But I can’t even ping to the WAN IP at the moment.
I am using RADMIN to connect to a remote computer, which I then use to ping and send traffic to the Mikrotik router. So I’m not pinging nor SSHing to the WAN IP from within my own LAN.

As you can see below, I’ve temporarily disabled all firewall rules to make sure that isn’t causing the problem.
Could someone explain to me how I can troubleshoot this. My most likely suspect is that the Mikrotik’s WAN port is part of a WAN-bridge together with a VLAN. I’m using this VLAN for devices that should not be firewalled and should recevice public IP’s from the cable ISP. Or -perhaps- the SSH server isn’t listening on the WAN IP and only on the LAN IP.

I can post more settings if needed and of course I’ll report back if I happen to find the issue myself:-)

Cheers,
Jeroen

/ip firewall filter

Flags: X - disabled, I - invalid, D - dynamic
 0 X ;;; Drop invalid connections
     chain=input action=drop connection-state=invalid

 1 X chain=input action=accept protocol=tcp src-address=0.0.0.0
     dst-address=81.165.200.20 dst-port=22

 2 X ;;; Allow established connections
     chain=input action=accept connection-state=established

 3 X ;;; Allow internal LAN to connect to the router (required for DNS!)
     chain=input action=accept src-address=192.168.0.0/24 in-interface=!WAN

 4 X chain=input action=log log-prefix="Dropped:"

 5 X ;;; Drop everything that is not previously allowed
     chain=input action=drop

I’ve deleted my bridge and assigned the WAN IP to my WAN interface instead assigning it to the brigde. Then everything decided to work. I’ve then recreated the brigde and set everything to what it was when it did not work, except now it does work.

Must be some glitch:-). :confused:

Blast, sorry for the posting frenzy but it stopped working after a reboot. If I do not assign the public IP to the WAN interface (ether 5) I cannot ping the routers’ WAN IP.

So the question is: why does assigning the public IP to the WAN-BRIDGE cause the router to stop responding to pings?