Re: [coLinux-devel] tap index

[<ch...@to...>]

> On Thursday 26 February 2004 17:48, ch...@to... wrote:
>> I am working on a dual boot setup native or coLinux. I have the fstab
>> situation worked out with so sym link tricks. The problem I am having
>> now
>> is with networking. I want to use eth0 with one config for native boot
>> (same IP address the windows setup uses to comunicate with outside) and
>> when under coLinux use a different interface on a private inside lan and
>> have window NAT it out. I will then work out the route issue in linux.
>>
>> I tried
>>
>> <network index="1" type="tap" name="TAP"></network>
>>
>> but when it booted coLinux ifconfig showed that etho was up and ther was
>> no eth1
>>
>> I realize that only 1 device is visable in each boot mode.
>>
>> I also saw this in the change log
>>
>>         I also prepared the ground for supporting more than one network
>> device
>>         (i.e, eth1, eth2, etc.), but it is not yet completed.
>>
>> is this the problem or is there some other workaround anyone can think
>> of?
>> I want to be able to use static addresses and I only have one address
>> for
>> comunicating with the outside world that is why I want to have windows
>> NAT
>> the address when in coLinux and when Native use the same address as in
>> the
>> windows config.
> If you want a nice solution to switching files around dependent on your
> environment check out http://hprofile.sourceforge.net
> Essentially what it allows for is determining a profile to be used through
> kernel parameters or checking for devices that would exist in one
> environment, but not another etc (you need to customise that through
> scripts). It switches to a runlevel accordingly and takes care of all of
> the
> symlinks for you. Works fantastic.

Looks interesting. do the kernel parameters pass through coLinux daemon
fine? I saw something a while back that someone couldn't get ro to pass.
right now I am using the fact that topologilinux uses an initrd to boot so
I have links to the real devices on the initrd and the coLinux devices in
the directory that is the mountpoint for the initrd. That seems to work
good for switching / and swap between /dev/cobd? and /dev/loop? I'll
definatly look into hprofile further.

chris

>
>>
>> I am taking notes as I do this and should have a good HowTo to post on
>> the
>> wiki (which is looking very nice, very quickly)
>>
>> I am using Topologilinux which runs off of loopback files on the windows
>> partition. Booting both ways so far but I want to get networking and
>> maby
>> floppy and cdrom access (I set them up in the rootfs but need to figure
>> out the colinux.xml setup for them.
>>
>> chris
>>
>>
>> -------------------------------------------------------
>> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
>> Build and deploy apps & Web services for Linux with
>> a free DVD software kit from IBM. Click Now!
>> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
>> _______________________________________________
>> coLinux-devel mailing list
>> coL...@li...
>> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>