Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
For my project, I need my basic Linux box to run more like a transparent L2-bridge.
So, i want to disable the TCP/IP kernel space stack from the user-space.
Though a new kernel build can be built with no TCP option.
But, I want an option to disable it from the kernel which has got already the
TCP/IP stack up, from my user-space application too, when in need during runtime,
through some ioctl() calls, etc.
Can anyone help me on this regard
Rgds, Kiran. K
Last edited by kiran_cyberpro; 05-22-2007 at 08:00 AM.
I’m not sure if you can do this easily on a per-process basis (is that the question?). You can always unload the tcp module (if in fact tcp was built as a module). You might also try looking at some of the options given by sysctl.
There is of course the counterintuitive approach of using additional networking functionality to disable normal networking functionality: netfilter. There are a few iptables matches/targets which might prove beneficial to you (e.g., the “owner” match that may deny or accept based on PID or UID). This still means the functionality is in the kernel, it just limits it.
Yep, customizing kernel and adding the API would be the choice possible, only if I provide the complete embedded solution(with hardware), or a custom distribution or some patch along with my application code.
But, say suppose end-user(may or may not know much about Linux OS stuff) have a fresh installation of any Linux distribution(Fedora, Ubuntu, SUSE, etc, etc).
With my code, without any hassles I want him to just install and make use of this functionality.
Firewalls: well, thats seems to be a good idea, if not for ever at least for temporary fix. The reason behind this i don't want to burden the kernel by doing more processing by doing packet classification and filtering. And wanna avoid it some extent
I need networking option very much. Since the project is going to accept network traffic. Process in Layer-2 level like a network bridge/switch. But i want to disable the TCP/IP stack from user-space.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.