BLOG OUT LOUD!

[VIDEO] - Step By Step Guide To Install NSM 2009 On RHEL 5

2012-01-04T04:31:00.000-08:00

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

Within this tutorial we will be installing Juniper NSM 2009.1 onto a RHEL (Redhat) 5 server.

Click Here To Play The Installation Video

Below describes the steps within the above video :

Transfer FilesCopy the required files across to your server. These files are : nsm2009.1r1-systemupdate-linux.zip & nsm2009.1r1_servers_linux_x86.zip.
You will also need to ensure you have rsync and unzip installed.

Update your server

To ensure that the NSM has all the required dependencies installed you will need to update you server by running the update package. This is done by unzipping the zip, untar`ing the tarball and running the install script.

Change Kernel Settings
The following kernel setting will need to be set "kernel.shmmax = 402653184". This change can be done by running the following line :

sed -i 's/kernel\.shmmax.*$/kernel\.shmmax = 402653184/g' /etc/sysctl.conf
Once done you will need to reboot your system.

Install NSM Software
Unzip the install package and then run the install script. Once installed you can run log into the NSM GUI and import your firewall device. This is outside the scope of this article.

Please Note : Within the video tutorial the sections where no input appears to be entered the default setting (value with sqaure [#] brackets) is being used by just pressing the enter key.

Problem Faced While Installations & Their Solutions

Problem1:

Some users might face some problem while installation of nsm2009.1r1_servers_linux_x86.sh as shown in the example below, this issue can be resolved by changing the transfer mode from ASCII to binary (We also faced the same problem while using WinSCP, finally the issue was resolved when the file transfer was done after changing the mode from ASCII to binary in WinSCP)

# sh nsm2009.1r1_servers_linux_x86.sh

Extracting payload....

Decompressing payload....

/bin/tar: Skipping to next header

/bin/tar: Archive contains obsolescent base-64 headers

gzip: payload.tgz: invalid compressed data--format violated

/bin/tar: Error exit delayed from previous errors

FAILED

Resolution: This error usually occurs when a file is transferred over to the server in ASCII mode. To resolve the issue, transfer the file over to the server again; this time in the binary mode. The best practice is to uncompress the file on the server which also helps to verify file integrity.

Source: Juniper Knowledge Base

Problem 2:

Once the file nsm2009.1r1_servers_linux_x86.sh is transfered to redhat server, some user might not be able to run the file

# sh nsm2009.1r1_servers_linux_x86.sh

error while executing ...

Resolutions: This can be resolve by just changing the mode of the file

# chmod 777 nsm2009.1r1_servers_linux_x86.sh

Note: If you are installing the UI on RHEL 5, first install the “libXp” package.

You can obtain libXp from RedHat.

Courtesy: Fir3net.com

[FIX] - Amazon Kindle Fire & Nook Tablet USB Driver Problems

2011-12-28T22:15:00.000-08:00

The Amazon Kindle Fire and the Nook Tablet are the most budget and popular android tablets today. Both of these two tablets have no USB driver software, because the USB driver is contained in its utilities. Generally, if you installed the uitility correctly, you wouldn’t have any problem with USB driver, as it would be installed spontaneously to your computer.
While we have found many Nook Tablet & Kindle Fire users encountered problems when the USB driver was installed, and fortunately we have also found a trick about fixing the USB driver issue on Nook Tablet, we think it should help you.

How to fix USB driver issue:
1. Make sure usb debugging is checked(both)

2. Automount is not checked
3. Uninstall all drivers in USBdreview
4. Go to Control Panel > Advanced System Settings > Hardware Tab > then click “Device Installation Settings”. Change this setting to “No, let me choose what to do”, and make sure “Never install driver software from Windows Update” is checked below that.
5. Go in Device Manager, expand the USB Mass Storage Device selection, search for the USBMass Storage device of your Nook Tablet
6. Click “update driver” and select the folder manually

Now you are able to use adb shell on your computer to execute orders. Please let us know from your feedback if it was helpful.

Kindle Fire Driver Problems In Windows XP & Windows 7

2011-12-28T22:06:00.000-08:00

While the Kindle Fire has been a sales sensation, some owners have had some early complaints about usb drivers, bugginess, particularly with the touchscreen. Amazon has done its best to remedy those problems with a new Kindle Fire update (6.2.1) which already rolled out. But still a large number of

users are still encountering the problems related to usb drivers on windows XP & Windows 7, these issues are discussed on different forums with very helpful solutions some of those solution are listed in this post below. We had already discussed some of these solutions in our earlier post on Kindle fire driver problems & solution.

Kindle Fire Driver Problem in Windows XP

Robert R says
Hello,
I am trying to locate the driver for my Kindle Fire. When I plug it into my laptop, an Inspiron 6400 with Windows XP, Windows can see that it is there, but asks to locate the driver. It will not show up as a mounted USB mass storage device.
Help?

Robert R says
Here is an update to my driver issue. I downloaded the Easy Installer application from the Amazon App store and installed it on my Fire. Now I notice that if I plug in the usb cable to my laptop and the Fire while my Fire is in "standby" or "sleep" mode... ie black screen, then the laptop will wake the Fire to the "open" screen, the one with the yellow arrow. If I do nothing, the laptop will open the New Device window and ask for a driver. At this point the Kindle is simply listed as a "Removable Disk" and clicking on it will prompt you to insert a disk. No disk capacity is listed. So, cancel out of the New device screen and then start the Fire by swiping the yellow arrow. Now my Fire will immediately tell me that it is connected via usb and the laptop now sees the "Removable Drive" as in fact a Kindle. All folders are available.

If the Easy Installer is actually to credit for this I do not know, but it works for me. I have not uninstalled the East Installer. Maybe later.

I hope this helps.

sgood1971 says:
That did the trick, thank you.

Kindle Fire Driver Problem in Windows 7

Bob Robesky says:
I was having the exact problem and, I think I found the solution. Plug in your cable as you have already done. Then login to the Kindle Fire. You should now have a message that "You can now transfer..." and the drive icon should now be enabled.

blogarsay says:
Yes, I get that message, and there's a drive icon, but when I click on it it says "please insert a disk in drive f".

Shoebox says:
I tried to transfer a movie to the Fire this morning. Would not work due to driver on my Vaio, so I tried my HP laptop. Said driver was not successfully loaded, however, I saw the Kindle on IE and transferred the movie OK. Later tried to transfer another movie and neither laptop would show a Kindle drive. Was too busy today to try again. ?? Tomorrow, I'll make sure to log into the Kindle before plugging in USB and see if it works.

Nospin says:
Have you tried a different cable and a different USB port?
What does your computer usually say when you insert a USB drive?

Shoebox says:
No, I didn't try a different cord. I just used the one that came with my previous KK. Usually, when I plug in something by USB, I get a box asking me what I want to do - view files, import, etc.

A. Gabriel says:
I am stuck in the same cycle! What to do?

Bob Robesky says:
If you can see a drive icon that appears greyed out on your desktop login to your kindle by sliding the orange arrow to the left. You should then see a page that says your Kindle is connected with the USB cable. Again check your drive letter icon. It should now be in color and you should be able to access your Kindle as a drive.
If you don't see any icon, I have no clue what you should do.

Gretchen Z says:
Try waking the Kindle up BEFORE connecting the usb cable. My Fire has to be on and awake when I connect it for the computer to recognize it.
ETA - I'm using Windows Vista.

blogarsay says:
I don't know about everyone else, but I've done that and it makes no difference.

AmeliaA says:
Last week, someone was on who had the same problem with the Fire not being recognized on their computer (running Win Vista), but it worked fine on his sister's computer. Their seems to be a random software glitch with some versions of Windows recognizing the Fire as a "removable drive."

Jon Case says:
I had a similar problem on both a win7 and vista PC - I would connect my Fire to the PC, but the PC would recognize it as a 'removable drive', and I couldn't view the files on the Fire. I had success with the 'wake the Fire' approach - before plugging in the USB cable to my PC, I woke up and unlocked the Fire, then plugged in the USB cable. After a few seconds, my Fire showed a message saying "You can now transfer files from your computer to Kindle", and the PC showed the Kindle as a regular USB device, which I could view and move files to. I confirmed this worked on both my win7 and vista PCs.

J.J. says:
I have the same problem and I think it's because Amazon just wants you to shop, shop, shop on their site and not use Project Guteberg, etc. So I am returning the Kindle and buying another table.

Old **Bah Humbug** Rocker says:
My Dell laptop has 2 USB ports, one in the back and one on the side. The Fire will connect on side one, but not the other. I recall there are different specs on the two ports, but I'm too lazy to look it up. I just know one works and the other doesn't.

Adrián Arias Marín says:
I want to transfer my music and videos from my computer to my kindle fire by usb cable, but it appear a message on mu kindle that say that i can't transfer files from my computer -.-

J. Dye says:
I followed your instructions and it worked as advertised. Thanks

TiUTiger says:
Have had similar problems with the Fire as well as some mp3 players. I use Xyplorer as my file manager, and it doesn't see the external drives. But, if I use Windows Explorer, they all show up.

Pete Berryman says:
I am having similar problems. When I plug my Kindle Fire in I get the message "One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it. For assistance in solving this problem, click this message." No clicking on message does not help.
I have tried it on all three PC's in the house (all running Windows 7) and same result.
I have done everything that I could find searching this forum and others such as making sure Fire is not in sleep, make sure drivers updated for both it and PC's, powered Fire down and power up reconnect. I have rebooted the PC. I have tried different USB ports. Although it doesn't appear to be a connection issue since the Fire is charging through the USB Port. I even went as far to a power reset.
No mattter what I do I get the same results.

Laura Knospler says:
I have Windows 7 home, service pack 1 .. same problem as you guys.. but after putting my password in while the kindle was connected to the computer it worked.. I'm using a usb mini cable from my daughters cheap cell phone..

Allyn Boldt says:
An alternate to using the USB cable. Buy WiFi File Explorer PRO app from the app store on your Fire. Purchasing from the Fire itself will automatically download and install the app without using the USB cable to sideload the app. Then you can transfer files from your home computer with your in-home WIFI.
The amazon link to look at the app is: WiFi File Explorer PRO
Remember, purchase it using your Fire for automatic downloading and installation on the Fire.

William Chinn says:
I have no problem, but here is the sequence: Connect cable to Kindle Fire, then connect cable to PC W7. Fire will boot and if you are passworded Fire it will ask for password. You will then get transfer message. The PC should beep recognizing the USB device. Now if you wait a few more seconds, the PC via Windows Explorer will recognize "Kindle" not "removable drive". You can view folders/files on the "Kindle" drive like any other drive. You should "Disconnect" before removing cables.

blogarsay says:
That's the first thing anyone's said in this thread that could actually help. Thanks!

Regina Oliver says:
I am having the exact same problem. New kindle fire. registered on line with amazon. usb port not recognized either through belkin or in back of computer. get message on kindle saying there is a connection and i can transfer files but no go.

Jordyn Doyle says:
I plug mine in and it tries to install the driver software and then it fails and I don't know why. The program I use to transfer documents doesn't find my Kindle and I'm sure it's because the software fails to install. Does anyone know why?

Ernie says:
There are no drivers. I don't know what software you're using to transfer files. But it should see the fire as a drive allowing for drag & drop.

Check out this video link on Kindle fire Windows 7 USB drivers

Courtesy: Amazon

XDA Developers Forum

Related Article:

Kindle Fire Driver Problems & Solutions

Step by Step Guide To Install Android 4.0 on Kindle Fire

2011-12-27T23:47:00.000-08:00

An early build of Google Android 4.0 is now available for the Amazon Kindle Fire tablet. While developers have solved a bug affecting the “sdcard” portion of the device, there are still audio, video, and application bugs that need to be fixed.

But if you’ve already rooted your Kindle Fire and installed TWRP 2.0 it’s actually pretty easy to take Android 4.0 Ice Cream Sandwich for a spin without much risk. You can always just revert to your previous software, whether that’s CyanogenMod 7 or Amazon’s stock software.
Be forewarned, it’s a kind of complicated process and there’s plenty of room for things to go wrong. While it’s tough to truly damage your Kindle Fire or leave it in an unbootable state, it’s pretty easy to leave it in a state that’s difficult to recover from without trying a half dozen different recovery techniques.
With that in mind, this guide is aimed at people that have already installed TWRP.

Download all the files you’ll need/want

There’s an active development thread at the xda-developers forum where you can find the latest tools for installing Android 4.0 on the Kindle Fire. It’s likely that the download links will change as new builds are released with new features and improvements.

So make sure to download the latest files from xda-developers. As of 12/27/2011, that involves:

tryforupdate.zip - I recommend using the version packaged by XperiaPlayer which includes the SD card fix.
gapps_ics_4.0.3_v8.koush.zip - This installs the Google Android Market and other Google apps.
Trubuchet.zip – This is the latest launcher app from CyanogenMod 9. You don’t need to install it, or even flash it from TWRP, but it might be easier or faster than installing it manually after Ice Cream Sandwich is up and running.

Once you’ve downloaded these files, copy them to your Kindle Fire’s storage by connecting your Fire to your PC with a USB cable, and dragging and dropping the files to your tablet. You can also simply download them all directly on your tablet using a web browser on your Kindle Fire.

If you put the files in a folder, make sure you know what folder they’re in.

Boot into TWRP

1. Turn off your tablet by pressing and holding the power button and then selecting the on-screen option to shut down.

2. Press the power button to turn on the tablet.

3. As soon as you see the yellow triangle with a fire icon in the center, press-and-hold the power button until it glows orange instead of green. If youdon’t see the yellow triangle then you probably don’t have the FireFireFire bootloader and TWRP 2.0 recovery installed.

4. It will take 10 to 20 seconds for your device to boot into TWRP 2.0

Backup your system

Before continuing it’s probably a good idea to backup your system. TWRP makes this easy to do, allowing you to restore your device to its current condition if you decide Android 4.0 isn’t for you yet. This is very likely, since the build that’s currently available is primarily designed for developers to test and improve.

1. Tap the button that says backup.

2. Select the items you want to backup. At a minimum this should probably include the System, Data, and Boot items.

3. Tap the Backup now button.

A progress meter should appear letting you know how things are going. You can also tap the terminal icon in the upper right corner to see a text description.

4. When the backup is complete, tap the button that says main menu to return to the home screen.

You can restore from this backup at any time by booting your device into TWRP and tapping the restore button on the home screen. Then choose the backup that you just made from the list.

By default, backups use the time and date you made them as their file names. You can also change the name to something more memorable without affecting the integrity of the backup.

Wipe your data

1. Tap the Wipe icon in the upper right corner.

2. Choose the Factory Reset option. This won’t erase data stored on the sdcard partition, but it will clear your data, system, and other partitions.

3. You have one more chance to change your mind. Tap the Factory Reset button to continue.

4. After the data is wiped, tap the back button to return to the previous screen.

5. From here you can tap the home icon or back arrow in the top right corner of the screen to return to the home screen.

Install Android 4.0

1. Tap the Install button on the home screen.

2. If your files are in the root directory of your sdcard, you should see them in the box on the right. If not, use the file browser on the left to navigate to the folder where your files are located.

3. Tap the file called tryforsdcard.zip.

4. Tap the big button that says Flash to get started.

5. You’ll see text on the screen and a progress bar. Wait until the installation completes. You may see some error messages, but it’s safe to ignore most of these.

6. When the progress is complete you can tap the reboot button to boot into Android 4.0 — but if you want to install Google Apps and other files, hit the back arrow instead.

7. Choose the next file you want to install and repeat steps 3 through 5. I installed gApps first and then repeated the process with Trebuchet.

Boot Android 4.0

When you’ve finished installing all the zip files, it’s time to boot into Android 4.0.

1. You don’t necessarily need to do this, but it may be a good idea to hit the button that says Wipe Cache/Dalvik after installing the last zip file. This is probably more important if and when you decide to use TWRP to flash an update to existing software, but in this case we’re performing a fresh install. Hit the back button when you’re done wiping your cache.

2. Choose the Reboot System option.

That’s pretty much it. Your device should now reboot and load Android 4.0.3 Ice Cream Sandwich. Follow the on-screen prompts to setup your device by enabling WiFi, logging into your Google account, and you should be good to go!

Thanks to JackpotClavin, bl1nkk, and XperiaPlayer from the xda-developers forum for making this possible.

Install Android 4.0 on Kindle Fire

[How To] - Untethered JailBreak iOS 5.0.1 For A4 Devices Only

2011-12-27T03:58:00.000-08:00

Finally, the day has arrived. The much awaited exploit from @Pod2G which was in development from few days is now released from DevTeam. You can apply the untethered from the tweak which has instantaneously come up in Cydia from @P0sixninja. If you are currently using a tethered JailBreak on iOS 5.0/iOS 5.0.1, open Cydia, search for ‘Corona’ and install it. After the reboot, you would be on an untethered JailBreak.

However, you always have the other alternative. You can download the recently updated Redsn0w from the DevTeam, run it over the tethered JailBroken iDevice , follow the instructions and you are done. Only the following A4 based devices are supported :

iPhone3GS

iPhone4

iPhone4-CDMA

iPad1

iPod touch 3G

iPod touch 4G

According to the DevTeam, you should update to iOS 5.0.1 if you haven’t done yet. The APTickets/SHSH Blobs can be saved using Redsn0w and eventually, Cydia has also started saving them. If you are one of they users who rely on ultrasn0w, update to iOS 5.0.1 using the custom firmware which would preserve your baseband. Ultrasn0w is now completely stable on iOS 5.0.1.

You shouldn’t confuse yourself between the two choices. Redsn0w and the package which is being offered from Chronic DevTeam uses the same exploit or patches and there’s not much of a difference. Though, the latter is more handy. While running Redsn0w second time for the untethered JailBreak, you should uncheck ‘Cydia’.

Download Redsn0w 0.9.10b1 from here: Mac, Windows

PS: The untethered JailBreak is not for A5 devices such as iPhone 4S and iPad 2.

Let’s know if you face any issues in the comment section