Is this a mikrotik thing, all my websites were working fine for several months and all of a sudden cloudflare can not reach them anymore and i am troubleshooting things i noticed some NAT work and others do not
this is not first time i notice strange things in network since i switched from juniper to mikrotik
like always weird networking stuffs where i can ping one NAT ip and i cant ping the other
It is just weird and i do not know how to troubleshoot these very weird NAT issues, because am not a network engineer as profession
Curl works when using the private IP but when i use the NAT IP then nothing works
but this was working fine for several months and i never touched anything
what can cause this kind of weirdness???
Also consider updating the software on various other devices,
and other administrators who manage the other routers involved in the operation of the Internet…
I am the only person managing the router..this is a home setup not a company
i am not talking about config for now, just ranting about why these types of weird things happen with mikrotik
did you hear what i said? some NAT still works and some not working
And they were all working before for several months ago until like yesterday
what does posting config going to do here?
this is a weird thing and just want to start with what could cause this for anyone with experience with this
Then take your rants elsewhere or at least have the courage to post your config so we can attempt to find out if the config is an issue or more likely you have a flaky ISP.
You’d be surprised … could even be on your ISP modem.
Logical thinking:
A- a router does not change config on its own (as far as I know there is still no AI involved on those things …)
B- You claim you did not change anything on the router. We believe you and will continue with that.
C- Something which did work before, all of a sudden doesn’t anymore
D- Given C, something has changed
E- Given A, B and D, the change was elsewhere
I dont think that will help anything, this is a weird issue not a misconfiguration
you guys should stop opting first for configuration
i get you want to help but just dont always ask for config all the time
this is not a misconfiguration issue so config will not help at all
i have same exact setup for other NAT that work but the others stopped working
i did not make any change whatsoever
i can curl the website with host headers on private local ip but i can when i use the public ip
but this works for other website, certain public IPs are affected but i have some that work
I have no idea how to troubleshoot this and please again this is not a misconfiguration as was working before and just stopped yesterday
I am thinking i will change to another set of public IPs left in my block to test, that is all i can do now
It happened before that seemingly correct config was working only by accident… most of the time until it didn’t. I’d say it’s more likely than weird bug in RouterOS. But if you want to debug it yourself, no problem. You know what traffic you’re expecting, so check if it comes at all, if it passes through router as it should, or where exactly it gets lost if it doesn’t. You can use Torch on interfaces, packet sniffer or logging rules in firewall. If you choose the last option, here’s a helpful image:
Any incoming traffic will be first in prerouting, then it will go either to input (if it’s for router itself) or to forward (if it’s for another device) and then to postrouting. Good place for logging rules is in mangle. You’ll need some conditions for rules to match the right traffic, which can be using source or destination, unique ports, whatever is appropriate, it depends on existing config (you don’t want to catch unrelated trafic or have conflicts with other stuff).
Apparently my static IP block on ISP gateway was on private subnet, i called them to explain this weird issue and they changed it to public subnet and everything is now working fine now
one of the weirdest thing for me to troubleshoot. Wasn't aware a static ip can have private subnet setting on ISP gateway Issues was not mikrotik config at all
Happy all solved now
thanks for the help at least
poorly written as it is in English, don't you understand that the phrase means that there are OTHER ROUTERS and OTHER Administrators involved in the operation of the Internet?
