Database Users

[VIDEO] Samsung Captivate IPSec VPN How-To

All links pulled due to XDA Request after an XDA member complained I was only out for profits to a moderator on a few products I have. Due to the fact I link to a product or two and a few other things in many videos, I was asked to pull any content relating to this.
I will still be offering all this great material at my website. Just go to google and search for MobileTechVideos.

I really think these how-to videos should be in Q&A (or general) instead of development.
Sent from my brain using Thumbs 2.0.

glitterballs said:
I really think these how-to videos should be in Q&A (or general) instead of development.
Sent from my brain using Thumbs 2.0.
Click to expand...
Click to collapse
I'd probably agree. I put that line in their for a MOD to move them if applicable. Now that I decided to dive into this, if a MOD moves this, might you be able to join my ROM flashing video with this one?
Thanks.

My company uses Cisco VPN along with RSA SecurID.
I've tried other "solutions" in the past with no success.
Will this process work in my situation?
I have access to all the settings from a .pcf configuration file.
When I had an iPhone, VPN worked perfectly (not that I'd go back to an iPhone just for that ).

The VPN Connections applications allows for a secure token so I think it may work. The SecureID just gives you a token correct? And then you input it for access?
If you watch near the end of video 2 I show you that application and there is clearly a field for token input. You should not need the .pcf file for the phone. I would think you would just input the current token each time.

I tried it and the connection fails every time.
Went through the process twice and followed directions to the letter.
I also tried the check box "Password + Token Digits" and that did not work either.
I'm using a 2.2 ROM currently but I think I'll put my phone back to stock and try again with 2.1.
Your video is excellent, by the way, and extremely easy to follow.

Thank you for compliments. Did you verify tun module was running using the lsmod command from a shell?

connexion2005 said:
Thank you for compliments. Did you verify tun module was running using the lsmod command from a shell?
Click to expand...
Click to collapse
Yes, tun was definitely running.

thank you much, works well.

jwolfburg said:
thank you much, works well.
Click to expand...
Click to collapse
Glad it was able to help you! I know I would have loved this info 6 months ago as I was figuring it out. If you are looking for a good RDP app, then use RemoteRDP. I'm using the $20 enterprise edition and it's amazing. They have cheaper versions as well with a few less bells and whistles options.
Now I'm just trying to crack DNS issues with Android not resolving hostnames of machines when VPN'd or on a WIFI network.

I am getting a device or resource busy when I do insmod android22tun.ko
I am running auxura and I skipped the rooting process as I am obviously already rooted.
Any ideas anyone?

I suppose you could try modprobe instead of insmod just to see. It could also very well be ROM dependent and something with this particular tun.ko file could be incompatible. There are many different tun.ko files for different kernels.

connexion2005,
I just wanted to thank you for the awesome step-by-step tutourial on getting my phone connected to IPSec VPN. I too am a IT Admin and recently got my phone with the objective in mine to remotely manage infraustruture. Your instructions are to the point and didn't leave much to guessing.
BTW: at the end of the video you mention the gscript tool to run the tun.ko for reloading. Shouldn't you actually had said adroid21tun.ko? That's what works.

mrjazze said:
connexion2005,
I just wanted to thank you for the awesome step-by-step tutourial on getting my phone connected to IPSec VPN. I too am a IT Admin and recently got my phone with the objective in mine to remotely manage infraustruture. Your instructions are to the point and didn't leave much to guessing.
BTW: at the end of the video you mention the gscript tool to run the tun.ko for reloading. Shouldn't you actually had said adroid21tun.ko? That's what works.
Click to expand...
Click to collapse
I mean the technical name of the vpn module on linux based equipment is tun.ko so that's what I went with. I understand that may be confusing now. Whatever the module is named is what needs to be loaded. So you could call it mobiletechvideosdotcom.ko and that's what you'd load...lol. Thanks for the compliments!

Your very welcome. I think i have watched all your videos and I have to say great job.
sent from my Samsung Captivate using XDA app.

connexion2005,
It seems I have run into a problem. I have been able to connect to our ASA a few times already, but when I just tried today it fails. After investigating, my script to load the android21tun.ko fails with error "init_module 'android21tun.ko' failed (file exists). I even get the failure after reboot phone. Do you have any suggestions.
PS: Out of curiosity, you suggested RemoteRDP, have you tried PocketCloud? I like it so much I will pay the $14.99 for full version.

Thank you. This worked like a charm.

mrjazze said:
connexion2005,
It seems I have run into a problem. I have been able to connect to our ASA a few times already, but when I just tried today it fails. After investigating, my script to load the android21tun.ko fails with error "init_module 'android21tun.ko' failed (file exists). I even get the failure after reboot phone. Do you have any suggestions.
PS: Out of curiosity, you suggested RemoteRDP, have you tried PocketCloud? I like it so much I will pay the $14.99 for full version.
Click to expand...
Click to collapse
I have not used PocketCloud but RemoteRDP is absolutely phenomenal. Is this occuring even after a reboot? Perform an lsmod from a terminal and check to see if the tun module is running. I'm not sure why this would happen. May have to uninstall everything including the tun and re-perform the steps.

I did get it to work again. Strangely, it was after receiving a phone call that the module would load. Thanks again for your assistance.

Well that's good. I can't explain any bugs as my dev work only extends so far!

[Q] Nook Color CM9/ICS Netfiler/IPtables

Long time reviewer, first time poster - can't post in the dev forums until I have 10 postings (sigh).
Question for the devs or others in the know - in the ICS (granted very early) builds, I can't get IPtables to work, but an earlier list of changes seems to indicate that this should be working.
Manifests itself with errors starting the firewall in Droidwall. So, am I doing something wrong or is IPtables not available in the current ICS builds (I'm using the 0120 nightly)?
Other than that and the lack of Flash, my experience with the NC ICS builds has been nothing short of amazing.
Many thanks for the answer and for the ICS builds.

I just noticed this last night when Sshtunnel wouldn't work on my nook, but is fine on a Touchpad. I'd rather not compile my own kernel if enough people would find iptables useful.

Apparently not many CM9 users are concerned about IPtables and restricting access to the internet by apps. Hopefully one of the devs will pick this up for a future build. I worry about the info that my apps are sending out to the extent that I might go back to CM7 on my NC...

It ain't that I am unconcerned, it is just that I don't know the answer. I actually consider a working firewall to be of the utmost importance. I am pretty sure we are not alone. I did have trouble with it too, it said that the kernel came loaded with an updated version of (all numbers approximate) iptables 1.4.1.11 instead of the 1.4.1.10 that the droidwall was looking for. I honestly don't know what the issue is, but I am trying to be kinda ok about it, simply because I bet you dollars to donuts that firewalls work on cm9 sooner or later.
Lots of stuff work on cm9, I just don't feel like I can get my panties in a bunch because my pet issue isn't ready yet. I bet if we're patient it wont be long.
Or I just need to learn how to run the software better. If figure it out I will report back.

I guess my issue is that one of the chagelogs indicated that Netfilter was functioning in the upstream builds, but wasn't (apparently) working in the NC version. "Glad" to see it's not just me, but not so good that it seems to be lingering without a Dev comment.

user17600 said:
I guess my issue is that one of the chagelogs indicated that Netfilter was functioning in the upstream builds, but wasn't (apparently) working in the NC version. "Glad" to see it's not just me, but not so good that it seems to be lingering without a Dev comment.
Click to expand...
Click to collapse
PS - Anyone able to post this question in the Dev thread (I can't due to low posting count)?

[Note: I am not addressing firewalls; just iptables and global SOCKS5 forwarding in this post]
I very much need iptables support in the kernel and it appears to be here now. My needs are for a global proxy that all Android apps using the network will use. In theory, it ought to be as easy as loading the relevant, pre-built kernel module, and writing the correct iptables script to route all outgoing connections through your already-running ssh proxy. There are several apps that do this already.
I noticed there's a newer app for iptables maintenance "Iptables (beta)" in the Market by Moroni Granja, who also wrote the Autoproxy utilities. His utility does indicate that CM 7.2.0-RC1-encore (as of 2012-03-24) does have the required modules on it and offers to update the iptables binary for you which may (or may not) be necessary. I did update mine.
Whether it automatically re-routes all your outgoing connections through your already running SOCKS proxy I have yet to find out [edit: see my **UPDATE** below]. I have seen several apps like this in the market but none have worked on my Nook Color CM 7.1.X but I will try to see if they work on CM 7.2.X with Moroni Granja's utility. Another one that claims "global proxy support" is MAX LV's "ProxyDroid." None of them will open an SSH tunnel using SOCKS dynamic proxying and then iptables to it [edit: see my **UPDATE** below].
Dropbear on Cyanogenmod is not built with "-D" option. If it were, you could open a dynamic socks proxy using "ssh" on the device, set Proxydroid to use 127.0.0.1:58080 as your SOCKS5 proxy, set it to global mode (or set up an iptables script for this), and you have your own SSH tunnel. I don't see any app that will do this all at once anywhere in the market but I'm close to putting together a skeleton if only I had OpenSSH or Dropbear with "-D" dynamic forwarding compiled into it. That's the big obstacle here [edit: see my **UPDATE** below]..
Well, I did write that last paragraph a little hastily. There are two apps, "SSHTunnel" and "SSHTunnel (beta)" which come close to these requirements, but the author specifically notes they are intended for people behind the "Great Firewall" and I have had very little luck getting this to work. However, these apps do have interesting internals that can be used to further the effort for a true SOCKS5 tunnel using SSH to a remote host because, as you may already know, all you need is a remote Unix host to get this to work completely.
**UPDATE** I have successfully used SSHTunnel (beta) to connect to a remote host through the SSH SOCKS5 tunnel without setting any browser settings on CM 7.2.0 on my Nook Color. It is working now, though it's cumbersome to say the least. I am observing several connections on my remote SSH host that are being made from my Nook Color to places like Wikipedia and Google Play Store using http and https, among other things. I cannot confirm that all of my outgoing connections are being made through the SOCKS5 proxy but many are.
The executable being used is named /data/data/org.sshtunnel.bat/sshtunnel and it is actually OpenSSH_5.8p2. OpenSSH is very inefficient as compared to Dropbear. Indeed, the author of SSHTunnel says it will significantly reduce battery life. Replacing this with a Dropbear binary with dynamic forwarding may result in significant speed increase, battery life, and decreased memory usage.
In conclusion, I can report that global SOCKS5 proxy via SSH does work on CM 7.2.0-RC1-encore using the "IPtables (beta)" app in conjunction with SSHTunnel (beta).

[Q] CM9 can't connect to DLNA/UPnP server

I am so stoked with the current state of CM9 ICS with the exception that I can no longer stream video from my DLNA/UPnP server. The problem is that I end up in a never ending search for servers. I have tried re-booting, toggling wifi, re-installing and while it works with CM7, I can't get it to work in CM.
I have searched high and low on xda and Google and found one fantastic user (jdommer) who seems to have solved the issue on the Kindle Fire. Any chance of bringing this fix to the Nook Color builds?
http://forum.xda-developers.com/showpost.php?p=23696294&postcount=2497

What app are you using? Or are you just doing the file manager/open with routine? View your files with a file manager and click a file to open with a media player?
Would you consider dual booting? I do and it's easy as pie.

Thanks for the reply. I have considered dual-booting but prefer CM9 for everything except this one failing.
With CM7 I used (and have attempted to use in CM9) BubbleUPnP or MediaHouse to brows networked media servers and initiate a stream which is opened in MoboPlayer or the like. The issue is that when opening one of the aforementioned UPnP network browsers, no servers are found and scanning takes an extraordinarily long time to complete.
As I said in my first post, this issue has been solved for the Kindle Fire so I'm hoping the fix could be incorporated into the nightly CM9 builds going forth.

So are we thinking this is essentially an issue with multicast not working properly, or... ?

I've been having problems, too... aVia, MediaHouse UPnP / DLNA Browser, neither one sees my Gentoo/MiniDLNA server. Logitech revue sees it fine, as does aVia on the TBolt. When I install any of those apps on the Nook, it causes some serious issues with network access. Maybe I'm just not being patient and giving it enough time to discover the server, but with both the Bolt and the Revue it was instantaneous.

I'm not allowed to post in the developer thread, so I hope a developer in reading this. The issue still persists in nightly 9/4/2012.
Regards
rom169

[Update 13/Oct] Beta Testers Wanted for WiFi Direct app

Hi guys,
Google market version is the most up-to-date.
Soon to remove the BETA tag out of it.
New Link as of 13th of October!!
Ok, file handling should be spot on now.
I've tried several different ways of sending from good sources and bad sources and I reckon I cover all the bases.
To organise some stuff I've removed the internationalisation, sorry, for now is english only, soon I'll put back the other languages.
If I managed to put the tutorial on it on the next few hours I'll update it as V0.4 on the google play, but I'm not sure it's going to happen, maybe tomorrow.
so the plan now is:
- tutorial
- tips n tricks
- logging for missing intents (maybe)
- future feature? NFC? bump? who knows.
have fun!
New Link as of 08th of October!!
Hi again guys,
I found out what was wrong on the file on the 7th, it was not the transmission or connection or even anything WiFi related. It's just that the files can come from several different sources I'm not properly dealing with them.
So here's the deal, this new build, I just blocked the files the app is not handling properly (most likely from 3rd parties galleries, and should work as expected on local files from the stock gallery). Files that are currently not handling properly should just close the app and pop-up a quick message saying "Can't handle this 'Share' at the moment, we're working on it!".
so let's recap:
- local media files from the gallery should work
- connection process is still and will always be hardware/manufacturer dependent and it might or not work.
- transmission (once passes connection) should work rock solid. Including canceling transmission midway through and also once completed tapping on the notification to open the media.
What I'll work on next:
- proper handling of every possible file/intent
- include a tutorial that will appear the 1st time the app is opened.
- a tips & tricks section with what I learned until now on what's best to get it connected.
and after that we should be in a V1.0... does it sound ok?
have fun!
New Link as of 07th of October!!
In this one I completely redid the transmission process and it's ROCK SOLID !!!!
The version on the market if you try really big videos they'll eventually fail, with this new protocol I've transferred HUGE 1.7giga video file without any problem.
Furthermore there's TONs of optimisations on the transfer speed that you won't see on this version, but it's already on the file and it will be unlocked by the future paid version that give around 2 to 3 times after transfer times.
Before put this version into the market I'll include a tutorial and link to the youtube video, but you guys can already test it.
PS.: also there's not much internationalization on this one, there some parts that language will be lacking, I'm aware of it don't need to come tell me.
Have fun!
---------------------------------------------------------------------------------------------
I've doing an open beta testing of the first and only (until now) WiFi Direct sharing app available in the Google Play.
here is the link for it:
https://play.google.com/store/apps/details?id=com.budius.WiFiShoot
I just finished refactor most of the code and should be smooth stable now.
So I'm creating this thread to invite anyone that have a FORCE CLOSE to get a Logcat and post it here for me
Please also state if it was the Sender or Receiver, the phone manufacturer/model and which ROM you're running.
Please do not post if you try to connect but the other device fail to reply, or if you device reboots when you try to switch the WiFi Direct on.
Those problems are 100% unrelated to the App itself and it's direct related to the hardware and OS on it.
Developers info:
The WiFi Direct API is 100% with callbacks. So the app just requests a connection and wait for a callback. And sometimes the callback is "failed to connect".... why this happens? is up to the OS.. the OS is responsible to all the transactions and there's no API available for any app to interfere with the process.

Hi, Nice app! It didn't force close on me at all and the UI design has a good look and feel. I just tried it with my Nexus 7 and Galaxy Nexus (both stock 4.1.1) and it worked. However, when launching the app to receive you might want to add a help menu or something to tell you what to do on the other device otherwise people might think to share something you need to launch the app on both devices and then share from there (this is what I did at first because I didn't watch your video!)
Is there any way you can launch the app automatically on the receiving device when the other device tries to send something? Also tapping "Shoot" to receive something is slightly odd. "Receive" or "Receive Shoot" might be better.

footboydog said:
However, when launching the app to receive you might want to add a help menu or something to tell you what to do on the other device otherwise people might think to share something you need to launch the app on both devices and then share from there (this is what I did at first because I didn't watch your video!)
Is there any way you can launch the app automatically on the receiving device when the other device tries to send something? Also tapping "Shoot" to receive something is slightly odd. "Receive" or "Receive Shoot" might be better.
Click to expand...
Click to collapse
Yeah, the help will definitely be necessary but at the moment I'm focusing on nailing the actual software functionality. Non nexus devices not always works so nicely.
When I started developing I though about the same (auto launching) but it can't be done, unfortunately, I wanted something liked the show on last year Google io for he ask. But no, I couldn't do it without taking over ALL WiFi direct transactions on the device, which I reckon it would be bad a behavior. Maybe in the future I'll thin about it as an option for the paid version.
About the shoot.... hmmmm..... it kinda feels better to have the confirmation on the receiver, but for sure feels like the text could be different, but then the "cool factor" of it is to have that single big button with a very simple and almost graphical SHOOT, that won't even be translated to other languages.
Something to think about it.
Sent from my Nexus 7 using xda app-developers app

nice app
waiting it support any file type
thanks

@Dev
Great work, any plans to expand the functionality and maybe expand to share a wireless shared connection from your laptop using direct wifi?
Sent from my htc_jewel using Tapatalk 2

Nice initiative, I am on evo 4g lte. I tried it with my laptop sony viao, installed to latest atheros utility which haves wifi direct interface.
wifi shoot found it, invited it, get connected.
I just tried to send a songs or 3gp file thru root explorer. without enabling wifi direct from setting.
In send option it shows wifi shoot. I clicked on wifi shoot.
wifi shoot connect to my laptop wifi direct. then nothing no transfer.
Great work. Very high potential. once again great initiative. Thanks.

I'm sorry but you misunderstood the function of the app.
Is a direct transfer from android device to Android device, and both devices must have the app installed. It has never been meant to be used with a laptop.
Sent from my Galaxy Nexus using xda app-developers app

Works great! I sent a small video from my S3 to my N7 successfully. Thanks a bunch, will try a big file later.
Sent from my Nexus 7 using xda premium

Budius said:
I'm sorry but you misunderstood the function of the app.
Is a direct transfer from android device to Android device, and both devices must have the app installed. It has never been meant to be used with a laptop.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
ohh got it. both device same apps. Thanks. will test it. Sorry

My Nexus 7 and S3 don't play wel together.
What does work is using the S3 as a hotspot and then run Samba on the Galaxy S3 (Root required)
Samba takes a while to activate.. but after it does you can browse your phone using the Nexus 7 and copy stuff... no limitations on specific file extansions either.

It work great... for a picture. But I want to transfert any file I want and Wifi Shoot! doesn't appear in "Send"/"Share" menu in ES file explorer or X-Port... What can I do ?

NFC pairing would be a great addition to this app! Maybe include it in a pro version of the app and charge a small fee? I'd definitely pay for it!

taylortr said:
I sent a small video from my S3 to my N7 successfully.
Click to expand...
Click to collapse
jwedda said:
My Nexus 7 and S3 don't play wel together.
Click to expand...
Click to collapse
It's not the first time I hear ppl saying that S3 and N7 doesn't play nice together, but on the other side, there're reports that they do work nice.
Can you both tell me which versions of the S3 you have? Some US variant or the international?
thanks.

Work great beetwin mu gnex and n7
Nice work bedalus, now we only need The ability to share every file, not only media from gallery
dropped by a jellybeans cup...

Just downloaded to both my N7 and my GNex.
I really need something like this for files. As of right now, I'm using WiFi Explorer. It works but this would be faster.

The version from the Google play store (v0.3.5) worked fine both ways with my Galaxy Nexus with JB and my bro's Galaxy Nexus with JB. We both had to looking at the program during pairing to get the notifications though.
I was able to transfer a 323 mb .mkv video file in 2:30 mins. Pretty good considering transferring the file originally to my phone took about 15 mins over wifi via a PC router.
By the way, is there any reason in particular you made it so you can only transfer pics and video files? The program would be much more useful if you could transfer any file type.

Can i use it between galaxy S and SIII?

Please, add all kind of file type. Not only image and videos, also others type (.pdf, .zip, .dat…).
Wifi shoot installed on i9100 and i9000, both devices on Rom ICS AOKP milestone 6. The process work fine only if I follow exactly the same steps on the demo video :
Receiver:
1- Open wifi shoot and wait
Sender:
2- Open the apps where the file to send is
3- Share via wifi shoot
4- wifi shoot apparears and select client to invite
Receiver:
5- Accept the invite
6- Click on big button shoot
Sending + receiving…
So, if we follow the guide of use, wifi shoot work fine. But please, add support for all kind of file type. Not only image and videos, also others type (.zip, .pdf…).
Please, continue to develop this great app, I hope one day you will be able to win money with it.
Wifi shoot are not still unique for wifi direct. There is also this apps, but not working at all for my devices.

philippe734 said:
The process work fine only if I follow exactly the same steps on the demo video
Click to expand...
Click to collapse
Hi,
thanks for the reply and tests. Could you further explain, how else were you expecting it to work? DId you try some other way?
I'm currently working on a better protocol to make the transfers more reliable, after that is fine tuned I'll enable every file type, multiple files and photos that are synchronised from picasa.

wifi shoot! is a great idea ... but would be better to have some kind of server on the phone that allow to share any file to another phone or tablet. Something like an ftp server or upnp/dlna server. This way we wont have to send the files frome the phone, we will just need to request it from the other device.
I don't know how wifi direct works ... but if it works using TCP/IP the only thing we need is to know de wifi direct IP address of the phone to connect to any available ftp/smb/upnp server phone from the other phone/tablet connected via wifi direct ...
the problem is: the available servers will be bound to the external IP only or will accept requests from the wifi direct interface? maybe this willraise the need of a special server and client prepared to work via wifi direct ..
PS: sorry about my poor english

Request: Tcping

I'm a network admin and I use the free utility Tcping to ping my access points remotely. I'd like to be able to use it on my phone as well, but there isn't an app that does anything like it as far as I can tell. I tried compiling it from source on my phone, but I wasn't able to get it to work.
Does anyone know if it is possible to port the linux version of tcping to android (without installing debian/ubuntu)?
Link: http://www.linuxco.de/tcping/tcping.html

cheezbergher said:
I'm a network admin and I use the free utility Tcping to ping my access points remotely. I'd like to be able to use it on my phone as well, but there isn't an app that does anything like it as far as I can tell. I tried compiling it from source on my phone, but I wasn't able to get it to work.
Does anyone know if it is possible to port the linux version of tcping to android (without installing debian/ubuntu)?
Link: http://www.linuxco.de/tcping/tcping.html
Click to expand...
Click to collapse
Have a look at https://play.google.com/store/apps/details?id=se.ping.android.hostmonitor
It's not tcping, but it's an app capable of tcp ping. A really good app, if I may say so myself.

kuisma said:
Have a look at https://play.google.com/store/apps/details?id=se.ping.android.hostmonitor
It's not tcping, but it's an app capable of tcp ping. A really good app, if I may say so myself.
Click to expand...
Click to collapse
Thanks for the suggestion! That app is capable of pinging a specific port, but it lacks certain features that I would need as well. I couldn't find a way to do a manual refresh (necessary for troubleshooting) and the way that this app manages port numbers is just not what I'm looking for. I need to be able to just type in a port and hit go, I don't want to be creating a gigantic list of ports in the app's settings.
However, I did find this app, which is a lot closer to what I want: http://play.google.com/store/apps/details?id=com.odinnet.servermonitor&hl=en

cheezbergher said:
I couldn't find a way to do a manual refresh (necessary for troubleshooting)
Click to expand...
Click to collapse
Ping HostMonitor refreshes each time the main activity (host list) opens/reopens.

Sorry, I just realized that was your app. Allow me to explain what I need so you can see what I'm looking to do.
I'm a wifi network technician. The company I work for manages the guest networks for hundreds of hotels all over the southeastern US. On each site, we have dozens of access points (theres actually one resort where we have over 500 aps). All of the access points are accessible through our firewall via specified ports that vary from site to site.
We have a webpage that displays all of the APs at each site with their port# and uptime display that is only accurate to within 15 minutes. So if I'm troubleshooting remotely I use tcping to see when an AP comes up in real time after a remote reboot.
Your app seems to be geared more towards what ipsentry does, where it pings in 15 minute intervals. I'm looking to run pings in 3 second intervals or less.
Also, I would like to be able to just type the hostname and port then hit go. Your app is made more for a network admin who manages a single or couple of networks, and it just takes too many steps to enter in a port to be pinged. However, there are some features of your app that I really really like including only pinging a specific host when conected to a certain ssid.
I really like your app, but I need to run pings in 3 second intervals and it's just too difficult on Ping HostMonitor. If you wouod consider adding this feature, I will be eternally grateful.

cheezbergher said:
Sorry, I just realized that was your app. Allow me to explain what I need so you can see what I'm looking to do.
Click to expand...
Click to collapse
Something like this?

Hey thanks man! I tried it though and I can't get it to run. I've attached a screenshot, am I doing it wrong?

cheezbergher said:
Hey thanks man! I tried it though and I can't get it to run. I've attached a screenshot, am I doing it wrong?
Click to expand...
Click to collapse
The sdcard isn't mounted allowing execute access. Put it someplace else, e.g. /data/local/tcping

holy moly it works perfectly! thanks a million man!
now if you had the time, you could make an app version with a gui. i'd definitely pay for an app that could do this.
thanks again for all your help!