niklas.berggren at consultant
Apr 26, 2004, 12:39 AM
Post #4 of 4
First of all, I'll admit that the ntop-issue was all my fault. The problem was that I never added support for RAM block-devices in my kernel, since I wanted to utilize my diskspace on my laptop. Rather than mounting a RAM-disk on /var/ramdisk, i created the directory /var/ramdisk with world read/write permissions. (it's not like security is paramount on this box). Appearantly ntop didn't like this. With a new kernel including the RAM block-device support however, everything works perfectly.
At best, I'm a mediocre C-programmer, so I'm not the man to analyze ntop meaning to find out why this method didn't work.
The frames issue was related to this. I'm currently stuck using MS Internet Explorer (ugh!), but it's still a browser issue.
Appearantly, when IE loads a 0-byte large frame, it screws up (yeah, what's new?) and completely ignores the target="targetframe" attribute in the <a> tag, and opens a blank, new window. With things fixed however, it appears to work fine.
Anyhow, I'll give the new version a go, and if I find more problems that are in fact my own fault, I know where to whine, yes? ;)
From: ntop-misc-admin [at] listgateway
[mailto:ntop-misc-admin [at] listgateway]On Behalf Of Luca Deri
Sent: den 26 april 2004 09:21
To: ntop-misc [at] fuji
Subject: Re: [Ntop-misc] Troubles with nBox.
-----BEGIN PGP SIGNED MESSAGE-----
I have just released an update (1.9.2) or if you want a new firmware
image that includes the latest ntop/nProbe. In my tests everything
seems to work perfectly. If not please let me know.
The problem of the frames is something I also experience using my Apple
Safari browser. I don't see the problem with any other browser so I
assume it's a problem of Safari also because if I open the ntop page in
a new window everything works fine.