colinux-users — coLinux users mailing list

Re: [coLinux-users] Smaller filesystems (gratuitous e2compr plug)

[Paul W. <Pau...@in...>]

----- Original Message ----- 
From: "Jason A. Pattie" <pat...@pc...>
To: "Paul Whittaker" <Pau...@in...>
Cc: <col...@li...>
Sent: Friday, June 11, 2004 12:53 AM
Subject: Re: [coLinux-users] Smaller filesystems (gratuitous e2compr plug)


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Paul Whittaker wrote:
> | Note that you will need special e2compr-aware versions of ext2 tools
> | (e2fsck, chattr, etc) available from the e2compr.sf.net site.  Please
note
> | also that, although it has been around for many years, e2compr is
> considered
> | experimental and should not be relied upon for storage of anything
> | particularly valuable.  But then the same is true of coLinux, I guess.
>
> I had my company laptop setup once using e2compr to compress everything
> on it (I have a 10GB harddrive with only 4.5GB available to Linux).  I
> pretty much lost everything on it.  Major filesystem corruption occurred
> after using it for a few months.  I can't remember the exact details,
> but files started not being able to decompress, and I think some may
> have ended up being deleted as well.  So, unless there has been some
> major work done on e2compr in the past year or so, I probably would not
> rely on it.

It depends what you are doing.  I will happily admit to not daring to use
e2compr with my main Linux distro myself, but have had no problems
whatsoever with it in an embedded role with a very small number of files on
an initrd filesystem that gets reset to a known-good state every time the
machine boots.  My uses of coLinux are along the same lines.

Nitpick: e2compr cannot cause "filesystem corruption", because it doesn't
compress metadata (ie. directories, inode info).  It's not to blame for any
files that go missing.  At worst it can only result in corruption of file
contents.

Re: [coLinux-users] Win2k and services.

[Patrick W. <pa...@im...>]

On Thursday 10 June 2004 04:07 am, ch...@to... wrote:
> bridging does not work with wireless...
> If by NAT you mean the crippled NAT called ICS that MS provides maby your
> problem is two lans that are the same network. Lots of wireless routers
> default to the 192.168.0.0/24 network and ICS also uses 192.168.0.0/24
> this is the only option in win2k

	FYI, it can also be changed in Win2k SP4.. after you enable it and let ICS=
=20
slam the IP for that adapter to 192...  I might have had to reboot or=20
disable/enable the adapter or something before it started working.  Of=20
course, this was with two physical adapters, not one physical and the TAP=20
one.  So try that if changing the wireless is harder or impractical.

later,
patbob

> but I think it may be possible to change
> it in XP after windows sets up ICS with the default. On 2k you must change
> the default network on the wireless router. (It may be possible to use the
> routing and remote access service but I think you need tools from the 2k
> server cd to configure it)
> >        I've been unsuccessful in getting the network working with either
> > the bridge or nat methods. Am using the Debian image.
> >
> > I got a little further with NAT but I suspect my routes were incorrect
> > because of my wireless router.
> >
> > My question is, is the "Routing and Remote Access" service needed under
> > win2k ? I hope not because that enables netbios. I couldn't find any
> > requirements list on the Wiki site.

[coLinux-users] Kernel Headers

[Ramkumar I. <rr...@bu...>]

Hi List,

      Where do I get the kernel headers for  2.4.26-co-0.6.1 kernel. I 
am trying to compile some kernel modules but the /lib/modules directiry 
does not exist.

Ram

Re: [coLinux-users] Smaller filesystems (gratuitous e2compr plug)

[Jason A. P. <pat...@pc...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul Whittaker wrote:
| Note that you will need special e2compr-aware versions of ext2 tools
| (e2fsck, chattr, etc) available from the e2compr.sf.net site.  Please note
| also that, although it has been around for many years, e2compr is
considered
| experimental and should not be relied upon for storage of anything
| particularly valuable.  But then the same is true of coLinux, I guess.

I had my company laptop setup once using e2compr to compress everything
on it (I have a 10GB harddrive with only 4.5GB available to Linux).  I
pretty much lost everything on it.  Major filesystem corruption occurred
after using it for a few months.  I can't remember the exact details,
but files started not being able to decompress, and I think some may
have ended up being deleted as well.  So, unless there has been some
major work done on e2compr in the past year or so, I probably would not
rely on it.

- --
Jason A. Pattie
pat...@xp...
Xperience, Inc. (http://www.xperienceinc.com)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFAyHXwuYsUrHkpYtARAsdlAJ9FJTGRv2sHorkjk7alU3BaMxSQ0wCeIToK
0qdQ/xXgDE0qehdOIPtna94=
=Qr3A
-----END PGP SIGNATURE-----


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

Re: [coLinux-users] Win2k and services.

[<ch...@to...>]

bridging does not work with wireless...
If by NAT you mean the crippled NAT called ICS that MS provides maby your
problem is two lans that are the same network. Lots of wireless routers
default to the 192.168.0.0/24 network and ICS also uses 192.168.0.0/24
this is the only option in win2k but I think it may be possible to change
it in XP after windows sets up ICS with the default. On 2k you must chang=
e
the default network on the wireless router. (It may be possible to use th=
e
routing and remote access service but I think you need tools from the 2k
server cd to configure it)

If this is not your problem or does not quite help please give some more
details.

chris

> Hello,
>
>        I've been unsuccessful in getting the network working with eithe=
r
> the bridge or nat methods. Am using the Debian image.
>
> I got a little further with NAT but I suspect my routes were incorrect
> because of my wireless router.
>
> My question is, is the "Routing and Remote Access" service needed under
> win2k ? I hope not because that enables netbios. I couldn't find any
> requirements list on the Wiki site.
>
> Thank you.
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: GNOME Foundation
> Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
> GNOME Users and Developers European Conference, 28-30th June in Norway
> http://2004/guadec.org
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

[coLinux-users] Win2k and services.

[mltd <ml...@ro...>]

Hello,

       I've been unsuccessful in getting the network working with either 
the bridge or nat methods. Am using the Debian image.

I got a little further with NAT but I suspect my routes were incorrect 
because of my wireless router.

My question is, is the "Routing and Remote Access" service needed under 
win2k ? I hope not because that enables netbios. I couldn't find any 
requirements list on the Wiki site.

Thank you.

[coLinux-users] Smaller filesystems (gratuitous e2compr plug)

[Paul W. <Pau...@in...>]

FYI, I have been able to compile a coLinux kernel with ext2 compression
support (http://e2compr.sf.net/), which when used in conjunction with a
sparse filesystem back-end created using mksparse
(http://www.acc.umu.se/~bosse/mksparse.zip) results in very significant
reductions in the on-disk footprint of the filesystem. You can smbmount a
region of the host filesystem, then on the host create an initial
zero-length file using mksparse, mke2fs it as large as you like (ignore
warnings), mount it via loopback, chattr +c the top level directory, and
then load it up with data.  You will see a bunch of scary-looking "IO error
syncing ext2 inode" errors, but AFAIK these are completely benign (I will
have to look into this further), and they go away if you remount the image
as a /dev/cobdN instead.  You definitely want to mount the filesystem image
via cobd in the long run, as performance of
e2compr-on-ext2-over-loop-over-smb is not good.

Note that you will need special e2compr-aware versions of ext2 tools
(e2fsck, chattr, etc) available from the e2compr.sf.net site.  Please note
also that, although it has been around for many years, e2compr is considered
experimental and should not be relied upon for storage of anything
particularly valuable.  But then the same is true of coLinux, I guess.

Taking this one step further I have created a prototype e2compr'd root FS
using my own embedded distro (http://diet-pc.sf.net) and have managed to get
root filesystem size as small as 3.5 Mb, and I'm not even trying hard
(DIET-PC is liberal for an embedded distro, using a real glibc 2.3.2 rather
than uclibc, etc - the "hard core" embedded distros are much smaller still).

Re: [coLinux-users] Colinux o.6.1 problem

[Robert C. <rw...@al...>]

On Wednesday, Jun 9, 2004, at 03:16 US/Central, ol...@ci... wrote:
> I have a problem. Colinux cannot start, when i try to start:

IIRC, you get that error when you don't have a filesystem image or when 
your defaults.colinux.xml file doesn't point to the right filesystem.

Regards,
- Robert

[coLinux-users] Colinux o.6.1 problem

[<ol...@ci...>]

Hello,

I have a problem. Colinux cannot start, when i try to start:

.....

daemon: module disconnected: conet0

Pipe broken, exiting

Console: Monitor0: Broken pipe



colinux: shutting down

daemon: daemon cleanup





I'm using windows 2000 SP4



Any idea?



Olavi Ivask

Re: [coLinux-users] Network dies after a while

[Blake <pb...@ta...>]

Oh, I forgot to answer your question about network stability.  I've put a
lot of network traffic through this scheme and haven't dropped connection.
I emerged a large number of things and rsynced a bunch of stuff to my
coLinux partitions ... about 6 GB worth.  It's held up well.

--Blake
pb...@ta...
----- Original Message ----- 
From: "Leeuw van der, Tim" <tim...@nl...>
To: "Blake" <pb...@ta...>
Cc: <col...@li...>
Sent: Tuesday, June 08, 2004 3:49 PM
Subject: Re: [coLinux-users] Network dies after a while


Ok, that might make WinXP bridging work, I'll give that a try... Guess it
wont work with WinPCAP then, too bad! :-)
Is promiscuous mode something that the driver remembers, or do you need to
set it every time you boot?

And if you do a lot of downloads from coLinux (like apt-get upgrade, or
emerge --update world), the network doesn't die after a while? B/c that's
what happens to me with the TAP driver.

I tried updating the TAP driver to the 8.0 from the just-released OpenVPN
2.0b4, but that doesn't work at all, so I'll have to downgrade.

greetings,

--Tim

-----Original Message-----
From: Blake [mailto:pb...@ta...]
Sent: dinsdag 8 juni 2004 21:14
To: Leeuw van der, Tim
Cc: col...@li...
Subject: Re: [coLinux-users] Network dies after a while


I'm not sure of the modes.  I use the TAP driver and use XP's "Network
Bridging" between the TAP device and my wireless card.  I had to set
promiscuous mode for the wireless nic for things to work consistently.

--Blake
pb...@ta...
----- Original Message ----- 
From: "Leeuw van der, Tim" <tim...@nl...>
To: "Blake" <pb...@ta...>
Cc: <col...@li...>
Sent: Tuesday, June 08, 2004 2:32 PM
Subject: RE: [coLinux-users] Network dies after a while


Hi,

I remember reading something about that on the Wiki, but forgot about it...
thanks for reminding me... If you don't mind me asking, was that trick
supposed to work with TAP, or with BRIDGE mode of coLinux networking?

greetings,

--Tim

-----Original Message-----
From: Blake [mailto:pb...@ta...]
Sent: dinsdag 8 juni 2004 18:30
To: Leeuw van der, Tim
Cc: col...@li...
Subject: Re: [coLinux-users] Network dies after a while


Did you do the "netsh bridge set" trick to set promiscuous mode for your
wireless NIC?  Reference:
http://www.microsoft.com/windowsxp/expertzone/columns/crawford/02april22.asp

--Blake
pb...@ta...
----- Original Message ----- 
From: "Leeuw van der, Tim" <tim...@nl...>
To: <col...@li...>
Sent: Tuesday, June 08, 2004 3:23 AM
Subject: [coLinux-users] Network dies after a while


Hi,

I got a basic coLinux/gentoo installation working without much trouble, but
networking is giving me headaches.

I'm using WindowsXP Pro SP1 with all latest updates, and coLinux 0.6.1 with
gentoo deluxe 2g. I also have a personal firewall installed: sygate 3.5
(corporate policy to have it running).

The only networking-option that seems to work for me at all, is using the
TAP driver and a proxy-server (I installed FreeProxy 3.72, which seems to
dislike the wget ftp client -- but that's another issue).

The Briding option in XP doesn't work for me, I have no clue why, but it
doesn't give me an IP address on the bridged driver and all my networking
dies.

Internet Connection Sharing? I'd rather not try, but I doubt it will make
any difference compared to the problems I currently have.

coLinux bridged networking doesn't work for me either, b/c my NICs are
wireless...

So I have to use the TAP driver with a proxy server.

I've configured the windows side with a static IP address of 10.10.10.1, and
the linux side with a static IP of 10.10.10.2. FreeProxy does HTTP proxying
on 8080, and SOCKS proxying on 1080.

Now my problem is: after some time, or perhaps rather after some amount of
traffic, the network dies. Not the connections that run over the TAP driver,
they seem to perhaps work, but all external networking dies. My web-browser
in windows no longer manages to load any page. No amount of
starting/stopping FreeProxy makes any difference.
But as soon as I stop coLinux, my networking is alive again.

When I restart coLinux I usually still have a working network, although it
seems not always. At which point I perhaps have to reboot...


Does anyone else have similar problems?


regards,

--Tim



-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users



-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users

Re: [coLinux-users] Network dies after a while

[Blake <pb...@ta...>]

Yeah, I had a bit of a hard time at first as well.  I'm not exactly sure why
it didn't work right off the bat and am pretty sure that my twiddling and
untwiddling settings didn't really help in getting things working (other
than the "netsh b" thing).

I don't use DHCP for the colinux instance, I use a static address.   With
this XP bridging scheme, XP hides the MAC of the TAP adapter behind my
wireless' MAC and so the outside world will only see the wireless' MAC ...
not good for DHCP or anything that relies on reverse arp (nothing that I can
think of).  It's the only drawback I can see with this scheme, I haven't
figured out how to get around this yet.  I'll probably end up just sending a
DHCP option from the coLinux client to the DHCP server and basing the DHCP
server's address assignment on this option.

--Blake
pb...@ta...
----- Original Message ----- 
From: "cgmelt" <cg...@xa...>
To: "Blake" <pb...@ta...>
Sent: Tuesday, June 08, 2004 4:02 PM
Subject: Re: [coLinux-users] Network dies after a while


>
> Hello,
> I'm so happy i found someone who did that,
> I am trying to setup bridge between my wrireless card and the TAP
> driver, and I just can't succeed.
> When I bridge between them, everything stops to work, seems like the
> "Bridge" has no access
> to the real network (DHCP doesn't work),
> maybe you can help?
> what should I do to fix this.
>
> thanks in advance ;)
>
> Blake wrote:
>
> >I'm not sure of the modes.  I use the TAP driver and use XP's "Network
> >Bridging" between the TAP device and my wireless card.  I had to set
> >promiscuous mode for the wireless nic for things to work consistently.
> >
> >--Blake
> >pb...@ta...
> >----- Original Message ----- 
> >From: "Leeuw van der, Tim" <tim...@nl...>
> >To: "Blake" <pb...@ta...>
> >Cc: <col...@li...>
> >Sent: Tuesday, June 08, 2004 2:32 PM
> >Subject: RE: [coLinux-users] Network dies after a while
> >
> >
> >Hi,
> >
> >I remember reading something about that on the Wiki, but forgot about
it...
> >thanks for reminding me... If you don't mind me asking, was that trick
> >supposed to work with TAP, or with BRIDGE mode of coLinux networking?
> >
> >greetings,
> >
> >--Tim
> >
> >-----Original Message-----
> >From: Blake [mailto:pb...@ta...]
> >Sent: dinsdag 8 juni 2004 18:30
> >To: Leeuw van der, Tim
> >Cc: col...@li...
> >Subject: Re: [coLinux-users] Network dies after a while
> >
> >
> >Did you do the "netsh bridge set" trick to set promiscuous mode for your
> >wireless NIC?  Reference:
>
>http://www.microsoft.com/windowsxp/expertzone/columns/crawford/02april22.as
p
> >
> >--Blake
> >pb...@ta...
> >----- Original Message ----- 
> >From: "Leeuw van der, Tim" <tim...@nl...>
> >To: <col...@li...>
> >Sent: Tuesday, June 08, 2004 3:23 AM
> >Subject: [coLinux-users] Network dies after a while
> >
> >
> >Hi,
> >
> >I got a basic coLinux/gentoo installation working without much trouble,
but
> >networking is giving me headaches.
> >
> >I'm using WindowsXP Pro SP1 with all latest updates, and coLinux 0.6.1
with
> >gentoo deluxe 2g. I also have a personal firewall installed: sygate 3.5
> >(corporate policy to have it running).
> >
> >The only networking-option that seems to work for me at all, is using the
> >TAP driver and a proxy-server (I installed FreeProxy 3.72, which seems to
> >dislike the wget ftp client -- but that's another issue).
> >
> >The Briding option in XP doesn't work for me, I have no clue why, but it
> >doesn't give me an IP address on the bridged driver and all my networking
> >dies.
> >
> >Internet Connection Sharing? I'd rather not try, but I doubt it will make
> >any difference compared to the problems I currently have.
> >
> >coLinux bridged networking doesn't work for me either, b/c my NICs are
> >wireless...
> >
> >So I have to use the TAP driver with a proxy server.
> >
> >I've configured the windows side with a static IP address of 10.10.10.1,
and
> >the linux side with a static IP of 10.10.10.2. FreeProxy does HTTP
proxying
> >on 8080, and SOCKS proxying on 1080.
> >
> >Now my problem is: after some time, or perhaps rather after some amount
of
> >traffic, the network dies. Not the connections that run over the TAP
driver,
> >they seem to perhaps work, but all external networking dies. My
web-browser
> >in windows no longer manages to load any page. No amount of
> >starting/stopping FreeProxy makes any difference.
> >But as soon as I stop coLinux, my networking is alive again.
> >
> >When I restart coLinux I usually still have a working network, although
it
> >seems not always. At which point I perhaps have to reboot...
> >
> >
> >Does anyone else have similar problems?
> >
> >
> >regards,
> >
> >--Tim
> >
> >
> >
> >-------------------------------------------------------
> >This SF.Net email is sponsored by: GNOME Foundation
> >Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
> >GNOME Users and Developers European Conference, 28-30th June in Norway
> >http://2004/guadec.org
> >_______________________________________________
> >coLinux-users mailing list
> >coL...@li...
> >https://lists.sourceforge.net/lists/listinfo/colinux-users
> >
> >
> >
> >-------------------------------------------------------
> >This SF.Net email is sponsored by: GNOME Foundation
> >Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
> >GNOME Users and Developers European Conference, 28-30th June in Norway
> >http://2004/guadec.org
> >_______________________________________________
> >coLinux-users mailing list
> >coL...@li...
> >https://lists.sourceforge.net/lists/listinfo/colinux-users
> >
> >
> >
> >
>

Re: [coLinux-users] Network dies after a while

[Blake <pb...@ta...>]

From what I take away from the article,  forcing compatibility mode on the
NIC should be done out of the box.  I don't know why you'd want to use pcap
for this since you can avoid it.  Why use something that runs at layer 3
(essentially) to do a layer 1 (or 2) job?  Not to mention that pcap wasn't
really created with windows in mind (no bpf).  Use the XP bridging ... it
works fine.  The "netsh b set" procedure only needs to be done once
apparently.  I just ran a "netsh b sh a" and it shows that my nic is still
in "ForceCompatibiltyMode" many boots after I originally set it.

--Blake
pb...@ta...
----- Original Message ----- 
From: "Leeuw van der, Tim" <tim...@nl...>
To: "Blake" <pb...@ta...>
Cc: <col...@li...>
Sent: Tuesday, June 08, 2004 3:49 PM
Subject: Re: [coLinux-users] Network dies after a while


Ok, that might make WinXP bridging work, I'll give that a try... Guess it
wont work with WinPCAP then, too bad! :-)
Is promiscuous mode something that the driver remembers, or do you need to
set it every time you boot?

And if you do a lot of downloads from coLinux (like apt-get upgrade, or
emerge --update world), the network doesn't die after a while? B/c that's
what happens to me with the TAP driver.

I tried updating the TAP driver to the 8.0 from the just-released OpenVPN
2.0b4, but that doesn't work at all, so I'll have to downgrade.

greetings,

--Tim

-----Original Message-----
From: Blake [mailto:pb...@ta...]
Sent: dinsdag 8 juni 2004 21:14
To: Leeuw van der, Tim
Cc: col...@li...
Subject: Re: [coLinux-users] Network dies after a while


I'm not sure of the modes.  I use the TAP driver and use XP's "Network
Bridging" between the TAP device and my wireless card.  I had to set
promiscuous mode for the wireless nic for things to work consistently.

--Blake
pb...@ta...
----- Original Message ----- 
From: "Leeuw van der, Tim" <tim...@nl...>
To: "Blake" <pb...@ta...>
Cc: <col...@li...>
Sent: Tuesday, June 08, 2004 2:32 PM
Subject: RE: [coLinux-users] Network dies after a while


Hi,

I remember reading something about that on the Wiki, but forgot about it...
thanks for reminding me... If you don't mind me asking, was that trick
supposed to work with TAP, or with BRIDGE mode of coLinux networking?

greetings,

--Tim

-----Original Message-----
From: Blake [mailto:pb...@ta...]
Sent: dinsdag 8 juni 2004 18:30
To: Leeuw van der, Tim
Cc: col...@li...
Subject: Re: [coLinux-users] Network dies after a while


Did you do the "netsh bridge set" trick to set promiscuous mode for your
wireless NIC?  Reference:
http://www.microsoft.com/windowsxp/expertzone/columns/crawford/02april22.asp

--Blake
pb...@ta...
----- Original Message ----- 
From: "Leeuw van der, Tim" <tim...@nl...>
To: <col...@li...>
Sent: Tuesday, June 08, 2004 3:23 AM
Subject: [coLinux-users] Network dies after a while


Hi,

I got a basic coLinux/gentoo installation working without much trouble, but
networking is giving me headaches.

I'm using WindowsXP Pro SP1 with all latest updates, and coLinux 0.6.1 with
gentoo deluxe 2g. I also have a personal firewall installed: sygate 3.5
(corporate policy to have it running).

The only networking-option that seems to work for me at all, is using the
TAP driver and a proxy-server (I installed FreeProxy 3.72, which seems to
dislike the wget ftp client -- but that's another issue).

The Briding option in XP doesn't work for me, I have no clue why, but it
doesn't give me an IP address on the bridged driver and all my networking
dies.

Internet Connection Sharing? I'd rather not try, but I doubt it will make
any difference compared to the problems I currently have.

coLinux bridged networking doesn't work for me either, b/c my NICs are
wireless...

So I have to use the TAP driver with a proxy server.

I've configured the windows side with a static IP address of 10.10.10.1, and
the linux side with a static IP of 10.10.10.2. FreeProxy does HTTP proxying
on 8080, and SOCKS proxying on 1080.

Now my problem is: after some time, or perhaps rather after some amount of
traffic, the network dies. Not the connections that run over the TAP driver,
they seem to perhaps work, but all external networking dies. My web-browser
in windows no longer manages to load any page. No amount of
starting/stopping FreeProxy makes any difference.
But as soon as I stop coLinux, my networking is alive again.

When I restart coLinux I usually still have a working network, although it
seems not always. At which point I perhaps have to reboot...


Does anyone else have similar problems?


regards,

--Tim



-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users

Re: [coLinux-users] Network dies after a while

[Leeuw v. d. T. <tim...@nl...>]

Ok, that might make WinXP bridging work, I'll give that a try... Guess =
it wont work with WinPCAP then, too bad! :-)
Is promiscuous mode something that the driver remembers, or do you need =
to set it every time you boot?

And if you do a lot of downloads from coLinux (like apt-get upgrade, or =
emerge --update world), the network doesn't die after a while? B/c =
that's what happens to me with the TAP driver.

I tried updating the TAP driver to the 8.0 from the just-released =
OpenVPN 2.0b4, but that doesn't work at all, so I'll have to downgrade.

greetings,

--Tim

-----Original Message-----
From: Blake [mailto:pb...@ta...]
Sent: dinsdag 8 juni 2004 21:14
To: Leeuw van der, Tim
Cc: col...@li...
Subject: Re: [coLinux-users] Network dies after a while


I'm not sure of the modes.  I use the TAP driver and use XP's "Network
Bridging" between the TAP device and my wireless card.  I had to set
promiscuous mode for the wireless nic for things to work consistently.

--Blake
pb...@ta...
----- Original Message -----=20
From: "Leeuw van der, Tim" <tim...@nl...>
To: "Blake" <pb...@ta...>
Cc: <col...@li...>
Sent: Tuesday, June 08, 2004 2:32 PM
Subject: RE: [coLinux-users] Network dies after a while


Hi,

I remember reading something about that on the Wiki, but forgot about =
it...
thanks for reminding me... If you don't mind me asking, was that trick
supposed to work with TAP, or with BRIDGE mode of coLinux networking?

greetings,

--Tim

-----Original Message-----
From: Blake [mailto:pb...@ta...]
Sent: dinsdag 8 juni 2004 18:30
To: Leeuw van der, Tim
Cc: col...@li...
Subject: Re: [coLinux-users] Network dies after a while


Did you do the "netsh bridge set" trick to set promiscuous mode for your
wireless NIC?  Reference:
http://www.microsoft.com/windowsxp/expertzone/columns/crawford/02april22.=
asp

--Blake
pb...@ta...
----- Original Message -----=20
From: "Leeuw van der, Tim" <tim...@nl...>
To: <col...@li...>
Sent: Tuesday, June 08, 2004 3:23 AM
Subject: [coLinux-users] Network dies after a while


Hi,

I got a basic coLinux/gentoo installation working without much trouble, =
but
networking is giving me headaches.

I'm using WindowsXP Pro SP1 with all latest updates, and coLinux 0.6.1 =
with
gentoo deluxe 2g. I also have a personal firewall installed: sygate 3.5
(corporate policy to have it running).

The only networking-option that seems to work for me at all, is using =
the
TAP driver and a proxy-server (I installed FreeProxy 3.72, which seems =
to
dislike the wget ftp client -- but that's another issue).

The Briding option in XP doesn't work for me, I have no clue why, but it
doesn't give me an IP address on the bridged driver and all my =
networking
dies.

Internet Connection Sharing? I'd rather not try, but I doubt it will =
make
any difference compared to the problems I currently have.

coLinux bridged networking doesn't work for me either, b/c my NICs are
wireless...

So I have to use the TAP driver with a proxy server.

I've configured the windows side with a static IP address of 10.10.10.1, =
and
the linux side with a static IP of 10.10.10.2. FreeProxy does HTTP =
proxying
on 8080, and SOCKS proxying on 1080.

Now my problem is: after some time, or perhaps rather after some amount =
of
traffic, the network dies. Not the connections that run over the TAP =
driver,
they seem to perhaps work, but all external networking dies. My =
web-browser
in windows no longer manages to load any page. No amount of
starting/stopping FreeProxy makes any difference.
But as soon as I stop coLinux, my networking is alive again.

When I restart coLinux I usually still have a working network, although =
it
seems not always. At which point I perhaps have to reboot...


Does anyone else have similar problems?


regards,

--Tim



-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users

Re: [coLinux-users] Network dies after a while

[Blake <pb...@ta...>]

I'm not sure of the modes.  I use the TAP driver and use XP's "Network
Bridging" between the TAP device and my wireless card.  I had to set
promiscuous mode for the wireless nic for things to work consistently.

--Blake
pb...@ta...
----- Original Message ----- 
From: "Leeuw van der, Tim" <tim...@nl...>
To: "Blake" <pb...@ta...>
Cc: <col...@li...>
Sent: Tuesday, June 08, 2004 2:32 PM
Subject: RE: [coLinux-users] Network dies after a while


Hi,

I remember reading something about that on the Wiki, but forgot about it...
thanks for reminding me... If you don't mind me asking, was that trick
supposed to work with TAP, or with BRIDGE mode of coLinux networking?

greetings,

--Tim

-----Original Message-----
From: Blake [mailto:pb...@ta...]
Sent: dinsdag 8 juni 2004 18:30
To: Leeuw van der, Tim
Cc: col...@li...
Subject: Re: [coLinux-users] Network dies after a while


Did you do the "netsh bridge set" trick to set promiscuous mode for your
wireless NIC?  Reference:
http://www.microsoft.com/windowsxp/expertzone/columns/crawford/02april22.asp

--Blake
pb...@ta...
----- Original Message ----- 
From: "Leeuw van der, Tim" <tim...@nl...>
To: <col...@li...>
Sent: Tuesday, June 08, 2004 3:23 AM
Subject: [coLinux-users] Network dies after a while


Hi,

I got a basic coLinux/gentoo installation working without much trouble, but
networking is giving me headaches.

I'm using WindowsXP Pro SP1 with all latest updates, and coLinux 0.6.1 with
gentoo deluxe 2g. I also have a personal firewall installed: sygate 3.5
(corporate policy to have it running).

The only networking-option that seems to work for me at all, is using the
TAP driver and a proxy-server (I installed FreeProxy 3.72, which seems to
dislike the wget ftp client -- but that's another issue).

The Briding option in XP doesn't work for me, I have no clue why, but it
doesn't give me an IP address on the bridged driver and all my networking
dies.

Internet Connection Sharing? I'd rather not try, but I doubt it will make
any difference compared to the problems I currently have.

coLinux bridged networking doesn't work for me either, b/c my NICs are
wireless...

So I have to use the TAP driver with a proxy server.

I've configured the windows side with a static IP address of 10.10.10.1, and
the linux side with a static IP of 10.10.10.2. FreeProxy does HTTP proxying
on 8080, and SOCKS proxying on 1080.

Now my problem is: after some time, or perhaps rather after some amount of
traffic, the network dies. Not the connections that run over the TAP driver,
they seem to perhaps work, but all external networking dies. My web-browser
in windows no longer manages to load any page. No amount of
starting/stopping FreeProxy makes any difference.
But as soon as I stop coLinux, my networking is alive again.

When I restart coLinux I usually still have a working network, although it
seems not always. At which point I perhaps have to reboot...


Does anyone else have similar problems?


regards,

--Tim



-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users

[coLinux-users] Time in coLinux

[Leeuw v. d. T. <tim...@nl...>]

Hi,

My coLinux has been up and running for a few hours now and I noticed =
something about time... My computer clock said 12:00, my coLinux said =
10:30 ! (rounding off a bit, the difference isn't exactly 1.30 hrs...)

The timezone wasn't set yet for coLinux; my real timezone is CET. Now I =
can't remember how the interaction between Windows and coLinux is with =
regards to time; if I set timezone to 'GMT' then the 'date' command in =
coLinux says 10:30 and if I set the timezone to 'CET' then 'date' tells =
me '12:30'.

So either the coLinux clock is 1.5hrs behind, or it's 0.5hrs ahead, I =
don't know, but I do know that it's not the right time!

WindowsOS: WinXP, SP1
coLinux: 0.6.1
LinuxOS: Gentoo (downloaded via installer)


regards,

--Tim

[coLinux-users] Network dies after a while

[Leeuw v. d. T. <tim...@nl...>]

Hi,

I got a basic coLinux/gentoo installation working without much trouble, =
but networking is giving me headaches.

I'm using WindowsXP Pro SP1 with all latest updates, and coLinux 0.6.1 =
with gentoo deluxe 2g. I also have a personal firewall installed: sygate =
3.5 (corporate policy to have it running).

The only networking-option that seems to work for me at all, is using =
the TAP driver and a proxy-server (I installed FreeProxy 3.72, which =
seems to dislike the wget ftp client -- but that's another issue).

The Briding option in XP doesn't work for me, I have no clue why, but it =
doesn't give me an IP address on the bridged driver and all my =
networking dies.

Internet Connection Sharing? I'd rather not try, but I doubt it will =
make any difference compared to the problems I currently have.

coLinux bridged networking doesn't work for me either, b/c my NICs are =
wireless...

So I have to use the TAP driver with a proxy server.

I've configured the windows side with a static IP address of 10.10.10.1, =
and the linux side with a static IP of 10.10.10.2. FreeProxy does HTTP =
proxying on 8080, and SOCKS proxying on 1080.

Now my problem is: after some time, or perhaps rather after some amount =
of traffic, the network dies. Not the connections that run over the TAP =
driver, they seem to perhaps work, but all external networking dies. My =
web-browser in windows no longer manages to load any page. No amount of =
starting/stopping FreeProxy makes any difference.
But as soon as I stop coLinux, my networking is alive again.

When I restart coLinux I usually still have a working network, although =
it seems not always. At which point I perhaps have to reboot...


Does anyone else have similar problems?


regards,

--Tim

Re: [coLinux-users] Colinux0-6-1 in windows2k

[David K. <da...@gi...>]

Yonghao Wang <yon...@ti...> wrote:
>
> It seems Matepad still convert my txt file into Unicode format. Or
> operating system does this (colinux comes same error)? And I tried
> using ultraeditor to have looked HEX code of file. Even when I was
> editing file it looks fine and save and open again it prepend and
> convert into 2byte code.
>
> Any suggestions will be appreciated

hi Yonghao,

even though you can't see the BOM charaters in MetaPad because it ignores
the binary, after you've saved the file with UltraEdit, they are there.

for me, to get it working i had to re-install coLinux just to get a "clean"
text xml file, then edit it only with MetaPad, and *never* let UltraEdit
touch it.  even if you remove the BOM characters with UltraEdit's hex mode,
UltraEdit replaces them when you save the file.

BTW: it is not necessary to email me off-list.  i monitor the lists i'm
subscribed to regularly, and will direct my replies back to the list so that
others can benefit from the discussion, and find these types of useful
discussions in the list archives, later.

-dave



> David Kaufman <da...@gi...> wrote:
>
> Dan Aloni <da...@co...> wrote:
>> On Fri, Jun 04, 2004 at 03:04:11PM +0100, Yonghao Wang wrote:
>>
>>> daemon: loading configuration from colinux.default.xml
>>>
>>> and it popup a windows error message:
>>>
>>> "The instruction at "0x0040af85" referenced memory at "0x00000000".
>>> The memory could not be "read".
>>
>> It appears the crash was inside mxml_string_getc. It is possible that
>> the mxml library crashed on an invalid XML. Please send it over.
>>
>
> i ran into this bug too.  the first text editor i tried to use to edit
> the coLinux config file was UltraEdit32.  this particular program
> feels that it's necessary to prepend a BOM (or Byte Order Mark) to the
> beginning of the file, just because it's "Unicode".  coLinux crashes
> if the xml file starts with a BOM - perhaps it should be renamed a
> BOMB :-)
>
> [...] Yonghao, if you need a text editor that doesn't screw up the
> colinux config file, check out MetaPad: http://liquidninja.com/metapad
>
> hope this helps!
>
> -dave

Re: [coLinux-users] coLinux - mesh with loop-based OS?

[<ch...@to...>]

topologilinux is a loopbased slackware compatable linux.
I wrote a howto to set topologilinux up to be able to boot both ways. see
http://www.colinux.org/wiki/index.php/TopoHowTo
This is an involved process to get it to boot both ways.

just to get it working under coLinux only, do a normal install create the
cobd's and edit fstab to use them and configure networking
appropriatly(this should be true of all loopbased distros)

In a little more than a week "topologilinux lite demo 5 beta-1" will be
released. ( I will anounce here) this version and then the upcomming full
version 5 will be setup to work out of the box with coLinux.

chris


> Can you make coLinux mesh/work with a linux distro
> like Slackware's Zipslack or DragonLinux? I have been
> trying, but I'm new to coLinux so I have yet to get it
> operational...
>
> ...Alan
>
>
>
> -------------------------------------------------------
> 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
>

RE: [coLinux-users] Colinux0-6-1 in windows2k

[Yonghao W. <yon...@ti...>]

Thank you very much, that's exactly what happens to me. I did with
Ultraeditor.=20

And should I also suggest patch current source code to tolerant this.

Thanks again.

-----Original Message-----
From: David Kaufman [mailto:da...@gi...]=20
Sent: 06 June 2004 06:02
To: Dan Aloni; Yonghao Wang
Cc: col...@li...
Subject: Re: [coLinux-users] Colinux0-6-1 in windows2k

Dan Aloni <da...@co...> wrote:
> On Fri, Jun 04, 2004 at 03:04:11PM +0100, Yonghao Wang wrote:
>
> > daemon: loading configuration from colinux.default.xml
> >
> > and it popup a windows error message:
> >
> > "The instruction at "0x0040af85" referenced memory at "0x00000000".
The
> > memory could not be "read".
>
> It appears the crash was inside mxml_string_getc. It is possible that
> the mxml library crashed on an invalid XML. Please send it over.
>
> --=20
> Dan Aloni
> da...@co...

hi Dan,

i ran into this bug too.  the first text editor i tried to use to edit
the coLinux config file was UltraEdit32.  this particular program feels
that it's necessary to prepend a BOM (or Byte Order Mark) to the
beginning of the file, just because it's "Unicode".  coLinux crashes if
the xml file starts with a BOM - perhaps it should be renamed a BOMB :-)

anyway i suppose colinux needs to be taught to tolerate this thing since
other editors do that as well -- apparently Notepad BOMbs xml files, too
(see
http://koti.mbnet.fi/akini/java/unicodereader/,
http://lists.xml.org/archives/xml-dev/200106/msg00389.html
and http://blogs.msdn.com/oldnewthing/archive/2004/03/24/95235.aspx).

it pisses me off that my editor did that, silently without telling me,
as it made my very first experience with coLinux a very frustrating one!
it was not until i opened the BOM-munged file in a real *text* editor
(rather than a wannabe Unicode editor) that i was warned that this
supposed text file now contained binary (high ASCII) characters, and
helped me avoid these nasty crashes.

and Yonghao, if you need a text editor that doesn't screw up the colinux
config file, check out MetaPad: http://liquidninja.com/metapad

hope this helps!

-dave

Re: [coLinux-devel] RE: [coLinux-users] Unable to connect to coLinux from same box

[Robert P. <rob...@ho...>]

Mike

Yup. Please put that in Wiki. That is all too important to miss.

Thanks.

Rob

----- Original Message ----- 
From: "Michael Laccetti" <mi...@s2...>
To: <col...@li...>;
<col...@li...>
Sent: Sunday, June 06, 2004 7:01 AM
Subject: [coLinux-devel] RE: [coLinux-users] Unable to connect to coLinux
from same box


> Well, my Intel Pro/1000 had separated the TCP/IP checksums into about six
> different options, but after fiddling with them, I got it to work.  Much
> thanks to Robert for his suggestion.  Time to put that in the Wiki?  :)
>
> -----Original Message-----
> From: col...@li...
> [mailto:col...@li...] On Behalf Of Vince
> Sent: June 6, 2004 4:41 AM
> To: 'Michael Laccetti'; col...@li...;
> col...@li...
> Subject: RE: [coLinux-users] Unable to connect to coLinux from same box
>
> Ok, after the email I just deleted (by mistake so I cant answer  to it,
> doh!) from someone suggesting Mike or I turn off the checksum in the
advance
> properties of the network card, it works.
> The actual setting was "Checksum Offload", which I had to rx/tx tcp/ip
> checksum And needed to be set to none.
>
> How about you Mike ?
>
> > -----Original Message-----
> > From: col...@li...
> > [mailto:col...@li...] On Behalf Of
> > Michael Laccetti
> > Sent: 06 June 2004 02:14
> > To: col...@li...;
> > col...@li...
> > Subject: Re: [coLinux-users] Unable to connect to coLinux from same
> > box
> >
> > Not quite that big of a newbie.  :)  As I said before, no firewall is
> > running on XP, there's a physically separate box doing all of that
> > stuff between the net and the local network.
> >
> > Vince, do you perchance have a MSI motherboard?  I have the same
> > Broadcom NIC as you do.
> >
> > -----Original Message-----
> > From: col...@li...
> > [mailto:col...@li...] On Behalf Of John
> > LeSueur
> > Sent: June 5, 2004 9:09 PM
> > To: Vince Hoffman
> > Cc: Michael Laccetti; col...@li...;
> > col...@li...
> > Subject: Re: [coLinux-devel] Re: [coLinux-users] Unable to connect to
> > coLinux from same box
> >
> > Try looking at your firewall settings, and remove any on your XP
> > installation.
> >
> > John
> >
> > Vince Hoffman wrote:
> >
> > >On Sat, 5 Jun 2004, Michael Laccetti wrote:
> > >
> > >
> > >
> > >>Hey guys, I've got a really weird issue.  When I have
> > coLinux running
> > >>on this machine (XP), I can't ping it from under XP, and I
> > can't ping
> > >>XP from under coLinux.  If I VNC to my dedicated Linux box, or my
> > >>Win2k3 server, I can SSH/VNC into the coLinux.  From coLinux, I can
> > >>see every other machine out there, just not the XP that
> > it's sitting
> > >>on.  This is all sorts of frustrating.  Anybody got any ideas as to
> > >>how I can make them see each other?
> > >>
> > >>
> > >
> > >Wish I did :(
> > >I have the dsame problem, I'm running the latest build from
> > >sourceforge, on windows XP sp1. I've tried both the winpcap
> > and the XP
> > >native bridging with no luck.
> > >
> > >some relevent (maybe ? ) data
> > >From daemon:
> > >
> > >Cooperative Linux Daemon, 0.6.1
> > >Compiled on Sat May 29 16:20:11 2004
> > >
> > >From config file:
> > >
> > > <network index="0" name="Broadcom NetXtreme Gigabit Ethernet"
> > >type="bridged"/>
> > >
> > >From startup:
> > >
> > >co_message_switch: setting callback rule for 6
> > >bridged-net-daemon: Checking adapter: Generic NdisWan adapter
> > >bridged-net-daemon: Checking adapter: MS Tunnel Interface Driver
> > >bridged-net-daemon: Checking adapter: Broadcom NetXtreme Gigabit
> > >Ethernet Driver  (Microsoft's Packet Scheduler)
> > >bridged-net-daemon: Listening on: Broadcom NetXtreme Gigabit
> > Ethernet
> > >Driver (Mi crosoft'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 established
> > >daemon: module connected: conet0
> > >co_message_switch: setting callback rule for 8
> > >
> > >More disturbingly a tcpdump of a ping between them (colinux=
> > 10.0.0.120
> > >windows= 10.0.0.10) ping gives:
> > >
> > >colinux root # ping 10.0.0.10
> > >PING 10.0.0.10 (10.0.0.10) 56(84) bytes of data.
> > >
> > >--- 10.0.0.10 ping statistics ---
> > >2 packets transmitted, 0 received, 100% packet loss, time 1015ms
> > >
> > >while tcpdump shows:
> > >
> > >listening on eth0, link-type EN10MB (Ethernet), capture size 68 bytes
> > >20:03:05.234086 IP 10.0.0.120 > 10.0.0.10: icmp 64: echo
> > request seq 1
> > >20:03:05.234811 IP 10.0.0.120.1034 > unsane.co.uk.domain:
> > >46843+[|domain]
> > >20:03:05.236848 IP 10.0.0.10 > 10.0.0.120: icmp 64: echo reply seq 1
> > >20:03:05.236878 IP unsane.co.uk.domain > 10.0.0.120.1034:  46843
> > >NXDomain*[|doma in]
> > >20:03:05.237063 IP 10.0.0.120.1034 > unsane.co.uk.domain:
> > >46844+[|domain] 20:03:05.238790 IP unsane.co.uk.domain >
> > >10.0.0.120.1034:  46844 NXDomain*[|doma in]
> > >20:03:05.238909 IP 10.0.0.120.1034 > unsane.co.uk.domain:
> > >46845+[|domain]
> > >20:03:05.240744 IP unsane.co.uk.domain > 10.0.0.120.1034:
> > >46845*[|domain]
> > >20:03:06.249358 IP 10.0.0.120 > 10.0.0.10: icmp 64: echo
> > request seq 2
> > >20:03:06.251320 IP 10.0.0.10 > 10.0.0.120: icmp 64: echo reply seq 2
> > >20:03:10.229086 arp who-has 10.0.0.10 tell 10.0.0.120
> > >20:03:10.229242 arp who-has unsane.co.uk tell 10.0.0.120
> > >20:03:10.231194 arp reply 10.0.0.10 is-at 00:0c:76:41:77:9f
> > >20:03:10.231695 arp reply unsane.co.uk is-at 00:50:8b:03:6d:00
> > >
> > >which if you cut out the DNS traffic, shoes ping request and replys.
> > >
> > >Any suggestions welcome, should i ask on the developers list ?
> > >
> > >Vince
> > > >
> > >
> > >
> > >>Mike
> > >>
> > >>
> > >>
> > >
> > >
> > >-------------------------------------------------------
> > >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-devel mailing list
> > >coL...@li...
> > >https://lists.sourceforge.net/lists/listinfo/colinux-devel
> > >
> > >
> >
> >
> >
> > -------------------------------------------------------
> > 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-devel mailing list
> > coL...@li...
> > https://lists.sourceforge.net/lists/listinfo/colinux-devel
> >
> >
> >
> > -------------------------------------------------------
> > 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
> >
>
>
>
> -------------------------------------------------------
> 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
>
>
>
> -------------------------------------------------------
> 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-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>

RE: [coLinux-users] Unable to connect to coLinux from same box

[Michael L. <mi...@s2...>]

Well, my Intel Pro/1000 had separated the TCP/IP checksums into about six
different options, but after fiddling with them, I got it to work.  Much
thanks to Robert for his suggestion.  Time to put that in the Wiki?  :) 

-----Original Message-----
From: col...@li...
[mailto:col...@li...] On Behalf Of Vince
Sent: June 6, 2004 4:41 AM
To: 'Michael Laccetti'; col...@li...;
col...@li...
Subject: RE: [coLinux-users] Unable to connect to coLinux from same box

Ok, after the email I just deleted (by mistake so I cant answer  to it,
doh!) from someone suggesting Mike or I turn off the checksum in the advance
properties of the network card, it works.
The actual setting was "Checksum Offload", which I had to rx/tx tcp/ip
checksum And needed to be set to none.

How about you Mike ? 

> -----Original Message-----
> From: col...@li...
> [mailto:col...@li...] On Behalf Of 
> Michael Laccetti
> Sent: 06 June 2004 02:14
> To: col...@li...;
> col...@li...
> Subject: Re: [coLinux-users] Unable to connect to coLinux from same 
> box
> 
> Not quite that big of a newbie.  :)  As I said before, no firewall is 
> running on XP, there's a physically separate box doing all of that 
> stuff between the net and the local network.
> 
> Vince, do you perchance have a MSI motherboard?  I have the same 
> Broadcom NIC as you do.
> 
> -----Original Message-----
> From: col...@li...
> [mailto:col...@li...] On Behalf Of John 
> LeSueur
> Sent: June 5, 2004 9:09 PM
> To: Vince Hoffman
> Cc: Michael Laccetti; col...@li...;
> col...@li...
> Subject: Re: [coLinux-devel] Re: [coLinux-users] Unable to connect to 
> coLinux from same box
> 
> Try looking at your firewall settings, and remove any on your XP 
> installation.
> 
> John
> 
> Vince Hoffman wrote:
> 
> >On Sat, 5 Jun 2004, Michael Laccetti wrote:
> >
> >  
> >
> >>Hey guys, I've got a really weird issue.  When I have
> coLinux running
> >>on this machine (XP), I can't ping it from under XP, and I
> can't ping
> >>XP from under coLinux.  If I VNC to my dedicated Linux box, or my
> >>Win2k3 server, I can SSH/VNC into the coLinux.  From coLinux, I can 
> >>see every other machine out there, just not the XP that
> it's sitting
> >>on.  This is all sorts of frustrating.  Anybody got any ideas as to 
> >>how I can make them see each other?
> >>    
> >>
> >
> >Wish I did :(
> >I have the dsame problem, I'm running the latest build from 
> >sourceforge, on windows XP sp1. I've tried both the winpcap
> and the XP
> >native bridging with no luck.
> >
> >some relevent (maybe ? ) data
> >From daemon:
> >
> >Cooperative Linux Daemon, 0.6.1
> >Compiled on Sat May 29 16:20:11 2004
> >
> >From config file:
> >
> >	<network index="0" name="Broadcom NetXtreme Gigabit Ethernet" 
> >type="bridged"/>
> >
> >From startup:
> >
> >co_message_switch: setting callback rule for 6
> >bridged-net-daemon: Checking adapter: Generic NdisWan adapter
> >bridged-net-daemon: Checking adapter: MS Tunnel Interface Driver
> >bridged-net-daemon: Checking adapter: Broadcom NetXtreme Gigabit 
> >Ethernet Driver  (Microsoft's Packet Scheduler)
> >bridged-net-daemon: Listening on: Broadcom NetXtreme Gigabit
> Ethernet
> >Driver (Mi crosoft'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 established
> >daemon: module connected: conet0
> >co_message_switch: setting callback rule for 8
> >
> >More disturbingly a tcpdump of a ping between them (colinux=
> 10.0.0.120
> >windows= 10.0.0.10) ping gives:
> >
> >colinux root # ping 10.0.0.10
> >PING 10.0.0.10 (10.0.0.10) 56(84) bytes of data.
> >
> >--- 10.0.0.10 ping statistics ---
> >2 packets transmitted, 0 received, 100% packet loss, time 1015ms
> >
> >while tcpdump shows:
> >
> >listening on eth0, link-type EN10MB (Ethernet), capture size 68 bytes
> >20:03:05.234086 IP 10.0.0.120 > 10.0.0.10: icmp 64: echo
> request seq 1
> >20:03:05.234811 IP 10.0.0.120.1034 > unsane.co.uk.domain:  
> >46843+[|domain]
> >20:03:05.236848 IP 10.0.0.10 > 10.0.0.120: icmp 64: echo reply seq 1
> >20:03:05.236878 IP unsane.co.uk.domain > 10.0.0.120.1034:  46843 
> >NXDomain*[|doma in]
> >20:03:05.237063 IP 10.0.0.120.1034 > unsane.co.uk.domain:  
> >46844+[|domain] 20:03:05.238790 IP unsane.co.uk.domain >
> >10.0.0.120.1034:  46844 NXDomain*[|doma in]
> >20:03:05.238909 IP 10.0.0.120.1034 > unsane.co.uk.domain:  
> >46845+[|domain]
> >20:03:05.240744 IP unsane.co.uk.domain > 10.0.0.120.1034:  
> >46845*[|domain]
> >20:03:06.249358 IP 10.0.0.120 > 10.0.0.10: icmp 64: echo
> request seq 2
> >20:03:06.251320 IP 10.0.0.10 > 10.0.0.120: icmp 64: echo reply seq 2
> >20:03:10.229086 arp who-has 10.0.0.10 tell 10.0.0.120
> >20:03:10.229242 arp who-has unsane.co.uk tell 10.0.0.120
> >20:03:10.231194 arp reply 10.0.0.10 is-at 00:0c:76:41:77:9f
> >20:03:10.231695 arp reply unsane.co.uk is-at 00:50:8b:03:6d:00
> >
> >which if you cut out the DNS traffic, shoes ping request and replys.
> >
> >Any suggestions welcome, should i ask on the developers list ?
> >
> >Vince
> > >
> >  
> >
> >>Mike
> >>
> >>    
> >>
> >
> >
> >-------------------------------------------------------
> >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-devel mailing list
> >coL...@li...
> >https://lists.sourceforge.net/lists/listinfo/colinux-devel
> >  
> >
> 
> 
> 
> -------------------------------------------------------
> 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-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
> 
> 
> 
> -------------------------------------------------------
> 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
> 



-------------------------------------------------------
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

[coLinux-users] New Debian image

[Dan A. <da...@co...>]

Hello All,

I took the time to upload a new and improved Debian root file system 
image. This is also aimed for developers - read on.

    http://prdownloads.sourceforge.net/colinux/Debian-20040605.ext3.1610mb.bz2?download

This image takes about 58MB compressed.   

A summary of changes against the old image:

 * Extracts to 1610MB.
 * All packages are updated to Debian-unstable of June 5, 2004.
 * Some fixes under /etc.
 * A few extra networking packages were installed, including ssh and 
   a local nameserver (no need to set up resolv.conf).
 * Under /usr/local/mingw32 I've added the full mingw32 toolchain required
   to compile the coLinux binaries. I can distribute this as a binary package
   on request - it takes about 15MB.

Have fun,
 
-- 
Dan Aloni
da...@co...

RE: [coLinux-users] Unable to connect to coLinux from same box

[Vince <vi...@un...>]

Ok, after the email I just deleted (by mistake so I cant answer
 to it, doh!) from someone suggesting Mike or I turn off the 
checksum in the advance properties of the network card, it works.
The actual setting was "Checksum Offload", which I had to rx/tx tcp/ip
checksum
And needed to be set to none.

How about you Mike ? 

> -----Original Message-----
> From: col...@li... 
> [mailto:col...@li...] On Behalf 
> Of Michael Laccetti
> Sent: 06 June 2004 02:14
> To: col...@li...; 
> col...@li...
> Subject: Re: [coLinux-users] Unable to connect to coLinux 
> from same box
> 
> Not quite that big of a newbie.  :)  As I said before, no 
> firewall is running on XP, there's a physically separate box 
> doing all of that stuff between the net and the local network.
> 
> Vince, do you perchance have a MSI motherboard?  I have the 
> same Broadcom NIC as you do.
> 
> -----Original Message-----
> From: col...@li...
> [mailto:col...@li...] On Behalf 
> Of John LeSueur
> Sent: June 5, 2004 9:09 PM
> To: Vince Hoffman
> Cc: Michael Laccetti; col...@li...;
> col...@li...
> Subject: Re: [coLinux-devel] Re: [coLinux-users] Unable to 
> connect to coLinux from same box
> 
> Try looking at your firewall settings, and remove any on your 
> XP installation.
> 
> John
> 
> Vince Hoffman wrote:
> 
> >On Sat, 5 Jun 2004, Michael Laccetti wrote:
> >
> >  
> >
> >>Hey guys, I've got a really weird issue.  When I have 
> coLinux running 
> >>on this machine (XP), I can't ping it from under XP, and I 
> can't ping 
> >>XP from under coLinux.  If I VNC to my dedicated Linux box, or my
> >>Win2k3 server, I can SSH/VNC into the coLinux.  From coLinux, I can 
> >>see every other machine out there, just not the XP that 
> it's sitting 
> >>on.  This is all sorts of frustrating.  Anybody got any ideas as to 
> >>how I can make them see each other?
> >>    
> >>
> >
> >Wish I did :(
> >I have the dsame problem, I'm running the latest build from 
> >sourceforge, on windows XP sp1. I've tried both the winpcap 
> and the XP 
> >native bridging with no luck.
> >
> >some relevent (maybe ? ) data
> >From daemon:
> >
> >Cooperative Linux Daemon, 0.6.1
> >Compiled on Sat May 29 16:20:11 2004
> >
> >From config file:
> >
> >	<network index="0" name="Broadcom NetXtreme Gigabit Ethernet" 
> >type="bridged"/>
> >
> >From startup:
> >
> >co_message_switch: setting callback rule for 6
> >bridged-net-daemon: Checking adapter: Generic NdisWan adapter
> >bridged-net-daemon: Checking adapter: MS Tunnel Interface Driver
> >bridged-net-daemon: Checking adapter: Broadcom NetXtreme Gigabit 
> >Ethernet Driver  (Microsoft's Packet Scheduler)
> >bridged-net-daemon: Listening on: Broadcom NetXtreme Gigabit 
> Ethernet 
> >Driver (Mi crosoft'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 established
> >daemon: module connected: conet0
> >co_message_switch: setting callback rule for 8
> >
> >More disturbingly a tcpdump of a ping between them (colinux= 
> 10.0.0.120 
> >windows= 10.0.0.10) ping gives:
> >
> >colinux root # ping 10.0.0.10
> >PING 10.0.0.10 (10.0.0.10) 56(84) bytes of data.
> >
> >--- 10.0.0.10 ping statistics ---
> >2 packets transmitted, 0 received, 100% packet loss, time 1015ms
> >
> >while tcpdump shows:
> >
> >listening on eth0, link-type EN10MB (Ethernet), capture size 68 bytes
> >20:03:05.234086 IP 10.0.0.120 > 10.0.0.10: icmp 64: echo 
> request seq 1
> >20:03:05.234811 IP 10.0.0.120.1034 > unsane.co.uk.domain:  
> >46843+[|domain]
> >20:03:05.236848 IP 10.0.0.10 > 10.0.0.120: icmp 64: echo reply seq 1
> >20:03:05.236878 IP unsane.co.uk.domain > 10.0.0.120.1034:  46843 
> >NXDomain*[|doma in]
> >20:03:05.237063 IP 10.0.0.120.1034 > unsane.co.uk.domain:  
> >46844+[|domain] 20:03:05.238790 IP unsane.co.uk.domain >
> >10.0.0.120.1034:  46844 NXDomain*[|doma in]
> >20:03:05.238909 IP 10.0.0.120.1034 > unsane.co.uk.domain:  
> >46845+[|domain]
> >20:03:05.240744 IP unsane.co.uk.domain > 10.0.0.120.1034:  
> >46845*[|domain]
> >20:03:06.249358 IP 10.0.0.120 > 10.0.0.10: icmp 64: echo 
> request seq 2 
> >20:03:06.251320 IP 10.0.0.10 > 10.0.0.120: icmp 64: echo reply seq 2
> >20:03:10.229086 arp who-has 10.0.0.10 tell 10.0.0.120
> >20:03:10.229242 arp who-has unsane.co.uk tell 10.0.0.120
> >20:03:10.231194 arp reply 10.0.0.10 is-at 00:0c:76:41:77:9f
> >20:03:10.231695 arp reply unsane.co.uk is-at 00:50:8b:03:6d:00
> >
> >which if you cut out the DNS traffic, shoes ping request and replys.
> >
> >Any suggestions welcome, should i ask on the developers list ?
> >
> >Vince
> > >
> >  
> >
> >>Mike
> >>
> >>    
> >>
> >
> >
> >-------------------------------------------------------
> >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-devel mailing list
> >coL...@li...
> >https://lists.sourceforge.net/lists/listinfo/colinux-devel
> >  
> >
> 
> 
> 
> -------------------------------------------------------
> 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-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
> 
> 
> 
> -------------------------------------------------------
> 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
> 

[coLinux-users] coLinux - mesh with loop-based OS?

[Alan B. <Nig...@ne...>]

Can you make coLinux mesh/work with a linux distro
like Slackware's Zipslack or DragonLinux? I have been
trying, but I'm new to coLinux so I have yet to get it
operational...

...Alan

RE: [coLinux-users] Unable to connect to coLinux from same box

[Vince <vi...@un...>]

 

> -----Original Message-----
> From: col...@li... 
> [mailto:col...@li...] On Behalf 
> Of Michael Laccetti
> Sent: 06 June 2004 02:14
> To: col...@li...; 
> col...@li...
> Subject: Re: [coLinux-users] Unable to connect to coLinux 
> from same box
> 
> Not quite that big of a newbie.  :)  As I said before, no 
> firewall is running on XP, there's a physically separate box 
> doing all of that stuff between the net and the local network.
> 
> Vince, do you perchance have a MSI motherboard?  I have the 
> same Broadcom NIC as you do.
> 

I do, MSI KT6delta. The only firewall I have is a separate freebsd box.

> -----Original Message-----
> From: col...@li...
> [mailto:col...@li...] On Behalf 
> Of John LeSueur
> Sent: June 5, 2004 9:09 PM
> To: Vince Hoffman
> Cc: Michael Laccetti; col...@li...;
> col...@li...
> Subject: Re: [coLinux-devel] Re: [coLinux-users] Unable to 
> connect to coLinux from same box
> 
> Try looking at your firewall settings, and remove any on your 
> XP installation.
> 
> John
> 
> Vince Hoffman wrote:
> 
> >On Sat, 5 Jun 2004, Michael Laccetti wrote:
> >
> >  
> >
> >>Hey guys, I've got a really weird issue.  When I have 
> coLinux running 
> >>on this machine (XP), I can't ping it from under XP, and I 
> can't ping 
> >>XP from under coLinux.  If I VNC to my dedicated Linux box, or my
> >>Win2k3 server, I can SSH/VNC into the coLinux.  From coLinux, I can 
> >>see every other machine out there, just not the XP that 
> it's sitting 
> >>on.  This is all sorts of frustrating.  Anybody got any ideas as to 
> >>how I can make them see each other?
> >>    
> >>
> >
> >Wish I did :(
> >I have the dsame problem, I'm running the latest build from 
> >sourceforge, on windows XP sp1. I've tried both the winpcap 
> and the XP 
> >native bridging with no luck.
> >
> >some relevent (maybe ? ) data
> >From daemon:
> >
> >Cooperative Linux Daemon, 0.6.1
> >Compiled on Sat May 29 16:20:11 2004
> >
> >From config file:
> >
> >	<network index="0" name="Broadcom NetXtreme Gigabit Ethernet" 
> >type="bridged"/>
> >
> >From startup:
> >
> >co_message_switch: setting callback rule for 6
> >bridged-net-daemon: Checking adapter: Generic NdisWan adapter
> >bridged-net-daemon: Checking adapter: MS Tunnel Interface Driver
> >bridged-net-daemon: Checking adapter: Broadcom NetXtreme Gigabit 
> >Ethernet Driver  (Microsoft's Packet Scheduler)
> >bridged-net-daemon: Listening on: Broadcom NetXtreme Gigabit 
> Ethernet 
> >Driver (Mi crosoft'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 established
> >daemon: module connected: conet0
> >co_message_switch: setting callback rule for 8
> >
> >More disturbingly a tcpdump of a ping between them (colinux= 
> 10.0.0.120 
> >windows= 10.0.0.10) ping gives:
> >
> >colinux root # ping 10.0.0.10
> >PING 10.0.0.10 (10.0.0.10) 56(84) bytes of data.
> >
> >--- 10.0.0.10 ping statistics ---
> >2 packets transmitted, 0 received, 100% packet loss, time 1015ms
> >
> >while tcpdump shows:
> >
> >listening on eth0, link-type EN10MB (Ethernet), capture size 68 bytes
> >20:03:05.234086 IP 10.0.0.120 > 10.0.0.10: icmp 64: echo 
> request seq 1
> >20:03:05.234811 IP 10.0.0.120.1034 > unsane.co.uk.domain:  
> >46843+[|domain]
> >20:03:05.236848 IP 10.0.0.10 > 10.0.0.120: icmp 64: echo reply seq 1
> >20:03:05.236878 IP unsane.co.uk.domain > 10.0.0.120.1034:  46843 
> >NXDomain*[|doma in]
> >20:03:05.237063 IP 10.0.0.120.1034 > unsane.co.uk.domain:  
> >46844+[|domain] 20:03:05.238790 IP unsane.co.uk.domain >
> >10.0.0.120.1034:  46844 NXDomain*[|doma in]
> >20:03:05.238909 IP 10.0.0.120.1034 > unsane.co.uk.domain:  
> >46845+[|domain]
> >20:03:05.240744 IP unsane.co.uk.domain > 10.0.0.120.1034:  
> >46845*[|domain]
> >20:03:06.249358 IP 10.0.0.120 > 10.0.0.10: icmp 64: echo 
> request seq 2 
> >20:03:06.251320 IP 10.0.0.10 > 10.0.0.120: icmp 64: echo reply seq 2
> >20:03:10.229086 arp who-has 10.0.0.10 tell 10.0.0.120
> >20:03:10.229242 arp who-has unsane.co.uk tell 10.0.0.120
> >20:03:10.231194 arp reply 10.0.0.10 is-at 00:0c:76:41:77:9f
> >20:03:10.231695 arp reply unsane.co.uk is-at 00:50:8b:03:6d:00
> >
> >which if you cut out the DNS traffic, shoes ping request and replys.
> >
> >Any suggestions welcome, should i ask on the developers list ?
> >
> >Vince
> > >
> >  
> >
> >>Mike
> >>
> >>    
> >>
> >
> >
> >-------------------------------------------------------
> >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-devel mailing list
> >coL...@li...
> >https://lists.sourceforge.net/lists/listinfo/colinux-devel
> >  
> >
> 
> 
> 
> -------------------------------------------------------
> 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-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
> 
> 
> 
> -------------------------------------------------------
> 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
>