[rancid] get running-config to other network
sarikoudis at googlemail.com
Fri Jan 20 17:24:11 UTC 2012
have a look on:
2012/1/20 Tony Tauber <ttauber at 1-4-5.net>:
> Actually, this question has come up before (I think even from me once) about
> devices which are only reachable via some sort of gateway (e.g. telnet from
> one device to another or console access via terminal server).
> I haven't done it and don't have the need in my current environment but I
> believe there may have been some patches or hacks devised to deal with it.
> On Thu, Jan 19, 2012 at 7:09 PM, Aaron Smith <list at soccergeek.net> wrote:
>> On 01/19/2012 03:15 PM, vincent wrote:
>>> I have the following scenario:
>>> - I have two separate networks: A=10.10.10.0/24 and B=126.96.36.199/24
>>> - The hosts on network "A" do not need to communicate with hosts on
>>> network "B"
>> At least one host on network "A" needs to communicate with hosts on
>> network "B" ;)
>>> If the network "A" (10.10.10.0/24) I can log into the router that
>>> divides the network, can allow rancid (with script or other method) to
>>> perform a second authentication of network devices to the network "B"
>>> (if: 188.8.131.52)?
>> I don't believe rancid supports bouncing through one router to get to
>> another. I suppose adding a static route on the RANCiD server to get to
>> network "B" might work, depending on what networks you're connected to and
>> what the routing/firewall policies are.
>> > I don't have a routing problem.
>> This seems like a routing problem to me. Your network admins either need
>> to let you route through to network "B" or install a RANCiD server in both
>> Rancid-discuss mailing list
>> Rancid-discuss at shrubbery.net
> Rancid-discuss mailing list
> Rancid-discuss at shrubbery.net
More information about the Rancid-discuss