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).<br>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.<br>
<br>Tony <br><br><div class="gmail_quote">On Thu, Jan 19, 2012 at 7:09 PM, Aaron Smith <span dir="ltr"><<a href="mailto:list@soccergeek.net">list@soccergeek.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 01/19/2012 03:15 PM, vincent wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have the following scenario:<br>
- I have two separate networks: A=<a href="http://10.10.10.0/24" target="_blank">10.10.10.0/24</a> and B=<a href="http://20.20.20.0/24" target="_blank">20.20.20.0/24</a><br>
- The hosts on network "A" do not need to communicate with hosts on<br>
network "B"<br>
</blockquote>
<br></div>
At least one host on network "A" needs to communicate with hosts on network "B" ;)<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If the network "A" (<a href="http://10.10.10.0/24" target="_blank">10.10.10.0/24</a>) I can log into the router that<br>
divides the network, can allow rancid (with script or other method) to<br>
perform a second authentication of network devices to the network "B"<br>
(if: 20.20.20.1)?<br>
</blockquote>
<br></div>
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.<div class="im">
<br>
<br>
> I don't have a routing problem.<br>
<br></div>
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 networks.<span class="HOEnZb"><font color="#888888"><br>
<br>
--<br>
@@ron</font></span><div class="HOEnZb"><div class="h5"><br>
______________________________<u></u>_________________<br>
Rancid-discuss mailing list<br>
<a href="mailto:Rancid-discuss@shrubbery.net" target="_blank">Rancid-discuss@shrubbery.net</a><br>
<a href="http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss" target="_blank">http://www.shrubbery.net/<u></u>mailman/listinfo.cgi/rancid-<u></u>discuss</a><br>
</div></div></blockquote></div><br>