Re: [IPCop-devel] Feedback on 1.2b3

just picking off a few bugs.

On Sun, 9 Jun 2002 12:27:47 +0100 Colin Tinker <col...@g1...> wrote:

CT> all round.  I agree with earlier comments about the ssh access could this
CT> be 
CT> split up again as the browser based ssh client is not compatable with all 
CT> browsers, it works with Mozilla 1.0 final and Galeon 1.2.5 but crashes 
CT> Konqueror from KDE 3.0, I dont use IE so cannot comment.

probably not a bad idea but I could use some suggestions as to where
to put the check box.  Code would be even better.

CT> All worked fine until I rebooted the firewall box it still had the external 
CT> access rules I had put in for port 80, 443 and 25, they where displayed as 
CT> being active but where not they denied any connections on these ports.  Re 
CT> setting these ie editing them and adding them back got it all working again 
CT> but this would be a pain if I had nore ports open.  The forwards from these 
CT> rules are kept fine.

I believe this has been fixed but let me know if it shows up again.

CT> 
CT> The graphs all work well and I like the new proxy graphs.  What about 
CT> combining Dans Guardian in the future or Squid Guard?  Maybe at least
CT> adding 
CT> them to the web interface so that you may add them as an extra, pherhaps 
CT> better as DansGurdian is not truly gpl and has to be paid for for
CT> commercial 
CT> use.  At least the option would be there.

this'll need to be a 0.2.x feature.

CT> Put the IDS activation into the services page I think a more logical place
CT> for 
CT> it to be?

good idea.  Moved it.

CT> 
CT> I dont run a floppy on my firewall so being able to backup to a file would
CT> be 
CT> useful and an option to scp it from the firewall and restore it back again 
CT> would be nice using scp?

understood and I agree but not likely to change anytime soon just
because I'm short on time and sleep.


CT> Shutdown seems to hang for a long time before it does eventually shutdown 
CT> where in previous versions it was pretty quick, any reason for this?

we had a bug in the HTML generation which caused mal formed pages.  Fixed (I think)

CT> With my ISDN at least checking the persistant connection box has never
CT> worked 
CT> unless I have dial on demand enabled also.

interesting.  I'm not sure if this is a PPP feature or bug.  Will need more information.

CT> 
CT> The links for older and newer on the bottom of the logs does not work.

that's because they don't work as you might think they work.  This
code is as ugly as a Mexican hairless with acne.  The best I can
figure is that the "newer" and "older" links only become active if
there is log entries that are older or newer on that day than the ones
you are currently looking at.  Try it out.  Take a day with a big set
of logs.  You'll notice that the newer or older link becomes active
and you can navigate through logs for that day but only that day.
Changing day boundaries means using the drop-down box at the top to
set the date.  I agree, it is confusing.  Need to think about better
options.

---eric