From: Dave C. <dc...@do...> - 2007-08-18 06:39:46
|
Sam, Did you ever find out why XP stops allowing the Slirp connection from Colinux? I keep finding I cannot connect, although removing the XP Local connection does seem to cure it for a while, it's a pain to have to keep doing this. Also, it seems to increment the name of the local connection ("Local Area Connection 16"). Many thank, Dave Coventry |
From: Henry N. <Henry.Ne@Arcor.de> - 2007-08-20 10:48:21
|
Dave Coventry wrote: > Sam, > > Did you ever find out why XP stops allowing the Slirp connection from > Colinux? > > I keep finding I cannot connect, although removing the XP Local > connection does seem to cure it for a while, it's a pain to have to keep > doing this. Also, it seems to increment the name of the local connection > ("Local Area Connection 16"). SLiRP should no hang on the TAP device. Under some situations the SLiRP hangs on the TAP instaed the real Ethernet for outgoing connections. For example, if you have no real Ethernet connection and the TAP device is "connected" before the slirp daemon starts. The 0.6.4 has an 10 sec timeout to re-connect over the current XP connection. So, should help to unplug the network cable (or "disable" in the network overview), wait 10 seconds and connect the cable (or "enable" the Ethernet card). Slirp should than read the current connection again and use the right DNS. As workarrount, you can add an other DNS behind the 10.0.2.15 in your resolve.conf The problem of old code: Slirp use the first connection, that is connected. This can also be the TAP device, and this would bad here. This all should solved in current coLinux versions (0.7.1 and 0.8.0 Snapshots). There coLinux don't cache the DNS and don't bind on one of the network cards directly. What coLinux version you are using? PS: Slirp can't ping to the world, you can only test it with "wget ...". Slirp have no IMCP protocol, read more here: http://lists.gnu.org/archive/html/qemu-devel/2004-09/msg00192.html -- Henry |
From: Dave C. <dgc...@gm...> - 2007-08-20 11:01:52
|
>What coLinux version you are using? Cooperative Linux Daemon, 0.8.0 Compiled on Wed Apr 25 22:19:16 2007 On 8/20/07, Henry Nestler <Hen...@ar...> wrote: > > Dave Coventry wrote: > > Sam, > > > > Did you ever find out why XP stops allowing the Slirp connection from > > Colinux? > > > > I keep finding I cannot connect, although removing the XP Local > > connection does seem to cure it for a while, it's a pain to have to keep > > doing this. Also, it seems to increment the name of the local connection > > ("Local Area Connection 16"). > > SLiRP should no hang on the TAP device. Under some situations the SLiRP > hangs on the TAP instaed the real Ethernet for outgoing connections. For > example, if you have no real Ethernet connection and the TAP device is > "connected" before the slirp daemon starts. > The 0.6.4 has an 10 sec timeout to re-connect over the current XP > connection. So, should help to unplug the network cable (or "disable" in > the network overview), wait 10 seconds and connect the cable (or > "enable" the Ethernet card). Slirp should than read the current > connection again and use the right DNS. As workarrount, you can add an > other DNS behind the 10.0.2.15 in your resolve.conf > The problem of old code: Slirp use the first connection, that is > connected. This can also be the TAP device, and this would bad here. > > This all should solved in current coLinux versions (0.7.1 and 0.8.0 > Snapshots). There coLinux don't cache the DNS and don't bind on one of > the network cards directly. > > What coLinux version you are using? > > PS: Slirp can't ping to the world, you can only test it with "wget ...". > Slirp have no IMCP protocol, read more here: > http://lists.gnu.org/archive/html/qemu-devel/2004-09/msg00192.html > > -- > Henry > > |
From: Henry N. <Henry.Ne@Arcor.de> - 2007-08-20 14:34:38
|
Dave Coventry wrote: > >What coLinux version you are using? > Cooperative Linux Daemon, 0.8.0 > Compiled on Wed Apr 25 22:19:16 2007 Ok. Is good. There no such problems known. I can give some hints, hope one of will help you. Please check, that TAP dosn't have an gateway. TAP and your real Ethernet card should have different networks (192.168.4.0 and 192.168.0.0 in my example). Here you can see an example from XP, where coLinux is running: C:\>ipconfig Windows-IP-Konfiguration Ethernetadapter TAP-Colinux: Verbindungsspezifisches DNS-Suffix: IP-Adresse. . . . . . . . . . . . : 192.168.4.71 Subnetzmaske. . . . . . . . . . . : 255.255.255.0 Standardgateway . . . . . . . . . : Ethernetadapter LAN-Connection: Verbindungsspezifisches DNS-Suffix: terminal IP-Adresse. . . . . . . . . . . . : 192.168.0.71 Subnetzmaske. . . . . . . . . . . : 255.255.255.0 Standardgateway . . . . . . . . . : 192.168.0.4 In my case slirp use the default gateway (german: "Standardgateway") 192.168.0.4 for all outgoings. If SLiRP is not working, then try "tracert.exe www.google.com" on Windows. Does this work? C:\>tracert www.google.com traceroute to www.google.com (209.85.129.147), 30 hops max: 1 <1 ms <1 ms <1 ms nameserver.local [192.168.0.4] ... In the example should see your current gateway as first router (my 192.168.0.4). If slirp not working, then it's working with ipaddresses instead the names? This can be a problem with DNS. For example inside coLinux try to get www.google.com page (adress seen on windows side from tracert): cd /tmp wget 209.85.129.147 An fixed "HWaddr" in the coLinux config is mutch better for DHCP clients. Configure this in the coLinux config as follow: eth0=slirp,00:11:22:33:44:55 An other problem is perhaps the losing packets from dhcp. You would see the difference from working and non working by "ifconfig eth0" inside colinux, and compair all numbers in the line "inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0". If some are different, then setup slirp inside coLinux with static address http://colinux.wikia.com/wiki/Network#SLiRP_with_Static_IP_Address Be carefully to have netmask 255.255.255.0 and broadcast 10.0.2.255 for slirp. SLiRP use non standard netmask. -- Henry |
From: Dave C. <dc...@do...> - 2007-08-20 20:17:32
|
On 8/20/07, Henry Nestler <Hen...@ar...> wrote: > > Dave Coventry wrote: > > Most of the time it works fine. > > > > Then, suddenly, I will go to use portage (I've got the gentoo > > installation), and it will be unable to find the servers. > > > > lynx will also not be able to access the net. > > > > If I do as Sam Moffat suggests, which is delete my XP lan connection and > > reboot XP, windows rebuilds my Lan connection and my colinux > > installation can access the Internet again. Which seems to suggest that > > the problem is from the windows side. > > > > It's not really a big deal, but it is a bit of a pain. > > Removing and adding TAP for SLiRP is a very big pain. Because SLiRP > works as normal winsock application. A normal windows logout or Reboot > should go with slirp again. But normalny a new start of coLinux should > be enough. Well, I find that it requires the drastic method that I described before it will reconnect. Rebooting windows doesn't do it. In error case: Can you access to the internet from other windows > applications, for example IE o other browsers? Yes, windows applications are not affected. If this case exist in the next time, then please do some protocols from > this state (before changing TAP): > - is the colinux-slirp-net-daemon.exe running? (check with taskman) > - is the ethernet card online and have a gateway? Check with > "ipconfig.exe /all" and compair with a working session before. Will do. An other question: Have you some specials on the networking installed: > - ICS? No. There is the LAN connection, a 1394 connection and a wireless adapter. - Special dial software for DSL or modem? No, I use a network connection with the ADSL modem as a DHCP server. - Have your network card a dynamic address? Yes. In South Africa the Monopoly Telkom Company charges tenfold for static IP addresses. Therefore, they do not like their customers to have an IP address for too long and will force a reallocation. Is your gateway and DNS changed from time to time? Yes, I think so. (Other mode would be an permanently address from local router.) > - Firewall with idle timeout (for example ZoneAlarm does) No. I ask, because I every day use slirp for internet and tap for putty, and > have long times no problems. And I'm hopping between different DHCP > environments with my laptop. > -- > Henry > > Dave Coventry |