Michael Warmuth wrote:

 I am sorry, but having two interfaces configured to the same subnet is wrong. If you mean that you disable one of either interface, this would be ok. But it is definitely not sufficient to just "not use" one of either interface. The IP stack will not care for if you don't use one of two interfaces - exactly one of two will just always win and the other will never be used.

Note that NetBEUI is currently ot handled by XWLAN, so you would have to do that with the script feature.

I would be interested though to have an exeperienced user telling me what else could be required/make sense for better NetBEUI support.

If this is not too much in one piece, I could think of integrating some support for it.

Off course this does take a longer time (two times waiting for the DHCP
lease), but the result is that it does actually work.
  

For testing I implemented something different, at least for the default route. If the WLAN interfaces is to be kept, the default route is saved, deleted, then LAN is deleted, then default route is reset - et voila: the defalt route is attached to the WLAN interface. I intend to cache _all_ routes for the cabled interface and restore them all on the correct interface, so network and hostroutes would also be handled properly. The only drawback is that I cannot do that for the way back (wireless to cabled). Here the setup script is to setup all routes properly again.

P.S. All the time I spent to get XWLAN working correctly was more or
less useless as my mini-PCI "IBM High Rate ..." still chocks up when
sending more than just a few KB (XWLAN shows "No Card"). But this is a
driver problem...
  

I am sorry to hear that. Did you post a request to netlabs.org on this ?