Folks, I've just gotten ndiswrapper to function with my wireless pcmcia card, thanks to some on-line lists. Now I can kiss Driverloader good-bye, helpful tho it's been. But in reading Novell's ndiswrapper set-up procedure, the instructions don't say precisely where to put ndiswrapper -m so that it starts up on boot. I'm trying to avoid having to go su then do a modprobe ndiswrapper every time I want to use my wireless link. I'd like to get ndiswrapper going somewhere between pcmcia startup and network startup so that when the ntd daemon starts farther down the line, it actually picks up the external time servers rather than giving me a "failed" status. Perhaps there's even a way to get ndiswrapper to show up in the system services section of yast2, where it can be associated with run-levels? Best, Pete
On Thursday 09 June 2005 11:05 pm, Peter N. Spotts wrote:
procedure, the instructions don't say precisely where to put ndiswrapper -m so that it starts up on boot. I'm trying to avoid having to go su then do a modprobe ndiswrapper every time I want to use my wireless link. I'd like to get ndiswrapper going somewhere between pcmcia startup and network startup so that when the ntd daemon starts farther down the line, it actually picks up the external time servers rather than giving me a "failed" status. Perhaps there's even a way to get ndiswrapper to show up in the system services section of yast2, where it can be associated with run-levels?
Peter, although I dont use the ndiswrapper anymore I still have a howto I put together a year ago which will answer your problem I hope. The excerpt follows: The instructions say if it all works then do ndiswrapper -m which should modify your modules.conf file. This is to make it install during boot, but that only works on pre 2.6 kernels, the later kernels use modprobe.conf for such things. I'm sure someone knows how to setup the modprobe.conf file but my solution is to use an editor to change the /etc/sysconfig/kernel file and set the line: MODULES_LOADED-ON-BOOT="ndiswrapper" If it is all working you should be able to do rcnetwork restart and see the NICs shut down and restart with the wlan0 getting its IP from your router. The ultimate proof of all this is if it fires up when you reboot. If you need to take down the eth0 with ifconfig, be sure you do ifconfig eth0 down THEN ifconfig wlan0 up in that sequence. I used it on suse 9.2 very effectively and I assume it will still work on 9.3. It was on LinuxQuestions.org in the network section. The whole thing might still be there. Good luck, RA
But in reading Novell's ndiswrapper set-up procedure, the instructions don't say precisely where to put ndiswrapper -m so that it starts up on boot.
The way I do it is that I set the card up in YaST with ndiswrapper as the module... yast lan Configure > Device Type: Wireless, Module Name: ndiswrapper > Next > Next > Finish That way it'll get loaded when the interface is setup at boot time. -- James Ogley james@usr-local-bin.org GNOME for SuSE: http://usr-local-bin.org/rpms
The way I do it is that I set the card up in YaST with ndiswrapper as the module... That way it'll get loaded when the interface is setup at boot time.
Forgot to mention that you can then use netapplet to switch between ethernet and wireless connections - install the netapplet package if you don't already have it. -- James Ogley james@usr-local-bin.org GNOME for SuSE: http://usr-local-bin.org/rpms
Thanks all... And James, does using netapplet eliminate the need to change firewall settings each time I switch between eth0 (office) and wlan0 (home)? Best, Pete -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Peter N. Spotts | Science Correspondent The Christian Science Monitor One Norway Street, Boston MA 02115 Office: 617-450-2449 | Office in home: 508-520-3139 Email: pspotts@alum.mit.edu | www.csmonitor.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
On 6/10/05, Peter N. Spotts
Thanks all...
And James, does using netapplet eliminate the need to change firewall settings each time I switch between eth0 (office) and wlan0 (home)?
Best,
Pete
I'm sure you'll do better using scpm profiles for this. Just switch the profile and it should bring up whatever interface is needed with the correct firewall settings. Sunny
And James, does using netapplet eliminate the need to change firewall settings each time I switch between eth0 (office) and wlan0 (home)?
Set your external interface to Auto, and it might ;) I dunno, not checked, don't really use my wlan interface as I don't have a WAP - I suspect it may require you to simply restart the firewall when you change interface. -- James Ogley james@usr-local-bin.org GNOME for SuSE: http://usr-local-bin.org/rpms
On Fri, 2005-06-10 at 15:35 +0100, James Ogley wrote:
And James, does using netapplet eliminate the need to change firewall settings each time I switch between eth0 (office) and wlan0 (home)?
Set your external interface to Auto, and it might ;)
I dunno, not checked, don't really use my wlan interface as I don't have a WAP - I suspect it may require you to simply restart the firewall when you change interface.
Take a look at the ifplugd package. I use it on my laptop to auto select which interface to use. YMMV -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
participants (5)
-
James Ogley
-
Ken Schneider
-
Peter N. Spotts
-
Richard Atcheson
-
Sunny