From: Mike M. <mme...@na...> - 2010-08-03 19:37:59
|
On 8/2/2010 9:47 PM, Mike Frysinger wrote: > On Mon, Aug 2, 2010 at 13:22, Mike Mestnik wrote: > >> On 8/2/2010 1:18 PM, Mike Frysinger wrote: >> >>> On Mon, Aug 2, 2010 at 13:07, Mike Mestnik wrote: >>> >>>> This looks to be a vary full featured installer, but I can't determine a >>>> solution to the issue I'm reporting. For my installation "ndis> >>>> winpcap" >>>> so winpcap was removed from the install. >>>> >>> i guess i missed what you were talking about. i thought you were >>> having problems configuring the taps between windows and colinux. i >>> dont have a clue wrt ndis vs winpcap; sorry. >>> >> That's correct I am. I'm confused, did you mean to say that wpcap could >> replace taps? I don't feel that wpcap is a solution >> > the wiki documents that wpcap is the fastest solution. > http://colinux.wikia.com/wiki/Network > > That may vary well be and I see the document... However WinPcap lives on-top of NDIS, so any performance impact that NDIS supplies should still exist. There is no clear documentation on what part of NDIS(driver or system) that winpcap uses, but based on it's absence in the Network Connection's screen I'd guess it uses the system API to access a driver so I don't clearly see the difference from what coLinux must do. I could completely not know what I'm talking about. >> and I don't feel that >> your patch corrects the issue I was having with taps. >> > the point of my patch was to show how to configure the network > interfaces after they've already been created. that's all. > -mike > Ahh, so I could do network configuration as part of my installer... I saw that and it looked interesting, I didn't quickly grasp how these variables were passed down to the init scripts living in a filesystem image. I can only imagine they pass through /proc/cmdline. This would not solve my issue though, the problem is post-configuration AFAIK. -- Mike Mestnik Technical Team ___ Nagios Enterprises, INC. Email: mme...@na... Web: www.nagios.com |