Database Info

Xoom stock rooted 3.2.1 openvpn

Has anybody been able to get openvpn working on 3.2.1? Can you please help with steps if u can.
Currently I get through the auth and at get config I get
Cannot allocate tun/tap dev dynamically.
I know I don't have tun.ko in my /system/lib/modules. I got the one for 3.2 but it seem to work. I didn't find a tun.ko for 3.2.1.
Help

[Q] Has anyone gotten OpenVPN to work?

i still havent been able to make openvpn work because trying to install a TUN.KO file always says an error, does anyone have a working tun file for the O3D?

here is it
works with GB and Kernet 2.6.35.7+

[Q] Missing TUN Module in OpenVPN

I am trying to get OpenVPN running on my phone and I am having an error where the phone reports it can't find the TUN module. I have tried running TUN.KO to install it, but it does not look like that app can find the correct module.
Any other ideas on how to get this to work?
ROM: Apex 1.0.2
Kernel: GLaDOS 2.10

[Q] kali linux on xoom - fb* kernel issue

hello,
i've got motorola xoom MZ604 (wifi-only), and following this link from kali linux, and also this one, i've managed to install kali linux natively on my xoom.
it is booting, i can login, i can connect to internet via wpa_supplicant and other methods, but i have one big issue - i can't get the Xserver to run.
looking it up - it is related to the fb* issue on the nvidia tegra here.
but when i try to recompile the kernel with the fix on that link, the compilation fails everytime.
is there a way to apply this patch to my already installed kali?
or rather - any other way to solve this?
thanks,
Ilan

ilanp13 said:
hello,
i've got motorola xoom MZ604 (wifi-only), and following this link from kali linux, and also this one, i've managed to install kali linux natively on my xoom.
it is booting, i can login, i can connect to internet via wpa_supplicant and other methods, but i have one big issue - i can't get the Xserver to run.
looking it up - it is related to the fb* issue on the nvidia tegra here.
but when i try to recompile the kernel with the fix on that link, the compilation fails everytime.
is there a way to apply this patch to my already installed kali?
or rather - any other way to solve this?
thanks,
Ilan
Click to expand...
Click to collapse
i just planning up install

ilanp13 said:
hello,
i've got motorola xoom MZ604 (wifi-only), and following this link from kali linux, and also this one, i've managed to install kali linux natively on my xoom.
it is booting, i can login, i can connect to internet via wpa_supplicant and other methods, but i have one big issue - i can't get the Xserver to run.
looking it up - it is related to the fb* issue on the nvidia tegra here.
but when i try to recompile the kernel with the fix on that link, the compilation fails everytime.
is there a way to apply this patch to my already installed kali?
or rather - any other way to solve this?
thanks,
Ilan
Click to expand...
Click to collapse
Generally, it's bad practice to patch a compiled kernel. Occasionally I'll run into issues like this and I have to start over in a new source folder and try to recompile from scratch. If it succeeds, you know something was changed in your source other than your patch that borked it. If it fails, it sounds like the patch may not work.

Building kernel with CONFIG_BRIDGE=y

I use my galaxy s6 phone as a wifi hotspot for my desktop (I know, im too cheap to buy an adapter, but bear with me), my phone connects to the internet with wifi and my desktop is tethered to my phone.
Recently I wanted for my PC to apear as if it was directly connected in my lan and not be behind the NAT of my phone.
So what I wanted was to bridge the wlan0 and rndis0 network interfaces. Unfortunantly, I came to discover that the stock S6 kernel doesn't support 802.1 bridges. So I went and compiled a custom kernel. I compiled the stock kernel updated it in my boot.img to see if I was doing everything right and yes, it all went dendy. But when I recompiled the kernel with the CONFIG_BRIDGE=y, the phone goes into a boot loop. Also, a msg apear saying SElinux is not enforced, which is odd.
The question is: wtf? Is it the case that the hardware doesn't support this option? How changing just this option interferes with SElinux. Is there anyone who tried to do this and got it to work? I was able to change some options, like CONFIG_IKCONFIG/IKCONFIG_PROC.. So I'm sure the process of compiling and flashing it is been done correctly.
Additional info:
I'm using G920IDVU4FRD3 samsung stock kernel, which is version 3.10.61
Mine is a sm-g920i.
My current .config file is attached.