fnlogin won't login
(2013-06-28)
(
Source)
Problem
Fortigate firewalls don't get updated. Error in rancid log is similar to:Getting missed routers: round 4. 192.168.2.1 fnlogin error: Error: Couldn't login: 192.168.2.1 192.168.2.1: missed cmd(s): show full-configuration,get system status 0: found end 192.168.2.1: End of run not found
Solution
Index: bin/fnlogin.in
===================================================================
--- bin/fnlogin.in (revision 2376)
+++ bin/fnlogin.in (revision 2435)
@@ -303,7 +303,7 @@
} elseif [string match "ssh*" $prog] {
regexp {ssh(:([^[:space:]]+))*} $prog methcmd suffix port
set cmd $sshcmd
- if {"$port" == ""} {
+ if {"$port" != ""} {
set cmd "$cmd -p $port"
}
set retval [ catch {eval spawn [split "$cmd -c $cyphertype -x -l $user $router" { }]} reason ]Source)
no comments |
post comment
Virtual Dave Megaplex:
- Home Page
- This wiki's start page
- Send Feedback To Dave
Logged in Users: (0)
Recently Changed
Check Internet Service Database Match- Device-Local Certificate Expired
- CLI Policy Lookup
- DH Selection For IPsec VPNs
- Scan For Newly Added Disk
- nmap
- Seconds Since Epoch to Local Time
- Link Monitor
- DH group to OAKLEY_GROUP table
- Fire Eater
- start
- FortiClient Error Codes
- dhparams Generation
- SSL Certificate Bundles
- ufw
- Grow A LVM Partition
- Creating Users
- whoami
- list databases
- 2023
- 2022
- 2019
- 2018
- 2017
- 2011
- 2010
- 2008
- 2001
- 2000
- 1999
Editing: snipsnap-help, Image Macro(Et auditum est, et idcirco ego nunc simulare)
This is a collection of techical information, much of it learned the hard way. Consider it a lab book or a /info directory. I doubt much of it will be of use to anyone else.