Discussion:
[rancid] Fortigate Fnlogin / Fnrancid Sending Premature Exit and showing up in diffs
Matthew Goeres
2014-08-15 15:41:41 UTC
Permalink
Hello,

We have an issue with nearly all of our Fortigate firewalls where we get an
extra exit in the config randomly somewhere in the config.

I can't seem to put any rhyme or reason to why it is occurring and can't
seem to figure out where in the script it decides it is done running the
command table and to send the exit to close the shell.

Line 382 is an example of the exit.

376: set tab-id 1 377: set
column 1 378: next 379: edit 4 380:
set widget-type sysres 381:
set tab-id 1 382: exit 383: set column 2 384:
set time-period 0 385: set
chart-color 0 386: next 387: edit 5
388: set widget-type sessions 389:
set tab-id 1 390: set column 2 391:
next

Line 262 is another example here:

255: next 256: edit "port8" 257: set vdom "MGMT"
258: set mode dhcp 259: set allowaccess ping https
ssh fgfm 260: set type physical 261: set defaultgw
enable 262: exit 263: next 264: edit "AuthLink0" 265:
set vdom "root" 266: set ip 169.254.255.1 255.255.255.252
267: set allowaccess ping 268: set type vdom-link
269: next

Thanks,

Matt
Matt Goeres
2014-09-16 20:51:46 UTC
Permalink
Anyone have any clue on this? I still haven’t been able to figure it out. 


On August 15, 2014 at 10:41:41 AM, Matthew Goeres (***@gmail.com) wrote:

Hello,

We have an issue with nearly all of our Fortigate firewalls where we get an extra exit in the config randomly somewhere in the config.

I can't seem to put any rhyme or reason to why it is occurring and can't seem to figure out where in the script it decides it is done running the command table and to send the exit to close the shell.

Line 382 is an example of the exit.

376: set tab-id 1
377: set column 1
378: next
379: edit 4
380: set widget-type sysres
381: set tab-id 1
382: exit
383: set column 2
384: set time-period 0
385: set chart-color 0
386: next
387: edit 5
388: set widget-type sessions
389: set tab-id 1
390: set column 2
391: next
Line 262 is another example here:
255: next
256: edit "port8"
257: set vdom "MGMT"
258: set mode dhcp
259: set allowaccess ping https ssh fgfm
260: set type physical
261: set defaultgw enable
262: exit
263: next
264: edit "AuthLink0"
265: set vdom "root"
266: set ip 169.254.255.1 255.255.255.252
267: set allowaccess ping
268: set type vdom-link
269: next
Thanks,

Matt
John Kougoulos
2014-09-17 16:06:45 UTC
Permalink
Hi,
Which version do you run on fortigates? I get similar things on version 4
but not in version 5

Regards,
John
Post by Matt Goeres
Anyone have any clue on this? I still haven’t been able to figure it out.
Hello,
We have an issue with nearly all of our Fortigate firewalls where we get
an extra exit in the config randomly somewhere in the config.
I can't seem to put any rhyme or reason to why it is occurring and can't
seem to figure out where in the script it decides it is done running the
command table and to send the exit to close the shell.
Line 382 is an example of the exit.
376: set tab-id 1 377: set column 1 378: next 379: edit 4 380: set widget-type sysres 381: set tab-id 1 382: exit 383: set column 2 384: set time-period 0 385: set chart-color 0 386: next 387: edit 5 388: set widget-type sessions 389: set tab-id 1 390: set column 2 391: next
255: next 256: edit "port8" 257: set vdom "MGMT" 258: set mode dhcp 259: set allowaccess ping https ssh fgfm 260: set type physical 261: set defaultgw enable 262: exit 263: next 264: edit "AuthLink0" 265: set vdom "root" 266: set ip 169.254.255.1 255.255.255.252 267: set allowaccess ping 268: set type vdom-link 269: next
Thanks,
Matt
_______________________________________________
Rancid-discuss mailing list
http://www.shrubbery.net/mailman/listinfo/rancid-discuss
Loading...