From: Tobbe L. <to...@tl...> - 2011-11-28 11:26:06
|
Hi I just installed VirtualBox and my colinux network stopped working. Any ideas why that happened and how to fix it? (except for uninstalling VB) I'm using winpcap for netoworking, and have a static ip configured. //Tobbe |
From: Henry N. <hen...@ar...> - 2011-11-28 22:30:08
|
At 28.11.2011 11:58, Tobbe Lundberg wrote: > I just installed VirtualBox and my colinux network stopped working. > Any ideas why that happened and how to fix it? (except for > uninstalling VB) > I'm using winpcap for netoworking, and have a static ip configured. Replace the word "pcap-bridge" with "ndis-bridge" in your config. Ndis use an other mechanism. Maybe this will work better. -- Henry N. |
From: <to...@tl...> - 2011-11-28 23:17:57
|
Thanks for your reply Henry. Unfortunately changing to ndis-bridge did not work. Infact, I couldn't tell any difference at all. //Tobbe Den, skrevHenry Nestler <hen...@ar...>: > At 28.11.2011 11:58, Tobbe Lundberg wrote: > > I just installed VirtualBox and my colinux network stopped working. > > Any ideas why that happened and how to fix it? (except for > > uninstalling VB) > > I'm using winpcap for netoworking, and have a static ip configured. > Replace the word "pcap-bridge" with "ndis-bridge" in your config. > Ndis use an other mechanism. Maybe this will work better. > -- > Henry N. |
From: Henry N. <hen...@ar...> - 2011-11-29 20:47:06
|
Hello Tobbe, please check, that the problem is or is not the renaming udev. Exist the network interface eth0 or what ever under "cat /proc/net/dev" inside the running coLinux? Have you maybe added a new network interface under windows, and coLinux use the wrong now? Check, that the name you have for "network connection name" in coLinux.conf, exist and has exactly this name in your windows network connections. eth0=ndis-bridge,"network connection name",MAC I can say, that I have also installed VirtualBox after coLinux, and I never found a problem. Henry At 28.11.2011 23:50, tobbe wrote: > Thanks for your reply Henry. > > Unfortunately changing to ndis-bridge did not work. Infact, I couldn't > tell any difference at all. > > //Tobbe > > Den, skrevHenry Nestler <hen...@ar...>: > > At 28.11.2011 11:58, Tobbe Lundberg wrote: > > > > > I just installed VirtualBox and my colinux network stopped working. > > > > > Any ideas why that happened and how to fix it? (except for > > > > > uninstalling VB) > > > > > I'm using winpcap for netoworking, and have a static ip configured. > > > > > > > > Replace the word "pcap-bridge" with "ndis-bridge" in your config. > > > > Ndis use an other mechanism. Maybe this will work better. > > > > > > > > -- > > > > Henry N. |
From: <to...@tl...> - 2011-11-29 22:18:55
|
Hi I have a private TAP network between colinux and my windows host. This uses eth0 and it works just as it did before installing VirtualBox And then I have a winpcap/ndis connection to speak to the internet using the wlan interface of my laptop. This uses eth1. > please check, that the problem is or is not the renaming udev. > Exist the network interface eth0 or what ever under "cat /proc/net/dev" > inside the running coLinux? Yes, both eth0 and eth1 show up there > Have you maybe added a new network interface under windows, and coLinux > use the wrong now? > Check, that the name you have for "network connection name" in > coLinux.conf, exist and has exactly this name in your windows network > connections. > eth0=ndis-bridge,"network connection name",MAC These are my network connections: http://i.imgur.com/tvcRh.png And these are the relevant lines from colinux.conf eth0=tuntap eth1=pcap-bridge,"wlan",00:1B:77:7E:B2:82 It doesn't matter if the VirtualBox network is enabled or disabled, and it doesn't matter if I use pcap or ndis. This is /etc/network/interfaces auto eth0 iface eth0 inet static address 192.168.37.20 netmask 255.255.255.0 network 192.168.37.0 broadcast 192.168.37.255 auto eth1 iface eth1 inet static address 192.168.0.42 netmask 255.255.255.0 gateway 192.168.0.254 broadcast 192.168.0.255 nameserver 192.168.0.254 I can ping both 192.168.37.40 and 192.168.0.103 which are the IP addresses of the windows host. In fact (I just tested this) I can even ping 173.194.32.51, which is a google.com IP address. pinging www.google.com does *not* work however. And wget www.google.com gets stuck at "Resolving www.google.com..." > I can say, that I have also installed VirtualBox after coLinux, and I > never found a problem. Great! That means there is hope for finding a solution :) > At 28.11.2011 23:50, tobbe wrote: > > Thanks for your reply Henry. > > > > Unfortunately changing to ndis-bridge did not work. Infact, I couldn't > > tell any difference at all. > > > > //Tobbe > > > > Den, skrevHenry Nestler hen...@ar...>: > > > At 28.11.2011 11:58, Tobbe Lundberg wrote: > > > > > > > I just installed VirtualBox and my colinux network stopped working. > > > > > > > Any ideas why that happened and how to fix it? (except for > > > > > > > uninstalling VB) > > > > > > > I'm using winpcap for netoworking, and have a static ip configured. > > > > > > > > > > > > Replace the word "pcap-bridge" with "ndis-bridge" in your config. > > > > > > Ndis use an other mechanism. Maybe this will work better. > > > > > > > > > > > > -- > > > > > > Henry N. |
From: Daniel L. <did...@gm...> - 2011-11-29 22:35:21
|
On Tue, Nov 29, 2011 at 22:18, <to...@tl...> wrote: > In fact (I just tested this) I can even ping 173.194.32.51, which is a > google.com IP address. pinging www.google.com does *not* work however. And > wget www.google.com gets stuck at "Resolving www.google.com..." that sounds suspiciously like your linux "box" doesn't know about your dns resolver. Check /etc/resolv.conf for lines like: nameserver 192.168.1.1 where the ip address should be that of your DNS resolver which may be on your router or provided by your ISP. -- Regards, The Honeymonster aka Daniel Llewellyn |