Menu
▾
▴
[coLinux-devel] [ colinux-Bugs-1792009 ] ftkl console breaks network?
|
From: SourceForge.net <no...@so...> - 2007-09-24 18:44:24
|
Bugs item #1792009, was opened at 2007-09-11 00:30 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1792009&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: ftkl console breaks network? Initial Comment: If i use set ET=LAN-ADM851X set ETH=eth0=pcap-bridge,"%ET%",, set OPTIONS=%OPTIONS% -k set OPTIONS=%OPTIONS% -t NT to start conlinu 0.8.0 0909all is well. but if i omit the -t NT the host looses connection to the ethernet interface but the colinux a reachable via ssh. #Linux colinux 2.6.22-co-0.8.0 #1 PREEMPT Mon Sep 10 08:36:19 UTC 2007 i686 GNU/ ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2007-09-24 20:44 Message: Logged In: YES user_id=579204 Originator: NO > conet-bridged-daemon: Auto selecting name for bridged interface > conet-bridged-daemon: checking connection: LAN-TAP V9 > conet-bridged-daemon: listening on: TAP-Win32 Adapter V9... > conet-bridged-daemon: listening for: (ether dst 00:ff:dd:e8:54:c0) or Auto selecting means, you was not given name on which Ethernet the bridge should listening. In your case the TAP was first found as connected Network. That's badly, but true, and the bridget network can't known it better. If you have more as one network cards in your environment (TAP is also a 'virtual card' here), then the AUTO probing can be listen on the wrong interface. You should give always a full name of your real Ethernet card in the bridge config. > eth0=pcap-bridge,"LAN-ADM851X" Yes, this is right and avoids such problems. That you find it by adding the "-t NT", can be the different spawn timing of daemons, in this case the TAP was shorter as the bridged network. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-09-17 23:01 Message: Logged In: NO Sorry, can't reproduce the problem. But i assume it's related to the "many" interfaces i have in the box and "happens" when colinux is taking the wrong. Failing (colinux not reachable): \coLinux\colinux-daemon.exe -k -t NT kernel=vmlinux initrd=initrd.gz mem=128 co bd4=\Device\Cdrom0 hdc=:cobd4 cobd1=\colinux.disks\swap_file hdb=:cobd1 cobd0=\c olinux.disks\Debian-3.0r2.ext3-mit-backports.imi root=/dev/cobd0 hda=:cobd0 cof s0=\colinux.disks\exchange eth0=pcap-bridge,"" Cooperative Linux Daemon, 0.8.0 Compiled on Sep 10 2007 09:00:06 PID: 2768 colinux: booting console: Coopeartive Linux console started conet-bridged-daemon: Auto selecting name for bridged interface conet-bridged-daemon: checking connection: LAN-TAP V9 conet-bridged-daemon: listening on: TAP-Win32 Adapter V9... conet-bridged-daemon: listening for: (ether dst 00:ff:dd:e8:54:c0) or (ether bro adcast or multicast) or (ip broadcast or multicast) \coLinux\colinux-daemon.exe -k kernel=vmlinux initrd=initrd.gz mem=128 cobd4=\D evice\Cdrom0 hdc=:cobd4 cobd1=\colinux.disks\swap_file hdb=:cobd1 cobd0=\colinux .disks\Debian-3.0r2.ext3-mit-backports.imi root=/dev/cobd0 hda=:cobd0 cofs0=\co linux.disks\exchange eth0=pcap-bridge,"LAN-ADM851X",, OK: (today, because interface was named on the comand line) colinux: booting conet-bridged-daemon: Looking for interface "LAN-ADM851X" conet-bridged-daemon: checking connection: LAN-TAP V9 conet-bridged-daemon: checking connection: LAN-TAP V8(colinux) conet-bridged-daemon: checking connection: LAN-ADM851X conet-bridged-daemon: listening on: ADMtek 851X Series AdapterNDIS 5.0 Miniport Driver... conet-bridged-daemon: listening for: (ether dst 00:ff:1c:1f:ba:00) or (ether bro adcast or multicast) or (ip broadcast or multicast) ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2007-09-17 18:36 Message: Logged In: YES user_id=579204 Originator: NO The complete command line would be helpful. Please set an "echo on" in your batch and let us see your line with colinux-daemon, and the first messages which includes teh seaching for network interface. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1792009&group_id=98788 |