RE: [coLinux-users] colinux 0.6.2 with pcap (snapshot coLinux-200 40710)

[Claude L. (QB/EMC) <cla...@er...>]

Hi,

The new network interface search order to be implemented seems to be:

	(1) exact match
	(2) first substring match

And this looks pretty good. I guess most of the users will use the =
exact match. So, most of the users will get the correct network =
behavior as expected from their config file.

Thanks,

Claude LeFran=E7ois=20



-----Original Message-----
From: Dan Aloni [mailto:da...@co...]
Sent: Sunday, September 05, 2004 2:09 PM
To: Claude LeFrancois (QB/EMC)
Cc: 'Andreas Brand'; gboutwel; col...@li...
Subject: Re: [coLinux-users] colinux 0.6.2 with pcap (snapshot
coLinux-200 40710)


On Fri, Aug 20, 2004 at 08:26:08AM -0500, Claude LeFrancois (QB/EMC) =
wrote:
> Hi,
>=20
> However, I suspect the interface selection code has some problems. By =
example,=20
> on my system, I have multiple "Local Area Connection" entries. =
Something like this:
>=20
> 	Local Area Connection
> 	Local Area Connection 2
> 	Local Area Connection 3
>=20
> I needed my system to bridge on "Local Area Connection". I have =
modified my=20
> xml file accordingly but coLinux never got attached to the proper =
interface.=20
> If I recall well, it has attached to the "Local Area Connection 3" =
instead.
>=20
> So, to work around this problem, I have renamed the "Local Area =
Connection" to=20
> "Local Area Connection Broadcom" and after the proper modification =
has been done=20
> to the xml file, coLinux has attached to the correct interface.

coLinux does string searching instead of string matching, and "Local =
Area Connection"
is obviously a substring of "Local Area Connection 3" - here shows the =
problem.=20
Perhaps we should change it to string matching instead. What's your =
opinion?

--=20
Dan Aloni
da...@co...