Mikrotik Remote Access via Winbox

[to0kenZA]

Good day guys,

I was wondering if any Mikrotik experts here would be able to help me with a solution to a weird problem I'm having.

I have a Mikrotik at a client that I need to remotely access, but having a bit of an issue accessing remotely with Winbox.

The router has been set up with two PPPoE interfaces. One for their data and another IPC ADSL account for their hosted PBX system.

The router has a default route using the data pppoe interface and then a static route to the SIP server via the VOIP pppoe account.

When I connect to the RB with Winbox on the data interface, it works fine, but when I connect to the VOIP ADSL IP, it refuses to connect, even though I can connect to the WebGUI (Which sucks balls!) on the VOIP interface. So, the routing works correctly but it refuses to connect on port 8291 on the VOIP interface.

Does anyone perhaps know if an inherent issue with MikrotikOS that only allows Winbox access through the default route? I cannot for the life of me understand why it's refusing to work. I can even see the connections on port 8291 coming from my source IP.

 

[morkhans]

Do the torch on both interfaces when connecting via the VoIP interface, you'll probably find that the return traffic on both the web gui and winbox is coming back out the default gateway. Basic rules of routing. Winbox probably just doesn't like the fact that the return traffic is a different IP, web browser might not be as fussy.

Some devices have a routing rule that you can setup to route based on the incoming interfaces (i.e. route it back out the same interface it came in on), not sure if RouterOS can do that though. Take a look a policy based routing.

Quick fix is another static route for your source address (assuming you have a fixed range) out over the VoIP interface.

 

[to0kenZA]

Do the torch on both interfaces when connecting via the VoIP interface, you'll probably find that the return traffic on both the web gui and winbox is coming back out the default gateway. Basic rules of routing. Winbox probably just doesn't like the fact that the return traffic is a different IP, web browser might not be as fussy.

Some devices have a routing rule that you can setup to route based on the incoming interfaces (i.e. route it back out the same interface it came in on), not sure if RouterOS can do that though.

Quick fix is another static route for your source address (assuming you have a fixed range) out over the VoIP interface.

Hi morkhans, than you for your response.

I am connecting to the IP of the PPPoE interface to so traffic is indeed coming in via that interface. Their is also a static route to my source IP, so technically, it should be coming in and out via the same interface.

I checked the torch just to be sure and the requests from my source IP is definitely only hitting the VOIP interface. Traceroute to my source IP is going through the wrong interface though, for some reason, even though the route is active and says reachable.... That will most likely then be the cause of the problem. Thanks!

 

[morkhans]

Does inbound SSH work via the VoIP interface?

You haven't locked down access to winbox port under IP -> Services or with firewall filter rules?

 

[to0kenZA]

Does inbound SSH work via the VoIP interface?

You haven't locked down access to winbox port under IP -> Services or with firewall filter rules?

Everything works hey- I can telnet, ssh and http to the VOIP interface. It's literally only Winbox that's not working. I've had this many times before with Mirkrotiks. I have gotten this particular router to get all traffic to go in and out to the same interface but I'm still having the same issue.

So ya, back to square one!

 

[morkhans]

Strange indeed, sorry but I'm out of ideas.