[opensuse-arm] networking problem with openSUSE 12.3 in chroot
Hi, Using the HCL:Chroot HOWTO [1] and the openSUSE 12.3 JeOS rootfs [2] I've tried to get oS12.3 running on my Galaxy S2 with half success... The chroot environment is working [3] but I'm unable to access the network. Even ping returns with an error "Unable to open socket" Any tips? Thanks, Gábor [1] http://en.opensuse.org/HCL:Chroot HOWTO [2] http://download.opensuse.org/ports/armv7hl/distribution/12.3/images/openSUSE...) [3] https://en.opensuse.org/User:Gnyers/openSUSE-12.3-on-SGS2 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Forgot to mention that oS12.3 is running besides Android and it has networking. On Wed, 3 Apr 2013 09:13:36 +0200 Gábor Nyers <gnyers@suse.com> wrote:
Hi,
Using the HCL:Chroot HOWTO [1] and the openSUSE 12.3 JeOS rootfs [2] I've tried to get oS12.3 running on my Galaxy S2 with half success... The chroot environment is working [3] but I'm unable to access the network. Even ping returns with an error "Unable to open socket"
Any tips?
Thanks, Gábor
[1] http://en.opensuse.org/HCL:Chroot HOWTO [2] http://download.opensuse.org/ports/armv7hl/distribution/12.3/images/openSUSE...) [3] https://en.opensuse.org/User:Gnyers/openSUSE-12.3-on-SGS2 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Gábor Nyers - 9:24 3.04.13 wrote:
Forgot to mention that oS12.3 is running besides Android and it has networking.
On Wed, 3 Apr 2013 09:13:36 +0200 Gábor Nyers <gnyers@suse.com> wrote:
Hi,
Using the HCL:Chroot HOWTO [1] and the openSUSE 12.3 JeOS rootfs [2] I've tried to get oS12.3 running on my Galaxy S2 with half success... The chroot environment is working [3] but I'm unable to access the network. Even ping returns with an error "Unable to open socket"
Any tips?
In android you have to be a member of specific group to be able to do any networking. #define GID Capability AID_NET_BT_ADMIN 3001 Can create an RFCOMM, SCO, or L2CAPP Bluetooth socket AID_NET_BT 3002 Can create a Bluetooth socket AID_INET 3003 Can create IPv4 or IPv6 socket AID_NET_RAW 3004 Can create certain kinds of IPv4 sockets?? AID_NET_ADMIN* 3005 Allow CAP_NET_ADMIN permissions for process -- Michal Hrusecky <Michal@Hrusecky.net> -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Wed, 10 Apr 2013 18:59:33 +0200 Michal Hrusecky <michal@hrusecky.net> wrote:
In android you have to be a member of specific group to be able to do any networking.
#define GID Capability AID_NET_BT_ADMIN 3001 Can create an RFCOMM, SCO, or L2CAPP Bluetooth socket AID_NET_BT 3002 Can create a Bluetooth socket AID_INET 3003 Can create IPv4 or IPv6 socket AID_NET_RAW 3004 Can create certain kinds of IPv4 sockets?? AID_NET_ADMIN* 3005 Allow CAP_NET_ADMIN permissions for process
Thanks... this seems to be an important bit of information. In the described case was the problem something different. I've managed to solve the issue after I noticed that the DroidWall (firewall App) settings were a bit too restrictive. the chroot-ed openSUSE 12.3 is now working as a charm on the phone. Regards, Gábor -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (2)
-
Gábor Nyers -
Michal Hrusecky