Orbot (Tor) Compatible ROMs/Kernels List (WHERE? WHO CARES?) - Galaxy S II Q&A, Help & Troubleshooting

Anyone here having success with ORBOT ?
It's a jungle out there trying to find out which ROM launches Orbot fine (I've tried several) and then a kernel with the simple module included loaded by issuing:
"modprobe ipt_owner"
So god damn simple.
Orbot is such a gain on an Android. Firstly, it opens up the opportunity to only route/proxy things such as syncing.
Other than that, it provides it's "Hidden Services", deepweb or what you would like to call it.
And lastly, it opens up Pandora for some users, it opens up ThePirateBay for others, and many other country restrictions.
I'm beginning to think many of the people who make ROMs and compile kernels never actually used a Linux computer, or know who to treat one, if they do at all know what the difference between a module and a built-in one is and what the "performance" gain is from leaving one module (especially ipt_owner) out of the kernel "for performance" ..
Yeah right, Ninphetamine (or other stimulants that fry your head), SpeedMod (or just amphetamine) ..
Well .. Actually, I think sometimes people patch too much just to write a long changelog, having NO god damn clue about new and old lines of code.
People not using Git at first when patching, well, it's up to them, if they can maintain it and make incremental backups.
So recently I tried "Tegrak Kernel 26" and the newest "Lulz Kernel Build 14" .. Very fine kernel !
Guess what ?
1. First clean Reboot (su, reboot)
2. Start 'Tegrak Kernel' app (works fine)
3. Start Orbot (manually) (disabled on boot to debug logcat)
3.5. Orbot is yellow (Not fully connected)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Start 'Tegrak Kernel' again .. This time, lost background connection.
5. Orbot magically turns green instantly when I started 'Tegrak Kernel' app ..
"Connected to the Tor Network" notification pops up, and the missing TRAY icon magically appears !
6. But the Orbot app still shows "YELLOW" incomplete
7. "Check connection" in Orbot is success .. Orbot is running, but is it functioning correctly ?
8. NO- Force Close. And what's the gain? A broken 'Tegrak Kernel' background service.
LOGCAT: http://paste.pocoo.org/show/495957/
I'm beginning to think there is no such thing as people developing for stability, for flexibility, and to support functions in the kernel that certain apps REQUIRE! This is more important than the average battery gauge mod or the so important script and cache tweak that increased your devices performance with about 0.0025% ?
Siyah says it's a unified kernel, well what's unified or flexible if it can't do Orbot ? "One Kernel to Rule Them All" - OK- then start supporting more devices, start supporting more features
And what is good about an "optimized" but unified kernel? Doesn't that mean it is compiled for several arch's and devices ?? Then you could just as well throw the ipt_owner module in and catch all orbot users while you're playing one-size-fits-all (Unified) .. Instead, release several builds, optimized for size, or whatever works for you. One with ipt_owner module and one without ..
And apparently, I'm not alone:
http://www.insecuresystem.org/2010/04/ultimate-droid-and-orbot.html

---

Neither Orbot or ProxyDroid (used with Irssi Connect) would work on
- XXKI4_CheckROM_RevolutionHD_V2.0.0 ROM
- DarkKnight_Siyah-v2.1-CWM kernel
Used to work fine on unmodified Samsung Frankestein XXKI4.
Alphazo

---

Who cares?? Well, I do!
I have been trying to get Orbot working for ages now...
Tonight i tried cooking up a ROM in romkitchen. I used speedmod as the kernel, and - lo and behold - orbot doesn't work.
Before that I had exynos extreme 7.2 (i believe the kernel is siyah) - didn't work.
Before that, I had stock everything (with root) - WORKED FINE.
I would happily post on the developer's page of speedmod for some help to enable the netfilter owner option - however not enough posts!!!
I CAN'T WIN LOL...
Having said that, ANY help enabling the netfilter owner option without having to reflash my phone again would be GREATLY appreciated.

---

http://gokhanmoral.com/
2.2 beta 5 should help. Also check olifee's post
Edit: issue has been communicated to bug tracker. Go here

---

Got it working!!!
Solution found in one of the 900+ pages of the Siyah kernel.
Both Siyah, DarkKnight Siyah kernels and probably many other should have the correct netfilter enabled.
Problem was not in the kernel but in a version of iptables that comes with Orbot (libc issue?). Copying over a working copy of iptables to Orbot directory did the trick and I now have transparent proxy working just fine
See full solution here:
http://forum.xda-developers.com/showpost.php?p=19179917&postcount=9265
What initially confused me was:
ROM developers, please ensure that the following configuration option is enabled in the kernel (either built-in or as a module): CONFIG_NETFILTER_XT_MATCH_OWNER
Click to expand...
Click to collapse
But Siyah developper confirmed that CONFIG_NETFILTER_XT_MATCH_OWNER=y is already enabled since 1.7...
You can check available options in /proc/config.gz

---

Thanks to both of you for your repies.
bclark said:
http://gokhanmoral.com/
Also check olifee's post
Click to expand...
Click to collapse
I installed droidwall from market, copied the iptables file as indicated in the post to the orbot folder, and I renamed it to 'iptables'.
Didn't work... Still using Speedmod S2 K2 3 though, so I'll give Siyah kernel a go and report back.

---

All working now, thanks!!!
Confirmed - swapping the iptables file from the droidwall install to the orbot folder + using siyah 2.0 = WORKING ORBOT!!!!!!
Thanks once again!

---

strange works fine for me on a rooted stock rom, guess I was lucky

---

I need a little bit of help.
Orbot is working for me if I set the proxy in the Wifi-Settings.
The Droidwall is also working.
So my guess is, my Rom Goa v 1.5 and Kernel ICS Abyss 1.3 should be working in general.
But I would love to set up the Transparent Proxying which is not working for me.
I tried the workaround by copying the Iptables-File but I get an error when activating the transparent proxying.
Should I still try another Kernel or do I need to set up anything else? As far as I know, for the transparent proxying, the proxy in the Wifi settings does not have to be enabled, right?

---

It is working now for me.
AngeloM fixed a config line in his Abyss Ics Kernel v 1.4.
But I also had to fix the permissions in the recovery console.
On the fly of my Galaxy S2
RogueZet

---

alphazo said:
See full solution here:
http://forum.xda-developers.com/showpost.php?p=19179917&postcount=9265
Click to expand...
Click to collapse
Great find, thanx 1 step closer to get Orbot running perfect