From: Henry N. <hen...@ar...> - 2010-08-03 20:49:14
|
Hello Mike, On 02.08.2010 18:40, Mike Mestnik wrote: > I'm able to ping Windows from coLinux, but Windows dose not attempt to > arp or ping back. Most odd, tcpdump under colinux shows only it's own > traffic and ping replies. I'm using ipv4ll for the tap interface on the > windows side and a static 169.254 address in coLinux. If you are using Windows 7 or XP-SP3, then remember to allow Ping in your Windows firewall. > eth0=ndis-bridge > > # Tuntap as private network between guest and host on second linux device > eth1=tuntap,,00:18:8B:26:44:88 For testing network interfaces, you should enable only one interface. So, please disable eth0 ("ifconfig eth0 down") at the time you are testing tap on eth1. Other case you can not see the packet way right. Please start the MAC with 02: for personal use (00: is reserved for real hardware cards). And I hope, this MAC number does not exist some there in your network! Using fixed MAC in an installer is a highly risk. Every body should have its one unique MAC. It would be better to leave this option out and let coLinux set a random number. The random number will generate only ones at first start, and is stored in registry for later use. > Push "create" > Push "Nagios Core" > Push 'path="C:\Program Files\Nagios Core\colinux-daemon.exe" @NagiosCore.conf --run-service "Nagios Core";autostart=1;depend=CoLinuxDriver;display=Nagios Core;description=Nagios Core Linux Service, this service manages a running instance of linux.;' > Call Service > Pop $0 ;response This part us ugly, wrong and will not run on all destinations. * Please never use "C:\Program Files\" directly! Please use the install path "$INSTDIR". * You should use the coLinux service installer. Or you should complete adding all dependensies. You are using TAP? Then should add "tap0801co". The colinux-daemon will parse your config and adds dependencies automatically, if you use such device. * You have not used full path to "NagiosCore.conf"? -- Henry N. |