lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] lwIP TCP/IP as the default TCP/IP stack on


From: address@hidden
Subject: Re: [lwip-users] lwIP TCP/IP as the default TCP/IP stack on
Date: Sat, 09 Nov 2019 19:33:37 -0200

 
If there is no easy way of replacing the entire default Linux kernel TCP/IP stack, then how are we supposed to use lwIP TCP/IP stack in our applications ?

 

 

De: address@hidden
Enviada: 2019/11/09 14:02:04
Para: address@hidden
Assunto: lwip-users Digest, Vol 195, Issue 12
 
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.nongnu.org/mailman/listinfo/lwip-users
or, via email, send a message with subject or body 'help' to
address@hidden

You can reach the person managing the list at
address@hidden

When replying, please edit your Subject line so it is more specific
than "Re: Contents of lwip-users digest..."


Today's Topics:

1. lwIP TCP/IP as the default TCP/IP stack on Linux (address@hidden)
2. Re: lwIP TCP/IP as the default TCP/IP stack on Linux (Joan Lledó)


----------------------------------------------------------------------

Message: 1
Date: Fri, 08 Nov 2019 23:09:38 -0200
From: "address@hidden" <address@hidden>
To: address@hidden
Subject: [lwip-users] lwIP TCP/IP as the default TCP/IP stack on Linux
Message-ID:
<address@hidden>
Content-Type: text/plain; charset="utf-8"

An HTML attachment was scrubbed...
URL: <https://lists.nongnu.org/archive/html/lwip-users/attachments/20191108/446f7a46/attachment.html>

------------------------------

Message: 2
Date: Sat, 9 Nov 2019 09:59:15 +0100 (CET)
From: Joan Lledó <address@hidden>
To: address@hidden
Subject: Re: [lwip-users] lwIP TCP/IP as the default TCP/IP stack on
Linux
Message-ID: <address@hidden>
Content-Type: text/plain; charset=utf-8


> Could anybody, please, tell us how to get rid of the *default TCP/IP*
> stack from *Linux* kernel so that only *lwIP* will be left to handle all
> IP networking traffic ?
>

I'm not an expert on Linux architecture, but I'd say you should create a
new module for the kernel, which embeds all lwip code + drivers,
intercepts all syscalls for sockets API and redirects it to lwip instead
of default stack.



------------------------------

Subject: Digest Footer

_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users

------------------------------

End of lwip-users Digest, Vol 195, Issue 12
*******************************************
reply via email to

[Prev in Thread] Current Thread [Next in Thread]