Hi all,
I have a rb493G with a few firewall rules and a pptp vpn setup. Every time I add a new route or setup a DHCP server and a route gets added automatically, the router can ping the clients along that route but clients on their subnets can not. After spending a while and talking to a friend who works with mikrotik’s we tried to reboot it and it fixed it. Is this normal.
Thanks Stephen.
Re: Router reboot required when routing table is changed. [SOLVED]
It depends on the structure of the network and the details of your configuration.
When you have a default route that goes to internet via NAT and you have tried to reach the remote system before you added the route, yes it could happen.
This is because the router has setup a NAT translation entry for your connection, and will re-use that after you have added the route.
It should not really be required to reboot. Waiting a couple of minutes should do it too (as the NAT entry that has not entered established state will soon time out).
To prevent this kind of problem, add the following routes to each router that you configure:
I always do this as a standard step to newly configuring each router (not only MikroTik!)
With this in place, you should not have that problem and you prevent other problems as well.
When you have a default route that goes to internet via NAT and you have tried to reach the remote system before you added the route, yes it could happen.
This is because the router has setup a NAT translation entry for your connection, and will re-use that after you have added the route.
It should not really be required to reboot. Waiting a couple of minutes should do it too (as the NAT entry that has not entered established state will soon time out).
To prevent this kind of problem, add the following routes to each router that you configure:
Code: Select all
/ip route
add distance=1 dst-address=10.0.0.0/8 type=unreachable
add distance=1 dst-address=169.254.0.0/16 type=unreachable
add distance=1 dst-address=172.16.0.0/12 type=unreachable
add distance=1 dst-address=192.168.0.0/16 type=unreachableWith this in place, you should not have that problem and you prevent other problems as well.
Re: Router reboot required when routing table is changed.
Thanks for your quick reply. This fixed my problem. when I add routes now the clients can ping them without needing to reboot.It depends on the structure of the network and the details of your configuration.
When you have a default route that goes to internet via NAT and you have tried to reach the remote system before you added the route, yes it could happen.
This is because the router has setup a NAT translation entry for your connection, and will re-use that after you have added the route.
It should not really be required to reboot. Waiting a couple of minutes should do it too (as the NAT entry that has not entered established state will soon time out).
To prevent this kind of problem, add the following routes to each router that you configure:
I always do this as a standard step to newly configuring each router (not only MikroTik!)Code: Select all/ip route add distance=1 dst-address=10.0.0.0/8 type=unreachable add distance=1 dst-address=169.254.0.0/16 type=unreachable add distance=1 dst-address=172.16.0.0/12 type=unreachable add distance=1 dst-address=192.168.0.0/16 type=unreachable
With this in place, you should not have that problem and you prevent other problems as well.
Re: Router reboot required when routing table is changed.
Good to hear that.
In fact I would vote for it when this config was added to the default setup!
In fact I would vote for it when this config was added to the default setup!
Who is online
Users browsing this forum: No registered users and 42 guests