Re: [lwip-users] lwIP Windows implementation

[Gisle Vanem]

Resending, sent too soon.

<address@hidden> wrote:

> > Gisle Vanem <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?

Actually Simon wrote that.

> This is, I think, quite superior than the WinPcap driver. The TAP is 
> real interface for Windows that is assuming that it is talking to a 
> real network. The "Network Bridge" will correctly switch the packet 
> based on there physical address.

Okay, I can see why you method could be more versatile. I.e. I have
a VPN connection to the outside; for this to work, Windows creates
a virtual adapter (WAN (PPP/SLIP) Interface). In my case it has the name:
\Device\NPF_{75451EE7-5145-471A-BAF5-124BE8439D10}. The downside
is that this is not writeable by any WinPcap/libpcap based programs. So
if a "virtual bridge" as you describe it could allow lwIP based programs to
talk over a VPN, it would be very nice. Remains to be tested.


> This could be improved by adding a 
> spawning tree support in the link layer. 

Do you mean "spanning tree"? http://en.wikipedia.org/wiki/Spanning_Tree_Protocol

> are irrelevant as we bypass it completly. This is impressive to see 
> your fake Ethernet MAC populating ARP list of computer around yours.

"ARP Spoofing" to sniff beyond switches? Yes, I can envision lwIP be used as the 
base for lots of cool network hackety-hackety tools and malware.

--gv