....even on the reccomended way
is simply wrong, as well as
- There should be no gateway="..." setting.
- The default file may contain one near the bottom.
iface_eth0="192.168.37.20 netmask 255.255.255.0 broadcast 192.168.37.255" iface_eth1="dhcp"
which doest sticks well to the graph above and uses dhcp as a way of showing the right setting...If dhcp was working, nonone would have read this wiki.
HOWTOs are suppose to be helpful. This guide just confuses people because it doesn't direct the user in a sequential manner but modulizes the problem. If people new exactly what the problem was they wouldn't be reading this anyway. They would just google for the solution.
pcap-bridge option be careful with ipv6/DAD=(Duplicate Address Detection), it checks duplicated ipv6 and ipv4 IP's when ipv6 is install in the kernel
You should use not an inused IP on coLinux side for the network Winpcap. This type of network adds a "virtual" network card in your real network. So, the main error is the duplicated address self, not the DAD. -- HenryNe
This guide really needs to be broken down a bit, with some little complete howtos in separate pages -it is a bit too monolithic. Also the old XML config file stuff should be switched for the new style. The old stuff is in the history for someone still using a previous version of colinux. -- Dannystaple
I second the motion on HOWTO's. For example, I myself want to do lamp-development hosted on a Vista LAPTOP that connects to all kind of different (mostly wifi) networks (office, home, hotel). Ideally, after each wifi-switch, I can still ssh to my colinux and I can reach the internet from within colinux (to install packages for example) both without reconfiguring any netwerk parameters by hand. Is this possible and if yes, how? -- Anonymous
- Add SLiRP to your coLinux config and inside coLinux use this as your default gateway and nameserver (/etc/resolve.conf). Than you can hopping between your networks and coLinux will still follow it without any change. I say add, because it is a nice idea to have the tuntap for your ssh between Host and Linux and the SLiRP for outgoing connections from Linux to the internet. -- HenryNe 20:58, 3 April 2009 (UTC)
There is a lot of redundancy in this article...
Windows Starter network restrictions Edit
I'm currently trying to setup CoLinux with Gentoo on a Samsung N150 Netbook
It appears some potential configurations are not possible when using Windows Starter as the host OS since it does not allow bridging of adapters - http://windows.microsoft.com/en-GB/windows7/Networking-in-Windows-7-Starter
188.8.131.52 11:17, January 15, 2012 (UTC)