#87 W2K+DialUp+ZoneAlarm for Debian: networking problem


I have problems making networking working.

Here is the relavant info: Win2K Sp4, Dial-up
connection, ZoneAlarm
firewall, coLinux version 0.6.2 with Debian

I managed to install colinux with debian image,
included the 1GB swap
file. Concerning networking, I used recommended (by
wiki pages) TAP
configuration. The dial-up connection does allow
Internet Connection
Sharing with the TAP device (called coLinux-Debian).
The TAP device
(colinux-Debian) has static IP address,
and static settings for DNS servers from my ISP. The
coLinuxed Debian is
configured with static IP and gateway

I can ping Debian (i.e. from Windows
shell, and Windows
(i.e. from Debian shell. However, when
connected to the
Internet (via Dial-up connection) apt-get does not
work, nor ping to any
other IP address (e.g. =
ftp.us.debian.org), as well as DNS
queries, etc.

In the Windows-side firewall (ZoneAlarm) I have set
both and in the trusted zone, so, it (firewall)
should not be in the
way of network communication.

I read through variety of networking explanations at
wiki and some linked
offsite pages, but nothing moves this situation an
inch. I guess I need
some help here, please.



Ps. The startup script is (from Cygwin):

./colinux-daemon.exe -t nt -c colinux.xml

and the config file colinux.xml is:

<?xml version="1.0" encoding="UTF-8"?>
<!-- This line needs to point to your root file
For example change "root_fs" to the name of the
Debian image.
Inside coLinux it will be /dev/cobd0

Block Device Aliasing: You can now handle most
dual-boot issues
by adding an alias="devname" to block_device. i.e.
alias="hda1" You can do this for SCSI as well as IDE.
You need
to be aware that if you add an alias, you need to
change your
bootparams root="devname" appropriately (you may need
to use
devfs naming in some situations). -->
<block_device index="0"

enabled="true" />

<!-- This line can specify a swap file if you wish,
or an additional
image file, it will /dev/cobd1. Additional
block_devices can
be specified in the same manner by increasing the
index -->

<block_device index="1"
enabled="true" />

<block_device index="2" path="\Device\Cdrom0"

<!-- bootparams allows you to pass kernel boot
parameters -->

<!-- Initial RamDISK (initrd) support -->
<initrd path="initrd.gz" />

<!-- image allows you to specify the kernel to boot -->

<image path="vmlinux" />

<!-- this line allows you to specify the amount of
memory available
to coLinux -->
<memory size="64" />

<!-- This allows you to modify networking
parameters, see the README
or website or wiki for more information -->
<network index="0" type="tap" name="TAP"/>


  • Logged In: YES

    Has this problem been resolved? This seems more like a
    support request than a bug.