Network quality and it’s correlation with bandwidth usage and numbers of packets in SETURAN12

Before continue reading this, I would like to remind you that the resulted images are solely for diagnosing purpose only, and is very subjective, since network quality is affected by many of factors.

The purpose of this post is to remind myself (just in case I got amnesia), the correlation of ping replies with bandwidth usage & packets count in pfSense 1.2 gateway.

One of the features in pfSense is RRD Graph, which graphs important information, such as bandwidth usage, CPU load, memory consumption, network (ping) quality, number of packets, and queues(if you’re utilizing Traffic shaper).

I would like to focus on network quality. These graphs basically just time based graph of ping replies to ISP gateway(s). The slower the ping responses, the higher the number on Y coordinate. 1 cell in X coordinate, correspond to 1 day.

As I stare this graph below, I notice some repetitive occurence/pattern:

Oh, forgot to mention, Week 39 and Week 40 are excluded, since we have
different modem and connection mode. Starting at week 41, I used Bridge
Mode in my ADSL modem, and a change from DHCP mode to PPPoE mode in pfSense’s WAN.

Pay attention on week 42 and 43. The quality starts to crumble down on weekend, starting at wednesday, usually at midnight. It’s getting worse when it gets to sunday, and they usually happen during midnight until the next day.

This week (week 43) it starts even ealier, in Tuesday , starting at around 10 pm and all the way to 5 am this morning.

Hmmmm, what is this? Let’s bring the bandwidth usage, see if anything similar occur here:

It seem that the correlation is (almost) linear, the higher the bandwidth usage, the data rush definetely hammered the network ping replies

Let see the packet graph:

Yes, we did see the same correlation. The higher the packet count per second, the higher the ping result

CONCLUSION: There is a linear correlation between pfSense Network Quality , Bandwidth Usage and Packet Count.

I hope this result will bring some lights to my customers of how their ISP is doing.



Telkomspeedy speed check

This is just a routine check of speed.

Hot Pixel and Pixel Mapping in Digital Camera

Today, I received an email from My-Olympus mailing list, regarding a member with hot pixel problem in her Olympus E-500. Suddenly this topic began to interest me, since I also owned E-500 second hand.

Basicly, what is Hot Pixel really?

Wikipedia give me this :

Hot pixels are sensors on the CCD with higher than normal charge leakage. On long exposure, they can appear as bright pixels.

Sensors on the CCD that always appears as brighter pixels are called stuck pixels while sensors that only brighten up after long exposure are called hot pixels.

A very good source about hot pixel & how to see/reproduce them can be located here :

  1. The longer the exposure and the higher the ISO and the hotter the temperature of the camera the more hot pixels you will see.
  2. Every camera will have hot pixels showing if you test it with long enough exposures.
  3. All cameras will develop more hot pixels over time.As your camera ages you will have more and brighter hot pixels.
  4. Some manufacturers have dealt with the problem in their newer cameras by allowing user mapout of the hot pixels.Since every camera will likely develop hot pixels if you keep it long enough, you might want to consider this when buying your next camera.

Points taken.

Example of Hot Pixel :

From Olympus website:

In short, even a brand new digital camera will definitely suffers hot pixels, and they will develop hot pixel along the lifetime of the camera.

What Olympus has to say about this issue? (well, I owned Olympus, that’s the first thing I want to hear):

The more pixels your camera’s imaging sensor (CCD) is made of, the more likely some of them may fail. Think of the lights on a Christmas tree.When the string is smaller, the lights usually fire without incident. But the longer the set of lights, the higher the probability one or more individual lights will need repair. These “stuck,” “dead,” or “hot” pixels, as they are often called, can cause the quality of your images to be compromised. Nearly every digital camera, regardless of the manufacturer, includes a sensor that experiences this to some degree. The issue may not be severe enough to be noticed, but if you do notice this phenomenon to occur, look into Pixel Mapping.

Wait, what’s that? Pixel Mapping, sounds familiar, Aha, I’ve seen it on my E-500 menu, but I never used it, ’cause I don’t know what it is for (silly me).
Let’s carry on:

Some digital cameras come with an Automatic Pixel Mapping function right inside the camera that helps prevent faulty pixels from affecting image quality. The feature can be manually selected from the camera’s menu and takes approx. 10-30 seconds to complete, depending on the camera model. By doing so, the location of the faulty pixels will be determined and stored to memory so the camera will automatically compensate for the missing information or incorrect data in subsequent exposures. It is recommended that this function be used at least once a year and if so, your camera should enjoy a much longer period of

Check your digital camera’s instruction manual to see if the Pixel Mapping feature is included.

Oke, I’m on it. Luckily, My E-500 has this feature. But my old Kodax DX-6340 and Sony HCR-90 don’t seem to own this. Sigh, It’s okay, I’m cool 🙂

pfSense 1.2.x MOD : Displaying time in Web Admin page

This mod is unsupported, and I’m not responsible for any loss

Source :,12063.msg66046.html#msg66046

edit /usr/local/www/index.php
make a new line before

System Overview

and add 

exec(“/bin/date”, $dateOutput, $dateStatus);
$currentDate = $dateOutput[0];

and change



         Platform / Current Date


Technorati Tags:

New Snapshot Update for Pfsense 1.2

Yuhuuuuu, finally, a new Snapshot update for Pfsense 1.2.1

Although it’s not final yet, some pfSense’s forum users claimed it is quite stable to be applied to production pfSense.

Version 1.3 is still undergoing major make over, so this snapshot update is the only available choice to give a new blood to pfsense.

From the wiki Known Issues in 1.2.1 Snapshots :

Load balancer was initially broken – problem with fping pfPort, fixed July 7. 
DHCP Server broken – devfs changed in 7.0, fixed as of July 9. 
VLAN problems – Appear to be resolved as of July 11. 
dhclient not using assigned DNS servers? – can’t replicate
PPTP server – apparently had issues, now working. 
Wireless has issues – apparently getting bitten by FreeBSD changes. see forum
DHCP clients don’t get DNS server assigned when forwarder is disabled and General page left blank – I think this is “by design”, and how it works in 1.2, but it needs to be verified that the two display the same behavior. 
Upgrades appear to not function with the 6.3-based 1.2 release
Various package issues
IPsec issues – new setkey causing problems with IPsec status page, other issues resolved


* Verify all packages
* VLAN issues
* ICMP issue – if the load balancer is pinging the same thing as the RRD quality graphs (which is the norm, as both typically use WAN gateway IPs), the load balancer will flap WAN connections. 
* grub problem – “The file /mntboot/grub/stage1 not read correctly”


I’ve came across this post in pfsense forum, regarding WAN flapping UP/DOWN in MultiWAN mode. The problem has been discovered, it’s the FreeBSD 7.0 issue:

When running simultaneous ping processes from the host to the same target on a FreeBSD host where 2 different processes ping the same host, one process will see the echo replies from the other process and fail.

We came to see this on pfSense 1.2.1 which is based on FreeBSD 7.0p4 and is using fping to monitor the gateways.

People in our forum started complaining that gateways were invalidly marked as down. More investigation from the users led to the discovery that out of sequence replies were causing fping to fail.

 It’s very sad news, so, in the mean time, my dear pfSense at Tekim, you will have to wait a little longer

Integrating Flickr + Joomla 1.5 + MetaWeblogAPI

This post will show you how to post to your Joomla 1.5 sites within Flickr, by utilizing MetaweblogAPI for Joomla

  1. Login to, if you’re already have YahooID, then use it. Then, at your Home page, click “Do you have a blog” link

2. There will be a description page about this feature, then we click “set up your blog”

3. You will be taken to Your Account / Blog Page, then you click “Set Up Your Blog”

4. We had to answer about what kind of weblog we had. Since we’re gonna use Joomla + Metaweblog, then choose “MetWeblog API Enabled Blog”

5. Then you must fill in some login details for your Joomla Site. Notice the syntax :
http://joomlasite.domain/xmlrpc/index.php”. Don’t forget to fill in Username & Password (for your joomla site). Click Next.

6. Next, Flickr will try to connect to your website. When it succeeded, you’ll notice the name of the Label & Weblog will match the name of your Joomlasite title

7. Flickr will display a message state that the blog has been added to flickr. Optionally, you could click “create a custom posting template now”

8. Choose templates which suit your purpose.

9. You’ll see the template preview, if you’re satisfied, then Click “Use This”

10. Then you’ll be redirected to Blog List page. You can make change settings, add another blogs, or test posting. We’ll try the later. Click on “Test Post”

11. Go to you joomla site, and if everything works correctly, you will see this kind of post on your website:

Congratulation, you’re done!

Technorati Tags: , ,