From: Paul M. <fka...@ya...> - 2006-03-01 19:15:15
|
Henry, I'm afraid one of us is not understanding the other. I'm not having a problem with allocating IP addresses or MAC addresses the way I want. My problem is that SUSE does not automatically attempt to load the network interface at boot time. I suspect it is related to the fact that a new interface number is allocated with each coLinux boot, even within the same Windows session. It was suggested that setting a fixed MAC would avoid that, but it hasn't; I'm already doing that. Or am I missing something? Again, it works perfectly under Debian... Native SUSE: MAC=000103E31656 (card's actual MAC) IP=192.168.1.4 coLinux SUSE: MAC=000103E31656 (bridged with fixed MAC) IP=192.168.1.4 Windows XP: MAC=000103E31657 (set in adapter configuration) IP=192.168.1.2 Thanks, -Paul --- Henry Nestler <Henry.Ne@Arcor.de> wrote: > Paul Mogren schrieb: > > Actually, I have been doing that since day one. > > coLinux is fixed to use the actual address of the > > card, same as native SUSE uses. In Windows, it's > > fudged to another address (+1). When I force the > > interface to come up, it gets the IP that is > reserved > > for that address in the DHCP server. > > If you jumps between native Linux starts and coLinux > pcap-Bridged with > DHCP you have a problem. The address what you gets > with last native > Linux is inuse from you Windows ;-( > > One solution is using fixed IP inside coLinux and > native Linux, but not > the windows IP. > > I have configured my SuSE to use different IP > adresses for native and > coLinux (with DHCP). This works for me with fixed > mac in coLinux. But > the mac is differ from native Linux. > > -- > Henry Nestler > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |