Make sure that "eth0" is not in the list of interfaces to bring up during boot. Otherwise parprouted will not initialize because it cannot find eth0.
Samuel Abreu wrote:
Ok, this "don't work" is in one particular case, i do not test in the normal way (With one wireless and one ethernet), in my case, i use 2 orinoco card (The old problem of the 2 wireless interface that do not rename the device of eth2 to netcs1, that you fixed!), and without ethernet, if i put the bridge, when the system is load, the parprouted process dont exist, in ps ax, then if i call manually the parprouted work fine, so, in the parpbridge initialization script, o change the normal call of the parprouted (The one with start-stop-daemon --start...), and put two lines calling parprouted direct from the path (/sbin/parprouted netcs0 netcs1), in that way, it works OK!
Now i trying put the bridge to work with 2 orinoco cards and 1 ethernet, but i dont have enough cards to make the necessary tests... =/
Samuel Abreu
Hi Samuel, That should happen. parprouted is restarted in /etc/network/ifup.Please give some more information, what do you mean "don't work well"?
_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
--
Best Regards,
Vladimir
Systems Engineer (RHCE)
-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
