From: <g4...@no...> - 2009-11-20 17:26:24
|
Not sure if this is a CoLinux or Debian issue, any help welcomed. The Debain image is from the CoLinux downloads page. Updated with latest bits, dnsutils etc. 0.7.5 installed on a Windows 7 x86 box. Wireshark works so I am guessing Winpcap is working too. In my CoLinux .conf file I have: # pcap eth0=pcap-bridge,"LAN" # tap eth1=tuntap At boot the set up for eth0 fails. No idea why. A grep through the logs in /var/log shows nothing. The console shows this: Setting up networking.... Configuring network interfaces...Operation failed. Failed to bring up eth0. As far as the Debian (sourceforge download) installation goes in /etc/network/interfaces I've got: # The primary network interface (win-pcap) auto eth0 iface eth0 inet dhcp # Second network (tap-win32) auto eth1 # DHCP works on tap iface eth1 inet dhcp # static works on tap #iface eth1 inet static # address 192.168.101.88 # netmask 255.255.255.0 # gateway 192.168.101.1 Bizarrely perhaps I get the same problem if I reverse the configuration i.e. have the tap adapter as eth0. Any clues on this? BTW For anyone else dealing with networking issues let me say that eth1 works perfectly in a standard SoHo 'behind the router' enviroment. I get DHCP and correct DNS resolution ( the latter only I removed the wretched resolvconf and manually added a nameserver entry to /etc/resolv.conf ) Bravo and thanks to the team. CoLinux is a much neater solution than VMWare. Jerry |
From: Henry N. <hen...@ar...> - 2009-11-22 22:43:48
|
> Not sure if this is a CoLinux or Debian issue, any help welcomed. The > Debain image is from the CoLinux downloads page. Updated with latest > bits, dnsutils etc. > > 0.7.5 installed on a Windows 7 x86 box. Wireshark works so I am > guessing Winpcap is working too. > > In my CoLinux .conf file I have: > > # pcap > eth0=pcap-bridge,"LAN" > > # tap > eth1=tuntap > > At boot the set up for eth0 fails. No idea why. A grep through the > logs in /var/log shows nothing. The console shows this: > > Setting up networking.... > Configuring network interfaces...Operation failed. > Failed to bring up eth0. > > As far as the Debian (sourceforge download) installation goes in > /etc/network/interfaces I've got: > > # The primary network interface (win-pcap) > auto eth0 > iface eth0 inet dhcp > > # Second network (tap-win32) > auto eth1 > # DHCP works on tap > iface eth1 inet dhcp > # static works on tap > #iface eth1 inet static > # address 192.168.101.88 > # netmask 255.255.255.0 > # gateway 192.168.101.1 > > Bizarrely perhaps I get the same problem if I reverse the > configuration i.e. have the tap adapter as eth0. > > Any clues on this? > > BTW For anyone else dealing with networking issues let me say that > eth1 works perfectly in a standard SoHo 'behind the router' > enviroment. I get DHCP and correct DNS resolution ( the latter only I > removed the wretched resolvconf and manually added a nameserver entry > to /etc/resolv.conf ) udev from Debian renames the network interfaces. Please read the comments and hints in Wiki: http://colinux.wikia.com/wiki/Wubi#udev:_renamed_network_interface_eth0_to_eth2 Please read the related Bug report http://sourceforge.net/tracker/?func=detail&aid=1861876&group_id=98788&atid=622063 -- Henry N. |