gnutella setup with firewall configuration and port forwarding Fedora 16

Just wanted to jot some notes down about setting up gnutella to go through the standard firewall on Fedora 16.

I was getting this little annoying message from an ugly red icon on the lower right bar of Gnutella:

You appear to be firewalled both TCP wise and UDP-wise...

The message is actually much longer than that, but that should do for search engine purposes, so that folks might find this little tut.

Let's change that message to read this:
People can connect to you using both TCP and UDP.  Push should work and you will be able to receive out-of-band results for your queries.
With a happy little yellow smiley face wearing sun-glasses...

{WARNING:  This method involves changing your connection to the internet through router settings and firewall changes.  You MUST have administrator privileges to execute this method.  I highly recommend either having a thorough knowledge of how to reconfigure your internet connection should something go wrong OR having another computer handy to look up trouble shooting information on the internet to FIX what got broke, should you make a mistake.  Obviously, you will NOT have the ability to look up help on this computer once you screw up your internet connection .  (NO, I do not recommend just using a phone, there would be far too much stuff to look up; it would take eons that way.)  Please proceed with caution, I've literally spent a week fixing a network at my parents that I screwed up many years ago, because I made just a mistake or two.  Learn from my mistake.}

I've got a Netgear router.  The method is very similar in LinkSys, Belkin, D-Link or any router I've ever worked with.  I logged into the router by typing 192.168.1.1 into the url field in Chrome.  This, I find, works for most router configurations.  You need to know your login and password, of course.  If you don't, then try admin/admin or password/password or admin/password.  Often routers are setup with one of those combinations as the default.  Also, if you can't figure out the password, you should be able to reset the router to default settings and THEN use one of those.  Look up the router through the manufacturer to find this default login.  Sometimes, depending on your isp, resetting your router could leave the router non-functional without contacting the isp and running some procedure, but, because I always choose the do-it-yourself method of installation, I have never had that problem.

Go to the Port Forwarding/Port Triggering tab/menu.
On Netgear, I chose, "add custom service".
I named the service "gnutella", just so I would know what it was.
Chose service type TCP/UDP.
Choose a start port between 49152-65534 (these are the recommended ranges)  I usually go with 55555 or 50505 or something really easy to remember like that.  It's up to you.
Make the end port the same.  In my case, also 55555.
For Server IP address I entered 192.186.1.70
Leave the first three digits the same.  The last one "70" in this case, is the only one you generally want to fiddle with.
When assigning static IP's I stay below 100, and I stay above 20.  DHCP (when the router dynamically assigns an IP to all the machines attached to it WHEN it discovers them) seems to always start with single digit numbers.  Going up from 1 as it finds new devices that wish to connect.

Now go to your Network Connections.  Either just click on the icon in the upper right and then click Network Settings, or go to Acitivities/Applications/Network Connections.
I'm wired, but it's pretty much the same for wireless.
Click "Configure..."
Select the IPv4 tab.
Click the "Add" button on the right.
Enter the Server IP address you chose above (192.168.1.70 in my case)
Netmask: 255.255.255.0
Gateway: 192.168.1.1
DNS servers: 8.8.8.8, 4.4.4.4 (the Google servers)
That should do it.  Now you have a static IP for that machine.  For THIS method you need it for the port forwarding to work.

Now that we've got the port forwarded, time to tell gnutella what it is:

Open gnutella.
Choose File/Preferences.
Under the "Network" tab at "Listen Port" enter 55555 ( or whatever you chose above ).
Network Protocol: IPv4 and IPv6.  Check box "Enable UDP" and "Enable DHT"
I went ahead and checked the box for Public hostname and entered a name, but this is somewhat irrelevant.
Leave the rest alone.
Now, the Fedora 16 part:
In the far upper left click on Activites and then choose Applications.  Find Firewall and open that.  You will be asked for your administrator password, so better know that.
Go to "Other Ports".
Click "Add" button on the right.
Select "User Defined".
Enter the port you chose (55555)
Select TCP.
Choose "Add" button again.
Select "User Defined">
Enter the port you chose (55555) yes the same one.
Select UDP.
Click Apply at the top.
That should do it!

Now I see a nice little smiley face at the bottom right of gnutella.

Setup Android Development in Eclipse Indigo 3.7.1 on Fedora 16

Go to http://fedoraproject.org/wiki/HOWTO_Setup_Android_Development.  Mostly, I followed that, but I throw in some details, hints and problem solutions below.

When you edit the path variable.  Just open a terminal CD to your home folder (if you are not there already), type:

gedit .bash_profile

I should mention that when I downloaded the SDK I unzipped it into my home folder and then renamed it "SDK".  I like my names short and sweet when I foresee having to type them in a terminal a lot.

Add this to the bottom of the file:

PATH=$PATH:$HOME/.local/bin:$HOME/bin
export PATH

PATH=$PATH:$HOME/bin:$HOME/SDK/tools:$HOME/SDK/platform-tools
export PATH

Under "Running Emulator" -
Note:  Hit "esc" to back out of the AVD manager.  And close the android SDK manager.

Back in the tutorial, when you get to running the emulator via the terminal, the part where you type:

./emulator -noaudio -avd android_dev1

be careful, because I noticed an error in the tutorial right there.  When creating the AVD they posted an image.  In that image the name of the AVD is "android_dev", but, as you see they then type "android_dev1" not "android_dev".  This could cause trouble.

When you get to -

Hello Fedora
Configure Android in Eclipse

NOW We have a real problem.
"Android" is supposed to be an item added to the menu under "Help/Preferences" when you update/install the Android Dev Tools with the SDK Manager.  Unfortunately, (again, possibly because of operator malfunction), this item did NOT appear in any Eclipse menus nor did anything related to Android appear anywhere inside Eclipse.  What you are saved from, if you read this in time, is literally days of searching for an answer to this, countless uninstalls/reinstalls, and much hair pulling and teeth grinding.  Android MUST be added to the menus.  Installing the ADT plugin in Eclipse is the entire point of this whole process, so luckily, Mike helped me find the solution.  It was INSANE, but we found it.

In order for the android menu items to show up we need to uninstall then install the Android Development plugins.  As mentioned, you cannot do this through "Help/Install New Software" which would be the logical solution.  If you try, you will get error messages saying that they are already installed (even though they are not functioning).  Even if you even completely uninstall Eclipse, these plugins will still claim to be "already installed."  A method I tried from 7 different angles without success.

Lucky for Fedora (because I was about to trash it and go back to Ubuntu), Mike, my brother, had the solution.

It turns out that Eclipse DOES have a way to uninstall these things.  The thing is they hid it behind a moving hedge inside the freaking Bat Cave.  To get to it you have to go under Help/About Eclipse Platform/Installation Details.  Yeah, that's right.  "About"!!!  The place you go to see what version you are using, copyright warnings, and company website information.  NOT where you would think to go to uninstall plugins.  BUT IT IS where you go to uninstall plugins.  So go to:

Help/About Eclipse Platform/Installation Details

And there they are!  Select all 4 android related items and click uninstall.

Restart Eclipse.  Go back to

Help/Install New Software

Go to the Android Plugin link you created.
Check box next to Developer Tools
Select Finish.

When done restart Eclipse and and voila!  On reboot a new dialog box popped right up in the front asking to either install the latest SDK's or point to existing ones.  I told it where the existing ones are:  home/ultrajones/SDK.  And just like that, Android listings have been added to the File, Window, and Window/Preferences menus.  We are ready to roll.

I decided to try and get the API Demos running on the HTC Inspire phone that GRQ is using as one of our dev phones.  Here is the process:

Plug the phone in via USB cable.

In the menu bar select:
File/New/Android Project

In dialog box select "Create project from existing sample".  Click next.

Select Android 2.2.  Click next.

Select ApiDemos and click Finish.
You will see it appear in the bar on the left.
Select it.  (hilight it in blue) and go to:

Run/Run Configurations...

I entered a "Name:" as Inspire (name of the phone, because we are creating a configuration to pull up whenever we are running anything on that particular device).

Click browse and select the newly created sample project.

Click Apply.
Click Run.

A dialog box pops down.  I see 2 selections.

"Choose a running Android device"
or
"Launch a new Android Virtual Device"

I chose HT14CT204610 because that is the phone I have plugged in.  With that hilighted...

Click OK.

Now I've got the ApiDemos (a whole slew of little sample apps) running on my phone!  Woo hoo! FINALLY!!!!