From: <ch...@to...> - 2004-02-26 00:26:41
|
Do I understand this correctly? bridged would be like a forewarding alias on the physical card of the machine and on the same physical lan. And if using dhcp it would use the networks real dhcp server. tap would be used if you wanted to have windows host to share it's network connection and provide NAT and dhcp. chris |
From: Alejandro R. S. <asedeno@MIT.EDU> - 2004-02-26 00:38:36
|
On Wed, 2004-02-25 at 19:17, ch...@to... wrote: > Do I understand this correctly? > > bridged would be like a forewarding alias on the physical card of the > machine and on the same physical lan. And if using dhcp it would use the > networks real dhcp server. > > tap would be used if you wanted to have windows host to share it's network > connection and provide NAT and dhcp. > > chris The bridged connection essentially 'shares' the host's NIC, using winPCap to send out packets and listen for packets that it should receive. Your dhcp example is right on, it would use the real dhcp server. -Alejandro |
From: <ch...@to...> - 2004-02-26 00:50:46
|
so nothing to prevent connection sharing with tap right? I havn't messed with networking beyond comunicating with the host os yet. chris > > The bridged connection essentially 'shares' the host's NIC, using > winPCap to send out packets and listen for packets that it should > receive. Your dhcp example is right on, it would use the real dhcp > server. > > -Alejandro > > > > ------------------------------------------------------- > 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 > |
From: Alejandro R. S. <asedeno@MIT.EDU> - 2004-02-26 01:22:51
|
Yes, that's right. You can do just that if you're using the TAP network interface. On Wed, 2004-02-25 at 19:57, ch...@to... wrote: > I just mean that you can set windows to share the hardware > connection and windows will NAT to the tap connection. if the windows > machine is on a staticly assigned corporate lan that uses public addresses > and I am not the admin I can have windows assign a private ip to the > coLinux virtual network and provide NAT to access internet or real LAN. > > I guess the best thing would be for me to just give it a try when I get > some other things working the way I want. > > chris |