Coming soon - Get a detailed view of why an account is flagged as spam!
view details

This post has been de-listed

It is no longer included in search results and normal feeds (front page, hot posts, subreddit posts, etc). It remains visible only via the author's post history.

6
Problems with cursed RIP and VPN redundancy.
Post Body

I have a dilemma regarding making redundancy with RIP (something i would never do but the devices are so old that they dont do OSPF)

The idea is that there's a main VPN concentrator connected to several locations through Cisco's VPN. Both the concentrator and the locations have two internet ISP lines each. The architecture is like this:

LAN - vpn concentrator ---internet(vpn)---- location - LAN

The LANS need to be connected. This was initially done through two static routes redirecting trafic through the VPN tunnel(one at cnc, one at location).

Now i have to do redundancy for all of them.

Considering the lans are 192.168.0.0'ish and the vpn tunnels are 172.16.1.0 and 172.16.2.0.

I've tried configuring RIP as such:

router rip version 2 no auto-summary network 172.16.0.0 network 192.168.0.0 this was done on both concentrator and locations

The result?

The tunnels are redundant, but the lan's aren't. More ironically, the lan on one specific device is seen among the others.

Any ideas? could there be some commands that are preventing the RIP routes?

Author
Account Strength
100%
Account Age
12 years
Verified Email
Yes
Verified Flair
No
Total Karma
25,618
Link Karma
19,438
Comment Karma
6,006
Profile updated: 5 days ago
Posts updated: 7 months ago
Cats, packets, booze and bitches

Subreddit

Post Details

We try to extract some basic information from the post title. This is not always successful or accurate, please use your best judgement and compare these values to the post title and body for confirmation.
Posted
10 years ago