Menu
▾
▴
colinux-users
|
From: Brendan J S. <Bre...@fa...> - 2004-07-08 05:05:05
|
I'm a first time user and have just installed the 0.6.1 release. I can get it to run in the terminal mode but I haven't had any success with the networking :( I have XP and from the docs I've read it seems that Bridged networking is the best method as NAT has a few limitations. Yes/No ??? One of the problems I have is that my firewall (and DHCP server) is 192.168.0.1. When I try to share the XP network conenction for other users it eventually gives me an error as it tries to assign 192.168.0.1 for the shared address (or the attaching interface). Does MS hardcode this value in???? If so then this sucks. What if one has more than one machine in this type of configuration on the local network ??? It doesn't scale. Maybe this is only intended for machines that connect direct to an ISP (eg. machine with modem, pstn or dsl, etc)??? Anyway, I can bridge the TAP interface and the 1GB Broadcomm interface but the TAP interface always has the red cross on it, even after I've started coLinux. So, has anyone got coLinux working with networking on XP using bridged mode? What about if another host has 192.168.0.1 on the network? Do I need to share my real interface? Any ideas, suggestions or thoughts muchly appreciated. Cheers, Brendan Simon. |
|
From: Ryan K. <rya...@co...> - 2004-07-08 06:17:20
|
Brendan, I had a similar problem (I have XP and a router). Bridging the connections work very well for me. I bridged the TAP device and the network card on my laptop that XP uses for its connection (I actually have a built in wired Ethernet card and a PCMCIA wireless card - the wireless card is the one that is actually used, so it is the one to bridge). My bridge is set up to be DHCP. I left the gateway setting in colinux as 192.168.0.1 so that it actually points to the router. Internet connection sharing is not enabled. Everything works well. Bridging is slightly voodooish to me, so I was surprised at how well it worked on the first try after I had failed at NAT for a while. Let me know if you want me to look up any other settings or try to remember any other details of how it works with my router and XP. Ryan -----Original Message----- From: col...@li... [mailto:col...@li...] On Behalf Of Brendan J Simon Sent: Wednesday, July 07, 2004 11:05 PM To: col...@li... Subject: [coLinux-users] Networking/XP issues I'm a first time user and have just installed the 0.6.1 release. I can get it to run in the terminal mode but I haven't had any success with the networking :( I have XP and from the docs I've read it seems that Bridged networking is the best method as NAT has a few limitations. Yes/No ??? One of the problems I have is that my firewall (and DHCP server) is 192.168.0.1. When I try to share the XP network conenction for other users it eventually gives me an error as it tries to assign 192.168.0.1 for the shared address (or the attaching interface). Does MS hardcode this value in???? If so then this sucks. What if one has more than one machine in this type of configuration on the local network ??? It doesn't scale. Maybe this is only intended for machines that connect direct to an ISP (eg. machine with modem, pstn or dsl, etc)??? Anyway, I can bridge the TAP interface and the 1GB Broadcomm interface but the TAP interface always has the red cross on it, even after I've started coLinux. So, has anyone got coLinux working with networking on XP using bridged mode? What about if another host has 192.168.0.1 on the network? Do I need to share my real interface? Any ideas, suggestions or thoughts muchly appreciated. Cheers, Brendan Simon. ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users |
|
From: Jonathan P. <j-g...@jo...> - 2004-07-08 09:04:43
|
From: "Brendan J Simon" <Bre...@fa...>
> I'm a first time user and have just installed the 0.6.1 release. I can
> get it to run in the terminal mode but I haven't had any success with
> the networking :(
>
> I have XP and from the docs I've read it seems that Bridged networking
> is the best method as NAT has a few limitations. Yes/No ???
As I see it, by avoiding NAT (as implemented under XP by
Internet Connection Sharing (ICS)) you give your Linux VM a
more 'first-class' status on your network, with its own IP
address etc. This can be either a good thing or a bad thing,
depending on your network.
> One of the problems I have is that my firewall (and DHCP server) is
> 192.168.0.1. When I try to share the XP network conenction for other
> users it eventually gives me an error as it tries to assign 192.168.0.1
> for the shared address (or the attaching interface). Does MS hardcode
> this value in????
> If so then this sucks. What if one has more than one machine in this
> type of configuration on the local network ??? It doesn't scale.
> Maybe this is only intended for machines that connect direct to an ISP
> (eg. machine with modem, pstn or dsl, etc)???
Yes. ICS is not meant to scale, it's as you guessed a home user solution.
These users don't even want to know what an IP address is.
If you have a firewall and a DHCP server on your network, you want to
use bridged networking anyway, which has none of these limitations.
> Anyway, I can bridge the TAP interface and the 1GB Broadcomm interface
> but the TAP interface always has the red cross on it, even after I've
> started coLinux.
What does your <network> element look like ? Here's what I use for
XP-bridged
networking :
<network index="0" type="tap" />
(do not use type='bridged' : it is supposed to make coLinux bridge itself
directly
to your real network card (so you don't have to use XP's bridge), but I
couldn't
get it to work)
> So, has anyone got coLinux working with networking on XP using bridged
mode?
Yes, it works fine for me.
> What about if another host has 192.168.0.1 on the network?
If you use XP's bridge and not ICS, there is no need to use 192.168.0.1.
Your
XP box keeps its IP address (actually, it's likely that the DHCP server will
give
it a new IP, since setting up the bridge makes it appear with a new MAC
address),
and the coLinux VM appears on the network with its own MAC address, which
allows the DHCP server to lease it an IP.
Hope this helps,
--Jonathan
|
Thanks for helping keep SourceForge clean.
X