Like I said, no changes had been made to the routes page. I'm well aware of
the idosyncracy's of the Apply/Save bit of Voyager, and that doesn't come
into it. Having reread my email, and having received several emails from
others who have had this happen "but it only happened once so we assumed it
was something stupid we did", I spotted that I missed out one vital piece of
information from my original post (apologies).
When this happened the first time, I readded the routes manually one by one.
The interesting part is that prior to the routes going missing, they all had
meaningful text comments attached to each one as is the norm. When I readded
the subnet and gateway for each of the missing statics, and applied the
changes the original text comments reappeared. This suggests to me that the
routes hadn't vanished at all, but had somehow become switched off! Remember
not all the statics vanished, just a proportion of them from the top of the
page to somewhere further down.
Noone likes to guess, but I wonder if there's adequate checks being
performed on the form data that is submitted, not so much from a field value
point of view (the Voyager interface is really pretty good at stopping you
trying to do something impossible or wildly stupid) but from a form-wide
integrity point of view. I mean, if a network problem hits halfway through
submitting a page of changes, or as has happened in the past, the SSH
forwarder for the http traffic suddenly has a heart attack, there's the
distinct possibility that the form data could become corrupt or cropped. Of
course all this is academic since I don't have time to spend exploring the
http mechanisms. I'll submit an official support call and see where it gets
me, and I'll forward any useful information that comes out of it.
In the meantime, be careful - like I said at the time we weren't making any
changes so there's no earthly reason why the routes should vanish.
Concerned,
Scott.
> -----Original Message-----
> From: Cristian Nicolae [SMTP:[EMAIL PROTECTED]]
> Sent: Saturday, September 30, 2000 9:17 PM
> To: McMeekin, Scott
> Cc: '[EMAIL PROTECTED]'
> Subject: Re: [FW1] Nokia: Possible serious bug in IPSO Voyager
> interface.
>
>
> *** Warning : This message originates from the Internet ***
>
>
> Scott,
> I am running the same version of IPSO and once I had a situation similar
> to yours.
> I have about 12 static routes configured on the box.
> Once it happened to me that one was lost.
> As it only happened to me once I didn't payed too much attention.
> One lesson I learned from then was to look very carefully at the static
> routing table after a new static route is added and afterwards saved in
> Voyager.
>
> Have you static routes disspeared after the routing table was changed
> somehow in Nokia
> (add or remove a route)?
>
> Cristian
>
>
>
>
> "McMeekin, Scott" wrote:
> >
> > Hi,
> >
> > I am unable to reproduce this problem, but it's happened twice now and
> it's
> > causing real concern. Has anyone else who is running Nokia firewalls
> ever
> > experienced an inexplicable loss of a variable number of static routes?
> I'm
> > using F-secure ssh v1.0 and Netscape Navigator to securely forward the
> http
> > Voyager interface to an IP440 running IPSO 3.2.1.
> >
> > What happened was at some point in the last couple of days I've been
> using
> > the voyager interface to look at a few things (no changes were made).
> Today
> > I get a call to say some connectivity has been lost, and on checking
> various
> > routing tables in other routers, certain routes appeared to have
> vanished. I
> > checked the firewall and Lo and Behold, 15 static routes (which get
> > redistributed internally) had vanished! After the initial scratching of
> > heads, I restored the IPSO backup and all was well, however this a
> serious
> > enough occurance to merit immediate and thorough investigation.
> >
> > Anyone experienced this before I go wading into the support channels?
> >
> > Many thanks,
> >
> > Scott.
> >
> > The Royal Bank of Scotland plc is registered in Scotland No 90312.
> Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB.
> >
> > The Royal Bank of Scotland plc is regulated by IMRO, SFA and Personal
> Investment Authority.
> >
> > This e-mail message is confidential and for use by the addressee only.
> If the message is received by anyone other than the addressee, please
> return the message to the sender by replying to it and then delete the
> message from your computer.
> >
> > 'Internet e-mails are not necessarily secure. The Royal Bank of Scotland
> plc does not accept responsibility for changes made to this message after
> it was sent.'
> >
> >
> ==========================================================================
> ======
> > To unsubscribe from this mailing list, please see the instructions
> at
> > http://www.checkpoint.com/services/mailing.html
> >
> ==========================================================================
> ======
>
>
> ==========================================================================
> ======
> To unsubscribe from this mailing list, please see the instructions at
> http://www.checkpoint.com/services/mailing.html
> ==========================================================================
> ======
The Royal Bank of Scotland plc is registered in Scotland No 90312. Registered Office:
36 St Andrew Square, Edinburgh EH2 2YB.
The Royal Bank of Scotland plc is regulated by IMRO, SFA and Personal Investment
Authority.
This e-mail message is confidential and for use by the addressee only. If the message
is received by anyone other than the addressee, please return the message to the
sender by replying to it and then delete the message from your computer.
'Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc does not
accept responsibility for changes made to this message after it was sent.'
================================================================================
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
================================================================================
