Re: [coLinux-devel] BSOD, DDK dependency

[Ian C. B. <ia...@bl...>]

On Mon, Feb 02, 2004 at 03:27:20PM -0500, Remy Porter wrote:
> ICS isn't working, nor is bridging. Bridging however, completely knocks 
> my computer off of the Internet (though not the local network, I fail to 
> understand this). With ICS, I give TAP the .0.1 IP, then when I activate 
> ICS, I'm told that my external connection will be set to .0.1 (is this 
> intentional, or is it some slight change in instructions between 2k and 
> XP?) I run ifup eth0, then try and ping and nothing. Any other thoughts?

Win2k doesn't have ICS, that I'm aware of. It's an XP thing.

You enabled ICS on your external interface, right? Not the Tap
interface.

You should not be setting your "external" connection to 192.168.0.1.
ICS only NATs IPs in the 192.168.0.x netblock, with the ICS gateway
itself at 192.168.0.1 on the "internal" connection.

   External Interface (Local Area Connection 1 - Ethernet)
   (24.164.164.210)
   WindowsXP w/ICS NAT
   (192.168.0.1)
   Tap Interface (Local Area Connection 2 - Tap interface)
   (192.168.0.40)
   Linux Image
   
When you enable bridging, you need to assign the bridge interface the
"external" IP of your PC (or use DHCP, as per default).

   Bridged Interface
   (24.164.154.210)
   	Local Area Connection 1 (Ethernet)
	Local Area Connection 2 (Tap interface)

   	(24.164.154.211)
   	Linux Image

Both your host's Bridge Interface *and* the Linux Image have IP adresses
on the same external public segment, with the same default gateway. 
All packets that your Windows host sees will also be seen by the Linux 
image, and vice-versa.

A Tap interface has two sides: the host side and the guest side.
- With ICS, the host side needs to be assigned an IP address. The guest
  must be given an IP address on that same virtual ethernet segment
  (think of it as a crossover cable). The ICS host acts as the default 
  gateway for the guest to route through. 
- With a bridge, you add the host side to the bridge - no IP is needed 
  on the host side for layer-2 bridging. The guest side may take any IP
  on that external network, just as the host itself would (think of it
  as a hub to which both the host and the guest are plugged into on the
  outside). The host side, however DOES need to assign an IP address 
  to the bridge interface itself (think of it as a virtual interface on
  that same segment that the host uses to talk to that network).

I hope that didn't confuse you more than it helped.

You know, a colinux-users list might be in order here at some point. I
hate spamming *-devel lists with user support traffic.

- Ian C. Blenke <ia...@bl...>