ping problem

RouterOS General
1

hey guys, im a newbie here. i have a question that follows with the problem im having.

here’s the basic topology that i have




i can’t for some reason ping from 192.66.1.1 to 192.168.1.120
router1 is a linksys wireless router and switch0 is a 3com switch.

i wonder what could be the problem here.

thanks :slight_smile:

2

check firewall rules
and also post config here so that we can check

3

hey thanks for replying, how do i get a copy off the router’s configuration?

4

/export file=xyz.rsc
then download it form files menu

5

okay this is my configuration file.

IP PUBLIC
139.6.3.234 → CLOUD

HO
192.66.4.1 → Router 1 (192.66.4.3) → (192.168.1.1) → WEBSERVER (192.168.1.120)


i hope everything is clear, in case if something is unclear, please let me know.


thanks
config2.rsc (22.4 KB)

6

Can you ping from 192.66.1.1 to 192.66.4.1?

Why are you using IP network 192.66.x.x?

7

yes i can ping from mikrotik to 192.66.4.1 but i cant ping to the 192.168.1.x i wonder whats blocking them

8

According to your network diagram, you should not be able to ping 192.66.4.1 from your MikroTik router because 192.66.1.1/24 and 192.66.4.1/24 belongs to completely different networks.

I think that host 192.66.4.1 responded because it is a publik IP address that belongs to the Danish company DKnet.

192.66.4.1 = eskv-gw1-0-0-0-666.lyngbol.dk

According to RIPE NCC, 192.66.0.0 - 192.66.255.255 belongs to DKnet Fruebjergvej 3 DK-2100 Copenhagen.

9

In order to reach (and ping) device 192.168.1.120 you have to tell the router 192.66.1.1 where it is. The core router itself (the one with 192.66.1.1) has a default gateway which points out to the internet, while the device 192.168.1.120 is on the private side. So, you need to add a route to that:

/ip route
add dst-address=192.168.1.120 gateway=192.66.4.1

This way, requests for host 192.168.1.120 will not go by the default route, but instead will be directed to the 192.66.4.1 router which does know where the host is, since it is a part of its networks.

But as THG mentions, the addresses 192.66.4.1 and 192.66.1.1 are public IP addresses, so it is not recommended to use those IPs on your private network, you need to use private addresses.
Also, my solution which I described above, is valid only if 192.66.1.1 and 192.66.4.1 are on the same broadcast domain. This means that both those addresses should have a subnet of at least /21, like 192.66.1.1/21 and 192.66.4.1/21

10

First solved issues with ip addressing…

11

hi guys, so i just figure out that it can only connect directly from switch to client PC 192.168.1.120 without using the router.

so the client’s IP address is now 192.168.100.5 (i changed the network because 192.66. belong to denmark)

is it possible to re-do the topology like from

mikrotik → switch → switch → 0/1 to client and 0/2 to the wireless router?



now the problem is how do i port forward? i can successfully do the 8282 port, so that i can access mypublicip:8282 but it wont stream my media, which is using port 9000, but when i check at online port scanner, port 9000 is already opened.


attached is my current configuration.


thanks for the help guys!!
config-new.rsc (22.9 KB)