To share what I've learned !

I was implementing time based queue change. Rather than using mikrotik in-built scheduler i thought to execute a crontab through central location. Therefore i tried with except scripting but with telnet it failed or not working properly. I think the returned results might have any color coding input. while searching i stumble on the mikrotik perl api written by Hugh [URL:http://forum.mikrotik.com/viewtopic.php?f=8&t=22744]. i just edited the example code as follows. this is the upgrade this will be edited for the download. #!/usr/bin/perl -w #to define the api. BEGIN {push @INC, '/root/upgradefolder'} use Mtik ; $mtik_host = "192.168.28.49"; $mtik_user = "user_script"; $mtik_passwd = "passwordscript"; my(@cmd); push(@cmd,"/queue/simple/set"); push(@cmd,"=limit-at=6144000/6144000"); push(@cmd,"=max-limit=6144000/6144000"); push(@cmd,"=.id=2M"); $Mtik::debug = 0; if (Mtik::login($mtik_host,$mtik_user,$mti...

Tasks are defined in the packet trace file. 10.10.12.0/24 network ip address not bound to the PC. Otherwise this is the basic diagram. Download:http://hotfile.com/links/88950992/ac4cb5e/acl.pkt.html

This is for my reference :) . Data Pattern AFB3 Little endian B3 AF Big endian AF B3 Network Byte Order Big-Endian Host Byte Order -Depend on the Host Ref: http://beej.us/guide/bgnet/output/html/multipage/ipstructsdata.html

Invisible Things Lab - they are focused on kernel security, virtualization security and system/firmware level security who brings up certain vulnerabilities in Intel process introducing qubes which is based on virtualization concept. core concept behind the OS is based on Security by Isolation . Architecture mentioned in the above diagram(taken from the documentation). I couldn't test / or willing to download ;) . !!NOTE: You can only install Qubes on a 64-bit CPU! (most recent laptops have 64-bit CPUs) !!!NOTE: Do not try to install Qubes in a VM, e.g. VMWare. By the way if you want to try : http://www.qubes-os.org/trac/wiki/InstallationGuide http://qubes-os.org/Architecture.html http://www.invisiblethingslab.com/itl/Welcome.html

Energy Efficient concept move from data centers to servers CPU and finally come up to the Ethernet controller level. I didn't want to read the IEEE standard ( i don't have capability to understand the content ). but in future drivers will interact to provide the dynamic negotiation of the bandwidth over the Ethernet, when the link idle it tries to save the power. Relevant resources: Overall intro : http://www.nanog.org/meetings/nanog50/abstracts.php?pt=MTY0NCZuYW5vZzUw&nm=nanog50 IEEE working group: http://www.ieee802.org/3/az/public/ One more tutorial : http://www.ieee802.org/802_tutorials/07-July/IEEE-tutorial-energy-efficient-ethernet.pdf Interesting concepts : Desktop-to-switch links – Are mostly idle • Lots of very low bandwidth “chatter” – High bandwidth needed for bursts • Bursts are often seconds to hours apart • Server links are also often not fully utilized – Higher speed links offer more opportunity to save energy – This is an area where more data is needed • Ev...

Few years back getting 1Mb bandwidth internet port cost much , the same scenario experienced by the mobile operators. when the competition increases the new price model and service oriented architecture and focus on the data services increases. But the wholesale internet business seems to be facing the same problem . "Wholesale Internet Bandwidth Prices Keep Falling" according to the 2008 report it suggest between 10$ -14$ this values indicate the US pops pricing . But in the Asian countries specially south Asian countries the pricing stricture really high when compared to Europe due to the lack of infrastructure. But the Indian market giving the pressure to reduce the pricing structure. That will have certain impact on the neighbor countries. with this in mind when reaching 2020 the per Gigabit cost will be the same and the services that use to offer will be the dominating factor in the service providers. Hosting may migrate to community offer or hybrid cloud structure. whe...

Some of the ideas I've thought may be some people already done, but need to do literature survey on these areas: 1) Application issue identification based on network analysis. Since i'm working in an ISP sometime really hard to figure out the application issues that affected by network interaction. such as packet loss , throughput , mtu , jitter etc ... analyzing the packet using wireshark or other tools sometimes won't reveal important factors. ( May be i don't know how to use this tool :) ) . initial search yields some commercial tools .... 2) Data management for Network Management data. This is related to my previous post. Data capturing and logging almost standardized but how we are analyzing and how to take action mostly depend on the requirement on hand. Based on the requirements there can be different ideas. * Mal-ware , bot control traffic etc .. signature extraction * CRM integration * Network event identification * Digital Forensic analysis * etc...