Wireless in 1.05- Network identified but unable to connect

[Guest]

I have built-in Intel Pro 2200b/g wireless in my Fujitsu laptop. I downloaded the intel 2200 wireless driver, followed the readme instructions, and used WAG. I can find my network, but WAG says the access point is not responding and the internet ping fails. I am using WPA encryption with ssid broadcasting disabled. My router is a Linksys broadband b/g. My wireless connection in XP works fine. Any suggestions?

[Walt H]

I don't know whether this will help, but I had a similar situation in Kanotix (haven't tried in Puppy yet) with my Belkin F5D7050 USB adapter. The network saw my device, but I could not get on the internet. Here's what solved the problem for me. From the command line run the following:

Code: Select all

dhclient wlan0

Replace the zero with whatever number your device is on, although it should probably be at wlan0. Hope that does the trick for you. Good luck!

[keenerd]

Puppy doesn't have dhclient.

WPA might be the problem. First, WPA support is iffy on some drivers. Second, iwconfig (what WAG uses to configure your card) doesn't support WPA passphrases.

"Access point not responding" mean WAG tried to ping your AP and it didn't work. Turn off dhcpcd. Connect to your network. Turn on dhcpcd. This might work.

On the other hand, I've had a problem with WAG for the past few days. Its kind of similar to yours, so try the next release. No guarantees as to how long you'll have to wait.

[tempestuous]

Are you referring to the dedicated ipw2200 driver at http://mymirrors.homelinux.org/puppy/wireless/ ?

If so, I did indicate in the ipw2200_README file that WPA encryption is supported by this driver, and I included additional kernel modules in the driver package to support WPA encryption ... but no one has tested this yet (WEP encryption is confirmed good).
Actually I just checked the official documentation at http://ipw2200.sourceforge.net and I see that WPA is currently enabled, but not officially supported.
Eventually the ipw220 driver may contain native support for WPA, but for now you can use the wpa_supplicant package, which I have also compiled.
According to the wpa_supplicant documentation, SSID name broadcast is necessary for WPA to work.

I urge you to go ahead and be a pioneer in this area, but take things one step at a time.
Don't use keenard's WAG until you know the various components work.
First I suggest you turn off ALL encryption at your router. Now connect to your wireless network -

modprobe ipw2200
iwconfig eth0 mode Managed
## notice no reference to "essid" or "key"
dhcpcd -t 20 -h puppypc eth0 ## assuming DHCP

Is the network connection OK?
Now turn on SSID name broadcast, and re-connect -

iwconfig eth0 essid MY_SSID mode Managed

Still working? Now you can install the wpa_supplicant package, and turn on WPA encryption at your router.
Then modify /etc/wpa_supplicant.conf to include your SSID and passphrase. Basically, wpa_supplicant is a "helper" utility for the ipw2200 driver. The README file contains more detailed information, but here's a summary -

wpa_supplicant -ieth0 -Dipw -c/etc/wpa_supplicant.conf -d
## this will run wpa_supplicant in the foreground,
## later it can be run in the background with -B instead of -d
## open a separate xterminal -
iwconfig eth0 essid MY_SSID mode Managed
dhcpcd -t 20 -h puppypc eth0

It would be good to let others know your success or failure at this thread - http://www.murga.org/%7Epuppy/viewtopic.php?t=2234

[kamranzaidi]

wondering if someone is able to setup wifi with LINKSYS WIRELESS-G notebook adapter , model No. WPC54G , V 1.2 on puppy 1.0.5.

I tryed wireless wizard with option 1B (installing perl with pupget,copying WIN XP driver lsbcmnds.inf file, and running ndiswrapper) but when i issue

Code: Select all

ndiswrapper -l

command, i get invalid driver error.

now i m going to try choice 2 "install from wifi-beta.pup", but unable to find this pup, geting 404 from the link...

i think the chipset for this card is of brand "broadcom" which does not have an linux drivers...

thk

[BlackAdder]

Presumably you were trying the old location for the wifi-beta-2 dot pup.
Revised download location is: http://www.yourfilehost.com/media.php?c ... beta-2.pup
If you get a file not found from there, let us know.

The wifi-beta-2 dot pup does include support for some versions of the WPC54G, but the .inf file you refer to is certainly not included.

BTW, when you tried to install the driver to ndiswrapper, did the directory with the .inf file also contain the other Windows driver files, e.g. .sys files? If there any of those extra files, they are needed for correct install and operation.

[kamranzaidi]

link seems ok, i should be able to download the file now.

BTW, when you tried to install the driver to ndiswrapper, did the directory with the .inf file also contain the other Windows driver files, e.g. .sys files? If there any of those extra files, they are needed for correct install and operation.

No, i just copy .inf file and that could be the problem, as i didn't copy rest of the .sys etc files. I will give it a try tonight after copying rest of the files..

I am using encryption(WPA i guess), does this pup supports any such thing?

thanks BlackAdder,

[BlackAdder]

kamranzaidi: The wifi-beta-2 dot pup does not include WPA. There is a separate package (wpa-supplicant) that tempestuous has created. See this topic for details:
http://www.murga.org/~puppy/viewtopic.php?t=2234

Please post details to the wiki when (or if) you get wireless working.

[tempestuous]

kamranzaidi,
The type of encryption is determined by the settings in your wireless router. WEP is most common. WPA is a more recent, high security system.
A few Linux wireless drivers support WPA natively.
With ndiswrapper, though, you would need to use wpa_supplicant. My wpa_supplicant package has been compiled to support ndiswrapper, amongst others.

[kamranzaidi]

thanks tempestuous n BlackAdder,

Last night i got chance to start where i left earlier and here are the findings..

wifi-1.0.4-beta-2.pup's help shows, my chipset is supported with this vendor n device id, good news..

Code: Select all

Vendor 0x14e4  device 0x4320

driver file details from wifi .pup help page.

Code: Select all

Driver file: bcmwl5a
VID:PID 14e4:4301
Broadcom 802.11b
VID:PID 14e4:4320
Broadcom 54g MaxPerformance 802.11g

but puppy does not detect my wifi card properly, plz note that i also have a NIC(wired) up n running (which is setup on eth0, i guss)

1: when i do #dmesg after #modprobe ndiswrapper looks like the windows driver is not being initlized, any idea why?
2: do i need to provide WEP/WPA encryption key info in wireless.conf and how, if i m not using encryption (for now!!).

Code: Select all

Encryption key : 4567-89AB-CD, s:password 
    KEY=""

Thanks..

Seems that driver installation for my wifi card is ok

Code: Select all

# ndiswrapper -i /mnt/cdrom/lsbcmnds.inf
Installing lsbcmnds

Shows that driver is present (last line)

Code: Select all

# ndiswrapper -l
Installed ndis drivers:
airplus driver present 
bcmwl5  driver present 
bcmwl5a driver present 
gplus   driver present 
lsbcmnds        driver present 
....

looks like the windows driver is not being initlized, any idea why?

Code: Select all

#modprobe ndiswrapper
#dmesg
. .
....
c(bus 2): vendor 0x14e4, device 0x4320
PCI: Enabling device 02:00.0 (0000 -> 0002)
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x408-0x40f 0x480-0x48f 0                                                             x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
hdc: attached ide-cdrom driver.
hdc: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
...
..
Registering unionfs version $Id: main.c,v 1.85 2005/03/14 22:19:49 dquigley Exp                                                              $
..
..
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport0: irq 7 detected
eth0: link up.
eth0: Setting full-duplex based on negotiated link capability.
eth0: remaining active for wake-on-lan
eth0: link up.
eth0: Setting full-duplex based on negotiated link capability.
i8253 count too high! resetting..
i8253 count too high! resetting..
ndiswrapper version 1.1 loaded (preempt=no,smp=no)
ndiswrapper: driver lsbcmnds (The Linksys Group, Inc.,07/17/2003, 3.30.15.0) loa                                                             ded
PCI: Setting latency timer of device 02:00.0 to 64
__alloc_pages: 0-order allocation failed (gfp=0x21/0)
ndiswrapper (NdisMAllocateSharedMemory:1004): Failed to allocate DMA coherent me                                                             mory. Windows driver requested 4096 bytes of cached memory

ndiswrapper (NdisWriteErrorLogEntry:273): log: C0001389, count: 1 (0000000d), re                                                             turn address: cc982be3, entry: cc9838c8 offset: 4294963995
ndiswrapper (ndiswrapper_add_one_pci_dev:188): Windows driver couldn't initializ                                                             e the device (C000009A)

still tring to see if wifi cameup..

Code: Select all

# dhcpcd wlan0
# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.


#ifconfig
eth0      Link encap:Ethernet  HWaddr XXXXXXXXXXXXXXXXXXXX
          inet addr:192.168.1.104  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:756 errors:0 dropped:0 overruns:0 frame:0
          TX packets:780 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:531542 (519.0 kiB)  TX bytes:115404 (112.6 kiB)
          Interrupt:11 Base address:0x9000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 iB)  TX bytes:0 (0.0 iB)

 

For refference, here are the contents of my rc.local file

Code: Select all

========================================
rc.local:
========================================
#this file called from rc.local0 you can edit this file
#When firewall is installed, will append lines to this file...
. /etc/rc.d/rc.wireless
/sbin/dhcpd wlan0

Here are the contents of my rc.wireless file

Code: Select all

========================================
rc.wireless
========================================
#!/bin/sh

# rc.wireless for Puppy 0.9.8 > (Rob Murphy 22/1/05)
# Bring up wireless card 
# Sections from
# wireless network 1.63 2000/02/09 03:12:42 (David Hinds/Jean Tourrilhes)


DEVICE="wlan0"
IWPATH="/usr/sbin"
. /etc/rc.d/wireless.conf

# Load the driver with default wlan0 interface name
# 
# /sbin/insmod ndiswrapper

# Load the driver with $IFACE interface name and give the driver a chance
# to finish loading
/sbin/insmod ndiswrapper if_name=$DEVICE
sleep 3

    # Mode need to be first : some settings apply only in a specific mode !
    if [ -n "$MODE" ] ; then
	 $IWPATH/iwconfig $DEVICE mode $MODE
    fi

    if [ -n "$ESSID" ] ; then
	 $IWPATH/iwconfig $DEVICE essid $ESSID
    fi

    # This is a bit hackish, but should do the job right...
    if [ ! -n "$NICKNAME" ] ; then
        NICKNAME=`/bin/hostname`
    fi
    if [ -n "$ESSID" -o -n "$MODE" ] ; then
	 $IWPATH/iwconfig $DEVICE nick $NICKNAME >/dev/null 2>&1
    fi
    # Regular stuff...
    if [ -n "$NWID" ] ; then
	 $IWPATH/iwconfig $DEVICE nwid $NWID
    fi
    if [ -n "$FREQ" ] ; then
	 $IWPATH/iwconfig $DEVICE freq $FREQ
    elif [ -n "$CHANNEL" ] ; then
	 $IWPATH/iwconfig $DEVICE channel $CHANNEL
    fi
    if [ -n "$SENS" ] ; then
	 $IWPATH/iwconfig $DEVICE sens $SENS
    fi
    if [ -n "$RATE" ] ; then
	 $IWPATH/iwconfig $DEVICE rate $RATE
    fi
    if [ -n "$KEY" ] ; then
	 $IWPATH/iwconfig $DEVICE key $KEY
    fi
    if [ -n "$RTS" ] ; then
	 $IWPATH/iwconfig $DEVICE rts $RTS
    fi
    if [ -n "$FRAG" ] ; then
	 $IWPATH/iwconfig $DEVICE frag $FRAG
    fi
    # More specific parameters
    if [ -n "$IWCONFIG" ] ; then
	 $IWPATH/iwconfig $DEVICE $IWCONFIG
    fi
    if [ -n "$IWSPY" ] ; then
	 $IWPATH/iwspy $DEVICE $IWSPY
    fi
    if [ -n "$IWPRIV" ] ; then
	 $IWPATH/iwpriv $DEVICE $IWPRIV
    fi
   ################################################################## 
   # Uncomment the following lines if you have a local DHCP server  #
   ################################################################## 
    
#  if [ -e /etc/dhcpc/*.pid ]; then
#   rm /etc/dhcpc/*.pid 
#   fi
#   dhcpcd $DEVICE

   ################################################################## 
   # Uncomment the following lines and plug in your values if you   #
   # need to define the IP address of your Puppy machine and set    #
   # the default route. Also remember to edit /etc/resolv.conf      # 
   # to include the addresses of the DNS servers                    #
   ################################################################## 
   
##  ifconfig $DEVICE 192.168.xxx.xxx netmask 255.255.255.0
##  route add -net default gateway 192.168.yyy.yyy $DEVICE

Here are the contents of my wireless.conf file

Code: Select all

==============================================
wireless.conf
===============================================
# Config for wireless card
# Change to suit your needs
# If a value is unneeded leave it as is
    # ESSID (extended network name) : My Network, any
    ESSID="MYSSID"
    # NWID/Domain (cell identifier) : 89AB, 100, off
    NWID="off"
    # Operation mode : Ad-Hoc, Managed, Master, Repeater, Secondary, auto
    MODE="Managed"
    # Frequency or channel : 1, 2, 3 (channel) ; 2.422G, 2.46G (frequency)
    FREQ="2.412G"
    CHANNEL="1"
    # Sensitivity (cell size + roaming speed) : 1, 2, 3 ; -70 (dBm)
    SENS=""
    # Bit rate : auto, 1M, 11M
    RATE="auto"
    # Encryption key : 4567-89AB-CD, s:password 
    KEY=""
    # RTS threshold : off, 500
    RTS="2347"
    # Fragmentation threshold : off, 1000
    FRAG="2346"
    # Other iwconfig parameters : power off, ap 01:23:45:67:89:AB
    IWCONFIG=""
    # iwspy parameters : + 01:23:45:67:89:AB
    # IWSPY=""
    # iwpriv parameters : set_port 2, set_histo 50 60
    # IWPRIV=""

[BlackAdder]

It looks as though ndiswrapper was in trouble using the driver you supplied, because there is a message:

Windows driver couldn't initialize the device (C000009A)

Why don't you try the bcmwl5a driver which is already installed. It is the driver commonly used for the chipset in your adapter. Removing the lsbcmnds driver should allow the bcmwl5a driver to claim it.

Code: Select all

ndiswrapper -e lsbcmnds 

You will not get any action until iwconfig shows your adapter.
Hang in there, we are making progress....I think.

[kamranzaidi]

Finally i m able to make it to work... here are the steps.

$bcmw15a was installed
$modprobe ndiswrapper
$dmesg
$iwconfig
$dhcpcd wlan0
$ifconfig [check if wlan0 got ip]
$ping kamranzaidi.com

for WEP, i added my key to wireless.conf

Code: Select all

# Encryption key : 4567-89AB-CD, s:password
    KEY="4567-89AB-CD" 

wlan0 conf at startup and even dhcpd also runs but puppy dont get ip. i have to run dhcpd manually to get ip, and i find pid file for dhcpd still there, so i delete pid file and run dhcpd again.. any idea what i am doing wrong, how i can makesure that pid get delete at shutdown?
rc.local

Code: Select all

. /etc/rc.d/rc.wireless
/sbin/dhcpd wlan0 

[BlackAdder]

If you are using the rc.wireless script you can get rid of old .pid files by uncommenting the lines close to the bottom of the script.

Code: Select all

##################################################################
# Uncomment the following lines if you have a local DHCP server  #
#################################################################
   
#  if [ -e /etc/dhcpc/*.pid ]; then
#   rm /etc/dhcpc/*.pid
#   fi
#   dhcpcd $DEVICE

Not sure why you might have to issue a separate dhcpcd command. Might possibly be a timing issue, but I would not have thought so.
dhcpcd does have a debug option (Google for the man page) and that could help track what is happening - or not happening. I have never used it so you will be pioneering.

[goncal]

Hello all

I am trying to make my Alcatel SpeedTouch 121g WiFi USB card work with Puppy 1.0.5... just downloaded wifi-beta... and of course my card is not on the list and ndiswrapper loaded but "USB device 3 is not claimed by any active driver"...

I would really like my laptop to work WiFi as I intend to install it beside the TV so that I can watch foreign channels and I am not too willing to watch them using Windows.

Thanks - cheers - Gon

[BlackAdder]

There is an entry in the ndiswrapper list that someone has been able to get the Speedtouch working, but one swallow may not make a summer.
The driver files supplied with the wifi beta dot pup do not include support for the Speedtouch.
Have you installed the Windows driver files that came with your card?
There is an explanation in the wifi beta HowTo file about installing drivers.

[goncal]

Thanks Blackadder, I never gave a thought to the fact I could use Win drivers when running Puppy. Will give it a try.

Cheers Gon

[goncal]

hi blackadder

I did try it and ndiswrapper loaded the .inf file and modprobe'd it and everything was fine as the green LED on the wifi device started flashing already. I am now in the stage of trying to actually connect to the network which is encrypted with a key.

cheers Gon

[BlackAdder]

Goncal,
There is a section in the HowTo for the wifi beta dot pup that should help you get setup for encrypted connection. There is also a rather old wiki page on WiFi connection.

Hope this helps.

[goncal]

thanks I discovered that WPA encryption is apparently trickier than other keys so I need to gather some free time and put it into solving the issue. I am now watching web TV on WinXP and really wish to leave that behind for Linux.

btw I just installed Zenwalk on an ex2 partition on my laptop which did not seem to be able to recognise the Alcatel 121g WiFi USB adapter either so will just go back to Puppy.

cheers gon

[BlackAdder]

Goncal,
Don't use WPA myself, but part of the thread on wireless network drivers has recently been about WPA. Look here:
http://www.murga.org/~puppy/viewtopic.p ... 4&start=15