could not make socket

RouterOS General
1

good evening

iam using RB2011 and iam trying to ping 8.8.8.8 from a source address but keep on getting an error message as below
ping 8.8.8.8 src-address=192.168.16.30
SEQ HOST SIZE TTL TIME STATUS
0 could not make socket
1 could not make socket
2 could not make socket
3 could not make socket
4 could not make socket
5 could not make socket
6 could not make socket
7 could not make socket
8 could not make socket
how can i solve this problem
thank you
sam

2

what is the output of /ip address print ?

3

the output of ip adress print is as follows:
/ip address> print
Flags: X - disabled, I - invalid, D - dynamic

ADDRESS NETWORK INTERFACE

0 ;;; defconf
192.168.16.1/24 192.168.16.0 bridge
1 19x.x.x.x/30 19x.x.x.x ether1
2 192.168.1.1/24 192.168.1.0 bridg

4

you don’t have that ip locally assigned, hence ping fails

try .16.1 instead

5

the ips are bieng assigned dynamically. so i would like t see if iam getting internet fro the clent’s side? 16.1 is replying…

6

in general you don’t need to use the src-address when pinging, Tik will select the appropriate one.

If you want to test client connectivity, then you need to test FROM client system, NOT the router.

7

I actually saw this same error myself, for the first time ever (on mikrotik). I had lost a few connections on my PC so i connected to winbox, and my internet connections was fine (other VPNs were connected and 4-8mbit of BW was flowing over my internet/isp uplink) but when i tried to ping a few random IPs via winbox, i saw this message (and dns resolution was not working in winbox).

I have a static pub IP from my ISP , confg’d on the mt uplink eth to my isp.

ROS was at 6.42.6 (on a CCR-1009-7G-1C-1S+). I used the opportunity to update to 6.42.12 (and check for update/download of update in winbox worked). Post update reboot all started working again.

8

This error is only when you are trying to use source address which is not configured on your router. If you want to craft packets with invalid source then use packet generators or other tools, that are using raw sockets.

9

Simple Resolution:

Go to: IP → Addresses → Add IP Address Subnet click OK

Then try by pinging it will resolve the issue.

Note: Do not forget to add NAT in Firewall, with Masquerading the Source Local Subnet to Destination address any (0.0.0.0/0)

10

After 2 years you write back on forum to resurrect this 2019 topic?