Page 1 of 1
simple routing ... need help
Posted: Thu Aug 03, 2006 12:59 pm
by d3v4
hi guys
i want to ping via mikrotik box set as a router, but can't work.
client ---------------- eth1 mikrotik eth2 ---------------------------- cisco
192.168.10.1/30 -------- 192.168.10.2/30 (eth1) 192.168.10.253/30 (eth2) ------------- 192.168.10.254 (cisco)
in mikrotik route : /ip route add gateway=192.168.10.254
the client can't ping the cisco router via mikrotik. why ??
please help !!
Posted: Thu Aug 03, 2006 1:12 pm
by cmit
Does the client have a default route to 192.168.10.2?
Does the Cisco also have a /30 netmask?
Best regards,
Christian Meis
try this
Posted: Thu Aug 03, 2006 1:15 pm
by gio9779
What default Gateways have you put?
You dont have to tell the Mikrotik Router about the networks because its directly attched to both.
BUT,
the cisco router doesnt know the clients network and the client doesnt know the cisco network.
try add in the cisco, a route that points to the mikrotik for the client network whole slash /30
then add on the client either a default 0.0.0.0/0 to the mikrotik or a route to point to the mikrotik that shows the cisco network
BTW also check your firewall rules to make sure youare allowing ICMP packets
Posted: Thu Aug 03, 2006 1:22 pm
by d3v4
thanks for the fast replay
client ------ eth1 mikrotik eth2 -------- cisco
this is the configuration :
client : 192.168.10.1
netmask : 255.255.255.252
gateway : 192.168.10.2
mikrotik eth1
ip : 192.168.10.2
netmask : 255.255.255.252
eth2
ip : 192.168.10.253/30
netmask : 255.255.255.252
/ip route add gateway=192.168.10.254
cisco :
ip eth : 192.168.10.254
netmask : 255.255.255.252
ip serial : 192.168.100.2
netmask : 255.255.255.252
ip route 0.0.0.0 0.0.0.0 192.168.100.1
no firewall added in all the router and client.
client still can't ping cisco via mikrotik, why ...
Posted: Thu Aug 03, 2006 1:23 pm
by cmit
Then it probably is the missing route on the Cisco...
Best regards,
Christian Meis
Posted: Thu Aug 03, 2006 1:26 pm
by d3v4
i put this in the cisco router
ip route 0.0.0.0 0.0.0.0 192.168.100.1
but the client still can't ping cisco
it's look like mikrotik can not pass connection from client to cisco
Re: simple routing ... need help
Posted: Thu Aug 03, 2006 1:29 pm
by balimore
-------------
Hai,
Gimana kopi lampungnya masih banyak ga', kalo masih kirim donk ke gue, karena udah lama kagak menikmatinya. tentang buat route anda bisa buat dengan single interface atau lebih, seingat gue kalo double interface sebaiknya IPnya bedakan saja satu dengan yang lainya. pasti ok.....
gue juga punya yang single interface[NIC] tapi bisa membuat banyak sesuai kebutuhan anda. dan sekarang saya sedang membangun yang baru dengan 3 pisik [NIC]. maklumlah gue disini juga masih perlu belajar banyak.... dan kondisi sekarang semuanya juga sedang running....untuk jaringan local dan luar local juga webserver.
salam, kenal
BalimoreDOTcom
--------------------
Re: simple routing ... need help
Posted: Thu Aug 03, 2006 1:34 pm
by d3v4
in english plzz
Posted: Thu Aug 03, 2006 2:40 pm
by cmit
You need to configure a route in the Cisco telling it to reach the subnet 192.168.10.0/30 over gateway 192.168.10.253!
Best regards,
Christian Meis
Posted: Thu Aug 03, 2006 2:46 pm
by d3v4
You need to configure a route in the Cisco telling it to reach the subnet 192.168.10.0/30 over gateway 192.168.10.253!
Best regards,
Christian Meis
can u give me an example ?
Posted: Thu Aug 03, 2006 2:48 pm
by balimore
You need to configure a route in the Cisco telling it to reach the subnet 192.168.10.0/30 over gateway 192.168.10.253!
Best regards,
Christian Meis
-----------------------
Sorry, CMIT
can you continue to him... one focus point from you is better.
i will go to dinner now
regards
gundul
----------------------
Posted: Thu Aug 03, 2006 2:51 pm
by cmit
Sorry, no Cisco guy
Have thrown out the last Cisco years ago.
But should be something like
ip route 192.168.10.0 255.255.255.252 192.168.10.253
or the like...
Don't you have a reference manual for the Cisco?
Best regards,
Christian Meis
Posted: Thu Aug 03, 2006 3:04 pm
by d3v4
You need to configure a route in the Cisco telling it to reach the subnet 192.168.10.0/30 over gateway 192.168.10.253!
Best regards,
Christian Meis
hi cmit
i ever expect like that too, i must put client route in cisco. but... it's not work.
this problem makes me try other network configurations take the cisco off and put a ms wondows PC:
client 1 (MS windows) ----- eth1 mikrotik eth2 ------- client 2 (MS windows)
client 1 (MS windows)
ip : 192.168.10.1
netmask : 255.255.255.252
gateway 192.168.10.2
mikrotik
ip eth1 : 192.168.10.2
netmask : 255.255.255.252
ip eth2 : 192.168.10.253
netmask 255.255.255.252
/ip route add gateway=192.168.10.254
client 2 (ms windows)
ip : 192.168.10.254
netmask : 255.255.255.252
client 1 still can't ping client 2
it's look like it can't passthough mikrotik box
Posted: Thu Aug 03, 2006 3:22 pm
by cmit
So now your Windows client (replacing the Cisco) must have a route to the subnet of client1 (or its' default route to the MikroTik)...
Best regards,
Christian Meis
Posted: Thu Aug 03, 2006 4:44 pm
by d3v4
So now your Windows client (replacing the Cisco) must have a route to the subnet of client1 (or its' default route to the MikroTik)...
Best regards,
Christian Meis
oh
i see... i'll try it first... thanks
Posted: Fri Aug 04, 2006 12:48 pm
by d3v4
So now your Windows client (replacing the Cisco) must have a route to the subnet of client1 (or its' default route to the MikroTik)...
Best regards,
Christian Meis
client 1 (MS windows) ----- eth1 mikrotik eth2 ------- client 2 (MS windows)
client 1 (MS windows)
ip : 192.168.10.1
netmask : 255.255.255.252
gateway 192.168.10.2
mikrotik
ip eth1 : 192.168.10.2
netmask : 255.255.255.252
ip eth2 : 192.168.10.253
netmask 255.255.255.252
/ip route add gateway=192.168.10.254
client 2 (ms windows)
ip : 192.168.10.254
netmask : 255.255.255.252
gateway : 192.168.10.253
can we make client 2 ping client 1 trough mikrotik box without adding an extra route to client 1 ?
i mean all route is handle by mikrotik.
Posted: Sun Aug 06, 2006 1:48 pm
by hideident
client 1 using IP Private .
client 1 using IP private.
i think u need add nat (src nat) from client A in your MT box.
Posted: Fri Sep 22, 2006 8:33 am
by beryl
From client 1, can you ping mikrotik ip eth2 first?
I think this is a simple routing, all client have same gateway device with diferent ip.
Mikrotik can do it without adding any rule like Linux system with ip_forward = 1.