aaa
Backup
aaa
Man plz we need detailed information
give the your configuration details
from the head till the last point on your network plz
dlink router os and so on???
aaa
aaa
aaa
I recall as the backup file being pretty much useless for outside parties to check or comment about. Just make an export to a file from relevant parts of your running configuration and post it here. That will be in human readable format and we can comment on it.
aaaa
The v6 syntax may be a little confusing to me, but does you have default route defined? action=unreachable is strange for the default route to have. Also, you should list configurations of other boxes as well, because in current state it is mildly to say confusing.
aaa
According to your graph they are, but are all those device down the line from the MikroTik in bridge mode or are there any routers in the mix as well?
Bridging between various brands of network equipment can be tricky business or even not work at all. I would go for routing instead, but you try it out.
Go to each box and try if these get to the internet or not (ping something (8.8.8.
for instance):
Does the Dlink 624 (192.168.0.1) make NAT for the 192.168.0.0/24 network?
Does the Dlink 624 (192.168.0.1) get to the Internet?
Does the Mikrotik AP (192.168.0.30) get to the Internet and/or can it ping 192.168.0.1?
Does the Dlink 2100 AP (192.168.0.50) get to the Internet and/or can it ping 192.168.0.1, 192.168.0.30?
Does the Dlink 2100 AP (192.168.0.51) get to the Internet and/or can it ping 192.168.0.1, 192.168.0.30, 192.168.0.50?
Does any Client PC (192.168.0.100) get to the Internet and/or can it ping 192.168.0.1, 192.168.0.30, 192.168.0.50, 192.168.0.51?
You can try pinging another way around toward the client side as well.
As a result of all that pinging around You’ll see what hop is broken.
aaa
If anything from 192.168.0.50 onward does not have a build in feature for pinging or other network testing then carry out your testing with the 192.168.0.30.
Does it ping 192.168.0.50, 192.168.0.51, 192.168.0.100?
aaa
It seems that we can rule out filtering, so I would blame the pseudobridge part of it. For starters, get rid of the MikroTik bridge and implement routing on that MT. If your Dlink 624 does let you define additional routes and NAT for multiple networks then implement these there. If not then you’ll have to do it within MT itself.
aaa
aaa
aaa
Where do you see a webproxy? In your configuration there is nothing about it.
How do you test DNS? By pinging something (ex. www.google.com)?
If your internal machines can reach Dlink 624 then I would try to find the error source from there. You may not have NAT enabled or firewall or some sort of MAC to IP-address binding going on.