[mdlug] Networking with open SUSE 11.1

[Robert Adkins]

Another thing to look at, if you have plans on only being a user of a Linux
desktop OS, instead of a hardcore Linux user, such as Gary, myself and other
members of the list here, is to take a look at Ubuntu Linux 9.04.

Ubuntu has, in my opinion, one upped several other distros in providing a
utility that will automatically locate and install the ndiswrapper package
along with the proper drivers for certain WiFi cards, specifically of the
Broadcom family of WiFi cards. I was pleasantly surprised when I started
playing with Ubuntu to find that my WiFi card was detected and it asked me
if I wanted to install the proper driver for it. (This was through an applet
under "Administration" relating to Hardware Drivers.)

Still, I find OpenSuSe 11.1 to be far more powerful in terms of what I can
make the OS do. For instance, out of the box you can install multiple
Network Interface Cards and assign how they will connect to your network
very easily with OpenSuSe. 

Ubuntu (Even the Server Edition) doesn't have any utilities or easy method
of stating that a particular NIC is going to be called Eth1 and will use a
particular static or DHCP related address every boot. I battled briefly with
an Ubuntu server that was going to be configured as a router/proxy for an
untrusted network branch before throwing up my arms and getting ready to
hammer smash the PC into pieces. For this situation, OpenSuSe 11.1 proved to
be the dead simple solution to the problem.

Anyway, good luck and welcome to the Linux Club.
Rob


> -----Original Message-----
> From: mdlug-bounces at mdlug.org 
> [mailto:mdlug-bounces at mdlug.org] On Behalf Of Ingles, Raymond
> Sent: Thursday, July 30, 2009 11:34 AM
> To: MDLUG's Main discussion list
> Subject: Re: [mdlug] Networking with open SUSE 11.1
> 
> > From: Jay P Hailey
> > To me this suggests that my networking card is like an old winModem
> and
> > depends on Winders for some functionality.
> 
>  In effect, yes. Here's the deal: the FCC puts limits on how 
> much power wifi cards can broadcast at. But the limits are 
> imposed by software, not hardware. So the drivers need to do 
> it. Some manufacturers don't give Linux developers the specs 
> they need to do this.
> 
> > Which give me hope that the problem can be resolved,  but I have no
> idea
> > what they're talking about.  Something about installing a 
> wrapper, to 
> > include the stuff the card looks to windows for.
> 
>  NDIS - Network Driver Interface Specification - is a 
> standard for how to talk to network cards. Mostly used by 
> Windows, but some code called "ndiswrapper" has been written 
> to allow Linux to talk to Windows drivers that use it. (See 
> here: http://en.wikipedia.org/wiki/NdisWrapper )
> 
>  So what you need is the .inf and .sys drivers from the 
> Windows driver of the card. I'm afraid that I haven't had to 
> do this so far (all the wifi cards I've gotten have happened 
> to have native Linux drivers) so I can't give you a lot of 
> details, but Googling on your Linux distro name and 
> "ndiswrapper" should get you the instructions you need...
> 
>  Sincerely,
> 
>  Ray Ingles                                              
> (313) 227-2317
> 
>  "There is a fine line between being on to something and on 
> something."
>                           -Friar Broccoli The contents of 
> this e-mail are intended for the named addressee only. It 
> contains information that may be confidential. Unless you are 
> the named addressee or an authorized designee, you may not 
> copy or use it, or disclose it to anyone else. If you 
> received it in error please notify us immediately and then destroy it.
> _______________________________________________
> mdlug mailing list
> mdlug at mdlug.org
> http://mdlug.org/mailman/listinfo/mdlug
>