Ok. I'm going to take the shotgun and deal with this problem directly. The=
thing about networking is that there are 10 million different ways to deal=
with the same issue. The way that I like to deal with laptop movement and=
keeping colinux working while the network changes is to set up a TAP networ=
on the local laptop and have it stay up all the time. Then, you route the=
network that the TAP network sits on to the laptop from whatever router the=
laptop is connected to. That will allow the coLinux system to reach the=20
Internet, as long as your router supports NAT management. The image is kind=
of like this:
Internet <----------> NAT Router <-----------> Windows Host=20
e1 i1 e1
Cable conn Internet Net TAP network
The "e1" and "i1" names refer to the external and internal networks=20
respectively, and that will only exist on the Windows host. E1 being your=
physical ethernet card, and i1 being the TAP network.
The only problem with this setup is that your Windows host will have to be=
configured for routing (usually turned off by default), and your NAT router=
needs to be configured to route the TAP network towards the Windows host=20
(not hard to do, but needs to be done if coLinux is to reach the Internet).=
The benefit of this setup is that the TAP network will always be up (as lon=
as your coLinux system is on), and it will always have the same addresses.=
You need to configure the NAT router to route that network for each network=
that you put your laptop on. The other solution is to tell your e1 address=
on your Windows host to run ICS for the rest of the system (including the=
TAP network) so that the TAP network can reach the Internet. I haven't=20
actually tried this yet, but I see no reason why it wouldn't work.
On 9/13/05, Andy Heath <a.k.heath@...> wrote:
> I'm fairly ok with unix but the complexities of networking
> sometimes are too much for me to figure out.
> So I have things running great - w2k with the TAP adapter
> and ICS using the Debian woody image. But this is a
> laptop so I want to be able to use colinux offline
> but still networked to the windows part of the machine.
> How can I set this up so it will work when the main
> network connection isn't up (or even present - the device
> goes away when the pcmcia wireless card isn't in) ?
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle=20
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q=
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> coLinux-users mailing list