VPN routing problem
We have an issue with a couple of Vigor routers in some of our properties around the country.
We have a set of three offices which are interconnected via three Vigors. Each Vigor then also has a seperate VPN back to our main network at Head Office.
Our main network is on a subnet of 192.168.100.0, with each router using 192.168.1.5, 192.168.,15.5 and 192.168.16.5 as their addresses.
However, we keep getting the following route added to the router in one of the sites which stops them communicating with our head office site.
R 192.168.100.0/ 255.255.255.0 via 192.168.15.5, IF5 (4/12000)
The router says R is for RIP
How do we stop this route being created as we cannot remove these local connections yet, but they must be able to connect back to head office.
We have a set of three offices which are interconnected via three Vigors. Each Vigor then also has a seperate VPN back to our main network at Head Office.
Our main network is on a subnet of 192.168.100.0, with each router using 192.168.1.5, 192.168.,15.5 and 192.168.16.5 as their addresses.
However, we keep getting the following route added to the router in one of the sites which stops them communicating with our head office site.
R 192.168.100.0/ 255.255.255.0 via 192.168.15.5, IF5 (4/12000)
The router says R is for RIP
How do we stop this route being created as we cannot remove these local connections yet, but they must be able to connect back to head office.
ASKER
We have RIP turned of the LAN settings, but it is left on for the VPN settings. Should we turn this off there for all VPN connections?
Do you have multiple routers that make up the LAN?
This might suggest that the location that has 192.168.15.0 either has a segment using 192.168.100.0 which leads to the overlap or it is rebroadcasting the 192.168.100.0 it receives but can not route this traffic for some reason.
Usually if you only have one router at each location and usually if you have a hub and spoke VPN setup, there is no need to use a routing protocol (RIP) since all routes are static.
This might suggest that the location that has 192.168.15.0 either has a segment using 192.168.100.0 which leads to the overlap or it is rebroadcasting the 192.168.100.0 it receives but can not route this traffic for some reason.
Usually if you only have one router at each location and usually if you have a hub and spoke VPN setup, there is no need to use a routing protocol (RIP) since all routes are static.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Did you configure the VPN to use RIP to handle the propagation/convergence of the VPN network?