From: Brendan S. <Brendan@BrendanSimon.com> - 2006-07-21 00:07:59
|
Hi, I'm using coLinux-0.7.1-devel-20051203 (linux-2.6.12). At the time 0.6.2 (or was it 0.6.1) was the latest stable and the networking was quite slow so I moved to the development snapshot. Since then 0.6.3 and 0.6.4 (linux-2.6.11) have been released. Is the 0.7.x branch still being developed. If so where can I find snapshots and what is the difference between that and the 0.6.x branch. Are the changes that were in 0.7.1 now in the latest 0.6.x? If so, would I be better going _back_ to the 0.6.x version? Maybe that depends on whether 0.7.x exists or not ??? One thing I am after is much better integration and bridging with the Windows Wireless Networking. I don't know if coLinux development has any affect on that, but if so then I guess I would like to use coLinux which best supports wireless on WinXP :) Talking of networking. TAP v WinPCAP. * I think I understand how TAP works. It basically is a pipe between the Windows TAP driver and the coLinux daemon right, but since TAP looks like a real Windows Ethernet driver it means it can be easily bridged using WinXP. * I'm a little vague on how WinPCAP works. It does not show up as a Windows network device, so I assume it is some kind of driver or service that attaches to an existing driver or the network stack, and the coLinux daemon can insert/monitor/remove packets through some kind of WinPCAP API. Is that correct ??? Thanks, Brendan. |
From: Holger K. <hol...@gm...> - 2006-07-21 06:14:00
|
Brendan Simon schrieb: > * I think I understand how TAP works. It basically is a pipe > between the Windows TAP driver and the coLinux daemon right, but > since TAP looks like a real Windows Ethernet driver it means it > can be easily bridged using WinXP. Right. > * I'm a little vague on how WinPCAP works. It does not show up as a > Windows network device, so I assume it is some kind of driver or > service that attaches to an existing driver or the network stack, > and the coLinux daemon can insert/monitor/remove packets through > some kind of WinPCAP API. Is that correct ??? Yes. It is attached to a Network Interface like a protocol. Look at the settings of your Interface, you will find an new entry. |
From: Brendan S. <Brendan@BrendanSimon.com> - 2006-07-21 13:47:59
|
Holger Krull wrote: > >> * I'm a little vague on how WinPCAP works. It does not show up as a >> Windows network device, so I assume it is some kind of driver or >> service that attaches to an existing driver or the network stack, >> and the coLinux daemon can insert/monitor/remove packets through >> some kind of WinPCAP API. Is that correct ??? > > Yes. > It is attached to a Network Interface like a protocol. Look at the > settings of your Interface, you will find an new entry. Oh, OK. Presumably the "Network Monitor Driver", yes? |
From: Holger K. <hol...@gm...> - 2006-07-21 13:50:11
|
Brendan Simon schrieb: > Holger Krull wrote: >>> and the coLinux daemon can insert/monitor/remove packets through >>> some kind of WinPCAP API. Is that correct ??? >> Yes. >> It is attached to a Network Interface like a protocol. Look at the >> settings of your Interface, you will find an new entry. > > Oh, OK. Presumably the "Network Monitor Driver", yes? Yes |
From: Brendan S. <Brendan@BrendanSimon.com> - 2006-07-21 14:36:17
|
Holger Krull wrote: > Brendan Simon schrieb: >> Holger Krull wrote: >>>> and the coLinux daemon can insert/monitor/remove packets through >>>> some kind of WinPCAP API. Is that correct ??? >>> Yes. >>> It is attached to a Network Interface like a protocol. Look at the >>> settings of your Interface, you will find an new entry. Does WinPCap translate MAC addresses? I presume so as a MAC address can be specified. I need this requirement so that my DHCP server will allocate a different address to coLinux and WinXP. |
From: Holger K. <hol...@gm...> - 2006-07-21 14:40:16
|
Brendan Simon schrieb: > Holger Krull wrote: >> Brendan Simon schrieb: >>> Holger Krull wrote: >>>>> and the coLinux daemon can insert/monitor/remove packets through >>>>> some kind of WinPCAP API. Is that correct ??? >>>> Yes. >>>> It is attached to a Network Interface like a protocol. Look at the >>>> settings of your Interface, you will find an new entry. > > Does WinPCap translate MAC addresses? I presume so as a MAC address can > be specified. Yes. Keep in mind that in your setup you may also use a wintap interface without bridgeing and make Windows route between colinux and wireless. This would avoid having a bridge with a wireless interface. |
From: Brendan S. <Brendan@BrendanSimon.com> - 2006-07-22 02:45:36
|
Holger Krull wrote: >> Does WinPCap translate MAC addresses? I presume so as a MAC address can >> be specified. > > Yes. Great. So any idea why does my DHCP server on my wireless router serve coLinux the _same_ address as the WinXP host ??? The only thing I can think of is that the WinXP MAC is getting through to the router, not the WinPCap MAC as specified in the config file. > Keep in mind that in your setup you may also use a wintap interface > without bridgeing and make Windows route between colinux and wireless. > This would avoid having a bridge with a wireless interface. Yep, I had this in mind. One of my options was to have a static 10.x.y.z network for my coLinux vm and the WinXP host, _AND_ have the WinXP host obtain its "real" IP address from DHCP. This allows me to take my laptop to work, home, etc. The problem I have is that WinXP does not allow me to set multiple IP addresses ("Add" button is greyed out) for an interface if DHCP is selected. If DHCP is disabled, I can add as many as I like. Maybe I'm being a Windows ignoramous and trying to do everything through the GUI instead of trying some command line settings? Problem is I _am_ a Windows ingoramous and don't know the command line very well :) :( Does WinXP be setup so that an interface (possibly a bridge) can have a DHCP assigned IP _and_ a static (or multiple static) IP addresses ??? If so, how ??? Thanks heaps, Brendan. |
From: Holger K. <hol...@gm...> - 2006-07-22 07:28:03
|
Brendan Simon schrieb: > Holger Krull wrote: >>> Does WinPCap translate MAC addresses? I presume so as a MAC address can >>> be specified. >> Yes. > > Great. So any idea why does my DHCP server on my wireless router serve > coLinux the _same_ address as the WinXP host ??? The only thing I can > think of is that the WinXP MAC is getting through to the router, not the > WinPCap MAC as specified in the config file. I don't know, maybe wireless interfaces are somewhat different. >> Keep in mind that in your setup you may also use a wintap interface >> without bridgeing and make Windows route between colinux and wireless. >> This would avoid having a bridge with a wireless interface. > > Yep, I had this in mind. One of my options was to have a static > 10.x.y.z network for my coLinux vm and the WinXP host, _AND_ have the > WinXP host obtain its "real" IP address from DHCP. This allows me to > take my laptop to work, home, etc. > > The problem I have is that WinXP does not allow me to set multiple IP > addresses ("Add" button is greyed out) for an interface if DHCP is > selected. If DHCP is disabled, I can add as many as I like. You do not need to give the additional private ip to your existing network card. Use the tap interface for that. With this setup you do not need any bridge at all. |