Page 1 of 1

Route traffic In Interface

Posted: Wed Aug 24, 2016 6:06 pm
by msbr
Hello..
I need help..
How do I make 10.116.40.190 IP traffic to go out the ETH5 ?
The rest by the ISP that is in the ETH1

Image

Re: Route traffic In Interface

Posted: Wed Aug 24, 2016 6:47 pm
by pe1chl
- assign your MikroTik an IP address in 192.168.25.0/24 on port ether5
- add a route to 10.116.40.190 via gateway 192.168.25.1
- add a route in the cisco back to 192.168.1.0/24 via the MikroTik's address

Re: Route traffic In Interface

Posted: Wed Aug 24, 2016 10:28 pm
by msbr
I am one Bridge in Eth2,Eth3 y Eth4 for LAN (192.168.1.0/24)

1-Should I add the eth5 within the Bridge? Currently it is not

2- This is my commands
/ip address add address=192.168.25.254 interface=ether5 netmask=255.255.255.0 network=192.168.25.0 
/ip route add dst-address=10.116.40.190 gateway=192.168.25.1
Ping From Mikrotik to 192.168.25.1 & 10.116.40.190 is OK
but Ping from LAN is error.
What can be ?

Re: Route traffic In Interface

Posted: Wed Aug 24, 2016 10:30 pm
by pe1chl
I am one Bridge in Eth2,Eth3 y Eth4 for LAN (192.168.1.0/24)

1-Should I add the eth5 within the Bridge? Currently it is not

but Ping from LAN is error.
What can be ?
1. no
2. maybe you have firewall rules in the router that you did not tell us about?

Re: Route traffic In Interface

Posted: Wed Aug 24, 2016 10:45 pm
by msbr
Traceroute from Mikrotik:

Trace to 10.116.40.190 (OK)
# ADDRESS LOSS SENT LAST AVG BEST WORST STD-DEV ST..
1 192.168.25.1 0% 21 0.5ms 0.6 0.4 2.2 0.4
...
...
6 10.116.40.190 0% 21 28.4ms 28.7 28.1 33.2 1

Traceroute from PC
Trace a 10.116.40.190 (ERROR)
1 5 ms 2 ms 1 ms shaas.loc [192.168.1.1]
2 * * * Tiempo de espera agotado para esta solicitud.
3 * * * Tiempo de espera agotado para esta solicitud.

Trace a 192.168.25.1 (ERROR)
1 2 ms 1 ms 1 ms shaas.loc [192.168.1.1]
2 * * * Tiempo de espera agotado para esta solicitud.
3 * * * Tiempo de espera agotado para esta solicitud.





Is there any way to detect what is the rule that is blocking?


Thanks!!!...

Re: Route traffic In Interface

Posted: Sun Aug 28, 2016 12:20 am
by neomega702
You may use torch tool to capture traffic
Also you should use ping tool from mk and send ping from local bridge interface.