From: Brendan S. <Brendan@BrendanSimon.com> - 2006-07-20 06:43:57
|
Hi, I have a wireless adaptor attached to a WinXP bridge. I'm using WinPCAP for coLinux as I believe that works better than TAP with wireless networks. I have two issues. 1) My WinXP gets a DHCP assigned IP address of 10.1.1.3 from the wireless access point. My colinux can also get an IP addresses assigned from the same access point, but unfortunately it is the exact same IP address. NOT GOOD. I have assigned a different MAC for the device and ifconfig shows the correct MAC which is different to the wireless MAC. Anyone know what's going on? My only solution at the moment is to give static IP address to coLinux. 2) I have a VNC connection from WinXP to coLinux. Every few minutes or so, the network connection between WinXP and coLinux is lost causing my VNC viewer to die. Sure my vnc session is still running and I can reconnect but having to do that every few minutes is a real pain in the a*se. Anyone know what's going on here? I don't have these problems when connecting using the Ethernet LAN so I suspect it is something to do with the Wireless stuff and/or the WinXP bridge ??? Is it possible to have two static IP addresses for a private coLinux subnet (eg. 10.1.1.3 for WinXP and 10.1.1.4 for coLinxu) _AND_ also have the WinXP use DHCP to get another IP address and gateway info. The only way I can set multiple addresses on WinXP is if DHCP is disabled. The idea is that I can use DHCP servers at home and at work (I have a notebook pc). Thanks, Brendan. |
From: Holger K. <hol...@gm...> - 2006-07-20 07:12:57
|
Brendan Simon schrieb: > I have a wireless adaptor attached to a WinXP bridge. I'm using WinPCAP > for coLinux as I believe that works better than TAP with wireless > networks. I have two issues. If you use WinPCAP what do you need the bridge for? Isn't WinPCAP directly attached to the wireless interface? |
From: Brendan S. <Brendan@BrendanSimon.com> - 2006-07-20 07:20:22
|
Holger Krull wrote: > Brendan Simon schrieb: >> I have a wireless adaptor attached to a WinXP bridge. I'm using WinPCAP >> for coLinux as I believe that works better than TAP with wireless >> networks. I have two issues. > > If you use WinPCAP what do you need the bridge for? Isn't WinPCAP > directly attached to the wireless interface? Not sure. I'm used to the TAP interface so that model is in my head. I'll try removing it from the bridge to see if that makes any difference. |
From: Brendan S. <Brendan@BrendanSimon.com> - 2006-07-21 16:35:50
|
Brendan Simon wrote: > Holger Krull wrote: >> Brendan Simon schrieb: >>> I have a wireless adaptor attached to a WinXP bridge. I'm using WinPCAP >>> for coLinux as I believe that works better than TAP with wireless >>> networks. I have two issues. >> If you use WinPCAP what do you need the bridge for? Isn't WinPCAP >> directly attached to the wireless interface? > > Not sure. I'm used to the TAP interface so that model is in my head. > I'll try removing it from the bridge to see if that makes any difference. OK, so I figured out what was going on (I think). 1. My Wireless driver (Intel Pro/Wireless 2915ABG) does NOT work with WinPCAP. I confirmed this with Ethereal not seeing my pings. 2. The setup I had that was working was using WinXP bridge with both LAN and WLAN devices in the bridge, and my coLinux config set to use the WinPCAP attached to the LAN device. Since no network cable was plugged in, it did not have a carrier. I think this is why the connection was continually dropping out, however it was very periodic so I think software was involved (eg. periodic retry and/or auto negotiation, etc). 3. The only way to get it to work was using the WinXP network bridge (I didn't try linux bridging). So, once I worked out that I was connecting to the LAN device, I decided to connect to the bridge device. This seems to be much more reliable as this interface is always up :) The only problem is that DHCP is repsonding with the same IP address of the WinXP box so I get lots of duplicate address messages :( This is presumably caused by the Bridge MAC address being sent in all packets and not the WinPCap MAC address. I'm not sure why or how to fix this!!! 4. I thought I could use the TAP driver, but that in the bridge and use WinPCap to attach to the TAP driver, but that didn't work. If the TAP driver did work with WinPCap then _maybe_ I could get a different MAC address and thus a different IP address via DHCP. Just speculating. Does anyone know why TAP does not work with WinPCap. If it did, we probably wouldn't need WinPCap right ??? Cheers, Brendan. |
From: Holger K. <hol...@gm...> - 2006-07-21 16:49:23
|
Brendan Simon schrieb: > 3. The only way to get it to work was using the WinXP network bridge (I > didn't try linux bridging). So, once I worked out that I was connecting > to the LAN device, I decided to connect to the bridge device. This > seems to be much more reliable as this interface is always up :) The > only problem is that DHCP is repsonding with the same IP address of the > WinXP box so I get lots of duplicate address messages :( This is > presumably caused by the Bridge MAC address being sent in all packets > and not the WinPCap MAC address. I'm not sure why or how to fix this!!! > 4. I thought I could use the TAP driver, but that in the bridge and use > WinPCap to attach to the TAP driver, but that didn't work. If the TAP > driver did work with WinPCap then _maybe_ I could get a different MAC > address and thus a different IP address via DHCP. Just speculating. > > Does anyone know why TAP does not work with WinPCap. If it did, we > probably wouldn't need WinPCap right ??? I really don't understand your setup. A winpcap attached to tap is nonsense. You have Win XP, so bridging works. The most common solution would be to bridge a TAP interface to your wireless connection, and configure colinux to use tap. Does this work? |
From: Brendan S. <Brendan@BrendanSimon.com> - 2006-07-22 02:56:13
|
Holger Krull wrote: > Brendan Simon schrieb: >> 4. I thought I could use the TAP driver, but that in the bridge and use >> WinPCap to attach to the TAP driver, but that didn't work. If the TAP >> driver did work with WinPCap then _maybe_ I could get a different MAC >> address and thus a different IP address via DHCP. Just speculating. >> >> Does anyone know why TAP does not work with WinPCap. If it did, we >> probably wouldn't need WinPCap right ??? > > I really don't understand your setup. > A winpcap attached to tap is nonsense. > You have Win XP, so bridging works. > > The most common solution would be to bridge a TAP interface to your > wireless connection, and configure colinux to use tap. Does this work? It was just a thought, as I view TAP as a virtual interface, and the interface is UP all the time. The problem was that WinXP bridging does not seem to work with my wireless card, so I thought WinCAP attached to another driver (TAP and bridged) might do the trick. It was just an idea ;-) I'm not sure if attaching WinCAP to my bridge interface actually solved the problem. It may have just made the drop-outs less frequent. My VNC was lost when I returned to my laptop in the morning, but I'm still testing :) My goals are: * Be able to use WinXP laptop with coLinux using LAN or WLAN, at home, work, cafes, airports, etc. * IP address for WinXP to be assigned via DHCP. * IP address for coLinux to be assigned either: - via DHCP - static assignment on different subnet (10.1.1.x) The key to me is: * be able to use either LAN or WLAN transparently without changing config files or running scripts, etc. * setup WinXP for DHCP and static IP addresses. Thanks, Brendan. |
From: Henry N. <Henry.Ne@Arcor.de> - 2006-07-21 17:02:04
|
Brendan Simon wrote: > 4. I thought I could use the TAP driver, but that in the bridge and use > WinPCap to attach to the TAP driver, but that didn't work. If the TAP > driver did work with WinPCap then _maybe_ I could get a different MAC > address and thus a different IP address via DHCP. Just speculating. > > Does anyone know why TAP does not work with WinPCap. If it did, we > probably wouldn't need WinPCap right ??? The TAP (from coLinux) works only between coLinux guest and the windows host. This is no good idea to listen with winpcap on coLinux-TAP device. The TAP device has no "connection" to the outside (LAN or WLAN). Why would you would use the TAP with winpcap? Listen with coLinux on coLinux self? Winpcap should only listen on real networking adapters, for sample LAN or WLAN cards. Additional you could use the TAP adapter as sepate network between your coLinux and Windows. With different network, please! For such scenario do you need to add a eth1 to your colinux config. The winpcap has a mode "no Promiscuous", this is a mode for some WLAN cards. Try to set promisc="false" in your XML. This option is new in coLinux 0.6.4, read your NEWS.TXT from installation. Last: The network type "slirp" was the preffered networking type for WLAN cards. This is more simple to configure, and use no additionals MAC and no additional IP on your WLAN card. See: http://wiki.colinux.org/mediawiki/index.php/Network#Debian_interface_setup_for_static_SLiRP -- Henry Nestler |
From: Brendan S. <Brendan@BrendanSimon.com> - 2006-07-22 03:08:44
|
Henry Nestler wrote: > Additional you could use the TAP adapter as sepate network between your > coLinux and Windows. With different network, please! For such scenario > do you need to add a eth1 to your colinux config. I understand the concept, but how do I do that with WinXP interfaces set to DHCP ??? How do I route the coLinux to WinXP. The only way I can think of is with a secondary static IP on the WinXP box but I can't seem to do that if DHCP is enabled. > The winpcap has a mode "no Promiscuous", this is a mode for some WLAN > cards. Try to set promisc="false" in your XML. This option is new in > coLinux 0.6.4, read your NEWS.TXT from installation. I'm running 0.7.1 (coLinux-0.7.1-devel-20051203) so I assume this new mode is not in my version. Is there a newer 0.7.1 or 0.7.x, or should I revert back to 0.6.4 ??? 0.7.x does not use XML config files. Is this still the way of coLinux or is 0.7.x stalled ??? > Last: The network type "slirp" was the preffered networking type for > WLAN cards. This is more simple to configure, and use no additionals > MAC and no additional IP on your WLAN card. > See: > http://wiki.colinux.org/mediawiki/index.php/Network#Debian_interface_setup_for_static_SLiRP OK, I'll have a look and maybe this is the solution to all my problems :) Thanks, Tchuss!! Brendan. |
From: Henry N. <Henry.Ne@Arcor.de> - 2006-07-24 18:40:06
|
Brendan Simon wrote: > Henry Nestler wrote: >> Additional you could use the TAP adapter as sepate network between your >> coLinux and Windows. With different network, please! For such scenario >> do you need to add a eth1 to your colinux config. > I understand the concept, but how do I do that with WinXP interfaces set > to DHCP ??? > How do I route the coLinux to WinXP. The only way I can think of is > with a secondary static IP on the WinXP box but I can't seem to do that > if DHCP is enabled. The TAP between windows and linux not need to 'route'. This is a different network. Set any new IP on the Windows-TAP, for sample 192.168.222.1 and a ipaddress inside your coLinux in same network, but differ address, for sample eth0 192.168.222.2 under Linux. This network you can use only between coLinux and your Windows. You not need any routing changes, not under linux and not under Windows. An additional network (eth1) you can configure with Pcap-bridge with DHCP inside coLinux. Inside coLinux you set the default route to the ipaddress of your router. Then your eth1 would be the connection to the world. WLAN cards have one big problem: They don't allow to change the MAC on same one card. That's why Pcap mostly not work, or the connection are losed. One card has normal only one MAC, and stupid WLAN routers see a new card and reconnet it. A secured WLAN firmware would also think, you are hacking the air and would reconnect you. Re-connection need WEP/WPA and all this key sharings starts again. >> The winpcap has a mode "no Promiscuous", this is a mode for some WLAN >> cards. Try to set promisc="false" in your XML. This option is new in >> coLinux 0.6.4, read your NEWS.TXT from installation. > I'm running 0.7.1 (coLinux-0.7.1-devel-20051203) so I assume this new > mode is not in my version. > Is there a newer 0.7.1 or 0.7.x, or should I revert back to 0.6.4 ??? > > 0.7.x does not use XML config files. Is this still the way of coLinux > or is 0.7.x stalled ??? promisc="false" is supported in latest devel 20060710, Testing and Autobuild. >> Last: The network type "slirp" was the preffered networking type for >> WLAN cards. This is more simple to configure, and use no additionals >> MAC and no additional IP on your WLAN card. >> See: >> http://wiki.colinux.org/mediawiki/index.php/Network#Debian_interface_setup_for_static_SLiRP > OK, I'll have a look and maybe this is the solution to all my problems :) If you follow my first steps, set eth0 to tap. Than use eth1 with slirp. This is a middle way for very good performance over tap on eth0 and the internet access via eth1 (Slirp). The default route inside linux should set to slirp 10.0.2.2 -- Henry Nestler |
From: Brendan S. <Brendan@BrendanSimon.com> - 2006-07-20 07:15:18
|
BTW, the connection is lost for about 8-10 seconds and then resumes. I don't why it the connectivity between the WinXP and coLinux box would be lost for 8-10 seconds. No packets get through. Continuous pings from both sides show them getting through ok, then dropped for 8-10 seconds, and then ok. Brendan Simon wrote: > Hi, > > I have a wireless adaptor attached to a WinXP bridge. I'm using WinPCAP > for coLinux as I believe that works better than TAP with wireless > networks. I have two issues. > > 1) My WinXP gets a DHCP assigned IP address of 10.1.1.3 from the > wireless access point. My colinux can also get an IP addresses assigned > from the same access point, but unfortunately it is the exact same IP > address. NOT GOOD. I have assigned a different MAC for the device and > ifconfig shows the correct MAC which is different to the wireless MAC. > Anyone know what's going on? My only solution at the moment is to give > static IP address to coLinux. > > 2) I have a VNC connection from WinXP to coLinux. Every few minutes or > so, the network connection between WinXP and coLinux is lost causing my > VNC viewer to die. Sure my vnc session is still running and I can > reconnect but having to do that every few minutes is a real pain in the > a*se. Anyone know what's going on here? I don't have these problems > when connecting using the Ethernet LAN so I suspect it is something to > do with the Wireless stuff and/or the WinXP bridge ??? > > Is it possible to have two static IP addresses for a private coLinux > subnet (eg. 10.1.1.3 for WinXP and 10.1.1.4 for coLinxu) _AND_ also have > the WinXP use DHCP to get another IP address and gateway info. The only > way I can set multiple addresses on WinXP is if DHCP is disabled. The > idea is that I can use DHCP servers at home and at work (I have a > notebook pc). > > Thanks, > Brendan. > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV |
From: Holger K. <hol...@gm...> - 2006-07-20 07:21:13
|
Brendan Simon schrieb: > BTW, the connection is lost for about 8-10 seconds and then resumes. I > don't why it the connectivity between the WinXP and coLinux box would be > lost for 8-10 seconds. No packets get through. Continuous pings from > both sides show them getting through ok, then dropped for 8-10 seconds, > and then ok. If you use a bridge between ethernet and wireless as connection point to colinux, i assume this link goes down every time the wireless connection has problems. Can you ping your access point while you can't ping colinux? |