From: Brendan S. <Brendan@BrendanSimon.com> - 2005-11-22 18:54:00
|
I have WinXP and coLinux (latest devel snapshot). 1. I can't get my Linux to connect to my TAP driver. The TAP driver says cable unplugged, but the colinux console says it attached OK. BTW, I'm using WinXP native bridging. Any ideas??? 2. Can I connect to coLinux without an Ethernet connection. i.e. without an Ethernet Carrier Detect. eg. In a plane with no networking. If so, how? Thanks, Brendan. |
From: Ian B. <ib...@gm...> - 2005-11-23 01:33:43
|
I have a feeling that the native bridging make things really confusing. WHe= n you native bridge an adapter, you literally have to ignore what the native adapter line in the Network Properties control panel says. Once you start u= p coLinux, check your bridged adapter in the properties sheet, and you should see "connected". Any network adapter in that bridge will *always* say unplugged, even if its not. The only way I know to connect to coLinux without networking is through the console and through the serial terminal ports, but the latter is not functional yet. Ian On 11/22/05, Brendan Simon <Br...@br...> wrote: > > I have WinXP and coLinux (latest devel snapshot). > > 1. I can't get my Linux to connect to my TAP driver. The TAP driver > says cable unplugged, but the colinux console says it attached OK. BTW, > I'm using WinXP native bridging. Any ideas??? > > 2. Can I connect to coLinux without an Ethernet connection. i.e. > without an Ethernet Carrier Detect. eg. In a plane with no networking. > If so, how? > > Thanks, > Brendan. > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the JBoss Inc. Get Certified Today > Register for a JBoss Training Course. Free Certification Exam > for All Training Attendees Through End of 2005. For more info visit: > http://ads.osdn.com/?ad_id=3D7628&alloc_id=3D16845&op=3Dclick > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
From: Alex <co...@al...> - 2005-11-23 23:34:06
|
TAP and Bridging are two completely separate methods for connecting coLinux to something... I suggest you also bother to read up on NAT to understand how your colinux session can access the internet. In short, ###### ####### ####### # # ### # # # # ## ## ### # # # # # # # # ### ###### # ##### # # # # # # # # # # # # # # # # ### # # # # # # ### On Wed, 23 Nov 2005, Brendan Simon wrote: > I have WinXP and coLinux (latest devel snapshot). > > 1. I can't get my Linux to connect to my TAP driver. The TAP driver says > cable unplugged, but the colinux console says it attached OK. BTW, I'm using > WinXP native bridging. Any ideas??? > > 2. Can I connect to coLinux without an Ethernet connection. i.e. without an > Ethernet Carrier Detect. eg. In a plane with no networking. If so, how? > > Thanks, > Brendan. > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the JBoss Inc. Get Certified Today > Register for a JBoss Training Course. Free Certification Exam > for All Training Attendees Through End of 2005. For more info visit: > http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > |
From: Brendan S. <Brendan@BrendanSimon.com> - 2005-11-24 00:51:56
|
That's a bit harsh. I have read the docs and I've had coLinux 0.6.2 with bridged XP working without any problems. I'm now using the development snapshot and can't get it working using the same techniques that I used with 0.6.2, so I'm wondering if anything has changed, or if anyone has seen this before and found a solution. The new config file seems to be more picky that previously but I do understand it is a development snapshot and there will be problems. I'm just wondering if I am hitting one of these problems and want to know how to work around it. Thanks for your assistance. Brendan. Alex wrote: > TAP and Bridging are two completely separate methods for connecting > coLinux to something... I suggest you also bother to read up on NAT > to understand how your colinux session can access the internet. > > In short, > > > ###### ####### ####### # # ### > # # # # ## ## ### > # # # # # # # # ### > ###### # ##### # # # # > # # # # # # > # # # # # # ### > # # # # # # ### > > > > On Wed, 23 Nov 2005, Brendan Simon wrote: > >> I have WinXP and coLinux (latest devel snapshot). >> >> 1. I can't get my Linux to connect to my TAP driver. The TAP driver >> says cable unplugged, but the colinux console says it attached OK. >> BTW, I'm using WinXP native bridging. Any ideas??? >> >> 2. Can I connect to coLinux without an Ethernet connection. i.e. >> without an Ethernet Carrier Detect. eg. In a plane with no >> networking. If so, how? >> >> Thanks, >> Brendan. >> >> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by the JBoss Inc. Get Certified Today >> Register for a JBoss Training Course. Free Certification Exam >> for All Training Attendees Through End of 2005. For more info visit: >> http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click >> _______________________________________________ >> coLinux-users mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-users >> >> >> |