[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-users] lwIP Windows implementation
From: |
Simon Goldschmidt |
Subject: |
Re: [lwip-users] lwIP Windows implementation |
Date: |
Tue, 20 Sep 2011 15:34:07 +0200 |
Gisle Vanem <address@hidden> wrote:
> <address@hidden> wrote:
>
> > I've ported lwIP on Windows
There's already a win32 port for lwIP in the contrib module. Is there anything
wrong with that port or why did you create your own port?
> > in userspace as a cool way to work around
> > Windows TCP/IP stack limitation. See here: http://www.dupuis.me/node/21
>
> I've read it briefly and looked at some of your src-code. TapWin32.cpp
> uses OpenVPN's tap-driver instead of WinPcap. I fail to see the advantage
> of this.
Yep.
> If there really is one or is it just another way of getting to the
> link-layer?
>
> And how does all this "work around Windows TCP/IP stack limitation" for an
> arbitrary
> program like nmap? lwIP can AFAICS not be used to replace Winsock
> completely.
> It would be cool though.
Hmm, you probably would "only" need to create "winsock.dll" or "ws2_32.dll"
that emulates the original dll's API and place it beside the exe... I haven't
tried that, though. Plus you would get one IP address per application...
> I'm only aware of libcurl using lwIP as a Winsock
> replacement
> at the moment.
Really? I didn't know that.
Simon
--
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de