'o-Dzin Tridral wrote:
Dear all,
I've read (and been part of) a number of threads of discussion relating to automatically starting the wireless connection on boot. A fair number of people seem to have this problem, and thesymptoms seem to be the same - the system recognises that there's a wrieles card but doesn't properly bring up the interface. The only way to get this running is to take some action - ifdown/ifup, Yast or NetGo. There seems to be no certain solution (that I've seen) to get the interface to start automatically. (I couldn't even get 'static' to work - but that might just be me!)
I'm entirely new to Suse. Is this a known bug? is there a workaround/solution? Did Suse behave like this in earlier versions?
(Failing all else, is there a way to put ifdown/ifup at the end of the boot process? Would that help?)
....
I would think that ifup and ifdown are already being run on boot and shutdown respectively. I wouldn't add them in anywhere until I found out whether or not this was the case. Perhaps more importantly, when asking for help, provide some information about the problem, the hardware and software used, what you've tried and what happened, what error messages resulted, what log files you examined and what you found or didn't find there, and so on. hth, ken