One note on point 1(d), I repeated steps 1(a-d) several times, both with
and without an alias to verify if the alias was causing my interceptor
message. It was.
--
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-796-9023
email: [EMAIL PROTECTED]
On Fri, 1 Jun 2001, Austin Gonyou wrote:
> Ok, I've determined the following, at least on my system at work. That
> having the following 2 things in place, causes problems:
>
> 1. Packet Socket: MMapped IO - kernel param.
> 2. A defined alias: I had a defined alias for my primary NIC. I proved
> conclusively that this is a problem by doing the following:
> a. killall vnetd-2.4
> b. ifconfig eth0:0 down
> c. /etc/init.d/Win4Lin (wait....)
> d. Get back into X and start win. I now have DHCP assigned IP. I also
> didn't get that stupid interceptor message.
> e. ifconfig eth0:0 xx.xx.xx.xx - I'm able to do this now and have it
> work. More on this later after I do more testing at home.
>
> There you go from this point of view. Both machines, at HOME and at work
> are now functioning properly with no issues.
>
>
>
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
