From: Ming-Ching T. <min...@re...> - 2007-05-31 05:51:53
|
This is my first post to this mail list. Issue 1: ===== I have this problem of unable to get bridged network working on colinux-6.4.0 and no matter what I do, I could not get it working. On the same computer, I later installed colinux-0.7.1-20070326, it then works without any changes on the host system ( win2k ). The 0.6.4 relevent portion of the xml is as follows :- <network index="0" type="tap" name="tap1" /> <network index="1" type="bridged" Name="External" /> I did try a few other options but they are all not working. The 0.7.1 conf is as follows :- eth0=tuntap eth1=pcap-bridge,External This works as per my expectation, except that the documentation is a bit obscure about the syntax. Wonder anyone could throw lights on why it's not working on 0.6.4. Issue 2 ===== I am using uclibc 0.9.28 and busybox 1.4.2. The problem I have is that when I run busybox applet 'ifconfig' to turn on/off arp, I will hit an error message at the second time :- # ifconfig eth1 arp on <--- no error # ifconfig eth1 arp on <-- error message ifconfig: on: Unknown host Is it a busybox problem or what ? But the same program is running fine when I run it natively or inside qemu. Cheers. |
From: Henry N. <Hen...@Ar...> - 2007-06-01 17:23:07
|
Hello, Ming-Ching Tiew wrote: > Issue 1: > ===== > I have this problem of unable to get bridged network working > on colinux-6.4.0 and no matter what I do, I could not get it working. > On the same computer, I later installed colinux-0.7.1-20070326, > it then works without any changes on the host system ( win2k ). > > The 0.6.4 relevent portion of the xml is as follows :- > > <network index="0" type="tap" name="tap1" /> > <network index="1" type="bridged" Name="External" /> > > I did try a few other options but they are all not working. > > The 0.7.1 conf is as follows :- > > eth0=tuntap > eth1=pcap-bridge,External > > This works as per my expectation, except that the documentation > is a bit obscure about the syntax. Wonder anyone could throw lights > on why it's not working on 0.6.4. The new version 0.7.1 more tolerate the network adapter name, it has also a substring search. Check the output from start of colinux-daemon, watch the texts about network parsing for bridged. Old coLinux has also problems with spaces in network adapter name. Rename the adapter to a name whithout spaces and give the complete name in the XML name="..." After start of coLinux, check the running subprocess colinux-bridged-net-daemon.exe and it's parameters (http://www.microsoft.com/technet/sysinternals/utilities/ProcessExplorer.mspx) Compair it with your setings from XML file. Perhaps are some misunderstanded. An other problem: Version 0.6.4 has known problems. Network damons tends to terminates after a time. Have you updated to 0.6.4-20060912 from zip archive? (http://downloads.sourceforge.net/colinux/colinux-0.6.4-20060912-update.zip?use_mirror=switch) But: Why not hapy with running 0.7.1? We no longer support the old version, and XML format is out. -- Henry |
From: Ming-Ching T. <min...@re...> - 2007-06-04 04:22:02
|
Any pointer to how to programmatically enumerate Windows Local area network connections ? This registry seems to hold the connection names :- [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325- 11CE-BFC1-08002BE10318}\{07209320-113C-4A5F-9F22-D393FDCFAB25}] But it seems to hold some old connections which I have already removed already. In a computer where I have 2 network cards, there are some older entries which I have already removed. Where else I should search in the registery for the current connections available ? |
From: Henry N. <Hen...@Ar...> - 2007-06-04 20:15:27
|
Ming-Ching Tiew wrote: > Any pointer to how to programmatically enumerate Windows > Local area network connections ? > > This registry seems to hold the connection names :- > > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325- > 11CE-BFC1-08002BE10318}\{07209320-113C-4A5F-9F22-D393FDCFAB25}] > > But it seems to hold some old connections which I have already removed > already. > > In a computer where I have 2 network cards, there are some older entries > which I have already removed. > > Where else I should search in the registery for the current connections > available ? Your registry path is ok, coLinux use this as NETWORK_CONNECTIONS_KEY. Think, you can not get it by registry only. This are the names only, not the connection state. See into source of coLinux src/colinux/os/winnt/user/conet-bridged-daemon/main.c The function "pcap_init" does search a connected interfaces, if no name was given. See also the function 'GetInterfaceInfo' on MSDN and the return as IP_INTERFACE_INFO->Adapter[i].Name -- Henry |