Tempestuous,
You are an absolute genius!!!!!!
I am writing this on my fully working wireless link on PUPPY 2 using the IPW3945 dotpup.
What can I say, this is fantastic. Thanks VERY much
Cheers
(I assume from your location you are an Australian. I now have to say I won't even begrudge you winning the Ashes back this year because of the help you have given me!!!)
Wireless driver packages for Puppy2
[quote="tempestuous"]
[...]
With Linux wifi drivers, "wifi0" is usually a "placeholder" or "virtual interface" for the true interface.[/quote]
thank you, no its only dhcpcd is not backgrounding with wlan0... so it looks like this:
sh-3.00# iwconfig wlan0 mode Managed
-> Interface is down after changeing mode, so followed by
sh-3.00# ifconfig wlan0 up
sh-3.00# iwlist wlan0 scan [you should see scan results... or interface down...]
sh-3.00# iwconfig wlan0 essid test key 1:2:3:4:5:6
sh-3.00# dhcpcd wlan0 &
[1] 24994
sh-3.00# ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:60:B3:2D:41:C8
inet addr:192.168.0.6 (...)
thats all. Great work. Thanks.
fudgy
[...]
With Linux wifi drivers, "wifi0" is usually a "placeholder" or "virtual interface" for the true interface.[/quote]
thank you, no its only dhcpcd is not backgrounding with wlan0... so it looks like this:
sh-3.00# iwconfig wlan0 mode Managed
-> Interface is down after changeing mode, so followed by
sh-3.00# ifconfig wlan0 up
sh-3.00# iwlist wlan0 scan [you should see scan results... or interface down...]
sh-3.00# iwconfig wlan0 essid test key 1:2:3:4:5:6
sh-3.00# dhcpcd wlan0 &
[1] 24994
sh-3.00# ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:60:B3:2D:41:C8
inet addr:192.168.0.6 (...)
thats all. Great work. Thanks.
fudgy
Last edited by fudgy on Thu 15 Jun 2006, 17:27, edited 1 time in total.
-
tempestuous
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
ipw3945
tempestuous
To put the finishing touch to this I am trying to automate the process of connecting the wireless access on boot. I have put all the commands (including the /sbin/ipw3945d) into the ipw3945-connect file but this doesn't seem to work, should I be doing something different?
If this is not an easy answer don't worry about spending time on it, it is not essential.
Thanks again
To put the finishing touch to this I am trying to automate the process of connecting the wireless access on boot. I have put all the commands (including the /sbin/ipw3945d) into the ipw3945-connect file but this doesn't seem to work, should I be doing something different?
If this is not an easy answer don't worry about spending time on it, it is not essential.
Thanks again
/* fudgy, do you think that the dhcpcd command should always be backgrounded as you did? */
-- no, actually i would recommend it for people with prism-card + Texas Instruments PCMCIA adaptor + Intel Chipset. Not more. It might be difficult to figure out why this happens.
We should wait a few days, maybe there's more feedback. If its really important one may ask the dhcpcd-devels and/or on Netstumbler forum. (Ch.Devine e.g.)
-- By default, the hostap_cs starts in mode Master. Likely this is on all machines. This means, if you type:
~# iwconfig wlan0 mode Managed essid wropen
then the interface will go down. This guy was confused by exactely this one:
http://www.netstumbler.org/showthread.p ... ght=dhcpcd
Greetings,
fudgy
-- no, actually i would recommend it for people with prism-card + Texas Instruments PCMCIA adaptor + Intel Chipset. Not more. It might be difficult to figure out why this happens.
We should wait a few days, maybe there's more feedback. If its really important one may ask the dhcpcd-devels and/or on Netstumbler forum. (Ch.Devine e.g.)
-- By default, the hostap_cs starts in mode Master. Likely this is on all machines. This means, if you type:
~# iwconfig wlan0 mode Managed essid wropen
then the interface will go down. This guy was confused by exactely this one:
http://www.netstumbler.org/showthread.p ... ght=dhcpcd
Greetings,
fudgy
-
tempestuous
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
smog, a script issues commands in quick succession, so if it's not working the solution is probably to put one or several "sleep" commands in to create pauses. Where, and for how long, will now require trial and error.
I would start by putting "sleep 5" just before /sbin/ip3945d, and another "sleep 5" after.
If successful, you can try removing one of them. Then try reducing the sleep period.
Please report the outcome. I will include it in the README.
fudgy, thanks for the info. I was already aware of the problems associated with changing modes, but the hostap's default master mode is news. I will incorporate this information into the hostap_README, and also the overall _Puppy2_wireless_README in case other drivers have similar issues.
It seems that each of these drivers has its own quirks.
I would start by putting "sleep 5" just before /sbin/ip3945d, and another "sleep 5" after.
If successful, you can try removing one of them. Then try reducing the sleep period.
Please report the outcome. I will include it in the README.
fudgy, thanks for the info. I was already aware of the problems associated with changing modes, but the hostap's default master mode is news. I will incorporate this information into the hostap_README, and also the overall _Puppy2_wireless_README in case other drivers have similar issues.
It seems that each of these drivers has its own quirks.
ipw3945
tempestuous
adding sleeps hasn't made any difference but I wonder if I am doing the whole process right. I am using Puppy on a dvd which I save sessions on. Once I have got the dotpup working and the wireless is connected I add the code into the script and save the session. Then when I boot in again I am not running the dotpup again and expecting the script to connect the wireless set up automatically on boot. Is this right or do I need to run either the dotpup or the script or both manually?
If I can get this working I will certainly report back, I would be happy to have helped the development process.
Cheers
adding sleeps hasn't made any difference but I wonder if I am doing the whole process right. I am using Puppy on a dvd which I save sessions on. Once I have got the dotpup working and the wireless is connected I add the code into the script and save the session. Then when I boot in again I am not running the dotpup again and expecting the script to connect the wireless set up automatically on boot. Is this right or do I need to run either the dotpup or the script or both manually?
If I can get this working I will certainly report back, I would be happy to have helped the development process.
Cheers
-
tempestuous
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
ipw3945
tempestuous
Yes I did that but it didn't seem to work.
What I am doing is booting a multi session DVD, running the dotpup, changing the script as you set out in your mesage then saving the session. When I tried this the wireless was not working when I rebooted.
What I am not clear about is; should I be able to simply reboot the saved session on the DVD and expect the wireless to be working without doing anything else, or do I have to do something manually, after booting up the saved session, to make the script work or to make the dotpup run before the script runs?
In simple terms what I have done so far is:
1) Burn multi session dvd
2) Boot Puppy
3) Run dotpup
4) Set up wireless using the commands you provided
5) Alter script to include sleep 5 commands, and save the file
6) Save session
7) Close down
Reboot the saved session
9) Open the browser, but it can't connect to the internet
Am I missing any steps or should this work?
Thanks
Yes I did that but it didn't seem to work.
What I am doing is booting a multi session DVD, running the dotpup, changing the script as you set out in your mesage then saving the session. When I tried this the wireless was not working when I rebooted.
What I am not clear about is; should I be able to simply reboot the saved session on the DVD and expect the wireless to be working without doing anything else, or do I have to do something manually, after booting up the saved session, to make the script work or to make the dotpup run before the script runs?
In simple terms what I have done so far is:
1) Burn multi session dvd
2) Boot Puppy
3) Run dotpup
4) Set up wireless using the commands you provided
5) Alter script to include sleep 5 commands, and save the file
6) Save session
7) Close down
Reboot the saved session9) Open the browser, but it can't connect to the internet
Am I missing any steps or should this work?
Thanks
-
tempestuous
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Ahh, you assumed the script would run automatically.
No, I never intended this. I intended the script to be run manually, so you could connect "on-demand" ... however, it can be made automatic if you wish.
So forget about the "sleep" commands. Just modify the script to include your SSID and WEP key.
Now launch the script from an xterminal. Does it run to completion and report an IP address?
If it works OK, you can make the process automatic at each boot by adding the script to the end of /etc/rc.d/rc.local
I personally dislike this idea, since I prefer to be in control of when my wifi connects. The concept is particularly unattractive in situations when your laptop might be at a business colleagues's office. You might not be popular when your laptop attempts to automatically connect to your colleague's wifi network.
My preference is to create a desktop icon for the script, which I just click when needed.
No, I never intended this. I intended the script to be run manually, so you could connect "on-demand" ... however, it can be made automatic if you wish.
So forget about the "sleep" commands. Just modify the script to include your SSID and WEP key.
Now launch the script from an xterminal. Does it run to completion and report an IP address?
If it works OK, you can make the process automatic at each boot by adding the script to the end of /etc/rc.d/rc.local
I personally dislike this idea, since I prefer to be in control of when my wifi connects. The concept is particularly unattractive in situations when your laptop might be at a business colleagues's office. You might not be popular when your laptop attempts to automatically connect to your colleague's wifi network.
My preference is to create a desktop icon for the script, which I just click when needed.
ipw3945
tempestuous
More good news, I have inserted sleep 4 before the /sbin/ipw3945d line and sleep 2 after it, and this makes the script work
thanks very much for all the help, Puppy is now working exactly how I want it, I am really pleased
tempestuous, you are a star
More good news, I have inserted sleep 4 before the /sbin/ipw3945d line and sleep 2 after it, and this makes the script work
thanks very much for all the help, Puppy is now working exactly how I want it, I am really pleased
tempestuous, you are a star
-
tempestuous
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
I just updated all wifi drivers, mainly to amend information in the README's, but also to add the older "ralink-legacy" drivers.
And iwpriv has been removed from all packages, since Puppy 2.01 now contains this wireless utility.
Also, kirk's Kismet dotpup has been added, and the patched version of the orinoco drivers has been added.
And iwpriv has been removed from all packages, since Puppy 2.01 now contains this wireless utility.
Also, kirk's Kismet dotpup has been added, and the patched version of the orinoco drivers has been added.
tempestuous i am giving up the idea of having my wifi usb device working with puppy in short, so i am planning to buy a pcmcia one (i want to play with aircrack) which one do u suggest me (that doesn't give problem, is B-G compatible, and is surely stable with kismet and aircrack?)
Thanks
Thanks
--
/sbin/Nevermore
/sbin/Nevermore
-
tempestuous
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
I have no experience of WEP cracking myself. I only use Kismet to scan and identify wifi access points, because my linux-wlan-ng driver won't work with WAG. This is overkill considering Kismet's size and capabilities.
Kismet will work with any wireless card which supports raw monitoring (rfmon) mode. This means almost every modern adaptor ... but I would avoid those devices for which the Linux driver is new and undeveloped - bcm43xx, marvell, prism54-softmac, and maybe zd1211.
See http://www.kismetwireless.net/ for more information.
Aircrack-ng is only fully compatible with -
MADWiFi (Atheros)
HostAP (Prism2, but not USB)
Prism54-fullmac (PrismGT)
rt2x00 (Ralink, RT2500 PCI & RT2570 USB models only)
rtl8180-sa2400 (Realtek)
There are many other reports of USB success on this forum. The ones I can recall are with the Zydas driver and Ralink drivers.
Kismet will work with any wireless card which supports raw monitoring (rfmon) mode. This means almost every modern adaptor ... but I would avoid those devices for which the Linux driver is new and undeveloped - bcm43xx, marvell, prism54-softmac, and maybe zd1211.
See http://www.kismetwireless.net/ for more information.
Aircrack-ng is only fully compatible with -
MADWiFi (Atheros)
HostAP (Prism2, but not USB)
Prism54-fullmac (PrismGT)
rt2x00 (Ralink, RT2500 PCI & RT2570 USB models only)
rtl8180-sa2400 (Realtek)
I'm using a D-Link USB adaptor (Prism2 chip) right now to send this.Nevermore wrote:i am giving up the idea of having my wifi usb device working with puppy in short
There are many other reports of USB success on this forum. The ones I can recall are with the Zydas driver and Ralink drivers.
-
tempestuous
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
-
displacedtexan
- Posts: 3
- Joined: Thu 06 Jul 2006, 04:59
Where's ipw394*.pup?
New puppy user... I was looking for a Linux distro that was lightning fast to boot up and shut down and I think I have found it with Puppy!
Now my probably... trying to install my Laptop's wireless card from:
http://www.dotpups.de/dotpups/Wifi/wireless-drivers/
is it just me, or is the ipw394*.pup file missing from the above link? I see ipw3945_README.txt but not the .pup
thanks...
Jason
Now my probably... trying to install my Laptop's wireless card from:
http://www.dotpups.de/dotpups/Wifi/wireless-drivers/
is it just me, or is the ipw394*.pup file missing from the above link? I see ipw3945_README.txt but not the .pup
thanks...
Jason
Nevermore,
Don't give up, I couldn't get my internal wireless to work, despite trying very hard!! so I bought a netgear pcmcia card. BUT, thanks to tempestuous' help, within 2 days of buying the pcmcia card, I did get the internal wireless card working.
Are you usng WEP? If so, are you sure you have set it up properly?
I found that setting the WEP key as iwconfig "key restricted MYWEPKEY" i.e. not just "key MYWEPKEY" solved my problem.
Also I spent a long time setting up iwconfig on wlan0 but it turned out I should have been using eth1.
Hope you get it working.
Don't give up, I couldn't get my internal wireless to work, despite trying very hard!! so I bought a netgear pcmcia card. BUT, thanks to tempestuous' help, within 2 days of buying the pcmcia card, I did get the internal wireless card working.
Are you usng WEP? If so, are you sure you have set it up properly?
I found that setting the WEP key as iwconfig "key restricted MYWEPKEY" i.e. not just "key MYWEPKEY" solved my problem.
Also I spent a long time setting up iwconfig on wlan0 but it turned out I should have been using eth1.
Hope you get it working.
I have repeated my tests of the bcm43xx-softmac.pup in Puppy 2.01. The results are different from what I reported to tempestuous in a PM, but, unfortunately, the dotpup still doesn't work. Using ndiswrapper does work well though.
This is a summary of printouts during testing.
The Dell Inspiron 510m laptop uses the Broadcom BCM94306 chip (802.11b/g). It has built-in 10/100 cable ethernet which was disconnected during testing.
# modprobe bcm43xx
dmesg shows:
I repeated the test with fw I got using fwcutter on Dell's latest XP driver, but I got the same results
Using ndiswrapper with two versions of XP drivers worked well.
dmesg output with older driver:
Tempestuous, thanks anyway for your effort in trying to make this work
Paul
This is a summary of printouts during testing.
The Dell Inspiron 510m laptop uses the Broadcom BCM94306 chip (802.11b/g). It has built-in 10/100 cable ethernet which was disconnected during testing.
# modprobe bcm43xx
dmesg shows:
ieee80211_crypt: no version for "struct_module" found: kernel tainted.
ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, git-1.1.7
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
bcm43xx driver
ACPI: PCI Interrupt 0000:01:03.0[A] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5
bcm43xx: Chip ID 0x4306, rev 0x3
bcm43xx: Number of cores: 5
bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243, enabled
bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243, disabled
bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243, enabled
bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243, disabled
bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243, enabled
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 2, Type 2, Revision 2
bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
bcm43xx: Radio turned off
bcm43xx: Radio turned off
I tried using a static IP address, but the interface still didn't work.sh-3.00# iwconfig eth1
eth1 IEEE 802.11b/g ESSID:off/any Nickname:"Broadcom 4306"
Mode:Managed Access Point: Invalid Bit Rate=1 Mb/s
RTS thr:off Fragment thr:off
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
# iwconfig eth1 essid MyAP
# iwconfig eth1
eth1 IEEE 802.11b/g ESSID:"MyAP" Nickname:"Broadcom 4306"
Mode:Managed Access Point: Invalid Bit Rate=1 Mb/s
RTS thr:off Fragment thr:off
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
# dhcpcd -t 30 -h puppypc -d eth1
dhcpcd: MAC address = 00:90:96:be:f5:41
# ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:90:96:BE:F5:41
BROADCAST MULTICAST MTU:1500 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:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:11 Base address:0x8000
I repeated the test with fw I got using fwcutter on Dell's latest XP driver, but I got the same results
Using ndiswrapper with two versions of XP drivers worked well.
dmesg output with older driver:
ndiswrapper version 1.15 loaded (preempt=no,smp=no)
ndiswrapper: driver bcmwl5 (Broadcom,07/17/2003, 3.30.15.0) loaded
ACPI: PCI Interrupt 0000:01:03.0[A] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5
ndiswrapper: using irq 5
wlan0: vendor: ''
wlan0: ndiswrapper ethernet device 00:90:96:be:f5:41 using driver bcmwl5, 14E4:4320.5.conf
wlan0: encryption modes supported: WEP; TKIP with WPA; AES/CCMP with WPA
dmesg output with latest Dell XP driver:# iwconfig wlan0
wlan0 IEEE 802.11g ESSID:"MyAP"
Mode:Managed Frequency:2.412 GHz Access Point: 00:11:2F:9D:1F:4A
Bit Rate:54 Mb/s Tx-Power:14 dBm
RTS thr:2347 B Fragment thr:2346 B
Encryption key:off
Power Management:off
Link Quality:100/100 Signal level:-24 dBm Noise level:-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
# ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:90:96:BE:F5:41
inet addr:192.168.0.125 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:90239 errors:0 dropped:0 overruns:0 frame:0
TX packets:72610 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:128777710 (122.8 MiB) TX bytes:6776522 (6.4 MiB)
Interrupt:5 Memory:fcffc000-fcffe000
ndiswrapper version 1.15 loaded (preempt=no,smp=no)
ndiswrapper: driver bcmwl5 (Broadcom,11/02/2005, 4.10.40.0) loaded
ACPI: PCI Interrupt 0000:01:03.0[A] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5
ndiswrapper: using irq 5
wlan0: vendor: ''
wlan0: ndiswrapper ethernet device 00:90:96:be:f5:41 using driver bcmwl5, 14E4:43200003.5.conf
wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
0003.5.confPerhaps the information above can be useful in troubleshooting the dotpup.# iwconfig wlan0
wlan0 IEEE 802.11g ESSID:"MyAP"
Mode:Managed Frequency:2.412 GHz Access Point: 00:11:2F:9D:1F:4A
Bit Rate:54 Mb/s Tx-Power:32 dBm
RTS thr:2347 B Fragment thr:2346 B
Encryption key:off
Power Management:off
Link Quality:100/100 Signal level:-33 dBm Noise level:-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
# ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:90:96:BE:F5:41
inet addr:192.168.0.125 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:48073 errors:0 dropped:0 overruns:0 frame:0
TX packets:34960 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:68738464 (65.5 MiB) TX bytes:3340065 (3.1 MiB)
Interrupt:5 Memory:fcffc000-fcffe000
Tempestuous, thanks anyway for your effort in trying to make this work
Paul