Menu
▾
▴
colinux-users — coLinux users mailing list
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(100) |
Jun
(134) |
Jul
(149) |
Aug
(123) |
Sep
(185) |
Oct
(122) |
Nov
(59) |
Dec
(127) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(128) |
Feb
(233) |
Mar
(210) |
Apr
(196) |
May
(85) |
Jun
(96) |
Jul
(76) |
Aug
(149) |
Sep
(65) |
Oct
(78) |
Nov
(121) |
Dec
(82) |
| 2006 |
Jan
(249) |
Feb
(181) |
Mar
(176) |
Apr
(156) |
May
(128) |
Jun
(102) |
Jul
(157) |
Aug
(80) |
Sep
(42) |
Oct
(49) |
Nov
(36) |
Dec
(42) |
| 2007 |
Jan
(64) |
Feb
(38) |
Mar
(45) |
Apr
(74) |
May
(26) |
Jun
(20) |
Jul
(17) |
Aug
(12) |
Sep
(40) |
Oct
(7) |
Nov
(14) |
Dec
(16) |
| 2008 |
Jan
(52) |
Feb
(49) |
Mar
(90) |
Apr
(80) |
May
(78) |
Jun
(82) |
Jul
(25) |
Aug
(8) |
Sep
(10) |
Oct
(11) |
Nov
(3) |
Dec
(17) |
| 2009 |
Jan
(12) |
Feb
(16) |
Mar
(20) |
Apr
(14) |
May
(17) |
Jun
(10) |
Jul
(13) |
Aug
(12) |
Sep
(21) |
Oct
(10) |
Nov
(30) |
Dec
(1) |
| 2010 |
Jan
(2) |
Feb
(7) |
Mar
(22) |
Apr
(6) |
May
(33) |
Jun
(5) |
Jul
(4) |
Aug
(38) |
Sep
(46) |
Oct
(23) |
Nov
(9) |
Dec
(5) |
| 2011 |
Jan
(21) |
Feb
(27) |
Mar
(1) |
Apr
(18) |
May
(12) |
Jun
(12) |
Jul
(10) |
Aug
(30) |
Sep
(4) |
Oct
|
Nov
(9) |
Dec
(19) |
| 2012 |
Jan
(26) |
Feb
(6) |
Mar
(8) |
Apr
(7) |
May
(3) |
Jun
|
Jul
(10) |
Aug
(1) |
Sep
(18) |
Oct
(5) |
Nov
|
Dec
(1) |
| 2013 |
Jan
(27) |
Feb
|
Mar
(11) |
Apr
(14) |
May
|
Jun
(1) |
Jul
|
Aug
(7) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
(25) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(2) |
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Blade <Bl...@ta...> - 2004-06-22 21:22:04
|
Hello, How to install links web browser, ftp client, irc client etc.? Do I need = to install networking package or smth else? Thanx in advance. |
|
From: Andreas <ge...@gm...> - 2004-06-21 22:14:42
|
hi, i'm using colinux 0.6.1 with bridged networking on a w2k host. when pinging colinux from a remote machine, i got the following, confusing timings: (behold the monotonous growing and then jumping back latency) 64 bytes from 172.17.0.2: icmp_seq=3 ttl=64 time=0.9 ms 64 bytes from 172.17.0.2: icmp_seq=4 ttl=64 time=2.3 ms 64 bytes from 172.17.0.2: icmp_seq=5 ttl=64 time=3.7 ms 64 bytes from 172.17.0.2: icmp_seq=6 ttl=64 time=5.2 ms 64 bytes from 172.17.0.2: icmp_seq=7 ttl=64 time=6.6 ms 64 bytes from 172.17.0.2: icmp_seq=8 ttl=64 time=7.9 ms 64 bytes from 172.17.0.2: icmp_seq=9 ttl=64 time=9.4 ms 64 bytes from 172.17.0.2: icmp_seq=10 ttl=64 time=0.7 ms 64 bytes from 172.17.0.2: icmp_seq=11 ttl=64 time=2.0 ms 64 bytes from 172.17.0.2: icmp_seq=12 ttl=64 time=3.6 ms 64 bytes from 172.17.0.2: icmp_seq=13 ttl=64 time=4.9 ms 64 bytes from 172.17.0.2: icmp_seq=14 ttl=64 time=6.4 ms 64 bytes from 172.17.0.2: icmp_seq=15 ttl=64 time=7.7 ms 64 bytes from 172.17.0.2: icmp_seq=16 ttl=64 time=9.2 ms 64 bytes from 172.17.0.2: icmp_seq=17 ttl=64 time=0.6 ms 64 bytes from 172.17.0.2: icmp_seq=18 ttl=64 time=1.9 ms 64 bytes from 172.17.0.2: icmp_seq=19 ttl=64 time=3.4 ms 64 bytes from 172.17.0.2: icmp_seq=20 ttl=64 time=4.7 ms 64 bytes from 172.17.0.2: icmp_seq=21 ttl=64 time=6.2 ms 64 bytes from 172.17.0.2: icmp_seq=22 ttl=64 time=7.6 ms 64 bytes from 172.17.0.2: icmp_seq=23 ttl=64 time=9.1 ms and so on... any clue, what might cause this strange behavior? regards, andreas |
|
From: <ft...@cs...> - 2004-06-21 19:14:20
|
Hi, Guys, I found this very nice project a few days ago and tried it on my XP box. Everythin seems OK, however, somethings look strange when colinux startup in the XP windows, the following is the output of the startup screen even I recompiled the kernel to add the required modules. Could you tell me what the problem is? Have a nice day Fengtian Jun 13 21:14:31 colinux modprobe: modprobe: Can't locate module char-major-14 Jun 13 21:21:42 colinux init: Switching to runlevel: 0 Jun 13 21:21:48 colinux modprobe: modprobe: Can't locate module char-major-10- 135 Jun 13 21:23:25 colinux modprobe: modprobe: Can't locate module char-major-14 Jun 13 21:24:50 colinux init: Switching to runlevel: 0 .... .... Jun 13 21:24:56 colinux modprobe: modprobe: Can't locate module char-major-10- 13 Jun 13 18:21:20 colinux modprobe: modprobe: Can't locate module char-major-14 Jun 13 19:54:42 colinux modprobe: modprobe: Can't locate module net-pf-11 Jun 13 19:54:42 colinux modprobe: modprobe: Can't locate module net-pf-4 Jun 13 19:54:42 colinux modprobe: modprobe: Can't locate module net-pf-5 Jun 13 19:54:42 colinux modprobe: modprobe: Can't locate module net-pf-18 ........ ........ Jun 16 04:24:29 colinux modprobe: modprobe: Can't locate module nls_cp437 Jun 16 04:24:29 colinux modprobe: modprobe: Can't locate module nls_iso8859-1 Jun 16 04:24:29 colinux last message repeated 2 times Jun 16 04:40:55 colinux modprobe: modprobe: Can't locate module nls_cp437 Jun 16 04:40:55 colinux modprobe: modprobe: Can't locate module nls_iso8859-1 Jun 16 04:40:55 colinux last message repeated 2 times Jun 16 05:56:34 colinux modprobe: modprobe: Can't locate module nls_cp437 Jun 16 05:56:34 colinux modprobe: modprobe: Can't locate module nls_iso8859-1 Jun 16 05:56:34 colinux last message repeated 2 times Jun 16 06:07:47 colinux modprobe: modprobe: Can't locate module nls_cp437 Jun 16 06:07:47 colinux modprobe: modprobe: Can't locate module nls_iso8859-1 Jun 16 06:07:48 colinux last message repeated 2 times |
|
From: Dan A. <da...@co...> - 2004-06-19 22:44:54
|
Hello,
After a few checks, it seems that an elusive init_ISA_irqs() call was
causing problems.
I wonder why it didn't crash my Linux 2.6.x or Windows 2000 boxes. I guess
these two are more 'similar' to this Linux kernel version when it comes
initializing the interrupt controller.
Anyway, here's an new snapshot:
http://www.colinux.org/snapshots/coLinux-20040620.exe
http://www.colinux.org/snapshots/colinux-20040620.tar.gz
BTW, I've also started uploading the Monotone [1] log of the tree, it's
available at:
http://www.colinux.org/snapshots/ChangeLog
* [1] We have started using Monotone (http://www.venge.net/monotone/) as
our source control system.
--
Dan Aloni
da...@co...
|
|
From: Dan A. <da...@co...> - 2004-06-19 13:37:14
|
Hello, New snapshot: http://www.colinux.org/snapshots/coLinux-20040619.exe http://www.colinux.org/snapshots/colinux-20040619.tar.gz The big news - we have managed to port the coLinux patch to the Linux 2.6.7 tree. There might be some bugs and quirks but fixing problems in that tree is easier than doing so in the old 2.4.x tree. More lengthy summary of changes: * Linux patch ported to Linux 2.6.7. Linux 2.4.x will not be officially supported anymore. (Dan Aloni and George Boutwell) * initrd support was added (teesoft2004 at yahoo.com.cn). To activate it you can specify e.g. <initrd path="..." /> in the configuration * Changed PCAP handling to use Connection Name instead of Adapter/Device/Driver name. Name is +now uniform between PCAP & TAP and multiple devices of the same/make/model should be able to be connected to. (George Boutwell) NOTE: This *requires* you to update your configuration. * Support AltGr for both FLTK & NT consoles. (Sascha Kettler) The 2.6.x port will make it easier adding the long awaited frame buffer support, as the FB kernel interfaces are more well-formed in that tree. I've also updated the Linux port of coLinux, and managed to run Linux 2.6.7 on Linux 2.6.7. -- Dan Aloni da...@co... |
|
From: C. R. O. <cr...@nc...> - 2004-06-16 17:37:30
|
Blake wrote: > The second way. =20 > <network index=3D"0" type=3D"tap" name=3D"tap"></network> Thanks. OK, I've confirmed that I can bridge my physical enet adapter and the coLinux adapter together and my coLinux install has a working network (at least on my work machine--haven't tried at home yet) and it doesn't seem to conflict with the SecuRemote VPN we have installed here. I have noticed that I can't seem to connect over the VPN from coLinux, but I can do without that. I did have to reboot before anything would work. I think that's because SecuRemote looks at all the network adapters and binds itself to the "right" ones at boot time. I'm guessing that since this is a Windows "native" solution that it will perform better than the coLinux bridge or NAT solution. The coLinux bridge did perform really well, though. --cro |
|
From: C. R. O. <cr...@nc...> - 2004-06-16 15:11:42
|
Greetings, I'm attempting to setup coLinux (0.6.1) with bridged networking. I get an IP address fine, and I can ping sites inside my local net as well as on the general Internet, but after a little bit of network traffic in the console I start to see a messages to the effect of 'packet: tx pcap FAILED'. This is Windows XP Pro. I made sure that 802.1x authentication is turned off for all my adapters. I want bridging because I need to expose several services in the coLinux instance to the Internet. =20 I have no software firewall installed. I do have SonicWall's VPN client installed (version 8), but it makes no difference if the client is enabled or disabled. I haven't tried using native network bridge support in windows XP as discussed at the bottom of http://www.colinux.org/wiki/index.php/coLinuxNetworking. Does this work for anyone? And if I use it, do I specify it in the config.xml file like a TAP or a bridge? <network index=3D"0" name=3D"NDIS 5.0 driver" = type=3D"bridged"></network> Or <network index=3D"0" name=3D"whatever" type=3D"TAP"></network> --=20 C. R. Oldham Director of Technology NCA CASI=20 |
|
From: <ib...@ge...> - 2004-06-16 14:02:23
|
Usually this requires - sharing internet access from your 'home' windows machine. I also had set the IP Forwarding flag in the windows registry long before I discovered/installed colinux, though I am not sure this is required at all - setup some routing scheme in the colinux to allow it to see at least until your proxy or the machine that connects to the rest of the world. You should be able to ping these machines or at least do something like ssh, in any case to access them. For routing you need to use the route command. - if you are behind a corporate proxy, then in a colinux shell define the variable http_proxy to point to the proxy/port : e.g. export http_proxy=http://xxx.xxx.xxx.xxx:port where xxx.xxx.xxx.xxx is the now visible IP address of the proxy machine by now you ought to be ready for apt-get. Check that your /etc/apt/sources.list points to where/what you would like to get ... Works ok for me. I get some small problems of 'bad header' messages from time to time and I need to restart the apt-get process, but I am not sure this is related to colinux Hope this helps ---- Ilias Biris, Ph.D. ASR, Senior Researcher Genius Instituto de Tecnologia TEL: +55 (0)92 6146503 FAX: +55 (0)92 6133144 http://www.genius.org.br/ Petar Tomic <pto...@ya...> Sent by: col...@li... 16/06/2004 09:41 Please respond to ptomic To: col...@li... cc: Subject: RE: [coLinux-users] Network ?? I was succesful. I can pingmy virtual gateway (192.168.0.1) and my public adress, from coLinux. New question is how to setup coLinux to do apt-get from internet. I use Debian-3.0r0.ext3.1gb in coLinux. ------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users ************************************************************************************************** O conteúdo desse e-mail ou de seus anexos são confidenciais e restritos ao destinatário da mensagem. Se você recebeu esse e-mail por engano, por favor notifique o remetente imediatamente e não faça cópias ou distribua seu conteúdo para ninguém. ************************************************************************************************** The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email in error please notify the system manager or the sender immediately and do not disclose the contents to anyone or make copies. ************************************************************************************************** |
|
From: <ch...@to...> - 2004-06-16 13:58:48
|
Probably just a matter of sharing the real interface on windows. Then using it as you normally would. I'm not a debian user so I have not tried it. If that does not work start a new thread. chris > I was succesful. I can pingmy virtual gateway > (192.168.0.1) and my public adress, from coLinux. > New question is how to setup coLinux to do apt-get > from internet. I use Debian-3.0r0.ext3.1gb in coLinux. > > --- "Leeuw van der, Tim" > <tim...@nl...> wrote: >> Hi, >> >> For reasons unknown to me but perhaps a firewall, >> ping doesn't work for me at all. But do basic things >> like telnet / wget work? (I don't know which >> distribution you were using; if gentoo then use wget >> and a URL to test network connections). >> >> Also, since no network actually works for me I >> installed a proxy (FreeProxy) and set up various >> proxy-variables so that gentoo-tools and wget >> actually work through the proxy. >> >> Did you install a proxy server on the WinXP host? >> >> regards, >> >> --Tim >> >> -----Original Message----- >> From: col...@li... >> [mailto:col...@li...]On >> Behalf Of Petar >> Tomic >> Sent: woensdag 16 juni 2004 8:52 >> To: colinux >> Subject: Re: [coLinux-users] Network ?? >> >> >> Here is how look my colinux.default.xml >> >> <network index=3D"0" name=3D"coLinux" >> mac=3D"00:0C:76:87:7D:49" type=3D"tap"></network> >> >> I can ping 192.168.0.40, which is network card under >> coLinux, but I can't ping 192.168.0.1 which is >> gateway >> under co Linux, and virtual network card under XP. >> From XP I can ping 192.168.0.40. >> --- ch...@to... wrote: >> > I don't think the metric would make a difference >> > (see man route if you >> > havn't already) >> > >> > not shure why you don't have a loopback >> (127.0.0.1) >> > but that should not >> > matter for ping by address but may mess up other >> > stuff. >> > >> > try Ilias's sugestion. but I think the index is >> > supposed to corespond to >> > the interface on the linux side ie: index=3D"0" for >> > eth0 and index=3D"4" for >> > eth4 >> > I think I had a name=3D parameter in an older xml >> that >> > I ended up removing >> > to get it working with 0.6.1 >> > >> > chris >> > >> > > I get this: >> > > # route >> > > Kernel IP routing table >> > > Destination Gateway Genmask >> > > Flags Metric Ref Use Iface >> > > 192.168.0.0 * 255.255.255.0 >> >> > U >> > > >> > > 0 0 0 eth0 >> > > default 192.168.0.1 0.0.0.0 >> UG >> > > 0 0 0 eth0 >> > > # >> > > >> > > As I see you have 1 at metric, and I have 0. >> > > >> > > --- ch...@to... wrote: >> > >> run the route command on coLinux you should get >> > >> something like this >> > >> # route >> > >> Kernel IP routing table >> > >> Destination Gateway Genmask >> > >> Flags Metric Ref Use Iface >> > >> localnet * 255.255.255.0 >> U >> > >> 0 0 0 eth0 >> > >> loopback * 255.0.0.0 >> U >> > >> 0 0 0 lo >> > >> default 192.168.0.1 0.0.0.0 >> > UG >> > >> 1 0 0 eth0 >> > >> # >> > >> >> > >> You may have not set the default gateway on the >> > >> linux side. this can be >> > >> done with the route command but will not >> persist >> > >> across reboots. The way >> > >> to do it so that it is set at boot is distro >> > >> dependant. >> > >> >> > >> chris >> > >> >> > >> >> > >> > I setup mz network as is in WiKi, and doesn't >> > >> work. >> > >> > I have WinXP and I can ping 192.168.0.40 from >> > XP >> > >> and >> > >> > from coLinux. But I can't ping 192.168.0.1 >> from >> > >> > coLinux I get a message Host unreachable ?? >> > >> > I must say that I install Tap32-Win diver and >> > it's >> > >> > visible in Windows, but .... >> > >> > >> > >> > Windows IP Configuration >> > >> > >> > >> > >> > >> > Ethernet adapter coLinux: >> > >> > >> > >> > Connection-specific DNS Suffix . : >> > >> > IP Address. . . . . . . . . . . . : >> > >> > 192.168.0.1 >> > >> > Subnet Mask . . . . . . . . . . . : >> > >> > 255.255.255.0 >> > >> > Default Gateway . . . . . . . . . : >> > >> > >> > >> > Ethernet adapter Local Area Connection: >> > >> > >> > >> > Connection-specific DNS Suffix . : >> > >> > IP Address. . . . . : *.*.*.*(not >> > private >> > >> > adress so I hide it) >> > >> > Subnet Mask . . . . : 255.255.255.0 >> > >> > Default Gateway . . : 212.102.130.1 >> > >> > >> > >> > >> > >> > >> > >> > __________________________________ >> > >> > Do you Yahoo!? >> > >> > Yahoo! Mail is new and improved - Check it >> out! >> > >> > http://promotions.yahoo.com/new_mail >> > >> > >> > >> > >> > >> > >> > >> >> > > >> > >> > ------------------------------------------------------- >> > >> > This SF.Net email is sponsored by The 2004 >> > >> JavaOne(SM) Conference >> > >> > Learn from the experts at JavaOne(SM), Sun's >> > >> Worldwide Java Developer >> > >> > Conference, June 28 - July 1 at the Moscone >> > Center >> > >> in San Francisco, CA >> > >> > REGISTER AND SAVE! >> > http://java.sun.com/javaone/sf >> > >> Priority Code NWMGYKND >> > >> > >> _______________________________________________ >> > >> > coLinux-users mailing list >> > >> > coL...@li... >> > >> > >> > >> >> > > >> > >> > https://lists.sourceforge.net/lists/listinfo/colinux-users >> > >> > >> > >> >> > >> >> > > >> > > >> > > >> > > >> > > __________________________________ >> > > Do you Yahoo!? >> > > Read only the mail you want - Yahoo! Mail >> > SpamGuard. >> > > http://promotions.yahoo.com/new_mail >> > > >> > > >> > > >> > >> > ------------------------------------------------------- >> > > This SF.Net email is sponsored by The 2004 >> > JavaOne(SM) Conference >> > > Learn from the experts at JavaOne(SM), Sun's >> > Worldwide Java Developer >> > > Conference, June 28 - July 1 at the Moscone >> Center >> > in San Francisco, CA >> > > REGISTER AND SAVE! >> http://java.sun.com/javaone/sf >> > Priority Code NWMGYKND >> > > _______________________________________________ >> > > coLinux-users mailing list >> > > coL...@li... >> > > >> > >> > https://lists.sourceforge.net/lists/listinfo/colinux-users >> > > >> > >> > >> >> >> >> >> __________________________________ >> Do you Yahoo!? >> Yahoo! Mail - You care about security. So do we. >> http://promotions.yahoo.com/new_mail >> >> >> > ------------------------------------------------------- >> This SF.Net email is sponsored by The 2004 >> JavaOne(SM) Conference >> Learn from the experts at JavaOne(SM), Sun's >> Worldwide Java Developer >> Conference, June 28 - July 1 at the Moscone Center >> in San Francisco, CA >> REGISTER AND SAVE! http://java.sun.com/javaone/sf >> Priority Code NWMGYKND >> _______________________________________________ >> coLinux-users mailing list >> coL...@li... >> > https://lists.sourceforge.net/lists/listinfo/colinux-users >> > > > > > __________________________________ > Do you Yahoo!? > Read only the mail you want - Yahoo! Mail SpamGuard. > http://promotions.yahoo.com/new_mail > > > ------------------------------------------------------- > This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference > Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer > Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA > REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKN= D > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
|
From: Petar T. <pto...@ya...> - 2004-06-16 13:54:01
|
It's finally start to work, I can ping other public IPs. Thank to all. P.S. I found what was my second problem. :) I was disable ICS. :):) __________________________________ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail |
|
From: Petar T. <pto...@ya...> - 2004-06-16 13:41:56
|
I was succesful. I can pingmy virtual gateway (192.168.0.1) and my public adress, from coLinux. New question is how to setup coLinux to do apt-get from internet. I use Debian-3.0r0.ext3.1gb in coLinux. --- "Leeuw van der, Tim" <tim...@nl...> wrote: > Hi, > > For reasons unknown to me but perhaps a firewall, > ping doesn't work for me at all. But do basic things > like telnet / wget work? (I don't know which > distribution you were using; if gentoo then use wget > and a URL to test network connections). > > Also, since no network actually works for me I > installed a proxy (FreeProxy) and set up various > proxy-variables so that gentoo-tools and wget > actually work through the proxy. > > Did you install a proxy server on the WinXP host? > > regards, > > --Tim > > -----Original Message----- > From: col...@li... > [mailto:col...@li...]On > Behalf Of Petar > Tomic > Sent: woensdag 16 juni 2004 8:52 > To: colinux > Subject: Re: [coLinux-users] Network ?? > > > Here is how look my colinux.default.xml > > <network index="0" name="coLinux" > mac="00:0C:76:87:7D:49" type="tap"></network> > > I can ping 192.168.0.40, which is network card under > coLinux, but I can't ping 192.168.0.1 which is > gateway > under co Linux, and virtual network card under XP. > From XP I can ping 192.168.0.40. > --- ch...@to... wrote: > > I don't think the metric would make a difference > > (see man route if you > > havn't already) > > > > not shure why you don't have a loopback > (127.0.0.1) > > but that should not > > matter for ping by address but may mess up other > > stuff. > > > > try Ilias's sugestion. but I think the index is > > supposed to corespond to > > the interface on the linux side ie: index="0" for > > eth0 and index="4" for > > eth4 > > I think I had a name= parameter in an older xml > that > > I ended up removing > > to get it working with 0.6.1 > > > > chris > > > > > I get this: > > > # route > > > Kernel IP routing table > > > Destination Gateway Genmask > > > Flags Metric Ref Use Iface > > > 192.168.0.0 * 255.255.255.0 > > > U > > > > > > 0 0 0 eth0 > > > default 192.168.0.1 0.0.0.0 > UG > > > 0 0 0 eth0 > > > # > > > > > > As I see you have 1 at metric, and I have 0. > > > > > > --- ch...@to... wrote: > > >> run the route command on coLinux you should get > > >> something like this > > >> # route > > >> Kernel IP routing table > > >> Destination Gateway Genmask > > >> Flags Metric Ref Use Iface > > >> localnet * 255.255.255.0 > U > > >> 0 0 0 eth0 > > >> loopback * 255.0.0.0 > U > > >> 0 0 0 lo > > >> default 192.168.0.1 0.0.0.0 > > UG > > >> 1 0 0 eth0 > > >> # > > >> > > >> You may have not set the default gateway on the > > >> linux side. this can be > > >> done with the route command but will not > persist > > >> across reboots. The way > > >> to do it so that it is set at boot is distro > > >> dependant. > > >> > > >> chris > > >> > > >> > > >> > I setup mz network as is in WiKi, and doesn't > > >> work. > > >> > I have WinXP and I can ping 192.168.0.40 from > > XP > > >> and > > >> > from coLinux. But I can't ping 192.168.0.1 > from > > >> > coLinux I get a message Host unreachable ?? > > >> > I must say that I install Tap32-Win diver and > > it's > > >> > visible in Windows, but .... > > >> > > > >> > Windows IP Configuration > > >> > > > >> > > > >> > Ethernet adapter coLinux: > > >> > > > >> > Connection-specific DNS Suffix . : > > >> > IP Address. . . . . . . . . . . . : > > >> > 192.168.0.1 > > >> > Subnet Mask . . . . . . . . . . . : > > >> > 255.255.255.0 > > >> > Default Gateway . . . . . . . . . : > > >> > > > >> > Ethernet adapter Local Area Connection: > > >> > > > >> > Connection-specific DNS Suffix . : > > >> > IP Address. . . . . : *.*.*.*(not > > private > > >> > adress so I hide it) > > >> > Subnet Mask . . . . : 255.255.255.0 > > >> > Default Gateway . . : 212.102.130.1 > > >> > > > >> > > > >> > > > >> > __________________________________ > > >> > Do you Yahoo!? > > >> > Yahoo! Mail is new and improved - Check it > out! > > >> > http://promotions.yahoo.com/new_mail > > >> > > > >> > > > >> > > > >> > > > > > > ------------------------------------------------------- > > >> > This SF.Net email is sponsored by The 2004 > > >> JavaOne(SM) Conference > > >> > Learn from the experts at JavaOne(SM), Sun's > > >> Worldwide Java Developer > > >> > Conference, June 28 - July 1 at the Moscone > > Center > > >> in San Francisco, CA > > >> > REGISTER AND SAVE! > > http://java.sun.com/javaone/sf > > >> Priority Code NWMGYKND > > >> > > _______________________________________________ > > >> > coLinux-users mailing list > > >> > coL...@li... > > >> > > > >> > > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > >> > > > >> > > >> > > > > > > > > > > > > > > > __________________________________ > > > Do you Yahoo!? > > > Read only the mail you want - Yahoo! Mail > > SpamGuard. > > > http://promotions.yahoo.com/new_mail > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by The 2004 > > JavaOne(SM) Conference > > > Learn from the experts at JavaOne(SM), Sun's > > Worldwide Java Developer > > > Conference, June 28 - July 1 at the Moscone > Center > > in San Francisco, CA > > > REGISTER AND SAVE! > http://java.sun.com/javaone/sf > > Priority Code NWMGYKND > > > _______________________________________________ > > > coLinux-users mailing list > > > coL...@li... > > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > > > > > > > > > > __________________________________ > Do you Yahoo!? > Yahoo! Mail - You care about security. So do we. > http://promotions.yahoo.com/new_mail > > > ------------------------------------------------------- > This SF.Net email is sponsored by The 2004 > JavaOne(SM) Conference > Learn from the experts at JavaOne(SM), Sun's > Worldwide Java Developer > Conference, June 28 - July 1 at the Moscone Center > in San Francisco, CA > REGISTER AND SAVE! http://java.sun.com/javaone/sf > Priority Code NWMGYKND > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail |
|
From: <ch...@to...> - 2004-06-16 11:59:23
|
If you can ping coLinux from windows then you must be getting 2 way comunication because the reply needs to find its way back. Try pinging the windows machine from coLinux with the -v for verbose to see if that gives you any more info. Check on what Tim said is ping somehow blocked on your machine some firewall tools and possibly "policys" if a domain member block that to prevent ping based ddos. it would be nice to have a smarter option here that would block the port for 2 minutes after 5 pings were received instead of blocking this usefull tool all together. From the windows host can you ping 127.0.0.1 and 192.168.0.1 and your rea= l network interface ip address? Can you ping your windows outside ip from another real host on your lan? Get putty or some other ssh client and try to connect to coLinux from windows. XP home or pro? does it have a telnet and/or ftp server included or with cygwin or ssh server. or you can try smbclient or smbmount if you know samba just some other client to verify other than ping. Are you sharing your outside connection. can you get anything on the outside? view webpages etc. ( for ICS you should set the nameserver on linux to 192.168.0.1 not your real outside nameserver windows needs to proxy the requests in order for the reply to get back to the private address range.) also try changing the coLinux.default.xml file line to simply <network index=3D"0" type=3D"tap"></network> I do not think the mac and name are necessary and your problem might be here. I had a name=3D in my previous .xml file but had connectivity probl= ems when upgrading to coLinux-0.6.1 I removed the name and was ok. The wiki was written for older versions and I think the mac is only necessary for bridged networking. chris > Here is how look my colinux.default.xml > > <network index=3D"0" name=3D"coLinux" > mac=3D"00:0C:76:87:7D:49" type=3D"tap"></network> > > I can ping 192.168.0.40, which is network card under > coLinux, but I can't ping 192.168.0.1 which is gateway > under co Linux, and virtual network card under XP. > From XP I can ping 192.168.0.40. > --- ch...@to... wrote: >> I don't think the metric would make a difference >> (see man route if you >> havn't already) >> >> not shure why you don't have a loopback (127.0.0.1) >> but that should not >> matter for ping by address but may mess up other >> stuff. >> >> try Ilias's sugestion. but I think the index is >> supposed to corespond to >> the interface on the linux side ie: index=3D"0" for >> eth0 and index=3D"4" for >> eth4 >> I think I had a name=3D parameter in an older xml that >> I ended up removing >> to get it working with 0.6.1 >> >> chris >> >> > I get this: >> > # route >> > Kernel IP routing table >> > Destination Gateway Genmask >> > Flags Metric Ref Use Iface >> > 192.168.0.0 * 255.255.255.0 >> U >> > >> > 0 0 0 eth0 >> > default 192.168.0.1 0.0.0.0 UG >> > 0 0 0 eth0 >> > # >> > >> > As I see you have 1 at metric, and I have 0. >> > >> > --- ch...@to... wrote: >> >> run the route command on coLinux you should get >> >> something like this >> >> # route >> >> Kernel IP routing table >> >> Destination Gateway Genmask >> >> Flags Metric Ref Use Iface >> >> localnet * 255.255.255.0 U >> >> 0 0 0 eth0 >> >> loopback * 255.0.0.0 U >> >> 0 0 0 lo >> >> default 192.168.0.1 0.0.0.0 >> UG >> >> 1 0 0 eth0 >> >> # >> >> >> >> You may have not set the default gateway on the >> >> linux side. this can be >> >> done with the route command but will not persist >> >> across reboots. The way >> >> to do it so that it is set at boot is distro >> >> dependant. >> >> >> >> chris >> >> >> >> >> >> > I setup mz network as is in WiKi, and doesn't >> >> work. >> >> > I have WinXP and I can ping 192.168.0.40 from >> XP >> >> and >> >> > from coLinux. But I can't ping 192.168.0.1 from >> >> > coLinux I get a message Host unreachable ?? >> >> > I must say that I install Tap32-Win diver and >> it's >> >> > visible in Windows, but .... >> >> > >> >> > Windows IP Configuration >> >> > >> >> > >> >> > Ethernet adapter coLinux: >> >> > >> >> > Connection-specific DNS Suffix . : >> >> > IP Address. . . . . . . . . . . . : >> >> > 192.168.0.1 >> >> > Subnet Mask . . . . . . . . . . . : >> >> > 255.255.255.0 >> >> > Default Gateway . . . . . . . . . : >> >> > >> >> > Ethernet adapter Local Area Connection: >> >> > >> >> > Connection-specific DNS Suffix . : >> >> > IP Address. . . . . : *.*.*.*(not >> private >> >> > adress so I hide it) >> >> > Subnet Mask . . . . : 255.255.255.0 >> >> > Default Gateway . . : 212.102.130.1 >> >> > >> >> > >> >> > >> >> > __________________________________ >> >> > Do you Yahoo!? >> >> > Yahoo! Mail is new and improved - Check it out! >> >> > http://promotions.yahoo.com/new_mail >> >> > >> >> > >> >> > >> >> >> > >> > ------------------------------------------------------- >> >> > This SF.Net email is sponsored by The 2004 >> >> JavaOne(SM) Conference >> >> > Learn from the experts at JavaOne(SM), Sun's >> >> Worldwide Java Developer >> >> > Conference, June 28 - July 1 at the Moscone >> Center >> >> in San Francisco, CA >> >> > REGISTER AND SAVE! >> http://java.sun.com/javaone/sf >> >> Priority Code NWMGYKND >> >> > _______________________________________________ >> >> > coLinux-users mailing list >> >> > coL...@li... >> >> > >> >> >> > >> > https://lists.sourceforge.net/lists/listinfo/colinux-users >> >> > >> >> >> >> >> > >> > >> > >> > >> > __________________________________ >> > Do you Yahoo!? >> > Read only the mail you want - Yahoo! Mail >> SpamGuard. >> > http://promotions.yahoo.com/new_mail >> > >> > >> > >> > ------------------------------------------------------- >> > This SF.Net email is sponsored by The 2004 >> JavaOne(SM) Conference >> > Learn from the experts at JavaOne(SM), Sun's >> Worldwide Java Developer >> > Conference, June 28 - July 1 at the Moscone Center >> in San Francisco, CA >> > REGISTER AND SAVE! http://java.sun.com/javaone/sf >> Priority Code NWMGYKND >> > _______________________________________________ >> > coLinux-users mailing list >> > coL...@li... >> > >> > https://lists.sourceforge.net/lists/listinfo/colinux-users >> > >> >> > > > > > __________________________________ > Do you Yahoo!? > Yahoo! Mail - You care about security. So do we. > http://promotions.yahoo.com/new_mail > > > ------------------------------------------------------- > This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference > Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer > Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA > REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKN= D > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
|
From: Leeuw v. d. T. <tim...@nl...> - 2004-06-16 07:36:21
|
Hi, For reasons unknown to me but perhaps a firewall, ping doesn't work for = me at all. But do basic things like telnet / wget work? (I don't know = which distribution you were using; if gentoo then use wget and a URL to = test network connections). Also, since no network actually works for me I installed a proxy = (FreeProxy) and set up various proxy-variables so that gentoo-tools and = wget actually work through the proxy. Did you install a proxy server on the WinXP host? regards, --Tim -----Original Message----- From: col...@li... [mailto:col...@li...]On Behalf Of Petar Tomic Sent: woensdag 16 juni 2004 8:52 To: colinux Subject: Re: [coLinux-users] Network ?? Here is how look my colinux.default.xml <network index=3D"0" name=3D"coLinux" mac=3D"00:0C:76:87:7D:49" type=3D"tap"></network> I can ping 192.168.0.40, which is network card under coLinux, but I can't ping 192.168.0.1 which is gateway under co Linux, and virtual network card under XP. From XP I can ping 192.168.0.40. --- ch...@to... wrote: > I don't think the metric would make a difference > (see man route if you > havn't already) >=20 > not shure why you don't have a loopback (127.0.0.1) > but that should not > matter for ping by address but may mess up other > stuff. >=20 > try Ilias's sugestion. but I think the index is > supposed to corespond to > the interface on the linux side ie: index=3D"0" for > eth0 and index=3D"4" for > eth4 > I think I had a name=3D parameter in an older xml that > I ended up removing > to get it working with 0.6.1 >=20 > chris >=20 > > I get this: > > # route > > Kernel IP routing table > > Destination Gateway Genmask > > Flags Metric Ref Use Iface > > 192.168.0.0 * 255.255.255.0 =20 > U > > > > 0 0 0 eth0 > > default 192.168.0.1 0.0.0.0 UG > > 0 0 0 eth0 > > # > > > > As I see you have 1 at metric, and I have 0. > > > > --- ch...@to... wrote: > >> run the route command on coLinux you should get > >> something like this > >> # route > >> Kernel IP routing table > >> Destination Gateway Genmask > >> Flags Metric Ref Use Iface > >> localnet * 255.255.255.0 U > >> 0 0 0 eth0 > >> loopback * 255.0.0.0 U > >> 0 0 0 lo > >> default 192.168.0.1 0.0.0.0 =20 > UG > >> 1 0 0 eth0 > >> # > >> > >> You may have not set the default gateway on the > >> linux side. this can be > >> done with the route command but will not persist > >> across reboots. The way > >> to do it so that it is set at boot is distro > >> dependant. > >> > >> chris > >> > >> > >> > I setup mz network as is in WiKi, and doesn't > >> work. > >> > I have WinXP and I can ping 192.168.0.40 from > XP > >> and > >> > from coLinux. But I can't ping 192.168.0.1 from > >> > coLinux I get a message Host unreachable ?? > >> > I must say that I install Tap32-Win diver and > it's > >> > visible in Windows, but .... > >> > > >> > Windows IP Configuration > >> > > >> > > >> > Ethernet adapter coLinux: > >> > > >> > Connection-specific DNS Suffix . : > >> > IP Address. . . . . . . . . . . . : > >> > 192.168.0.1 > >> > Subnet Mask . . . . . . . . . . . : > >> > 255.255.255.0 > >> > Default Gateway . . . . . . . . . : > >> > > >> > Ethernet adapter Local Area Connection: > >> > > >> > Connection-specific DNS Suffix . : > >> > IP Address. . . . . : *.*.*.*(not > private > >> > adress so I hide it) > >> > Subnet Mask . . . . : 255.255.255.0 > >> > Default Gateway . . : 212.102.130.1 > >> > > >> > > >> > > >> > __________________________________ > >> > Do you Yahoo!? > >> > Yahoo! Mail is new and improved - Check it out! > >> > http://promotions.yahoo.com/new_mail > >> > > >> > > >> > > >> > > > ------------------------------------------------------- > >> > This SF.Net email is sponsored by The 2004 > >> JavaOne(SM) Conference > >> > Learn from the experts at JavaOne(SM), Sun's > >> Worldwide Java Developer > >> > Conference, June 28 - July 1 at the Moscone > Center > >> in San Francisco, CA > >> > REGISTER AND SAVE! > http://java.sun.com/javaone/sf > >> Priority Code NWMGYKND > >> > _______________________________________________ > >> > coLinux-users mailing list > >> > coL...@li... > >> > > >> > > > https://lists.sourceforge.net/lists/listinfo/colinux-users > >> > > >> > >> > > > > > > > > > > __________________________________ > > Do you Yahoo!? > > Read only the mail you want - Yahoo! Mail > SpamGuard. > > http://promotions.yahoo.com/new_mail > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by The 2004 > JavaOne(SM) Conference > > Learn from the experts at JavaOne(SM), Sun's > Worldwide Java Developer > > Conference, June 28 - July 1 at the Moscone Center > in San Francisco, CA > > REGISTER AND SAVE! http://java.sun.com/javaone/sf > Priority Code NWMGYKND > > _______________________________________________ > > coLinux-users mailing list > > coL...@li... > > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > >=20 >=20 =09 __________________________________ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail ------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users |
|
From: Petar T. <pto...@ya...> - 2004-06-16 06:52:21
|
Here is how look my colinux.default.xml <network index="0" name="coLinux" mac="00:0C:76:87:7D:49" type="tap"></network> I can ping 192.168.0.40, which is network card under coLinux, but I can't ping 192.168.0.1 which is gateway under co Linux, and virtual network card under XP. From XP I can ping 192.168.0.40. --- ch...@to... wrote: > I don't think the metric would make a difference > (see man route if you > havn't already) > > not shure why you don't have a loopback (127.0.0.1) > but that should not > matter for ping by address but may mess up other > stuff. > > try Ilias's sugestion. but I think the index is > supposed to corespond to > the interface on the linux side ie: index="0" for > eth0 and index="4" for > eth4 > I think I had a name= parameter in an older xml that > I ended up removing > to get it working with 0.6.1 > > chris > > > I get this: > > # route > > Kernel IP routing table > > Destination Gateway Genmask > > Flags Metric Ref Use Iface > > 192.168.0.0 * 255.255.255.0 > U > > > > 0 0 0 eth0 > > default 192.168.0.1 0.0.0.0 UG > > 0 0 0 eth0 > > # > > > > As I see you have 1 at metric, and I have 0. > > > > --- ch...@to... wrote: > >> run the route command on coLinux you should get > >> something like this > >> # route > >> Kernel IP routing table > >> Destination Gateway Genmask > >> Flags Metric Ref Use Iface > >> localnet * 255.255.255.0 U > >> 0 0 0 eth0 > >> loopback * 255.0.0.0 U > >> 0 0 0 lo > >> default 192.168.0.1 0.0.0.0 > UG > >> 1 0 0 eth0 > >> # > >> > >> You may have not set the default gateway on the > >> linux side. this can be > >> done with the route command but will not persist > >> across reboots. The way > >> to do it so that it is set at boot is distro > >> dependant. > >> > >> chris > >> > >> > >> > I setup mz network as is in WiKi, and doesn't > >> work. > >> > I have WinXP and I can ping 192.168.0.40 from > XP > >> and > >> > from coLinux. But I can't ping 192.168.0.1 from > >> > coLinux I get a message Host unreachable ?? > >> > I must say that I install Tap32-Win diver and > it's > >> > visible in Windows, but .... > >> > > >> > Windows IP Configuration > >> > > >> > > >> > Ethernet adapter coLinux: > >> > > >> > Connection-specific DNS Suffix . : > >> > IP Address. . . . . . . . . . . . : > >> > 192.168.0.1 > >> > Subnet Mask . . . . . . . . . . . : > >> > 255.255.255.0 > >> > Default Gateway . . . . . . . . . : > >> > > >> > Ethernet adapter Local Area Connection: > >> > > >> > Connection-specific DNS Suffix . : > >> > IP Address. . . . . : *.*.*.*(not > private > >> > adress so I hide it) > >> > Subnet Mask . . . . : 255.255.255.0 > >> > Default Gateway . . : 212.102.130.1 > >> > > >> > > >> > > >> > __________________________________ > >> > Do you Yahoo!? > >> > Yahoo! Mail is new and improved - Check it out! > >> > http://promotions.yahoo.com/new_mail > >> > > >> > > >> > > >> > > > ------------------------------------------------------- > >> > This SF.Net email is sponsored by The 2004 > >> JavaOne(SM) Conference > >> > Learn from the experts at JavaOne(SM), Sun's > >> Worldwide Java Developer > >> > Conference, June 28 - July 1 at the Moscone > Center > >> in San Francisco, CA > >> > REGISTER AND SAVE! > http://java.sun.com/javaone/sf > >> Priority Code NWMGYKND > >> > _______________________________________________ > >> > coLinux-users mailing list > >> > coL...@li... > >> > > >> > > > https://lists.sourceforge.net/lists/listinfo/colinux-users > >> > > >> > >> > > > > > > > > > > __________________________________ > > Do you Yahoo!? > > Read only the mail you want - Yahoo! Mail > SpamGuard. > > http://promotions.yahoo.com/new_mail > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by The 2004 > JavaOne(SM) Conference > > Learn from the experts at JavaOne(SM), Sun's > Worldwide Java Developer > > Conference, June 28 - July 1 at the Moscone Center > in San Francisco, CA > > REGISTER AND SAVE! http://java.sun.com/javaone/sf > Priority Code NWMGYKND > > _______________________________________________ > > coLinux-users mailing list > > coL...@li... > > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > > __________________________________ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail |
|
From: <ch...@to...> - 2004-06-15 17:28:50
|
I don't think the metric would make a difference (see man route if you havn't already) not shure why you don't have a loopback (127.0.0.1) but that should not matter for ping by address but may mess up other stuff. try Ilias's sugestion. but I think the index is supposed to corespond to the interface on the linux side ie: index=3D"0" for eth0 and index=3D"4" = for eth4 I think I had a name=3D parameter in an older xml that I ended up removin= g to get it working with 0.6.1 chris > I get this: > # route > Kernel IP routing table > Destination Gateway Genmask > Flags Metric Ref Use Iface > 192.168.0.0 * 255.255.255.0 U > > 0 0 0 eth0 > default 192.168.0.1 0.0.0.0 UG > 0 0 0 eth0 > # > > As I see you have 1 at metric, and I have 0. > > --- ch...@to... wrote: >> run the route command on coLinux you should get >> something like this >> # route >> Kernel IP routing table >> Destination Gateway Genmask >> Flags Metric Ref Use Iface >> localnet * 255.255.255.0 U >> 0 0 0 eth0 >> loopback * 255.0.0.0 U >> 0 0 0 lo >> default 192.168.0.1 0.0.0.0 UG >> 1 0 0 eth0 >> # >> >> You may have not set the default gateway on the >> linux side. this can be >> done with the route command but will not persist >> across reboots. The way >> to do it so that it is set at boot is distro >> dependant. >> >> chris >> >> >> > I setup mz network as is in WiKi, and doesn't >> work. >> > I have WinXP and I can ping 192.168.0.40 from XP >> and >> > from coLinux. But I can't ping 192.168.0.1 from >> > coLinux I get a message Host unreachable ?? >> > I must say that I install Tap32-Win diver and it's >> > visible in Windows, but .... >> > >> > Windows IP Configuration >> > >> > >> > Ethernet adapter coLinux: >> > >> > Connection-specific DNS Suffix . : >> > IP Address. . . . . . . . . . . . : >> > 192.168.0.1 >> > Subnet Mask . . . . . . . . . . . : >> > 255.255.255.0 >> > Default Gateway . . . . . . . . . : >> > >> > Ethernet adapter Local Area Connection: >> > >> > Connection-specific DNS Suffix . : >> > IP Address. . . . . : *.*.*.*(not private >> > adress so I hide it) >> > Subnet Mask . . . . : 255.255.255.0 >> > Default Gateway . . : 212.102.130.1 >> > >> > >> > >> > __________________________________ >> > Do you Yahoo!? >> > Yahoo! Mail is new and improved - Check it out! >> > http://promotions.yahoo.com/new_mail >> > >> > >> > >> > ------------------------------------------------------- >> > This SF.Net email is sponsored by The 2004 >> JavaOne(SM) Conference >> > Learn from the experts at JavaOne(SM), Sun's >> Worldwide Java Developer >> > Conference, June 28 - July 1 at the Moscone Center >> in San Francisco, CA >> > REGISTER AND SAVE! http://java.sun.com/javaone/sf >> Priority Code NWMGYKND >> > _______________________________________________ >> > coLinux-users mailing list >> > coL...@li... >> > >> > https://lists.sourceforge.net/lists/listinfo/colinux-users >> > >> >> > > > > > __________________________________ > Do you Yahoo!? > Read only the mail you want - Yahoo! Mail SpamGuard. > http://promotions.yahoo.com/new_mail > > > ------------------------------------------------------- > This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference > Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer > Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA > REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKN= D > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
|
From: Petar T. <pto...@ya...> - 2004-06-15 14:23:57
|
I get this: # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.0 * 255.255.255.0 U 0 0 0 eth0 default 192.168.0.1 0.0.0.0 UG 0 0 0 eth0 # As I see you have 1 at metric, and I have 0. --- ch...@to... wrote: > run the route command on coLinux you should get > something like this > # route > Kernel IP routing table > Destination Gateway Genmask > Flags Metric Ref Use Iface > localnet * 255.255.255.0 U > 0 0 0 eth0 > loopback * 255.0.0.0 U > 0 0 0 lo > default 192.168.0.1 0.0.0.0 UG > 1 0 0 eth0 > # > > You may have not set the default gateway on the > linux side. this can be > done with the route command but will not persist > across reboots. The way > to do it so that it is set at boot is distro > dependant. > > chris > > > > I setup mz network as is in WiKi, and doesn't > work. > > I have WinXP and I can ping 192.168.0.40 from XP > and > > from coLinux. But I can't ping 192.168.0.1 from > > coLinux I get a message Host unreachable ?? > > I must say that I install Tap32-Win diver and it's > > visible in Windows, but .... > > > > Windows IP Configuration > > > > > > Ethernet adapter coLinux: > > > > Connection-specific DNS Suffix . : > > IP Address. . . . . . . . . . . . : > > 192.168.0.1 > > Subnet Mask . . . . . . . . . . . : > > 255.255.255.0 > > Default Gateway . . . . . . . . . : > > > > Ethernet adapter Local Area Connection: > > > > Connection-specific DNS Suffix . : > > IP Address. . . . . : *.*.*.*(not private > > adress so I hide it) > > Subnet Mask . . . . : 255.255.255.0 > > Default Gateway . . : 212.102.130.1 > > > > > > > > __________________________________ > > Do you Yahoo!? > > Yahoo! Mail is new and improved - Check it out! > > http://promotions.yahoo.com/new_mail > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by The 2004 > JavaOne(SM) Conference > > Learn from the experts at JavaOne(SM), Sun's > Worldwide Java Developer > > Conference, June 28 - July 1 at the Moscone Center > in San Francisco, CA > > REGISTER AND SAVE! http://java.sun.com/javaone/sf > Priority Code NWMGYKND > > _______________________________________________ > > coLinux-users mailing list > > coL...@li... > > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > > __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail |
|
From: <ch...@to...> - 2004-06-15 11:54:03
|
run the route command on coLinux you should get something like this # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use I= face localnet * 255.255.255.0 U 0 0 0 e= th0 loopback * 255.0.0.0 U 0 0 0 l= o default 192.168.0.1 0.0.0.0 UG 1 0 0 e= th0 # You may have not set the default gateway on the linux side. this can be done with the route command but will not persist across reboots. The way to do it so that it is set at boot is distro dependant. chris > I setup mz network as is in WiKi, and doesn't work. > I have WinXP and I can ping 192.168.0.40 from XP and > from coLinux. But I can't ping 192.168.0.1 from > coLinux I get a message Host unreachable ?? > I must say that I install Tap32-Win diver and it's > visible in Windows, but .... > > Windows IP Configuration > > > Ethernet adapter coLinux: > > Connection-specific DNS Suffix . : > IP Address. . . . . . . . . . . . : > 192.168.0.1 > Subnet Mask . . . . . . . . . . . : > 255.255.255.0 > Default Gateway . . . . . . . . . : > > Ethernet adapter Local Area Connection: > > Connection-specific DNS Suffix . : > IP Address. . . . . : *.*.*.*(not private > adress so I hide it) > Subnet Mask . . . . : 255.255.255.0 > Default Gateway . . : 212.102.130.1 > > > > __________________________________ > Do you Yahoo!? > Yahoo! Mail is new and improved - Check it out! > http://promotions.yahoo.com/new_mail > > > ------------------------------------------------------- > This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference > Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer > Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA > REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKN= D > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
|
From: <ib...@ge...> - 2004-06-15 11:41:15
|
Hi Petar, In your default.colinux.xml configuration file there ought to be a line <network index="4" type="tap"/> where the index is the index of the "network connection" in the "dial-up and network connections" that you get at from the control Panel ... Had exactly the same problem but just needed to alter the index and hey presto the thing started working regards etc ---- Ilias Biris, Ph.D. ASR, Senior Researcher Genius Instituto de Tecnologia TEL: +55 (0)92 6146503 FAX: +55 (0)92 6133144 http://www.genius.org.br/ Petar Tomic <pto...@ya...> Sent by: col...@li... 15/06/2004 06:17 Please respond to ptomic To: col...@li... cc: Subject: [coLinux-users] Network ?? I setup mz network as is in WiKi, and doesn't work. I have WinXP and I can ping 192.168.0.40 from XP and from coLinux. But I can't ping 192.168.0.1 from coLinux I get a message Host unreachable ?? I must say that I install Tap32-Win diver and it's visible in Windows, but .... Windows IP Configuration Ethernet adapter coLinux: Connection-specific DNS Suffix . : IP Address. . . . . . . . . . . . : 192.168.0.1 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : IP Address. . . . . : *.*.*.*(not private adress so I hide it) Subnet Mask . . . . : 255.255.255.0 Default Gateway . . : 212.102.130.1 __________________________________ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail ------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users ************************************************************************************************** O conteúdo desse e-mail ou de seus anexos são confidenciais e restritos ao destinatário da mensagem. Se você recebeu esse e-mail por engano, por favor notifique o remetente imediatamente e não faça cópias ou distribua seu conteúdo para ninguém. ************************************************************************************************** The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email in error please notify the system manager or the sender immediately and do not disclose the contents to anyone or make copies. ************************************************************************************************** |
|
From: Petar T. <pto...@ya...> - 2004-06-15 10:17:37
|
I setup mz network as is in WiKi, and doesn't work.
I have WinXP and I can ping 192.168.0.40 from XP and
from coLinux. But I can't ping 192.168.0.1 from
coLinux I get a message Host unreachable ??
I must say that I install Tap32-Win diver and it's
visible in Windows, but ....
Windows IP Configuration
Ethernet adapter coLinux:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . :
192.168.0.1
Subnet Mask . . . . . . . . . . . :
255.255.255.0
Default Gateway . . . . . . . . . :
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
IP Address. . . . . : *.*.*.*(not private
adress so I hide it)
Subnet Mask . . . . : 255.255.255.0
Default Gateway . . : 212.102.130.1
__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail
|
|
From: peter g. <plu...@p1...> - 2004-06-11 20:54:20
|
you could also try my connection trapping code its mentioned in the networking section of the wiki just search for connection trapping -----Original Message----- From: col...@li... [mailto:col...@li...]On Behalf Of Patrick White Sent: 10 June 2004 20:49 To: col...@li... Subject: Re: [coLinux-users] Win2k and services. 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 slam the IP for that adapter to 192... I might have had to reboot or disable/enable the adapter or something before it started working. Of course, this was with two physical adapters, not one physical and the TAP 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. ------------------------------------------------------- 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 --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.701 / Virus Database: 458 - Release Date: 07/06/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.701 / Virus Database: 458 - Release Date: 07/06/2004 |
|
From: Leeuw v. d. T. <tim...@nl...> - 2004-06-11 11:43:34
|
Hi Blake, Thanks for your help and your answers! I haven't yet changed my setup actually; I'm still using a proxy. Didn't = yet find time to fiddle with the network bridge and wireless driver = settings... When I do, it tends to upset my VPN connection and other = things, which I need while working. So I never find the right moment. But the networking stability issues seemed to have resolved themselves = somehow and I now suspect the WinPCAP driver which I had been = experimenting with before, and without rebooting WinXP. I'm on a wired LAN today so I thought I'd give the briding-mode another = try and although it works really like a charm, after I shut down coLinux = my network was dead and I needed to reboot Windows. I'll stay with TAP networking for now :-) Either bridged or proxied. greetings, --Tim -----Original Message----- From: Blake [mailto:pb...@ta...] Sent: dinsdag 8 juni 2004 23:07 To: Leeuw van der, Tim Cc: col...@li... Subject: Re: [coLinux-users] Network dies after a while 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... |
|
From: David S <da...@cb...> - 2004-06-11 08:46:21
|
It works, Thanks Tim. ----- Original Message ----- From: "Leeuw van der, Tim" <tim...@nl...> To: "David S" <da...@cb...>; <col...@li...> Sent: Friday, June 11, 2004 03:38 PM Subject: RE: [coLinux-users] colinux login Hi, user: root passwd: (none) |
|
From: Leeuw v. d. T. <tim...@nl...> - 2004-06-11 08:38:45
|
Hi, user: root passwd: (none) doesn't that work? --Tim -----Original Message----- From: col...@li... [mailto:col...@li...]On Behalf Of David S Sent: vrijdag 11 juni 2004 10:29 To: col...@li... Subject: [coLinux-users] colinux login Hi! I just install colinux and using Debian-3.0r0.ext3.1gb, in colinux = console, it ask me to input colinux login and pasword. What should I do ? Thx, Dave ------------------------------------------------------- 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 |
|
From: David S <da...@cb...> - 2004-06-11 08:29:06
|
Hi! I just install colinux and using Debian-3.0r0.ext3.1gb, in colinux console, it ask me to input colinux login and pasword. What should I do ? Thx, Dave |
|
From: Alan B. <Nig...@ne...> - 2004-06-11 01:22:45
|
I don't know if this is much console, but I just got my XP & coLinux Debian image running, and by doing a bridge and DHCP only on the machine was able to pick up on either an ICS server, or a router DHCP server. was seemless once rebooted... just use the new debian image and set to use DHCP... ...Alan Patrick White wrote: >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 >slam the IP for that adapter to 192... I might have had to reboot or >disable/enable the adapter or something before it started working. Of >course, this was with two physical adapters, not one physical and the TAP >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. >>> >>> > > > >------------------------------------------------------- >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 > > > |
119 messages has been excluded from this view by a project administrator.
