Menu
▾
▴
Re: [coLinux-devel] Installation problem, XP Pro
|
From: John N. <jo...@mo...> - 2004-05-05 22:25:24
|
It seems to me that you are trying to do a whole bunch of things at the
same time, so first I'd suggest you cut that out. Don't worry about
starting colinux as a service until after you can get it working right
as a standalone daemon. First things first.
You have an error in your config as well... I figure either you want to
use XP's native bridging, or else you want to use ICS. Either way,
you'll be using the TAP-Win32 driver instead of the WinPCAP bridge, and
so your colinux configuration needs to reflect that by setting the
"type" variable to "tap" instead of "bridged". You only want "bridged"
if you are bridging via WinPCAP instead of doing it natively (which only
XP can do). (Yeah, yeah, the "bridged" value is stupid and confusing
for us XP folks... I for one would like it renamed to something more
appropriate, like "winpcap".)
You need to know whether or not your organization will allow you to have
a second IP address for your system. Bridging makes a lot of sense for
many people, but it won't work unless you can have a second IP. Find
that out first. If you can't have a second IP, you'll need to use
Internet Connection Sharing instead. As it is, I have no idea whether
you can do bridged mode since you haven't given sufficient information
for that.
If you can have a second IP, you need to know whether it will be given
out dynamically (via DHCP) or statically. If it is given via DHCP, your
colinux system will have to be configured to obtain it via DHCP. If you
have any problems with Windows' own networking once you have bridged the
two connections, it may be a configuration issue of your admin's DHCP
server (some admin's like to have it setup so that specific IP addresses
are assigned to specific hosts, but bridging will change your MAC
address, so the assignment criteria breaks -- use "ipconfig /all" from
command prompt to learn your new MAC address after the connection is
bridged, and get that to your admin if things don't work).
If you can't have a second IP, you need to clear out *all* the bridging
crap... your network connections should be entirely barren without a
bridge in sight. Only then will you be able to enable ICS.
You should be following the instructions under "Networking" in the wiki
online:
http://www.colinux.org/wiki/index.php
dc...@ro... wrote:
>John Nelson wrote:
>
>
>>You will not be able to setup ICS until you
>>have colinux up and running and having initialized its eth0 interface
>>(it doesn't need to have assigned an IP to it, but the driver for the
>>interface must have been enabled in the kernel -- if the driver is
>>running, "ifconfig eth0" will produce a non-error result).
>>
>>
>
>
>
>>Did you try using bridged
>>mode already and are now falling back to NAT mode?
>>
>>
>
>Yes, bridging didn't appear to work properly, so I thought I'd try NAT.
>That may have been a poor choice, so I'll go back to trying bridging.
>
>I did find the reference to first starting colinux before enabling ICS.
>It wasn't in the first instruction file I found, the one which came with
>the distribution. But even after starting colinux, I still didn't see any
>sharing options. See the log I sent separately.
>
>I've uninstalled TAP and rebooted. Then, following the instructions with
>the Fedora distribution, I ran these commands with the results shown. (My
>shell is Cygwin bash. I've wrapped a few lines to get around limitations
>in the corporate mail system.)
>
> $ cd c:/colinux
> $ cat fc1.colinux.xml
> <?xml version="1.0" encoding="UTF-8"?>
> <colinux>
> <block_device index="0" path="\DosDevices\c:\colinux\fc1_2GB_root"
> enabled="true">
> </block_device>
> <block_device index="7" path="\DosDevices\c:\colinux\swap_device"
> enabled="true">
> </block_device>
> <bootparams>ro root=/dev/cobd0</bootparams>
> <image path="vmlinux"></image>
> <memory size="128"></memory>
> <network index="0" type="bridged"
> name="Intel(R) PRO/1000 MT Network Connection">
> </network>
> </colinux>
> $ ./colinux-daemon -c fc1.colinux.xml -i CoLinux
> Cooperative Linux daemon
> daemon: manager not opened
> daemon: removing driver leftover
> driver: stopping driver service
> driver: removing driver service
> daemon: installing kernel driver
> daemon: loading configuration from fc1.colinux.xml
> daemon: creating monitor
> co_message_switch: setting callback rule for 7
> co_message_switch: setting callback rule for 2
> co_message_switch: setting callback rule for 6
> co_message_switch: setting callback rule for 3
> co_message_switch: setting callback rule for 0
> co_message_switch: setting callback rule for 4
> colinux: launching net daemons
> daemon: launching daemon for conet0
> executing: colinux-bridged-net-daemon -i 0 -n
> Intel(R) PRO/1000 MT Network Connection -mac 00:43:4f:4e:45:30
> daemon: launching console
> executing: colinux-console-fltk -a 0
> Linux version 2.4.25-co-0.6.0 (ka...@ca...)
> (gcc version 3.3.3 (Debian)) #57 Mon Mar 22 23:56:28 IST 2004
> 128MB LOWMEM available.
> On node 0 totalpages: 32768
> zone(0): 0 pages.
> zone(1): 32768 pages.
> zone(2): 0 pages.
> Kernel command line: ro root=/dev/cobd0
> Initializing CPU#0
> Setting proxy interrupt vectors
> CPU_HAS_TSC: 1Detected 2394.049 MHz processor.
> Console: colour CoCON 80x25
> Calibrating delay loop... 418.61 BogoMIPS
> Memory: 126892k/131072k available (1126k kernel code, 0k reserved,
> 62k data, 52k init, 0k highmem)
> Dentry cache hash table entries: 16384 (order: 5, 131072 bytes)
> Inode cache hash table entries: 8192 (order: 4, 65536 bytes)
> Mount cache hash table entries: 512 (order: 0, 4096 bytes)
> Buffer cache hash table entries: 8192 (order: 3, 32768 bytes)
> Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
> CPU: Trace cache: 12K uops, L1 D cache: 8K
> CPU: L2 cache: 512K
> CPU: After generic, caps: bfebfbff 00000000 00000000 00000000
> CPU: Common caps: bfebfbff 00000000 00000000 00000000
> CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 09
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... OK.
> POSIX conformance testing by UNIFIX
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Initializing RT netlink socket
> Starting kswapd
> Journalled Block Device driver loaded
> devfs: v1.12c (20020818) Richard Gooch (rg...@at...)
> devfs: boot_options: 0x0
> pty: 256 Unix98 ptys configured
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> loop: loaded (max 8 devices)
> cobd0 size: 2048000 kb
> cobd: loaded (max 8 devices)
> 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.
> EXT3-fs: INFO: recovery required on readonly filesystem.
> EXT3-fs: write access will be enabled during recovery.
> pipe client 0/6: Connecting to daemon...
> pipe client 0/6: Connection established
> bridged-net-daemon: Checking adapter: Intel(R) PRO/1000 MT
> Network Connection (Microsoft's Packet Scheduler)
> bridged-net-daemon: Listening on: Intel(R) PRO/1000 MT
> Network Connection (Microsoft's Packet Scheduler) ...
> bridged-net-daemon: Listening for: (ether dst 00:43:4f:4e:45:30)
> or (ether broad cast or multicast) or (ip broadcast or multicast)
> pipe client 0/8: Connecting to daemon...
> pipe client 0/8: Connection establisheddaemon: module connected: console
> co_message_switch: setting callback rule for 6
> daemon: module connected: conet0
> co_message_switch: setting callback rule for 8
> kjournald starting. Commit interval 5 seconds
> EXT3-fs: recovery complete.
> EXT3-fs: mounted filesystem with ordered data mode.
> VFS: Mounted root (ext3 filesystem) readonly.
> Freeing unused kernel memory: IMPLEMENTATION MISSING
> EXT3 FS 2.4-0.9.19, 19 August 2002 on cobd(117,0), internal journal
> conet0: initialized
>
>That leaves the shell occupied and, of course, Windoze can't do ^Z. So
>from a different shell, I entered:
>
> $ net start CoLinux
> The service name is invalid.
>
> More help is available by typing NET HELPMSG 2185.
>
>I also tried "net start colinux" with the same result.
>
>Within the console window which colinux opened, I logged-in as root and
>got these results (manually typed since there doesn't appear to be any
>clipboard active in the console window):
>
> # ifconfig eth0
> eth0 Link encap:Ethernet HWaddr 00:43:4F:4E:45:30
> inet addr:192.168.0.40 Bcast:192.168.0.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:45 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:3431 (3.3 Kb) TX bytes:168 (168.0 b)
> Interrupt:2
>
>I'm not usually very dense about these things, but I'm lost as to what
>should come next.
>
>
>
>>If that isn't it, or doesn't work, feel free to drop me a note with your
>>screenshots.
>>
>>
>
>I'll hold off for now. Thanks, anyway.
>
> Dave Close
>
>
>
>
>
|