<br><br><div><span class="gmail_quote">On 9/18/06, <b class="gmail_sendername">john heasley</b> <<a href="mailto:heas@shrubbery.net">heas@shrubbery.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Sun, Sep 17, 2006 at 03:49:17PM -0500, Eric Humphries:<br>> Hey guys,<br>><br>> I'm using rancid on a FreeBSD 6.1-Stable box, and I'm trying to log into<br>> some fortinet equipment (more specifically a Fortigate 60M) using the
<br>> fnrancid module.<br>><br>> I'm able to manually use clogin to log into the firewall and it brings me to<br>> the prompt but immediately after the session freezes and I'm unable to<br>> type/run commands. Using rancid-run fails to run the commands as well so it
<br>> appears to be something with how the script expects the login prompt to<br>> appear, possibly. The hostname I have on the device is "testdevice $" when I<br>> log in as a user and "testdevice #" when I log in with admin. There is not
<br>> enable password required.<br><br>I'm not familiar with the fortinet (or the netscreen), but there seems to have<br>been a change in the UI.<br>1) nlogin expects the prompt to end with "-> "<br>2) nlogin does not know about an "enable" mode.
</blockquote><div><br><br>1) Well I've yet to see any fortinet equipment have a prompt that ends in ->, default or otherwise.<br>2) Well, I guess the noenable business isn't going to do the trick then.<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
So, this is not going to work. nlogin will need to be changed. Or, try<br>clogin to see if it works: clogin -c 'some command; some other command'<br><br>> I'm quite new to rancid (a few days) and I've searched around for help
<br>> regarding this specific issue but I've yet to find anything that matches my<br>> problem well. I can provide information as necessary, just tell me what you<br>> need to see.<br>><br>> Is there something I'm doing wrong that would cause the shell to hang? I've
<br>> tried running rancid with tcsh, and sh - both with the same result.<br><br>It should not hang forever. If it is expecting output and not receiving it,<br>the timeout should trip and the login script should close the connection.
<br>If it is hanging forever, then I suspect you're using solaris/linux and you<br>need to apply the expect patch from the rancid web page.<br></blockquote></div><br><br clear="all">It does trip the TIMEOUT. <br><br>So I guess my main question is is the fnrancid module setup to expect a prompt that ends in "-> "? I haven't had time to dig into fnrancid or nlogin to lear the innerworkings as I've only been messing with it in my freetime. Eventually, I would like to deploy this for close to 1,000 firewalls or so.
<br><br>I guess my next step is to dig into fnrancid and try to figure out what its doing. I know the modules are fancy front-ends for expect that are used to describe device behavior but thats as far as I've gone.<br> <br>
--<br>efk