Hello, On Sun, Jun 28, 2009 at 05:02:51PM +0800, Da Zheng wrote: > Da Zheng wrote: >> I should test again whether they can work if the Ethernet card cannot >> be set in promiscuous mode. >> I look into the code of eth-multiplexer again. It seems that >> eth-multiplexer should work even if the ethernet card cannot be set in >> promiscuous mode. >> > I just tested eth-multiplexer that doesn't set the ethernet card in the > promiscuous mode, and it can still work. > In order to exclude the possibility that setting the ethernet card in > the promiscuous mode can cause the problem, you can remove the > corresponding code in eth-multiplexer. > The code of setting the promiscuous mode is in > eth-multiplexer/ethernet.c. Remove the function call of set_promisc() in > ethernet_open() and ethernet_close(). > Maybe it can help.
Just out of curiosity, I did the same wget of which I was talking about in the other mail, but with the whole devnode-eth-multiplexer-pfinet set up. I mean, I did the following: # settrans -a /dev/eth0 devnode eth0 # settrans -a multiplexer eth-multiplexer -i /dev/eth0 # settrans -a /servers/socket/2 pfinet -i multiplexer/veth0 -a <ip> -g <ip> -m <mask> In this case wget behaves exactly the same as it does in the case when I don't run eth-multiplexer, the only difference being that things happen somewhat slower. This makes me suspect that eth-multiplexer is not the troublesome component we are looking for. Do you share this opinion or do you still insist on my trying to deprive eth-multiplexer of the functionality of setting the device in promiscuous mode? Regards, scolobb
