> [..] So, in > this situation, I need to manually check from one machine to another what > is the actual adapter it is using and update the PACKET_LIB_ADAPTER_NR. Do > I really need to do this? Or maybe lwIP supports automatic detection of > which adapter to use? Please advise.
Since I wrote that part, I can tell for sure it doesn't support automatic detection. But of course you can implement that if you want. You can search for - the GUID of the adapter (don't know if that helps you much) - the name of the adapter (could be difficult, too, as that name can be changed by the user) - have some automatic fallback, but that would mean with a real and a virtual LAN, it could go wrong - rely on the company part of the adapter's MAC (that should be the same for all your virtual LANs) As you can see, all approaches have a downside, which is why there is no automatic detection, yet. You could also write the index into a configuration file, which is parsed when the lwIP process is started. After all, the win32 port was started as a development project. I don't know if it is safe to be used in a production environment (if that's what you are looking for). Simon -- Jetzt 1 Monat kostenlos! GMX FreeDSL - Telefonanschluss + DSL für nur 17,95 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
