Thank you Could you confirm the Netfilter support/framework is actually present, its just that the ability to use it in this way is disabled by default (if so, out of curiosity, was that for security and/or performance reasons?).
Is it possible to obtain all the necessary constituent parts (hardware specific drivers etc.) from somewhere in order to include in a custom system image that can be successfully executed on hardware? On Jul 25, 2:03 pm, Dianne Hackborn <hack...@android.com> wrote: > Whether or not you have to rebuild the kernel, you are going to need to > create your own custom system image, because nothing like this is available > to normal apps in the SDK. > > On Sun, Jul 25, 2010 at 1:12 PM, potassium > <symbianprofessio...@hotmail.com>wrote: > > > > > Thanks Dianne > > > However I don't want to intercept the traffic to determine the number > > of bytes sent, I want to intercept TCP, replace it with a proprietary > > protocol (based on UDP) and then re-inject the packets into the stack > > as UDP (and do the reverse for incoming UDP packets which have been > > also converted from TCP by a server sitting in the network). I'm > > trying to find out the best way of achieving this. > > > Netfilter seems to be specifically designed to do this in Linux, > > however I'm under the understanding netfilter is disabled by default > > in the stock Android release. Is this correct? > > Are there any (many) devices on the market with it enabled? > > > If we had to rebuild the kernel with it enabled we'd have to create a > > new rom image to flash devices with, ultimately we would need to do > > this with a network operator / device manufacturer as customer/partner > > so ultimately that's no problem. However if we wanted to create a > > proof-of-concept demo first, if we re-built the kernel, I'm presuming > > we wouldn't be able to flash a device because we wouldn't have access > > to the hardware specific drivers that would need to be included in the > > rom image. (i.e. suppose we want to demo on device X and Y, there will > > be I'm assuming be specific hardware drivers for things such as the > > screen, keyboard, modem etc. and if we had to re-build the kernel in > > order to actually that build onto a device we'd need those specific > > drivers for devices X and Y, along with anything else else necessary > > for the image to execute on those pieces of hardware). > > > Could anybody comment on my speculation? > > > Thanks > > > -- > > unsubscribe: > > android-kernel+unsubscr...@googlegroups.com<android-kernel%2bunsubscr...@googlegroups.com> > > website:http://groups.google.com/group/android-kernel > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
