Re: [coLinux-users] Private Network and wireless trouble

[Henry N. <Hen...@Ar...>]

Hello Mike,

Mike schrieb:
> Hi,
> I've been trying to get the 'private network' design, as shown in the Network
> Howto (section 'Keep Windows off the network -- surf via Linux') to work. On my
> pc with wired internet connection it works like a charm, but now I'm trying to
> set it up on a pc with a wireless connection. Tried all kind of variants (w/wo
> loopback, taptun/pcap-bridge, various IP configurations, w/wo promisc) but did
> not succeed to get it to work. 
> 
> OS: WinXP pro and Archlinux on Colinux (0.7.2)
> 
> I connect to internet through a router using wep encryption and fixed IP 
> adresses.
> 
> The host has a wifi card (ZyDas zd1211, usb), 
> -MAC 00:11:E2:00:EA:93
> -ip 192.168.2.23 (name PhysicalNetwork)
> -gw 192.168.2.254
> -pcap-bridge 192.168.2.24 (Colinux-TAP-external-network)
> -taptun 192.168.100.1 (Colinux-TAP-guest-network)
> 
> 
> The guest (Archlinux, runs squid),has
> eth0: 192.168.2.25  (name Colinux-TAP-external-network)
> eth1: 192.168.100.2 (name Colinux-TAP-guest-network)
> 
> The connection to the guest through 192.168.100.1-192.168.100.2 works.
> 
> Now the simple question is: how do I get it to work?
> More precise:
> -When I use a loopback adapter in windows, what would the design look like (e.g.
> which IP addresses and gw's I should use ). What type of bridge I should use
> (the ICS or bridge) between PhysicalNetwork and Colinux-TAP-host?
> 
> -Can I also use pcap-bridge adapter on the client, to inject directly into the
> PhysicalNetwork adapter, should I, in that case, install the wireless extensions
> (iwconfig, etc) in the guest, or would the connection use the wireless-settings
> of the host? Should I provide a MAC address for Colinux-TAP-host (a unique one
> or a copy of the PhysicalNetwork adapter)
> 
> Lots of questions, but I would love to get this to work...

true lot of. :-)

Hope, we talk about a scene, that was in wiki as
http://colinux.wikia.com/wiki/Network#TAP_-_Private_Connection_with_Hosting_OS

First you should configure the networks separately. I see, eth1 is
working for you - the connection between host and guest. Disable eth1
while you configure the eth0. After both of network works separately,
you can enable both at same time.

eth0 should not bridge to any "TAP". The "pcap-bridge 192.168.2.24"
should configure to your real LAN "(name PhysicalNetwork)" or the name
of WiFI card. But, I'm afraid pcap-bridge does not work for your card.
Some times helps to disable CRC checksum in this card. Some Access
points don't allow to injecting different MAC on same air channel. In
that case pcap-bridge would never work.

Check the outgoing and response of network with
http://www.wireshark.org/ on your WiFi. Test to send a Ping to your
router, and watch the answer from your router. I currently not know the
state of wireshark. Have it a option to inject (send) ping packets? If
yes, try it with this tool. It uses also the WinPcap, the same coLinux
use for pcap-bridge.

An other way would better work: Let windows bridge the WiFi with you
second TAP (Colinux-TAP-external-network), hope this is the name. You
needs to have 2 Win32-TAP drivers for that scenario and you must give
the right names in the colinux config, autodetection does not work with
more as one TAP-Win32.

Don't use the same MAC more as ones, this would never work.

iwconfig is not usable inside coLinux. The client does not know the
external hardware (wifi, ethernet cable, or DSL modem).

-- 
Henry N.