In my Linux box, the local ips (127.0.0.1) are defined in the “/etc/hosts” file. I have not tried an additional entry there. Mine shows only the 127.0.0.1 ip. If you like to experiment as much as I do, you might try a 127.0.0.2 entry there.
Here is something I found on the internet. From a shell logged in as root:
ifconfig lo add 127.0.0.2
Then when you enter just
ifconfig
it should show the two assignments
lo
lo:0
Where do i find this “/etc/hosts” file in the winbox kernel? possibly to add 127.0.0.2? If that file can be edited, it might work!
My bad. I was thinking Linux/RADIUS, not RouterOS.
I just tried to ping 127.0.0.2 from my router, and it timed out.
I tried to ping 127.0.0.1, and it timed out.
Then I changed my “/ip firewall nat” rule from
add chain=srcnat action=src-nat to-addresses=xx.xx.xx.xx
to
add chain=srcnat action=src-nat to-addresses=xx.xx.xx.xx out-interface=ether1
The out-interface addition allowed me to ping everything, including 127.0.0.1, 127.0.0.2, etc.
This look like solving the problem but mine is
add chain=srcnat action=masqurede
if I change it to add src to adress list, it ask for address list and not interface!
or can i add a new rule? if yes which ip did you specify? route interface ip? or hotspot ip?
I think that may solve your problem.
/ip firewall nat
set 0 out-interface=ether1
…considering ether1 is your wan interface. Then try to ping 127.0.0.2
Hmmmm! no way!
You know i can ping 127.0.0.1 replying correct but 127.0.0.2 … 254 timed out!
My out interface is set to ether1 (wan). Are you running hotspot on these router os? No! I guess!!
I have disabled all the port blocking firewall rule living only the default hotspot rule but not replying.
Oh contrar, mon frer! I run multiple hotspots on this test router.
Trust me when I say; This router would rather be out in the rain and cold, than in this room with me! 
ADD: RB433AH, V3.30
why i am getting confused is the fact that i can ping 127.0.0.1 and could not ping the rest. This could not possibly be firewall issue, but even if it, i have disabled all the rules and yet no way.
I can ping up to 127.0.0.4. I see no sense in going farther. If you think it can’t be the firewall, why is it I could not ping any of those until I changed my firewall nat rule? Or the localnet ips assigned to ether2 and ether3 until I changed that rule?
I just tried pinging 127.0.0.1 from another router and it reply but all others 127.0.0.2… did not reply. a ping from a router board configured as bridge to 127.0.0.1 reply but 127.0.0.2 .. timed out.
How com yours is replying?
They must be something not there by default that you have added to your bcos all these board i tried on all has the default settings except the hotspot server. in short some are even acting as client.
pls help me check!
What version of RouterOS are you using? I am using V3.30
v4.6 on x86 pc based
OK. Show me “/ip firewall nat” from the malfunctioning RouterOS boxes. Well, maybe not all of them if you have a lot. But at least one other.
Can anyone else here ping 127.0.0.2? Best if you are using V4.x.
ADD: The giveaway was what I could ping with my old setting. This one:
chain=srcnat action=src-nat to-addresses=xx.xx.xx.xx
The only ip I could ping was xx.xx.xx.xx. Nothing else. Not 192.168.0.1 (assigned to wlan1), nor 192.168.1.1 (assigned to ether2). Now I can ping both. ??
[admin@JP Wireless NOC] > ip firewall nat pri
Flags: X - disabled, I - invalid, D - dynamic
0 X ;;; place hotspot rules here
chain=unused-hs-chain action=passthrough
1 ;;; redirect http trafic to proxy
chain=dstnat action=redirect to-ports=8080 protocol=tcp dst-port=80
2 ;;; masquerade hotspot network
chain=srcnat action=masquerade src-address=202.202.1.0/24
out-interface=ether1-gateway
3 ;;; masquerade hotspot network
chain=srcnat action=masquerade src-address=20.20.1.0/24
out-interface=ether1-gateway
[admin@JP Wireless NOC] >
here is!
Pls anybody ping 127.0.0.2 from his winbox?
Those src-address settings are not localnet ips. I would remove the src-address settings on both. Actually, I would remove the second nat (line #3) and remove the src-address from the remaining one. These:
src-address=202.202.1.0/24
src-address=20.20.1.0/24
Are you using these ip subnets for localnet ips?
yes but i have tried that as well and not working, I removed all the sources address, http proxy redirect but still not working.
Did you have any icmp firewall rule?
Mine is all open to all pinging!
“Yes” meaning you are using those ip subnets for localnets?
Here are the only approved private ips:
10.0.0.0 – 10.255.255.255
172.16.0.0 – 172.31.255.255
192.168.0.0 – 192.168.255.255
And I am open to pinging. One of my firewall filter rules specifically allows icmp.
In real sense, the localnet ips has nothing to do with it.
I have just find out that, all the router os with v3.x are replying fine but all with 4.6 are not. I have tested about 9 routers out of which 5 are running v4.6 and are not replying 127.0.0.2 while the other 4 with v3.13, v3.24, v3.25 and v3.13 are all replying fine.
I think it is a problem associated with this version. Can you confirm that pls before we take it forward? or could there be any way out?
Has anybody been able to ping 127.0.0.2 (localhost ips) from MT v4.6? I have only been able to reach it from v3.x and below.