RE: [coLinux-users] Upgraded to 0.6.1, but networking stopped - F ixed

[<joe...@ce...>]

When I started colinux without the -t nt, I noticed this message at the end
of the dos window:
bridged-net-daemon: Checking adapter: Generic NdisWan adapter
bridged-net-daemon: Checking adapter: NOC Extranet Access Adapter
bridged-net-daemon: Checking adapter: Broadcom NetXtreme Gigabit Ethernet
Driver

When I changed the _name_ colinux.xml bridged network node from:
"Broadcom 570x Gigabit Integrated Controller"
to be:
"Broadcom NetXtreme Gigabit Ethernet Driver"

it fired right up!

However, why would the name of the interface change between wincap, tap,
and/or colinux versions?


-----Original Message-----
From: col...@li...
[mailto:col...@li...]On Behalf Of
joe...@ce...
Sent: Friday, June 04, 2004 3:48 PM
To: col...@li...
Subject: [coLinux-users] Upgraded to 0.6.1, but networking stopped


Greetings.
	I upgraded today from 0.6 to 0.6.1, and I'm having a little trouble.

	I'm working on a W2K box connected to the company lan.  My old
install was the debian 1g version, and I was very proud to have not only
changed my machine name, but also gotten the company dhcp to give me an IP
and the DNS to recognise the local name.
	I uninstalled via add/remove programs as suggested, then installed
and let the installer install the tap driver and colinux.  I renamed the tap
driver connection TAPConnection.  I hadn't changed the default.colinux.xml
to a different name, so I was chagrined to see that it had been overwritten.
After the install, I read about it in the readme.

	So, I rebooted and pointed the default.colinux.xml (now renamed) to
my old image and swap and gave it a try.  It hung on the network
connections, but eventually got up to the login.  I haven't installed it as
a service, because I wanted to make sure that it was working first.

	However, when I log in my eth0 interface does not connect.

fermi_01:~# ifconfig
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

dmesg includes these lines:
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 1024 buckets, 8Kbytes
TCP: Hash tables configured (established 8192 bind 16384)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.

In the dos window ipconfig reveals this:
Ethernet adapter TAPConnection:

        Connection-specific DNS Suffix  . :
        Autoconfiguration IP Address. . . : 169.254.179.187
        Subnet Mask . . . . . . . . . . . : 255.255.0.0
        Default Gateway . . . . . . . . . :

Trying to ping that IP address from the colinux side I get
fermi_01:~# ping 169.254.179.187
PING 169.254.179.187 (169.254.179.187): 56 data bytes
ping: sendto: Network is unreachable
ping: wrote 169.254.179.187 64 chars, ret=-1
ping: sendto: Network is unreachable

ping for 127.0.0.1 from colinux works OK
fermi_01:~# ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.0 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.1 ms

Meanwhile, I'm looking at the TAPConnection Status, and every couple of
minutes or so the sent packets goes up by 2 or 3, but receieved remains at
zero.  No pings that I'm doing seem to have any effect on these numbers.

The colinux.xml network node looks like this:
<network index="0" type="tap" />


What else am I missing?
Thanks,
Joe


-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users