Not able to ping any address with pingtool

RouterOS Beginner Basics
1

Hi, I’m trying to set up a mikrotik RB3011 to use for network monitoring on a existing network. Currently I have the quick setup as a bridge but I cannot figure out what to add/change to be able to ping local devices and external ip’s

# 2025-03-10 13:36:08 by RouterOS 7.18.2
# software id = U7U5-7F56
#
# model = RB3011UiAS
# serial number = B88D0A5E56CF
/interface bridge
add name=bridge1
/interface list
add name=WAN
add name=LAN
/port
set 0 name=serial0
/interface bridge port
add bridge=bridge1 interface=ether1
add bridge=bridge1 interface=ether2
add bridge=bridge1 interface=ether3
add bridge=bridge1 interface=ether4
add bridge=bridge1 interface=ether5
add bridge=bridge1 interface=ether6
add bridge=bridge1 interface=ether7
add bridge=bridge1 interface=ether8
add bridge=bridge1 interface=ether9
add bridge=bridge1 interface=ether10
add bridge=bridge1 interface=sfp1
/ip neighbor discovery-settings
set discover-interface-list=!dynamic
/interface list member
add interface=ether1 list=WAN
add interface=ether2 list=LAN
add interface=ether3 list=LAN
add interface=ether4 list=LAN
add interface=ether5 list=LAN
add interface=ether6 list=LAN
add interface=ether7 list=LAN
add interface=ether8 list=LAN
add interface=ether9 list=LAN
add interface=ether10 list=LAN
add interface=sfp1 list=LAN
/ip address
add address=192.168.0.242/20 interface=bridge1 network=192.168.0.0
/ip dns
set servers=192.168.0.8,8.8.8.8
/lcd
set default-screen=interfaces
/lcd interface
set ether1 disabled=yes
set ether3 disabled=yes
set ether4 disabled=yes
set ether5 disabled=yes
set sfp1 disabled=yes
set ether6 disabled=yes
set ether7 disabled=yes
set ether8 disabled=yes
set ether9 disabled=yes
set ether10 disabled=yes
add disabled=yes interface=bridge1 max-speed=auto
/system identity
set name="The Dude"
/system note
set show-at-login=no

What I get when I ping

[admin@The Dude] > ping 8.8.8.8
SEQ HOST SIZE TTL TIME STATUS
0 8.8.8.8 timeout
1 8.8.8.8 timeout
2 8.8.8.8 timeout
3 8.8.8.8 timeout
sent=4 received=0 packet-loss=100%

[admin@The Dude] > ping 192.168.0.100
SEQ HOST SIZE TTL TIME STATUS
0 192.168.0.100 timeout
1 192.168.0.100 timeout
2 192.168.0.100 timeout
3 192.168.0.100 timeout
4 192.168.0.100 timeout
sent=5 received=0 packet-loss=100%

2

The more I look for the the WAN IP & router, the more I couldn’t find it.

Please edit your post and include verbatim copy of config using < / > code tags. Remove serials. No need to use external services.

3

Is a spammer for the classical NameSurname and edit some week later the post for add the spam…

The config is from 2025-03-10 13:36:08 by RouterOS 7.18.2

4

ether1 part of the bridge bridge1 BUT set as WAN doesn’t sound as a good start.
But 192.168.0.100 (if it exists on the network) should be reachable from at least ports ether2-10.
What about 192.168.0.8 (which is indicated as dns server)?
No way those settings (without gateway or routes) will ever make 8.8.8.8 (or any IP outside range 192.168.0.1 - 192.168.15.254) reachable (which is good as there is no firewall at the moment).
BTW. WHY a /20? That is a heck of a LAN, with 4094 devices accessible.

5

Hi thanks for your suggestion i did edit my post.

If I understand correctly your saying that I should have a route to the existing gateway but that i don’t
any idea of what i can search for to get a guide/ tutorial.

6

[/quote]

Is a spammer for the classical NameSurname and edit some week later the post for add the spam…

The config is from 2025-03-10 13:36:08 by RouterOS 7.18.2
[/quote]

Hi i don’t quite get what you are saying. I ensure you by question is genuine. or at least with genuine intent.
I’m very new to all this so not quite sure why the date of export could be wrong as i exported it when creating the post.

7

As far as I understand no port should be set to wan as this device is not directly connected to the wan.
I can ping 192.168.0.8(did not think to test that when making the post) but 192.168.0.100 is my pc plugged into eth2 and cannot reach it as well as the network gateway.
I have no idea how to set up routes and most guides/ tutorials i’m looking at are for a different use case. I would really apricate if someone can point me in the right direction. This router will just be used for running dude to check if cameras are loosing connection. pinging external ip’s just to see if the internet drops.
In regards to firewall, Is it necessary as this router is already behind the main router and firewall.
the /20 I got from how the dhcp is broadcasted. i’m not sure why the network is setup that way myself, but there are hosts set to 192.168.0.x all the way to 192.168.3.x that i would like to be able to ping.

8

Let’s start by setting the interfaces:

/interface bridge
add name=bridge1

Good, you have a bridge called “bridge1”.

/interface list
add name=WAN
add name=LAN

Good, you have two categories of interfaces, WAN and LAN.

/interface bridge port
add bridge=bridge1 interface=ether1
add bridge=bridge1 interface=ether2
add bridge=bridge1 interface=ether3
add bridge=bridge1 interface=ether4
add bridge=bridge1 interface=ether5
add bridge=bridge1 interface=ether6
add bridge=bridge1 interface=ether7
add bridge=bridge1 interface=ether8
add bridge=bridge1 interface=ether9
add bridge=bridge1 interface=ether10
add bridge=bridge1 interface=sfp1

You added ALL ports to bridge1 (this is usually not advised, it would be better if you could reserve a single port outside of the bridge to management as it may be relatively easy to lock oneself out when fiddling with bridge settings).

/interface list member
add interface=ether1 list=WAN
add interface=ether2 list=LAN
add interface=ether3 list=LAN
add interface=ether4 list=LAN
add interface=ether5 list=LAN
add interface=ether6 list=LAN
add interface=ether7 list=LAN
add interface=ether8 list=LAN
add interface=ether9 list=LAN
add interface=ether10 list=LAN
add interface=sfp1 list=LAN

This makes no sense whatsoever, right now you have only one interface, bridge1, and that is definitely LAN.

So you should have:

/interface bridge port
add bridge=bridge1 interface=ether1
add bridge=bridge1 interface=ether2
add bridge=bridge1 interface=ether3
add bridge=bridge1 interface=ether4
add bridge=bridge1 interface=ether5
add bridge=bridge1 interface=ether6
add bridge=bridge1 interface=ether7
add bridge=bridge1 interface=ether8
add bridge=bridge1 interface=ether9
add bridge=bridge1 interface=ether10
add bridge=bridge1 interface=sfp1

and:

/interface list
add name=WAN
add name=LAN
add name=MGM

and:

/interface list member
add interface=ether1 list=WAN
add interface=ether2 list=LAN
add interface=ether3 list=LAN
add interface=ether4 list=LAN
add interface=ether5 list=LAN
add interface=ether6 list=LAN
add interface=ether7 list=LAN
add interface=ether8 list=LAN
add interface=ether9 list=LAN
add interface=ether10 list=LAN
add interface=sfp1 list=LAN
add interface=bridge1 list=LAN
add interface=ether10 list=MGM

Then assign a static IP address to ether10:

/ip address
add address=192.168.88.1/24 interface=ether10 network=192.168.88.0

Now - if needed - you can set the IP of your PC to (say) 192.168.88.2/24 and connect to ether10 no matter what happens to the bridge.

The IP address you have now:

/ip address
add address=192.168.0.242/20 interface=bridge1 network=192.168.0.0

will create automatically a route for the whole 192.168.0.0/20 network, do check that this is the case by running:

/ip route print

so the Mikrotik device only knows that it can reach any address in 192.168.0.0/20 via bridge1.
As said having a /20 network is unusual, it is a very large one, for 4094 devices, commonly /24 or /23 are used, if your devices are in the range 192.168.0.1-192.168.3.254 that is covered by a /22:
https://www.calculator.net/ip-subnet-calculator.html?cclass=any&csubnet=22&cip=192.168.0.0&ctype=ipv4&x=Calculate

When you add the IP address for ether10 another “C” (by connection) route will be created allowing the device to reach 192.168.88.0/24 via ether10.


So (again if the IP address exists on the network) you should be able to ping 192.168.0.100 via bridge1.

No way the device knows how to reach 8.8.8.8.

You can add (it depends on what you actually want to do) a route for either only 8.8.8.8/32 or for the whole internet 0.0.0.0/0.
To do this you need to use the gateway (router) of your network, probably 192.168.0.1 :question: .
This gateway should also now be reachable (pingable) via bridge1.

Like:

/ip route
add dst-address=8.8.8.8/32 gateway=192.168.0.1 distance=1

or:

/ip route
add gateway=192.168.0.1 distance=1

this latter is the short form of:

/ip route
add dst-address=0.0.0.0/0 gateway=192.168.0.1 distance=1

Try the above changes and report what happens.
Besides ping, try also a traceroute, in case of issues it may show where the hops stop.

If your PC is running a recent (stupid) version of Windows (like 10 or 11) the Windows firewall is by default set to NOT respond to pings, you may want to change that setting.

9

jaclaz you are a legend. i’m going to try that tomorrow.

10

@jaclaz

on 3rd comment: ether1 is on LAN bridge and also on WAN

11

Yep, hence the suggestion to have instead just:

/interface list member
add interface=bridge1 list=LAN
add interface=ether10 list=MGM

(taking BTW ether10 out of the bridge for management).