you can find interesting OpenNMS (http://www.opennms.org/) and Capsa Free (http://www.colasoft.com/capsa-free/). Another one is a web based network tool Xymon  that you can find at http://sourceforge.net/projects/xymon/. In my opinion OpenNMS is what you're searching for.

Can you give more details on what you are looking for? It sounds like your Wireshark causes packet loss during capture, but I don't think that is likely. The software just puts a network interface in listening mode and receives all packets, even packets that are not addressed to your machine. It is not a computationally expensive task, so I can't think of a reason Wireshark should cause losses. At least other software will have the same problem, they probably also use the standard libpcap to capture the packets.

cisco packet tracer or OpenMP

you can try this Portable network analyzer(packet sniffer) freeware.

http://www.colasoft.com/capsa-free/ 

I always use tcpdump and prefer to develop my own scripts for processing the traces.

Explain your setup please. Are you capturing local computer on which wireshark also running. Or you are capturing by using mirroring port. Loss can be any place. Anyway, I will recommend tcpdump. Dont use graphical tools, graphics always increase CPU load and so increase possibility of packet loss.

 I agree with Taner Karagol, the capture environment is an important point. A sniffer which does not degrade the performance of the applications/network traffic has to be included at the best location for capturing.

I used wire shark in many test environments without any lost packets at all. Are you sure that all your packets are getting to your computer? I am in doubt about your hub. Actually, if you use a switch or a hub able to learn MAC addresses, you will experience the same problem. Use a very simple and old HUB instead.

Packet losses can happen due to your physical medium channel (copper cable, radio link, optical fiber), network equipments malfunction/configuration, network topology or QOS, or be related with one or both of your network endpoints (which includes network stack, protocols, etc). And these packets are really losses, which means that the packet information get lost at some point and the receiver never receives it.

But you may be experiencing another type of "packet loss" which can be caused by wireshark (or other capturing tool) itself and it is usually called "dropped packets". This type of loss is shown in the wireshark status bar, alongside with the number of packets captured, displayed and marked statistics. PLEASE NOTE that this information is only displayed if Wireshark was unable to capture all packets [refer to https://www.wireshark.org/docs/wsug_html_chunked/ChUseStatusbarSection.html ], which allows you to immediately infer if this is your situation. Please note also that this metric IS NOT SAVED in your pcapng files; you can see it - if it occurs - while capturing or even after you stop the capture process but still displaying the capture in the wireshark; even if you save that capture, once you close it, you will not see this metric again.

This type of packet loss relates with the performance of the capturing system, usually due to your hard drive read/write rate and overall system load. What happens in this situation is that wireshark was able to detect one or more packets in the capture network interface, but due to the low performance, it could not save the related packet information, so the capture algorithm chooses to drop that packet(s). There are some tricks you can follow to minimize (not avoid!) the low performance impact, which are explained in the "optimized Wireshark settings" section, https://wiki.wireshark.org/Performance . Note also, that the operating system has an important role in the performance; some time ago, while facing some problems related to this, I discover that the number of packets dropped by wireshark on Linux was (much!) less while capturing with Wireshark on Windows - what was not really a surprise for me. Notice that the performance issue can also happen with other software tools. I will assume that you are not generating network traffic in the same capture system, because this negatively influences the performance too.

If you are dealing with optical fiber links, I advise you to - if possible - forget wireshark or similar software tools and use instead a dedicated network performance measure equipment. These kind of equipments usually have dedicated high performance hardware, like FPGAs, that will allow you to generate all kind of network traffic and get almost all measures and statistics you may desire or need.

From my personal experience, considering a I7 Quad Processor, with 16GB RAM but a mechanical 5400rpm or 7200rpm HDD, when considering a large number of packets, from time to time - say 1 in 10/15 times - I was facing dropped packets even on a 1Gbps ethernet link. The problem was more notorious as the number of packets increases (typically for < 1 million packets it were dropped less than 1k packets but for 9 M, the number of dropped packets increases to 3M easily!). Although I successfully reduced the number of packets dropped, I could not avoid the problem because from time to time, I still get some dropped packets, which do not allow me to have 100% confidence in my measures.

Since at the beginning I have no access to a dedicated Network Performance measure hardware, I developed a simple measure system based on FPGA that allow me to despite this problem and prove the correct system function.

I hope that this information can help you.