The tutorial describes steps required for creating Cisco switch based on IOUl2. The Qemu image with installed CentOS Linux is loaded with IOU image. The IOU (IOS on UNIX) instances are attached to the network using iou2net.pl script written by Jeremy L. Gaddis. The script forwards frames between a IOU instance and a Qemu network adapters. The script is started using tap mode when Qemu interfaces are bridged with virtual tap interfaces.

Here’s a detailed comparison chart from Apple themselves which compares the iPad mini, iPad 2 and iPad 4 together. But, choose wisely! 
You can find more detail about this on apple's own website. I'll be posting more on this soon, keep following.

Note: This article is based on a Cisco Catalyst 2900, 3500XL, 2940, 2950, 2955, and 3550 switches, for other you can search and find them easily using any search engine
To recover a password on a Cisco switch, you will have to be connected to the console port of the Cisco switch using 9600 baud, 8 bits, no parity, 1 stop bit, and xon/xoff flow control. I recommend using Hyperterminal that comes with Windows XP.
Once you are connected and see something on the terminal window when you press enter, unplug the power cable. Next, hold down the mode button on the front, as seen in the photo below, and connect the power cable.


On a 2900, 3500XL or 3550 (like the one shown) release the mode button after the 1x port LED goes out. On a 2940 or 2950 switch release the mode button after the stat light goes out. On a 2955, press the break key (ctrl-break on Windows) when you see the message that the switch will autoboot.

As the subject of this topic states I want to create a dialup VPN to a Netscreen Firewall. To make it more complex I will choose the onboard Windows VPN client. At the moment only a few documentations exist and most of them contain only pieces of the whole setup process. Different threads in discussion groups out there state that the whole XP-VPN/Netscreen thing will not be possible but they lack the proof that this cannot be done.

Note: This is for educational purpose only.

These steps are based on tutorial "Defeating Cisco IOU’s License Protection" and are adapted for Fedora Linux. After the video from you-tube was deleted the creator of video made the "patch" which you can check here.

Please, consider using IOU – it is meant for internal use only thus it is probably illegal to use in case you are not Cisco employee or partner. For further information about licensing, please visit this site. http://evilrouters.net/2011/01/18/cisco-iou-faq/

Many GNS3 users use Qemu emulator to run various network OS installed on Qemu images – for example Olive, ASA, Vyatta and many others. Some users complain about not having a network connections between these devices or a console window appears and disappears after the short time. In both cases Qemu hosts are not started properly and Qemu images don’t work.
This issues are typically caused by entering a wrong parameter in GNS3 setting. For instance when user checks a box “Use kvm” in GNS3 settings and CPU doesn’t support kvm or kvm is not enabled in BIOS, it ends with warning message “unknown parameter kvm” and Qemu image is not started. Please remember that kvm is not supported by Windows so you shouldn’t have “Use kvm” checked if GNS3 is installed on Windows.
Another issue mainly occurs on Linux and Mac OS and it is caused by using unpatched Qemu binary. GNS3 create UDP tunnels in order to make connection between Qemu devices and that is why Qemu source have to be patched for UDP tunnels, compiled and installed by user. Although many Linux distributions already have Qemu installed in /usr/bin/ directory, this version of Qemu is unlikely to be patched for UDP tunnels. For this reason the Qemu doesn’t understand parameter -net type udp and it is halted after its start.
As long as patched Qemu binary is included in GNS3 all-in-one package, the Windows users don’t need to patch, compile and install Qemu by themselves.
Except of the wrong parameters I have already mentioned there can be another problems which prevent Qemu starting successfully. If you find Qemu difficult to start you should consider to do following troubleshooting to find out the reasons why Qemu doesn’t work.

Yes you read that right! iPhone 5 has been jailbroken successfully on the launch day! Popular and respected iPhone developer chpwn tweeted a picture of his iPhone 5’s homescreen with Cydia icon on it in full 1136 x 640 resolution glory (the same res. as iPhone 5).

As is usually the case when this time comes around, jailbreakers have been waiting patiently for the official word on whether it is safe to update their devices to iOS 6 or not. Although Apple have taken some design and functionality inspiration from a number of Cydia based tweaks and offerings, the hardcore jailbreak faithful still need to experience that freedom on their hardware.
iPhone Dev-Team’s Redsn0w tethered jailbreak works on today’s final iOS 6 release. Follow the simple steps below to jailbreak iOS 6 using the latest version of the iPhone Dev Team’s Redsn0w tool.
Before going through any jailbreak process it is always good housekeeping to perform a full backup of all information on the device. It is unlikely that anything will go wrong during the process but when undertaking any process that modifies the internals of a file system it is always prudent to err on the side of caution.

Here we have made comprehensive comparison of the smartphone released in last few month, but we are not giving any verdict on them though it is pretty clear. It is on you all to judge it by yourself. Do let us know what are your opinions.
     

	Appple iPhone 5	SAMSUNG GALAXY S III	Nokia Lumia 920
OS	Apple iOS 6	Android 4.0.4 Ice Cream Sandwich (upgradable to 4.1 Jelly Bean)	Windows Phone 8
Display	4-inch LED-backlit IPS TFT	4.8-inch HD Super AMOLED w/ Corning Gorilla Glass 2	4.5-inch PureMotion HD+ w/ Corning Gorilla Glass
Pixel density	~326 ppi pixel density	~306 ppi pixel density	~332 ppi pixel density
Resolution	1136 x 640	HD (1280 x 720)	HD (1280 x 768)
Height Width Thickness	123.8 mm 58.5 mm 7.6 mm	136.6mm 70.6mm 8.6mm	130.3 mm 70.8 mm 10.7 mm
Weight	112 grams	133 grams	185 grams
Processor	Apple A6	1.4GHz quad-core Cortex A9 processor Exynos 4212 Quad	1.5GHz dual-core Krait processor Qualcomm MSM8960 Snapdragon
GPU	-	Mali-400MP	Adreno 225
RAM	TBA	1GB	1GB
Storage	16GB / 32GB / 64GB	16GB / 32GB / 64GB	32GB
microSD card slot	No	Yes, up to 64GB	No
Primary camera	8 MP, 3264×2448 pixels, autofocus	8 MP, 3264×2448 pixels, autofocus	8 MP, 3264×2448 pixels, autofocus
Primary camera extras	Touch focus, geo-tagging, face detection, panorama, HDR	Simultaneous HD video and image recording, geo-tagging, touch focus, face and smile detection, image stabilization	Carl Zeiss optics, optical image stabilization, autofocus, dual-LED flash, PureView technology, geo-tagging
Front camera	720p	1.9MP 720p@30fps	1.3MP 720p@30fps
Battery	-	Li-Ion 2100 mAh	Li-Ion 2000 mAh
Wi-Fi	Wi-Fi 802.11 a/b/g/n, dual-band, Wi-Fi Plus Cellular	Wi-Fi 802.11 a/b/g/n, DLNA, Wi-Fi Direct, Wi-Fi hotspot	802.11 a/b/g/n, DLNA, Wi-Fi Direct, Wi-Fi hotspot
Network	2G Network GSM 850 / 900 / 1800 / 1900 CDMA 800 / 1900 – for Verizon 3G Network HSDPA 850 / 900 / 1900 / 2100 CDMA2000 1xEV-DO – for Verizon 4G Network LTE 700 MHz Class 17 / 2100 – for AT&T LTE 700 MHz Class 13 – for Verizon	2G Network GSM 850 / 900 / 1800 / 1900 3G Network HSDPA 850 / 900 / 1900 / 2100 4G Network LTE (regional)	2G Network GSM 850 / 900 / 1800 / 1900 3G Network HSDPA 850 / 900 / 1900 / 2100 4G Network LTE 800 / 1800 / 2600 / 900 / 2100
USB	Yes, proprietary 9-pin connector	Yes, microUSB v2.0 (MHL), USB On-the-go	Yes, microUSB (MHL) v2.0
Bluetooth	Yes, v4.0 with A2DP, EDR	Yes, v4.0 with A2DP, EDR	Yes, v3.1 with A2DP, EDR
NFC	No	Yes	Yes
Sensors	Gyroscope, G-Sensor, Digital Compass, Ambient Light Sensor, Proximity Sensor	Gyroscope, Accelerometer, Digital Compass, Ambient Light Sensor, Proximity Sensor	Gyroscope, G-Sensor, Digital Compass, Ambient Light Sensor, Proximity Sensor, Barometer
Availability	September 21	Currently available	Expected release 2012, Q4

Article Source: http://blog.gsmarena.com

The article describes installation of Junos 12.1R1.9 on emulated x86 hardware. Hardware is emulated by Qemu and Junos installed on it is known as Olive.
As Olive does not have Packet Forwarding Engine PFE attached, packet forwarding is exclusively depending on performance of the host CPU. In addition, they are also configurations known as not working on Olive. Considering these limits, Olive can never substitute real Juniper hardware.
In spite all of that Olive is an excellent tool for testing configurations that can be later deployed on real Juniper hardware. Thanks to GNS3 project that offers lightweight GUI for Qemu, complex labs can be easily deployed without real need of knowing Qemu commands.
My goal was to rewrite these articles for actual Junos 12.1R1.9 version and create a guide that helps you to install Junos. Please use links above if you feel that you need to clarify details or further explanation.

We have already posted some of the important information related to iPhone 5 earlier. These posts will helps you to decide which way to go and what you should be expecting.
 
In the articles below you can find the comparison videos of the rumored design of the upcoming 'iPhone 5' to the Samsung Galaxy S3. So if you have still not decides which phone to buy you might be able to makeup your mind from here.

Here you can find the comparison of the rumored design of the upcoming 'iPhone 5' to the Samsung Galaxy S3. So if you have still not decides which phone to buy you might be able to makeup a mind from here.

Note: Tested on jailbroken 2.2.1 3G

First download JunOS Olive 12.1R1.9 and setup all requirement http://certcollection.org/forum/topic/150241-juniper-junos-olive-121r19-for-vmwareqemu/ 
Note: you can also download from some other link by searching on google if this link is found inactive

then download StarWind V2V Converter
http://www.starwindsoftware.com/converter

Step 1

Emulators runs the real JUNOS software(which runs on a router) on a virtual machine using Qemu or the VMware. As per experience you can practice almost all the features but for sure there are few which you can't.

1:- Basic system configuration like snmp, syslog, user accounts & NTP etc.
2:- OSPF & ISIS. If you are using Qemu, under protocol ISIS you need to
configure interface type "point-to-point" otherwise adjacency will not be up. If you are using VM ware then you don’t need "point-to-point".
3:- BGP, you can configure almost all the knobs mentioned in the books.
4:- Policies works just fine with either emulators.
5:- MPLS TE also works fine.

1:- VRRP on either emulators
2:- Few firewall features
3:- L2 VPN
4:- Multicasting

JUNOS allows to configure the hardware or services which are currently not running in the router, means you can configure an ATM or a frame-relay interface and save the configuration but this configuration will not be associated with any interface, in short you can just type the command even for the hardware which is not present but you cannot see it working.
If you are a beginner then there is lot more you could do with these.

Best of luck.

NetScreen has implemented XAuth to allow another layer of authentication for VPN between a Remote Client and a Netscreen VPN Device. This negotiation takes please after the first phase of the IPSEC. You may verify authentication to the Netscreen Device’s local authentication database, radius, Secure ID, and LDAP server. You may as before use groups to combine the dial-up users or use individual dial-up users.You cannot use the group function if you are using Secure-ID or a LDAP server.

Use Funk RADIUS server to support such NetScreen-specific attributes as admin privileges, user groups, and remote L2TP and XAuth IP address, and DNS and WINS server address assignments, you must load the Funk dictionary file (netscreen.dct) that defines these attributes onto the RADIUS server. If using Cisco ACS Radius, load the Cisco dictionary file (NSRadDef2.ini). A dictionary file defines vendor-specific attributes (VSAs) that you can load onto a RADIUS server. Afterdefining values for these VSAs, NetScreen can then query them when a user logs in to the NetScreendevice. NetScreen VSAs include admin privileges, user groups, and remote L2TP and XAuth IP address, and DNS and WINS server address assignments.

In today's network environment, redundancy is one of the most important aspects, whether its on the LAN side or on the WAN side. In this topic I will be covering WAN redundancy with multiple WAN links terminating on a single router.

The best and simplest way to achieve WAN redundancy on Cisco devices is to use Reliable Static backup routes with IP SLA tracking.

IP SLAs is a feature included in the Cisco IOS Software that can allow administrators the ability to Analyze IP Service Levels for IP applications and services. IP SLA's uses active traffic-monitoring technology to monitor continuous traffic on the network. This is a reliable method in measuring over head network performance. Cisco Routers provide IP SLA Responders that give accuracy of measured data across a network.

IP SLA
Cisco IOS IP SLAs can send SNMP traps that are triggered by events such as the following:

• Connection loss
• Timeout
• Round-trip time threshold
• Average jitter threshold
• One-way packet loss
• One-way jitter
• One-way mean opinion score (MOS)
• One-way latency

Alternately, an Cisco IOS IP SLAs threshold violation can trigger another Cisco IOS IP SLAs operation for further analysis.

The Cisco IOS IP SLAs MPLS VPN Awareness feature provides the capability to monitor IP service levels within Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs). IP SLAs operations can be configured for a specific VPN by specifying a VPN routing and forwarding (VRF) name.

I have just completed the installation of nsm20091r1 on RHEL(Redhat) 5 with the help of this tutorial, but there were also some additional steps done by me that are not mentioned in this tutorial. All the additional steps are also added in the tutorial below