Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Wed 22 Oct 2014, 08:31
All times are UTC - 4
 Forum index » Advanced Topics » Hardware
Wireless driver packages for Puppy2
Moderators: Flash, Ian, JohnMurga
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
Page 3 of 7 Posts_count   Goto page: Previous 1, 2, 3, 4, 5, 6, 7 Next
Author Message
smog

Joined: 13 Jun 2006
Posts: 134

PostPosted: Thu 15 Jun 2006, 08:08    Post_subject: ipw3945  

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!!!)
Back to top
View user's profile Send_private_message 
fudgy


Joined: 07 Jun 2006
Posts: 86
Location: Berlin, Germany

PostPosted: Thu 15 Jun 2006, 08:52    Post_subject:  

[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

Edited_time_total
Back to top
View user's profile Send_private_message 
tempestuous

Joined: 10 Jun 2005
Posts: 5271
Location: Australia

PostPosted: Thu 15 Jun 2006, 09:46    Post_subject:  

Good news smog. I will amend the ipw3945 README shortly.
I don't assume the Ashes will return to Australia next time. It appears the English now have a good cricket team.

fudgy, do you think that the dhcpcd command should always be backgrounded as you did?
Back to top
View user's profile Send_private_message 
smog

Joined: 13 Jun 2006
Posts: 134

PostPosted: Thu 15 Jun 2006, 13:17    Post_subject: 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
Back to top
View user's profile Send_private_message 
fudgy


Joined: 07 Jun 2006
Posts: 86
Location: Berlin, Germany

PostPosted: Thu 15 Jun 2006, 14:35    Post_subject:  

/* 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.php?t=12471&highlight=dhcpcd

Greetings,
fudgy
Back to top
View user's profile Send_private_message 
tempestuous

Joined: 10 Jun 2005
Posts: 5271
Location: Australia

PostPosted: Thu 15 Jun 2006, 23:20    Post_subject:  

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.
Back to top
View user's profile Send_private_message 
smog

Joined: 13 Jun 2006
Posts: 134

PostPosted: Fri 16 Jun 2006, 12:38    Post_subject: 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
Back to top
View user's profile Send_private_message 
tempestuous

Joined: 10 Jun 2005
Posts: 5271
Location: Australia

PostPosted: Tue 20 Jun 2006, 23:21    Post_subject:  

smog, I was suggesting that you modify your wifi script /root/my-applications/bin/ipw3945-connect so it looks like this -

modprobe ipw3945
sleep 5
/sbin/ipw3945d
sleep 5
ifconfig eth0 up
... etc
Back to top
View user's profile Send_private_message 
smog

Joined: 13 Jun 2006
Posts: 134

PostPosted: Wed 21 Jun 2006, 05:10    Post_subject: 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
Cool 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
Back to top
View user's profile Send_private_message 
tempestuous

Joined: 10 Jun 2005
Posts: 5271
Location: Australia

PostPosted: Wed 21 Jun 2006, 06:48    Post_subject:  

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.
Back to top
View user's profile Send_private_message 
smog

Joined: 13 Jun 2006
Posts: 134

PostPosted: Thu 22 Jun 2006, 17:44    Post_subject: 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
Back to top
View user's profile Send_private_message 
tempestuous

Joined: 10 Jun 2005
Posts: 5271
Location: Australia

PostPosted: Mon 26 Jun 2006, 21:07    Post_subject:  

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.
Back to top
View user's profile Send_private_message 
Nevermore

Joined: 26 Nov 2005
Posts: 365
Location: Italy

PostPosted: Tue 27 Jun 2006, 18:22    Post_subject:  

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

_________________
--
/sbin/Nevermore
Back to top
View user's profile Send_private_message 
tempestuous

Joined: 10 Jun 2005
Posts: 5271
Location: Australia

PostPosted: Tue 27 Jun 2006, 22:22    Post_subject:  

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)

Nevermore wrote:
i am giving up the idea of having my wifi usb device working with puppy in short

I'm using a D-Link USB adaptor (Prism2 chip) right now to send this.
There are many other reports of USB success on this forum. The ones I can recall are with the Zydas driver and Ralink drivers.
Back to top
View user's profile Send_private_message 
pakt


Joined: 04 Jun 2005
Posts: 1089
Location: Sweden

PostPosted: Wed 28 Jun 2006, 04:44    Post_subject:  

tempestuous, thanks again for all your work in keeping the drivers up-to-date Smile

I have just tried the bcm43xx-softmac.pup. Unfortunately, there seems to be a bug in the script. When I click on 'OK to install', only an Xdialog usage window pops up.

Paul
Back to top
View user's profile Send_private_message 
Display_posts:   Sort by:   
Page 3 of 7 Posts_count   Goto page: Previous 1, 2, 3, 4, 5, 6, 7 Next
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
 Forum index » Advanced Topics » Hardware
Jump to:  

Rules_post_cannot
Rules_reply_cannot
Rules_edit_cannot
Rules_delete_cannot
Rules_vote_cannot
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0794s ][ Queries: 13 (0.0062s) ][ GZIP on ]