From: Patrick H. <pat...@gm...> - 2005-02-21 13:10:10
|
Cooperative Linux Daemon, 0.6.2 Compiled on Sat Feb 5 10:19:28 2005 WARNING: error launching network daemon! I get this error message when starting colinux-daemon 0.6.2 0.6.1 works w/o problems I tried winpcap 3.0 and 3.1beta any chance to get a slightly more verbose error message? TIA Patrick <?xml version="1.0" encoding="UTF-8"?> <colinux> <block_device index="0" path="\DosDevices\d:\coLinux\colinux_root" enabled="true" /> <block_device index="1" path="\DosDevices\d:\coLinux\swap_device" enabled="true" /> <block_device index="2" path="\DosDevices\d:\coLinux\projekte" enabled="true" /> <bootparams>root=/dev/cobd0</bootparams> <initrd path="initrd.gz" /> <image path="vmlinux" /> <memory size="64" /> <network index="0" name="LAN-Verbindung" type="bridged" /> </colinux> |
From: Holger K. <hol...@gm...> - 2005-02-21 13:15:26
|
> WARNING: error launching network daemon! > > I get this error message when starting colinux-daemon 0.6.2 > 0.6.1 works w/o problems > > I tried winpcap 3.0 and 3.1beta Check if the executable (colinux-net-daemon.exe) really there. If you use the installer and don't let it install winpcap it won't unpack the network daemon. |
From: Patrick H. <pat...@gm...> - 2005-02-21 13:37:52
|
Hi, On Mon, 21 Feb 2005 14:15:11 +0100, Holger Krull <hol...@gm...> wrote: > If you use the installer and don't let it install winpcap it won't unpack the network daemon. thanks. colinux-net-daemon.exe was there. But I re-installed 0.6.2 with pcap option enabled though. All right. Now the "WARNING: error launching network daemon!" error message is gone, but I get a different error message later in the boot process: Error in pcap_findalldevs: PacketGetAdapterNames: Es sind keine weiteren Dateien vorhanden. Error initializing winPCap Looking for interface "LAN-Verbindung" Adapter Generic NdisWan adapter doesn't have a connection Checking connection: LAN-Verbindung Checking connection: LAN-Verbindung 2 Listening on: Intel 8255x-based Integrated Fast Ethernet (Microsoft's Packet Sch eduler) ... Listening for: (ether dst 00:ff:9e:90:c0:00) or (ether broadcast or multicast) o r (ip broadcast or multicast) kernel sees the network interfaces but they don't do anything, though. Ethereal running on host sees no packets at all when I try to ping my host system from colinux. Oh, and pcap service is running, of course. Patrick |
From: Holger K. <hol...@gm...> - 2005-02-21 13:59:00
|
> Error in pcap_findalldevs: PacketGetAdapterNames: Es sind keine weiteren Dateien > vorhanden. > Error initializing winPCap I've not seen this so far, i don't know what's causing this > Looking for interface "LAN-Verbindung" > Adapter Generic NdisWan adapter doesn't have a connection > Checking connection: LAN-Verbindung > Checking connection: LAN-Verbindung 2 > Listening on: Intel 8255x-based Integrated Fast Ethernet (Microsoft's Packet Sch > eduler) ... > Listening for: (ether dst 00:ff:9e:90:c0:00) or (ether broadcast or multicast) o > r (ip broadcast or multicast) This looks pretty normal. Is the network monitor (Netzwerkmonitortreiber) activated on LAN-Verbindung? How does eth0 get its ip-address? Fixed or dhcp? Does it get one at all (ifconfig eth0) ? |
From: Sam M. <pa...@gm...> - 2005-02-21 14:07:59
|
have you tried removing the name in the xml config file? thats not right, its picking up a physical device, which is why things aren't working. On Mon, 21 Feb 2005 14:58:50 +0100, Holger Krull <hol...@gm...> wrote: > > > Error in pcap_findalldevs: PacketGetAdapterNames: Es sind keine weiteren Dateien > > vorhanden. > > Error initializing winPCap > > I've not seen this so far, i don't know what's causing this > > > > Looking for interface "LAN-Verbindung" > > Adapter Generic NdisWan adapter doesn't have a connection > > Checking connection: LAN-Verbindung > > Checking connection: LAN-Verbindung 2 > > Listening on: Intel 8255x-based Integrated Fast Ethernet (Microsoft's Packet Sch > > eduler) ... > > Listening for: (ether dst 00:ff:9e:90:c0:00) or (ether broadcast or multicast) o > > r (ip broadcast or multicast) > > This looks pretty normal. > Is the network monitor (Netzwerkmonitortreiber) activated on LAN-Verbindung? > How does eth0 get its ip-address? Fixed or dhcp? Does it get one at all (ifconfig eth0) ? > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
From: Patrick H. <pat...@gm...> - 2005-02-21 14:12:43
|
Hi, On Tue, 22 Feb 2005 00:07:56 +1000, Sam Moffatt <pa...@gm...> wrote: > have you tried removing the name in the xml config file? I have to assign names because I have two network interfaces. If I don't use names, then how is colinux supposed to know which one is eth0 and which one is eth1? > thats not right, its picking up a physical device, which is why things > aren't working. I thought there was a change w.r.t. network device naming between 0.6.1 and 0.6.2? Patrick |
From: Sam M. <pa...@gm...> - 2005-02-21 14:15:59
|
Thats definately not right. I have 4 ethernet devices and a network bridge and colinux seems to do fine with this: <network index="0" type="tap" /> Two of my devices are colinux related, the other two are physical. coLinux isn't stupid, it'll detect which ethernet port its supposed to use with accuracy 90%, I'd only set this if you were getting issues to begin with On Mon, 21 Feb 2005 15:12:35 +0100, Patrick Huesmann <pat...@gm...> wrote: > Hi, > > On Tue, 22 Feb 2005 00:07:56 +1000, Sam Moffatt <pa...@gm...> wrote: > > have you tried removing the name in the xml config file? > > I have to assign names because I have two network interfaces. If I > don't use names, then how is colinux supposed to know which one is > eth0 and which one is eth1? > > > thats not right, its picking up a physical device, which is why things > > aren't working. > > I thought there was a change w.r.t. network device naming between > 0.6.1 and 0.6.2? > > Patrick > |
From: Holger K. <hol...@gm...> - 2005-02-21 14:21:06
|
Sam Moffatt schrieb: > Thats definately not right. I have 4 ethernet devices and a network > bridge and colinux seems to do fine with this: > <network index="0" type="tap" /> But he is using winpcap not tap. I have similar setup and giving 'LAN-Verbindung' is exactly what made it work. I have no idea what winpcap is complaining about though. > Two of my devices are colinux related, the other two are physical. Winpcap means there are only physical devices on windows. |
From: Patrick H. <pat...@gm...> - 2005-02-21 14:08:45
|
Hi, On Mon, 21 Feb 2005 14:58:50 +0100, Holger Krull <hol...@gm...> wrote: > > Error in pcap_findalldevs: PacketGetAdapterNames: Es sind keine weiteren Dateien > > vorhanden. > > Error initializing winPCap > > I've not seen this so far, i don't know what's causing this Then we're already two ;-) > > Looking for interface "LAN-Verbindung" > > Adapter Generic NdisWan adapter doesn't have a connection > > Checking connection: LAN-Verbindung > > Checking connection: LAN-Verbindung 2 > > Listening on: Intel 8255x-based Integrated Fast Ethernet (Microsoft's Packet Sch > > eduler) ... > > Listening for: (ether dst 00:ff:9e:90:c0:00) or (ether broadcast or multicast) o > > r (ip broadcast or multicast) > > This looks pretty normal. > Is the network monitor (Netzwerkmonitortreiber) activated on LAN-Verbindung? yes, it's activated on both interfaces > How does eth0 get its ip-address? Fixed or dhcp? Does it get one at all (ifconfig eth0) ? eth1 has static ip and can ping itself, but none else. eth0 is configured for dhcp but it doesn't get a IP, of course, because bridging is somehow broken and packets are not forwarded. I wish colinux and pcap had some logging or error reporting functionality. regards Patrick |
From: Holger K. <hol...@gm...> - 2005-02-21 14:16:18
|
>>How does eth0 get its ip-address? Fixed or dhcp? Does it get one at all (ifconfig eth0) ? > > > eth1 has static ip and can ping itself, but none else. > > eth0 is configured for dhcp but it doesn't get a IP, of course, > because bridging is somehow broken and packets are not forwarded. > > I wish colinux and pcap had some logging or error reporting functionality. How can you have eth0 and eth1 in colinux if you only have one definition in the xml file? You stated only <network index="0" name="LAN-Verbindung" type="bridged" /> Btw. i recommend to define a fixed MAC Adress if you use DHCP, my server quickly ran out of leases while testing as i uses the MAC for reassigning the former IP-Adress. Like in <network index="0" type="bridged" name="LAN-Verbindung 2" mac="00:ff:39:29:51:50"/> |
From: Patrick H. <pat...@gm...> - 2005-02-21 13:45:45
|
Hi, On Mon, 21 Feb 2005 14:38:43 +0100, Holger Krull <hol...@gm...> wrote: > Did you reboot after reinstalling? Yes. Same effect. regards Patrick |
From: Patrick H. <pat...@gm...> - 2005-02-21 15:11:09
|
Hi, Problem solved. Network option was <network index="1" name="LAN-Verbindung2" type="bridged" mac="D0:0F:DE:AD:BE:EF"/> instead of <network index="1" name="LAN-Verbindung 2" type="bridged" mac="D0:0F:DE:AD:BE:EF"/> What a shame. ;-) Thanks Patrick |