(old)Puppy Linux Discussion Forum

Dougal wrote:One thing I wasn't sure about, though: with WPA, it mentions using WEP-40, while the wizard actually says it uses WPA/TKIP... is this ok?

No, there's something wrong here.
"WEP40" relates only to WEP encryption.
The Group Cipher/Pairwise Ciphers for WPA should be "TKIP"
and the Group Cipher/Pairwise Ciphers for WPA2 should be "AES"

Dougal, you say you are using rt73usb; does that mean you are using the actual rt73usb module from one of the 2.6.25.x kernels in the 4.1alpha series?
If so, that's good news that WPA works, because some of the new wifi drivers (such as rt2500pci) have been reported to fail with WPA.

hayagix wrote:The only flaw I noticed is that it specified wep when it scanned for networks.

What do you mean "specified"? You mean the scan window told you the encryption is WEP, when in fact it was WPA/WPA2? If so, could you post here the output of "iwlist wlan0 scan" (replace wlan0 with your interface name), so I can try and find out why it is wrong?

tempestuous wrote:

Dougal wrote:One thing I wasn't sure about, though: with WPA, it mentions using WEP-40, while the wizard actually says it uses WPA/TKIP... is this ok?

No, there's something wrong here.
"WEP40" relates only to WEP encryption.
The Group Cipher/Pairwise Ciphers for WPA should be "TKIP"
and the Group Cipher/Pairwise Ciphers for WPA2 should be "AES"

Well... google finds all kinds of variants on what is displayed. this shows the WEP-40, but in some AP's actually shows both WEP-40/WEP-40 and WEP-40/TKIP WEP-40!
In any case, this guy has the WEP-40 thing, but his wpa_supplicant.conf uses WPA-PSK/TKIP, so I guess it's ok.

Dougal, you say you are using rt73usb; does that mean you are using the actual rt73usb module from one of the 2.6.25.x kernels in the 4.1alpha series?
If so, that's good news that WPA works, because some of the new wifi drivers (such as rt2500pci) have been reported to fail with WPA.

I don't actually use it to connect to a WPA AP, it's just the info shown by foreign networks that I detect. I'm using a 2.6.24 kernel.

I've updated the original post, adding support for detection WPA2 through "Extra:rsn_ie".

"What do you mean "specified"? You mean the scan window told you the encryption is WEP, when in fact it was WPA/WPA2? "

Yes.

sh-3.00# iwlist wlan0 scan
wlan0 Scan completed :
Cell 01 - Address: 00:60:B3:A4:F5:7E
ESSID:"WDM 2"
Mode:Managed
Channel:6
Encryption key:on
Bit Rates:0 kb/s
Cell 02 - Address: 06:60:B3:A4:F5:7E
ESSID:"WDM2WLAN2"
Mode:Managed
Channel:6
Encryption key:off
Bit Rates:0 kb/s

sh-3.00# iwconfig
lo no wireless extensions.

ra0 RT2500 Wireless ESSID:""
Mode:Managed Frequency=2.412 GHz Bit Rate=11 Mb/s
RTS thr:off Fragment thr:off
Encryption key:off
Link Quality:0 Signal level:136 Noise level:177
Rx invalid nwid:0 invalid crypt:0 invalid misc:0

eth0 no wireless extensions.

wlan0 RT73 WLAN ESSID:"WDM 2"
Mode:Managed Frequency=2.437 GHz Access Point: 00:60:B3:A4:F5:7E
Bit Rate=18 Mb/s
RTS thr:off Fragment thr:off
Encryption key:C12B-00E1-D136-07DF-7592-9507-EFBA-506F-29C3-TT8D-49A9-FC4F-0248-1958-R9F1-A8A4
Link Quality=63/100 Signal level:-74 dBm Noise level:-115 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

hayagix wrote: sh-3.00# iwlist wlan0 scan
wlan0 Scan completed :
Cell 01 - Address: 00:60:B3:A4:F5:7E
ESSID:"WDM 2"
Mode:Managed
Channel:6
Encryption key:on
Bit Rates:0 kb/s

Is this network encrypted with WPA? If so, it seems like the driver doesn't supply us with any info, so we can't rely on it and I'll have to disable that feature...
However, I was wondering: which kernel are you using? You have a rt73 and I know that for me the rt73usb does show that info, so maybe you're using an older driver?

The network is encrypted with Wpa-psk.
Dingo 4.0 install with default kernel. 2.6.21.7

hayagix wrote:The network is encrypted with Wpa-psk.
Dingo 4.0 install with default kernel. 2.6.21.7

Ok, so I guess I'll have to disable that feature until Barry stops using the old kernels...

4.1 will not use that kernel. I can't recall what it was right now, but I had problems when tried to run 4.1alpha5 built with the 2.6.21.7 kernel.

So in Unleashed I will only provide the 2.6.25.15 kernel -- but there will be a choice of the standard and conservative versions (at least until or if we can find out if we really o need the conservative kernel).

EDIT: Oh yeah, different kernel uevents. Something else too, but can't think what.

4.1 alpha 6: rt73usb
Default network manager brings up the network with "encryption on". Will not connect.

4.1 alpha 6: rt73usb
Updated network manager detects network as "Master; Encryption: WPAWPA2". Refuses to connect.

Cannot connect rt2500 usb using windows drivers on two other machines with alpha 6.

It would be nice if puppy and the network wizard allowed the user to configure the speed and duplexity of the ethernet interfaces. This would assist with speeding up transfers across the local area network.

jcoder24

something like this?

http://www.cyberciti.biz/tips/howto-lin ... anent.html


Aitch

Like that or even with mii-tool depending on size.

http://linux-ip.net/html/tools-mii-tool.html

developer's site /2005 tool

http://j.metux.de/index.php?option=com_ ... &Itemid=30

freshmeat

http://freshmeat.net/projects/mii-tool/

Aitch

Dougal,
JustGreg has just reported a WPA connection failure using the Network Wizard in 4.1alpha6, even though he can successfully make a WPA connection using manual commands.
http://www.murga-linux.com/puppy/viewto ... 637#225637

I'm very suspicious about the "wpa_cli" stuff around line 1000 of wag-profiles.sh. I'm sure wpa_cli does something useful, but it's black magic to me, and I can connect to a WPA router without using it.
Do we really need wpa_cli?
Could we just set up the wpa_supplicant.conf file in a simple way - maybe echo the correct contents once the user has defined their SSID and PSK?

Hi folks, there's issues with some people reporting in the eeetiger forum (TigerPup on eeepc) that WPA only works with TKIP, i.e., the AEP algorithim is not supported. Has anyone else run across this in Puppy? TigerPup is based on Puppy 3.01, and currently uses the 3.01 version of the network wizard. Is this latest redesign likely to fix this problem, or is it more ingrained than that? Thanks!
~dinky

hayagix wrote:4.1 alpha 6: rt73usb
Updated network manager detects network as "Master; Encryption: WPAWPA2". Refuses to connect.

I fixed the WPAWPA2 part. The WPA connection problems will need more serious looking into, likely with tempestuous.
You could try running the wizard from a terminal (net-setup.sh -d) and see if you get any helpful error messages.

jcoder24 wrote:It would be nice if puppy and the network wizard allowed the user to configure the speed and duplexity of the ethernet interfaces. This would assist with speeding up transfers across the local area network.

I could probably add some "extra settings" button to the interface dialog, allowing to control such things, but I first need to know Barry will agree to add ethtool to Puppy... (it is also used by laptop-mode-tools to disable wake-on-lan)

tempestuous wrote:Dougal,
JustGreg has just reported a WPA connection failure using the Network Wizard in 4.1alpha6, even though he can successfully make a WPA connection using manual commands.
http://www.murga-linux.com/puppy/viewto ... 637#225637

I'm very suspicious about the "wpa_cli" stuff around line 1000 of wag-profiles.sh. I'm sure wpa_cli does something useful, but it's black magic to me, and I can connect to a WPA router without using it.
Do we really need wpa_cli?
Could we just set up the wpa_supplicant.conf file in a simple way - maybe echo the correct contents once the user has defined their SSID and PSK?

I know wicd uses templates and just substitutes the right fields, which should be easy to do.
I always assumed that wpa_cli sets each field individually and then it gets written to the wpa_supplicant.conf...
I'll have a look at what Grep writes and see what I can do.

I think I have raised this before, but I still hope, some day the FireWire (1394) is detected and that it can be configured to do eth IPv4 over FireWire.

Now I do it by hand: Well in fact it's in rc.local
But since Dingo 406 this doesn't work anymore and I have to type in rxvt: Kinda annoying.