Re: [coLinux-users] Networking insights - bridging with multiple ips, no bridging with subnets, etc

[dizzi <dizzi@at...>]

Hi,
im using winpcap. (I have two real IP's and i need exact MAC addresses 
for both because our network policy)

So my guide:

1. remove TAP adapter, you dont need it.
2. set your real network card as usuall
3. install winpcap (there is not any visible change in system)
4. run colinux with parameters in config.xml like:
<network index="0" type="bridged" name="Local Area Connection" 
mac="xx:xx:xx:xx:xx:xx"/> (mac is optional, i think)
5. set correct values in /etc/network/interfaces and /etc/resolv.conf
6. now yours box acts like 2 computers

I had tried to make same with TAP, but i wasnt succesfull. I dont know 
way how to change bridge's MAC in windows (even registry change doesnt 
work!)

Btw try this too:
http://wiki.colinux.org/cgi-bin/coLinuxNetworking

cu,
dizzi


Chirayu Krishnappa wrote:
> Hi,
> 
> I have coLinux running on Win XP with the TAP adapter. I have an Ethernet
> card plugged into a router which connects to the internet.
> 
> I searched the archives and the net but I still only have a half baked
> solution. I am hoping someone has some insight to share.
> 
> I would like WinXP to keep its current IP address (192.168.1.100), DNS
> server etc as provided by the router (it recognizes the mac and gives it a
> static ip and forwards certain ports.)
> 
> I would like coLinux to have a different IP address on the same subnet (say
> 192.168.1.101).
> 
> Try 1 - bridging the Ethernet and the TAP adapters.
> If I do this - it seems that I cannot assign an IP address to the original
> Ethernet adapter - only to the Bridge. I assumed that the bridge of the 2
> ethernet adapters would function like a software hub - so that each of the
> adapters in the bridge could get their own ip address. I can assign a fixed
> different ip address on coLinux - but because the MAC address of the bridge
> is different - I have to reconfigure the router. I would prefer not to use
> windows bridging.
> 
> Try 2 - a separate subnet 
> I used the instructions from
> http://wiki.colinux.org/cgi-bin/YetAnotherNetworkConfiguration
> I can ping to external IP's from coLinux (eg. google) but name resolution
> does not work. Perhaps I need to install bind?
> Even so - I not have a 192.169.2.xx network - which is a different subnet.
> 
> Has someone gotten winpcap bridging to work? It seems that this may be a
> nicer solution.
> 
> Does anyone understand what is happening with the TAP adapter - I seem to be
> able to set a static IP (192.168.2.1) in the adapter properties but cannot
> use that it in coLinux for eth0. I need to use a different one (192.168.2.2)
> and make 192.168.2.1 the gateway. It seems like TAP is behaving as more than
> just an adapter which coLinux is listening to.
> 
> Any insights are appreciated.
> 
> Thanks,
> Chirayu.
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> coLinux-users mailing list
> coLinux-users@...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
> 
> 
> 
> 
> 

[coLinux-users] Networking insights - bridging with multiple ips, no bridging with subnets, etc

[Chirayu Krishnappa <chirayu@ch...>]

Hi,

I have coLinux running on Win XP with the TAP adapter. I have an Ethernet
card plugged into a router which connects to the internet.

I searched the archives and the net but I still only have a half baked
solution. I am hoping someone has some insight to share.

I would like WinXP to keep its current IP address (192.168.1.100), DNS
server etc as provided by the router (it recognizes the mac and gives it a
static ip and forwards certain ports.)

I would like coLinux to have a different IP address on the same subnet (say
192.168.1.101).

Try 1 - bridging the Ethernet and the TAP adapters.
If I do this - it seems that I cannot assign an IP address to the original
Ethernet adapter - only to the Bridge. I assumed that the bridge of the 2
ethernet adapters would function like a software hub - so that each of the
adapters in the bridge could get their own ip address. I can assign a fixed
different ip address on coLinux - but because the MAC address of the bridge
is different - I have to reconfigure the router. I would prefer not to use
windows bridging.

Try 2 - a separate subnet 
I used the instructions from
http://wiki.colinux.org/cgi-bin/YetAnotherNetworkConfiguration
I can ping to external IP's from coLinux (eg. google) but name resolution
does not work. Perhaps I need to install bind?
Even so - I not have a 192.169.2.xx network - which is a different subnet.

Has someone gotten winpcap bridging to work? It seems that this may be a
nicer solution.

Does anyone understand what is happening with the TAP adapter - I seem to be
able to set a static IP (192.168.2.1) in the adapter properties but cannot
use that it in coLinux for eth0. I need to use a different one (192.168.2.2)
and make 192.168.2.1 the gateway. It seems like TAP is behaving as more than
just an adapter which coLinux is listening to.

Any insights are appreciated.

Thanks,
Chirayu.

Re: [coLinux-users] Networking insights - bridging with multiple ips, no bridging with subnets, etc

[dizzi <dizzi@at...>]

Hi,
im using winpcap. (I have two real IP's and i need exact MAC addresses 
for both because our network policy)

So my guide:

1. remove TAP adapter, you dont need it.
2. set your real network card as usuall
3. install winpcap (there is not any visible change in system)
4. run colinux with parameters in config.xml like:
<network index="0" type="bridged" name="Local Area Connection" 
mac="xx:xx:xx:xx:xx:xx"/> (mac is optional, i think)
5. set correct values in /etc/network/interfaces and /etc/resolv.conf
6. now yours box acts like 2 computers

I had tried to make same with TAP, but i wasnt succesfull. I dont know 
way how to change bridge's MAC in windows (even registry change doesnt 
work!)

Btw try this too:
http://wiki.colinux.org/cgi-bin/coLinuxNetworking

cu,
dizzi


Chirayu Krishnappa wrote:
> Hi,
> 
> I have coLinux running on Win XP with the TAP adapter. I have an Ethernet
> card plugged into a router which connects to the internet.
> 
> I searched the archives and the net but I still only have a half baked
> solution. I am hoping someone has some insight to share.
> 
> I would like WinXP to keep its current IP address (192.168.1.100), DNS
> server etc as provided by the router (it recognizes the mac and gives it a
> static ip and forwards certain ports.)
> 
> I would like coLinux to have a different IP address on the same subnet (say
> 192.168.1.101).
> 
> Try 1 - bridging the Ethernet and the TAP adapters.
> If I do this - it seems that I cannot assign an IP address to the original
> Ethernet adapter - only to the Bridge. I assumed that the bridge of the 2
> ethernet adapters would function like a software hub - so that each of the
> adapters in the bridge could get their own ip address. I can assign a fixed
> different ip address on coLinux - but because the MAC address of the bridge
> is different - I have to reconfigure the router. I would prefer not to use
> windows bridging.
> 
> Try 2 - a separate subnet 
> I used the instructions from
> http://wiki.colinux.org/cgi-bin/YetAnotherNetworkConfiguration
> I can ping to external IP's from coLinux (eg. google) but name resolution
> does not work. Perhaps I need to install bind?
> Even so - I not have a 192.169.2.xx network - which is a different subnet.
> 
> Has someone gotten winpcap bridging to work? It seems that this may be a
> nicer solution.
> 
> Does anyone understand what is happening with the TAP adapter - I seem to be
> able to set a static IP (192.168.2.1) in the adapter properties but cannot
> use that it in coLinux for eth0. I need to use a different one (192.168.2.2)
> and make 192.168.2.1 the gateway. It seems like TAP is behaving as more than
> just an adapter which coLinux is listening to.
> 
> Any insights are appreciated.
> 
> Thanks,
> Chirayu.
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> coLinux-users mailing list
> coLinux-users@...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
> 
> 
> 
> 
> 

Re: [coLinux-users] Networking insights - bridging with multiple ips, no bridging with subnets, etc

[Tomas Fasth <tomas@eu...>]

Hi Chirayu,

just to give you a viable alternative to dizzi's approach, here is
what I did, using the bundled tap driver and XP's native network
bridge facility. I did not install winpcap, by the way.

After installation of CoLinux, in the property display of "my
network places", select the icon of your network card and the icon
of the TAP device, right click and select "create bridge". For a
simpler configuration you can then rename the TAP device to "tap" or
similar.

In the XML config file, set the network node to the following:
<network index="0" type="tap" name="tap" mac="F0:12:34:56:78:9F"/>
The mac address is from my own imagination and must be unique in
your local network. I'm not sure that is absolutely needed, though.

Part from the the above, you also need to edit
/etc/network/interfaces in the root file system.
Well, that did the trick for me anyway. Hope it helps.

Tomas

dizzi skrev:
> Hi,
> im using winpcap. (I have two real IP's and i need exact MAC addresses
> for both because our network policy)
> 
> So my guide:
> 
> 1. remove TAP adapter, you dont need it.
> 2. set your real network card as usuall
> 3. install winpcap (there is not any visible change in system)
> 4. run colinux with parameters in config.xml like:
> <network index="0" type="bridged" name="Local Area Connection"
> mac="xx:xx:xx:xx:xx:xx"/> (mac is optional, i think)
> 5. set correct values in /etc/network/interfaces and /etc/resolv.conf
> 6. now yours box acts like 2 computers
> 
> I had tried to make same with TAP, but i wasnt succesfull. I dont know
> way how to change bridge's MAC in windows (even registry change doesnt
> work!)
> 
> Btw try this too:
> http://wiki.colinux.org/cgi-bin/coLinuxNetworking
> 
> cu,
> dizzi
> 
> 
> Chirayu Krishnappa wrote:
> 
>> Hi,
>>
>> I have coLinux running on Win XP with the TAP adapter. I have an Ethernet
>> card plugged into a router which connects to the internet.
>>
>> I searched the archives and the net but I still only have a half baked
>> solution. I am hoping someone has some insight to share.
>>
>> I would like WinXP to keep its current IP address (192.168.1.100), DNS
>> server etc as provided by the router (it recognizes the mac and gives
>> it a
>> static ip and forwards certain ports.)
>>
>> I would like coLinux to have a different IP address on the same subnet
>> (say
>> 192.168.1.101).
>>
>> Try 1 - bridging the Ethernet and the TAP adapters.
>> If I do this - it seems that I cannot assign an IP address to the
>> original
>> Ethernet adapter - only to the Bridge. I assumed that the bridge of the 2
>> ethernet adapters would function like a software hub - so that each of
>> the
>> adapters in the bridge could get their own ip address. I can assign a
>> fixed
>> different ip address on coLinux - but because the MAC address of the
>> bridge
>> is different - I have to reconfigure the router. I would prefer not to
>> use
>> windows bridging.
>>
>> Try 2 - a separate subnet I used the instructions from
>> http://wiki.colinux.org/cgi-bin/YetAnotherNetworkConfiguration
>> I can ping to external IP's from coLinux (eg. google) but name resolution
>> does not work. Perhaps I need to install bind?
>> Even so - I not have a 192.169.2.xx network - which is a different
>> subnet.
>>
>> Has someone gotten winpcap bridging to work? It seems that this may be a
>> nicer solution.
>>
>> Does anyone understand what is happening with the TAP adapter - I seem
>> to be
>> able to set a static IP (192.168.2.1) in the adapter properties but
>> cannot
>> use that it in coLinux for eth0. I need to use a different one
>> (192.168.2.2)
>> and make 192.168.2.1 the gateway. It seems like TAP is behaving as
>> more than
>> just an adapter which coLinux is listening to.
>>
>> Any insights are appreciated.
>>
>> Thanks,
>> Chirayu.
>>
>>
>>
>> -------------------------------------------------------
>> SF email is sponsored by - The IT Product Guide
>> Read honest & candid reviews on hundreds of IT Products from real users.
>> Discover which products truly live up to the hype. Start reading now.
>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>> _______________________________________________
>> coLinux-users mailing list
>> coLinux-users@...
>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>
>>
>>
>>
>>
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> coLinux-users mailing list
> coLinux-users@...
> https://lists.sourceforge.net/lists/listinfo/colinux-users

Re: [coLinux-users] Networking insights - bridging with multiple ips, no bridging with subnets, etc

[Sam Moffatt <pasamio@gm...>]

Hey,

I've got a similar set up for work. I have one computer, e2342 (asset
ID code) and 'colinux'. e2342 is 172.19.5.40 and colinux is
172.19.5.40;

All that is needed to do is install coLinux normally, bridge the
supplied network interface with your normal LAN interface, then set
the IP on the bridge (not the interface) to be whatever the IP of your
computer should be. Then under coLinux, set up networking normally,
and give it the IP its assigned.

The network bridge actually relays any raw information it receives
onto the other network (unless it owns it). Its acting like a
transparent gateway of sorts. This way, the coLinux system appears to
be directly connected to the network, both inside and out.

Hope this helps!

Sam

On 4/23/05, Chirayu Krishnappa <chirayu@...> wrote:
> Hi,
>=20
> I have coLinux running on Win XP with the TAP adapter. I have an Ethernet
> card plugged into a router which connects to the internet.
>=20
> I searched the archives and the net but I still only have a half baked
> solution. I am hoping someone has some insight to share.
>=20
> I would like WinXP to keep its current IP address (192.168.1.100), DNS
> server etc as provided by the router (it recognizes the mac and gives it =
a
> static ip and forwards certain ports.)
>=20
> I would like coLinux to have a different IP address on the same subnet (s=
ay
> 192.168.1.101).
>=20
> Try 1 - bridging the Ethernet and the TAP adapters.
> If I do this - it seems that I cannot assign an IP address to the origina=
l
> Ethernet adapter - only to the Bridge. I assumed that the bridge of the 2
> ethernet adapters would function like a software hub - so that each of th=
e
> adapters in the bridge could get their own ip address. I can assign a fix=
ed
> different ip address on coLinux - but because the MAC address of the brid=
ge
> is different - I have to reconfigure the router. I would prefer not to us=
e
> windows bridging.
>=20
> Try 2 - a separate subnet
> I used the instructions from
> http://wiki.colinux.org/cgi-bin/YetAnotherNetworkConfiguration
> I can ping to external IP's from coLinux (eg. google) but name resolution
> does not work. Perhaps I need to install bind?
> Even so - I not have a 192.169.2.xx network - which is a different subnet=
.
>=20
> Has someone gotten winpcap bridging to work? It seems that this may be a
> nicer solution.
>=20
> Does anyone understand what is happening with the TAP adapter - I seem to=
 be
> able to set a static IP (192.168.2.1) in the adapter properties but canno=
t
> use that it in coLinux for eth0. I need to use a different one (192.168.2=
.2)
> and make 192.168.2.1 the gateway. It seems like TAP is behaving as more t=
han
> just an adapter which coLinux is listening to.
>=20
> Any insights are appreciated.
>=20
> Thanks,
> Chirayu.
>=20
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
> _______________________________________________
> coLinux-users mailing list
> coLinux-users@...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

RE: [coLinux-users] Networking insights - bridging with multiple ips, no bridging with subnets, etc

[Chirayu Krishnappa <chirayu@ch...>]

Awesome. This works great and that's what I'm doing now. Thanks.

Chirayu.



-----Original Message-----
From: colinux-users-admin@...
[mailto:colinux-users-admin@...] On Behalf Of Sam =
Moffatt
Sent: Saturday, April 23, 2005 10:00 PM
To: Chirayu Krishnappa
Cc: colinux-users@...
Subject: Re: [coLinux-users] Networking insights - bridging with =
multiple
ips, no bridging with subnets, etc

Hey,

I've got a similar set up for work. I have one computer, e2342 (asset
ID code) and 'colinux'. e2342 is 172.19.5.40 and colinux is
172.19.5.40;

All that is needed to do is install coLinux normally, bridge the
supplied network interface with your normal LAN interface, then set
the IP on the bridge (not the interface) to be whatever the IP of your
computer should be. Then under coLinux, set up networking normally,
and give it the IP its assigned.

The network bridge actually relays any raw information it receives
onto the other network (unless it owns it). Its acting like a
transparent gateway of sorts. This way, the coLinux system appears to
be directly connected to the network, both inside and out.

Hope this helps!

Sam

On 4/23/05, Chirayu Krishnappa <chirayu@...> wrote:
> Hi,
>=20
> I have coLinux running on Win XP with the TAP adapter. I have an =
Ethernet
> card plugged into a router which connects to the internet.
>=20
> I searched the archives and the net but I still only have a half baked
> solution. I am hoping someone has some insight to share.
>=20
> I would like WinXP to keep its current IP address (192.168.1.100), DNS
> server etc as provided by the router (it recognizes the mac and gives =
it a
> static ip and forwards certain ports.)
>=20
> I would like coLinux to have a different IP address on the same subnet
(say
> 192.168.1.101).
>=20
> Try 1 - bridging the Ethernet and the TAP adapters.
> If I do this - it seems that I cannot assign an IP address to the =
original
> Ethernet adapter - only to the Bridge. I assumed that the bridge of =
the 2
> ethernet adapters would function like a software hub - so that each of =
the
> adapters in the bridge could get their own ip address. I can assign a
fixed
> different ip address on coLinux - but because the MAC address of the
bridge
> is different - I have to reconfigure the router. I would prefer not to =
use
> windows bridging.
>=20
> Try 2 - a separate subnet
> I used the instructions from
> http://wiki.colinux.org/cgi-bin/YetAnotherNetworkConfiguration
> I can ping to external IP's from coLinux (eg. google) but name =
resolution
> does not work. Perhaps I need to install bind?
> Even so - I not have a 192.169.2.xx network - which is a different =
subnet.
>=20
> Has someone gotten winpcap bridging to work? It seems that this may be =
a
> nicer solution.
>=20
> Does anyone understand what is happening with the TAP adapter - I seem =
to
be
> able to set a static IP (192.168.2.1) in the adapter properties but =
cannot
> use that it in coLinux for eth0. I need to use a different one
(192.168.2.2)
> and make 192.168.2.1 the gateway. It seems like TAP is behaving as =
more
than
> just an adapter which coLinux is listening to.
>=20
> Any insights are appreciated.
>=20
> Thanks,
> Chirayu.
>=20
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real =
users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
> _______________________________________________
> coLinux-users mailing list
> coLinux-users@...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id=14396&op=3Dick
_______________________________________________
coLinux-users mailing list
coLinux-users@...
https://lists.sourceforge.net/lists/listinfo/colinux-users