Will someone post a tutorial on how to configure and start droid wall firewall app on xperiax10i 2.1? I tried hard but everytime it says failed initialization, ip tables not found, your kernel needs to be updated.
I want it badly as 3g network sucks my battery. Too many apps installed.
Please.
Sent from my X10i using XDA App
Until bootloader isn't cracked this is not possible. Droidwall is only a frontend for iptables, which uses a module from kernel to do its job. However, this module(netfilter) is missing from the X10's kernel.
10/30/11 Update: Added modules for GB kernels (e.g., EH17).
Since they're somewhat frequently requested, this thread contains compiled (in-tree) kernel modules that don't come with stock kernels. They should, for the most part, work in any custom kernel based on the same kernel version/build.
Note that the EB13 modules are identical to EC05, so there is a single set posted for both kernel versions.
GB (EH17) Modules (mirror links):
cifs.ko (& slow-work.ko): CIFS/SMB file system (Samba/Windows shares): Mount w/CifsManager or Mount Manager).
fuse.ko: FUSE file system: For sshfs, other user-space file systems.
tun.ko: TUN/TAP network device: For Cisco VPN, OpenVPN, etc.
xt_TCPMSS.ko: Netfilter TCPMSS target: For MSS clamping in Wired/WiFi tether.
Built from GB kernel sources with these changes.
EB13 (& EC05) Modules (mirror links, do not require forum login):
cifs.ko (& slow-work.ko): CIFS/SMB file system (Samba/Windows shares): Mount w/CifsManager or Mount Manager).
fuse.ko: FUSE file system: For sshfs, other user-space file systems.
tun.ko: TUN/TAP network device: For Cisco VPN, OpenVPN, etc.
xt_TCPMSS.ko: Netfilter TCPMSS target: For MSS clamping in Wired/WiFi tether.
Built from Samsung kernel sources (SPH-D700_Froyo_update_EB13.tar.gz) with these changes.
If anyone is interested in a module not listed here, feel free to request it and myself or someone will compile it and add it to this thread.
So wait...these put abilities into kernals? Such as wired tether..........?????? >_>
Sent from my SPH-D700 using XDA App
What exactly is the implementation workflow for these?
A_Flying_Fox said:
So wait...these put abilities into kernals?
Click to expand...
Click to collapse
Sort of, they're loadable kernel drivers, to add functionality that's not found in the stock EB13 kernel. See Wikipedia. Typically the modules themselves aren't particularly useful alone, but are often required for third-party programs to function.
dannyzen said:
What exactly is the implementation workflow for these?
Click to expand...
Click to collapse
Typically one downloads a third-paty app for Cisco VPN, OpenVPN, or something like that. These apps require driver functionality (e.g., tun) in the kernel which do not come stock on the Epic. So one has to, as root, run "insmod tun.ko" (or whichever module) before running these to get them to work.
The kernel modules are specific to a kernel version, so it's typically recommended that one builds them per-device out of the Linux source tree. So I posted these for the Epic.
With regard to the TCPMSS module, this is a Netfilter feature that was previously included in the Eclair (e.g., DI18) stock kernels. For some reason Samsung decided to build it as a module in Froyo, but not actually include it in the initramfs.
So what exactly would be the benifit if I installed the tcp kernel mod? And are these compatible with the 0.2a genocide kernel? Thank you.
Sent from my SPH-D700 using XDA App
Cam3ron1 said:
So what exactly would be the benifit if I installed the tcp kernel mod?
Click to expand...
Click to collapse
If you use Wired Tether or a recent version of the WiFi Tether v3.0-preX series, then the module will allow MSS clamping while tethering.
In WiFi Tether, this has to be enabled in the Settings, and the option only appears if kernel support is available. I'm not sure if Harald has had a chance to integrate the change needed to detect modular TCPMSS support (as opposed to built-in), so it may not be available there yet.
MSS Clamping:
Network devices (Ethernet, wireless, whatever) communicate by encapsulating IP packets into frames. For any connection, these frames are limited to a certain size (maximum tranmission unit, MTU)--typically 1500 bytes. Now, TCP connections (HTTP, FTP, most of everything you do on the Internet except possibly gaming and real-time streaming) generate packets that are also limited in size, and that limit is negotiated during the connection handshake to whomever you're communicating with. This is the maximum segment size (MSS).
Typically, when a computer establishes a TCP connection, the MSS is set as large as possible, but small enough that each packet fits into one frame. It calculates this based on the MTU used for the network connection.
The problem is that, when tethering, typically the tethered-computer uses an MTU of 1500, but the tethered conection uses a lower MTU. For example, Sprint 3G uses 1492 (typical of PPP), and Sprint 4G uses 1400. This means, when tethering, your phone has to fragment each (large enough) packet into two frames before sending them over this air. This is somewhat space inefficient, and might reduce throughput--although I've not tested to see how noticable the effect is.
The TCPMSS module allows the phone to change (clamp) the MSS in TCP connections from tethered-devices to fit the MTU of the outgoing network conection. This makes sure that each TCP packet transmitted to/from the tethered-device fits in a single frame without fragmentation.
The real reason for MSS clamping is that some ISPs (particularly cable providers it seems) just drop fragmented packets. So, for example, in the context of a home wireless router, if you don't do MSS clamping, bulk downloads don't work at all--so most routers clamp. It's possible that some mobile providers don't support fragmentation either, although Sprint does.
So the practical benefit for you might be slightly-faster tethering. Or it might have no noticeable difference.
Cam3ron1 said:
And are these compatible with the 0.2a genocide kernel?
Click to expand...
Click to collapse
They should be, but I've not tested/used that kernel.
Samba would be pretty sweet. I hope someone uses it.
Sent from my SPH-D700 using XDA App
Schuby said:
Samba would be pretty sweet. I hope someone uses it.
Click to expand...
Click to collapse
CifsManager (xda thread) and Mount Manager support mounting SMB shares with the CIFS module. So yeah, you can stream music/movies that way.
Added those to the OP.
Dumb question, would the tun.ko for EB13 work with DK28 kernel? Both froyo, but I don't know if there are enough differences to matter.
rcboosted said:
Dumb question, would the tun.ko for EB13 work with DK28 kernel?
Click to expand...
Click to collapse
Probably, it doesn't touch any Samsung-specific code that would've changed since DK28, but YMMV.
This must be a noob Question but where to you put these? to get them working?
zman519 said:
This must be a noob Question but where to you put these?
Click to expand...
Click to collapse
It doesn't really matter, /sdcard, /data/local/tmp, etc. Permanently I'd put them in /data/modules or /system/lib/modules even.
To load them you have to use insmod. So, for example, if you put tun.ko in /sdcard, from a shell (e.g. ConnectBot local or adb) run:
Code:
su
insmod /sdcard/tun.ko
Modules stay loaded until you reboot the phone. If you want to unload one anyways (e.g tun), run from a shell:
Code:
su
rmmod tun
Most programs that typically require a kernel module have a feature that lets you specify their location and it will load them automatically. CifsManager and Mount Manager do this I believe.
Can I Flashes these with clock work 3.0.0.6?
Can these be flashed with clock work? I guess not. I tried and I failed.
Thanks, useful. Is the source published?
k0nane said:
Is the source published?
Click to expand...
Click to collapse
They're built from unmodified EB13 kernel sources. I've made that more explicit in the OP and attached a diff against the stock kernel configuration along with the Samsung source link.
jamice4u said:
Can these be flashed with clock work? I guess not. I tried and I failed.
Click to expand...
Click to collapse
these are more for devs to cook into roms and custom kernels.
For the life of me I cannot get this working. I tell CIFSmanager exactly where the module is but it never loads it.
Could the lack of tethering module be the cause of my wired tethering randomly disconnecting? It does not randomly disconnect in DI18.
Sent from my SPH-D700 using XDA App
muyoso said:
For the life of me I cannot get this working. I tell CIFSmanager exactly where the module is but it never loads it.
Click to expand...
Click to collapse
It looks like the stock kernel doesn't have the slow_work stuff enabled, which cifs requires. For cifs, a whole new kernel needs to be compiled and installed.
dnathan13 said:
these are more for devs to cook into roms and custom kernels.
Click to expand...
Click to collapse
These are really intended for folks running a stock kernel, but who need an extra module or two to use VPN clients, CIFS, etc. Every so often a thread pops up in General requesting "tun.ko" or some other module for the stock kernel. This thread is intended to provide those modules in a single location.
These modules may also be useful for folks running custom kernels that don't include these features yet. However, kernel developers don't need these, they'll just compile whichever feature is desired either as a module, or into the kernel itself.
tartarhead said:
It looks like the stock kernel doesn't have the slow_work stuff enabled, which cifs requires. For cifs, a whole new kernel needs to be compiled and installed.
Click to expand...
Click to collapse
Good catch. CIFS didn't depend on slow-work in Eclair, so I didn't notice the kernel config change nor did I test that module, as I don't use CIFS myself.
Anyways, Tab folks have had success building slow-work as a module. I've done so here and updated cifs-EB13.zip, along with the source modifications, in the OP. I've tested the new cifs module and it at least inserts, although I have no way to verify its functionality.
Do note, the slow-work.ko module needs to be inserted before cifs.ko as it's a dependency.
muyoso said:
For the life of me I cannot get this working. I tell CIFSmanager exactly where the module is but it never loads it.
Click to expand...
Click to collapse
It should work now with the updated modules. According to this, if you place slow-work.ko & cifs.ko in /sdcard, you should tell CifsManager to load "/sdcard/slow-work.ko:/sdcard/cifs.ko".
DeeODoubleD said:
Could the lack of tethering module be the cause of my wired tethering randomly disconnecting?
Click to expand...
Click to collapse
No, that's likely something else. Are you using the Wired Tether client?
What up everyone!
As we all know, Zdzihu has released zKernel that is capable of many things, one of which include full netfilter support (droid wall & wifi tether). I know that many of have used barnacle wifi but one of the issues I had with it was that it sets up an ad hoc network to allow wifi tethering. The problem with android is that, for whatever reason, it can not connect to ad hoc networks. As such those of us with android tablets or other android phones could not tether using our X10s.
Now fast forward to today. The zKernel (probably other ones by Goro kun too) has full netfilter support but how can we use it? Well, rather simple. Download this handy dandy app from this here link:
http://code.google.com/p/android-wifi-tether/
I downloaded the latest evo 4g version for eclair and wifi tethering works! Now I've got my X10s tethered with each other. No more ad hoc support via barnacle wifi for me!
Note: Remember to install zKernel first! Also, I had issues with connecting to a secure network via this app. However, there is an option to enable access controls that allows you to authorize connections.
Thanks to all the developers for making this possible!
Installation Instructions:
1. Download & Install Z's zKernel via Xrecovery found here: http://forum.xda-developers.com/showthread.php?t=1135475
2. Download apk in the link in the middle of the page.
be more specific about the kernel, as far as i know the best way to tether is whit bernacle thats on our x10,, and for the use of os tether i read on zdzihu page that is kernel related...
Huh?
MacDrunk said:
be more specific about the kernel, as far as i know the best way to tether is whit bernacle thats on our x10,, and for the use of os tether i read on zdzihu page that is kernel related...
Click to expand...
Click to collapse
Not trying to start a fight but how more specific do you want me to be? Please read my post carefully as I do mention Z's zKernel not only in the name of the thread but in the OP multiple times too. I will bold them for your entertainment as well as provide a useful link to Z's thread. To my knowledge there is only one zKernel that was released as of today's date of 6/22/2011. Please let me know if you know of any others. Additionally, I do mention the use of barnacle wifi in the second sentence above and the problem associated with it. But what if you have another android device? How do you tether it using barnacle wifi?
Thanks for your concerns but please read a bit more carefully as this does relate to a kernel.
can u upload the app u are use? please, because i download more than one but without sucess, only get ad-hoc mode =/
SeeHarrier said:
can u upload the app u are use? please, because i download more than one but without sucess, only get ad-hoc mode =/
Click to expand...
Click to collapse
Yes, me too! Only ad-hoc mode!
Still, it's better than Barnacle though, more stable!
Hey all. Looks like I made a mistake. In my haste and excitement I automatically thought the app was not running an ad-hoc mode because I was able to tether my other X10 (with no sim/service) to my X10 that had service/sim. After reading the FAQ of the android-wifi-tether app, I found that it does indeed connect via ad-hoc mode.
The FAQ can be found here:
http://code.google.com/p/android-wifi-tether/wiki/FAQ
My understanding was that Android devices could not connect to ad-hoc mode so I wonder why this app is different from Barnacle. I tried connecting via Barnacle to test if it would work but to no avail.
I'm interested in setting up VPN between my home computer and my Skyrocket. But before I go through the process, I wanted to ensure that VPN (and tun module) is available/possible in the stock Skyrocket kernel. The "OpenVPN Installer" and "OpenVPN Settings" android apps indicate that "tun" module must be available on the phone and this seems to be the case for NON-stock ROMs.
If VPN is available in stock rom, can anyone recommend a good walkthrough for setup?
The phone has built in vpn but it's. Very flawed. Most encrypted connections will die after a few min.
This is an android-wide problem and according to forum posts, has existed for years.
Sent from my SAMSUNG-SGH-I727 using xda premium
Does that include third party vpn solutions like openvpn? I was hoping to use vpn for tethering uses.
As long as openvpn supports pptp ipsec or l2tp then yes it will work.
Sent from my SAMSUNG-SGH-I727 using xda premium
After reading this thread, I'm not sure this is necessarily the case. There it is claimed that the required TUN/TAP driver for VPN on the Skyrocket isn't in the stock ROM:
http://forum.xda-developers.com/showthread.php?p=19963725#post19963725
The built in vpn solutions are fine, but rather complicated, and geared more towards those who use enterprise VPN solutions, like the Cisco VPN Concentrators and such.
If you want to use the built in vpn client, you can use raccoon (runs on linux, *bsd and a bunch of others) as the vpn server, but it is a total ***** to configure.. hell, it is a total ***** and a half.
One we start getting more custom kernels out, the developers will start to include the tun driver into the kernel, and we can use openvpn which is simple to setup.
So anyone who has a White Pandigital Novel (WPDN), Randomblame has created a ROM with ICS (Android 4.0) from the AOSP source and pulled for various drivers (S3M6410, eGL, RT2870, etc)
I take zero credit for this - it's all randomblame
However, he and a few of us over at slatedroid just can't get wifi to work. I'm throwing the question out to other developers who might have run into this or could suggest something/anything to fix it.
WORKS:
graphics (slow, no hw acceleration)
touchscreen
NOT WORKING:
wifi - almost, so close, yet so far
audio
http://www.mediafire.com/?4cokc8bqc80th59
So the Wifi drivers are loaded and we can connect to various SSID's (WPA, open WPA-2 etc).
Using adb, I can ssh out using root to the internet (dreamhost.com) and log in successfully
Using adb, I can ping www.google.com as root
Switching to the user system when I ping it says "You must have access to the internet to use ping."
Browser doesn't work (connection to server was unsuccessful)
Non-android browser doesn't work (same error as above)
Telnet doesn't work using root or system or anything. For that it gives "telnet: socket: permission denied).
Pandigital hasn't released source code, so randomblame has hacked the .29 (from Android 2.0) kernel to make it work in ICS.
We've added "group system wifi inet" to the init.rc under wpa_supplicant.
I've tried adding users in the same wpa_supplicant service block.
Anyone have any ideas?
Also, the Opera browser (not mini) works and allows us to surf the web - with varying degrees of success. Mostly it works - BBC works great, others not so much.
Anyone know why the normal browsers (Dolphin Mini, stock browser etc) don't work, and Opera browser does? What's different about it?
Randomblame is the man, I'm not a Dev, but have a Pandigital Novel and would like some ICS!
Sent from my SPH-D700 using XDA
http://www.slatedroid.com/topic/25163-ice-cream-sandwich-cm9-base-now-with-moar-internet/
I just wanted to post the link so others can look at it. Apparently there is more WPN owners than I thought!
Can i get a bit more instructions? Im a suprisingly fast learner. Downloaded zip file and followed instructions. Didnt work.
Sent from my LG-P920 using xda premium