(old)Puppy Linux Discussion Forum

Update June 12 2008:
The version of dhcpcd in Puppy 4.x uses different locations for its configuration files than in earlier versions of Puppy.
So I have just updated the first post regarding the correct dhcpcd commands.

Hi to all
i am useing puppy2.02 with kernel 2.6.16.7.when i am connect to modem (ZTE Model no:-Classic 23) its can't connect.
when i am cat /proc/bus/usb/devices its shows me

=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=10c4 ProdID=ea60 Rev= 1.00
S: Manufacturer=Silicon Labs
S: Product=USB to UART Bridge Controller
S: SerialNumber=0001
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)
E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms

when i am useing Minisys kernel 2.6.21.7 its get connected to my pc.
when i am cat /proc/bus/usb/devices its shows me

=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=10c4 ProdID=ea60 Rev= 1.00
S: Manufacturer=Silicon Labs
S: Product=USB to UART Bridge Controller
S: SerialNumber=0001
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=cp2101
E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms

how to get cp2101.ko file for kernel 2.6.16.7 or any other source code to download this file.or any other tips or trics to connect modem (ZTE Model no:-Classic 23) with kernel 2.6.16.7.

Your device is a wireless modem, not a wifi network adaptor.
It is not relevant to this thread.

And please don't cross-post your query in multiple threads.

sorry tempestuous.
next time i do this.

Hi,

I am a newbie in Linux arena, but have enuf knowledge of command line to navigate around. I am facing a issue configuring my Vaio to have wireless net access from Puppy Linux 4.0.

Hardware:
Sony VAIO VGN CR23G
Intel Core 2 Duo 2 GHz
1 GB RAM
Intel Pro Wireless 3945

Router:
Bilion Bipac 5200 Wireles modem + Router
SSID TESTINGHOME <example>
passphrase testing <example>
WPA2-PSK using TKIP

Software:
Puppy Linux 4.00
wpa_supplicant

I have tried all the things that have been mentioned previously but am not able to access wirelessly. Any hellp will be much appreciated.


+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
ctrl_interface=/var/run/wpa_supplicant
ap_scan=2
update_config=1

network={
ssid="XXXXXXXXXX"
psk="XXXXXXXXXXX"
proto=WPA2
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
}
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The commands I ran were :

modprobe ipw3945
<<nno response>>

ifconfig eth1 up
<<nno response>>

rm /var/run/wpa_supplicant/*
<<no such file found>>

wpa_supplicant -i eth1 -D wext -c /etc/wpa_supplicant2.conf -dd
<<this runs in a loop and never comes back to console>>

<<did not run the below commands>>
rm /etc/dhcpc/*.pid
dhcpcd -t 30 -h puppypc -d eth1

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Output from the wpa_supplicant command.
I had it aborted as it was looping indefintely.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Initializing interface 'eth1' conf '/etc/wpa_supplicant2.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant2.conf' -> '/etc/wpa_supplicant2.conf'
Reading configuration file '/etc/wpa_supplicant2.conf'
ctrl_interface='/var/run/wpa_supplicant'
ap_scan=2
update_config=1
Line: 5 - start of a new network block
ssid - hexdump_ascii(len=14):
54 68 65 20 4c 6f 73 74 20 57 6f 72 6c 64 The Lost World
PSK (ASCII passphrase) - hexdump_ascii(len=14): [REMOVED]
proto: 0x2
key_mgmt: 0x2
pairwise: 0x8
group: 0x8
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='The Lost World'
Initializing interface (2) 'eth1'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=22 WE(source)=16 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1c:bf:59:b3:70
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Added interface eth1
RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
State: DISCONNECTED -> SCANNING
Trying to associate with SSID 'The Lost World'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: No WPA/RSN IE available from association info
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 2
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 02 01 00 00 0f ac 02 01 00 00 0f ac 02 00 00
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 60 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=22
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface eth1
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Cancelling scan request
Cancelling authentication timeout
WEXT: Operstate: linkmode=0, operstate=6


+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Well it may be worth trying Puppy4.1alpha3 since the wifi drivers are very different to those in Puppy4.0, and anything you learn in Puppy4.0 may have to be "re-learned" in Puppy 4.1.

Otherwise your procedure looks correct.
First I would disable encryption at the wifi router and check that a wifi connection can be made in this unencrypted state.
If OK, now I would load all encryption-related modules before running the wpa_supplicant command - Note, these modules are relevant to Puppy4.0, not Puppy4.1.

Hello,

I seem to have moved further than yesterday.
Now I am able to see via iwconfig that my router is being associated with the adapter. However I still cannot ping either the router or ny other machines in network.
The router has firewall ability which has been disabled.

eth1 IEEE 802.11g ESSID:"XXXXXXXXXXXXXXXXXXXXXXXXXXX"
Mode:Managed Frequency:2.412 GHz Access Point: 00:04:ED:78:16:46
Bit Rate:54 Mb/s Tx-Power:15 dBm
Retry limit:15 RTS thr:off Fragment thr:off
Encryption key:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Security mode:open
Power Management:off
Link Quality=91/100 Signal level=-40 dBm Noise level=-41 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:7534 Missed beacon:0


I am confused about twothings highlighted above.
1. Mode being open
I would assume that since I am using WPA , the mode should be restricted. Any idea where it can be changed to restricted.

2.Invalid misc messages
Other that this nothing else is being populated, which means all messages are being declared invalid. Can you point me in the right direction.

Thanks.

Its done atlast.

The problem was with the routing table.
It was defining a default gateway which was something other than my own router.
I just edited it with route and bingo, t was working.

Thanks for all the help.

AceVentura wrote:I seem to have moved further than yesterday.

You haven't explicitly said so, but it appears that your wpa_supplicant command now runs successfully? If so, was it the additional modules that helped?

AceVentura wrote:Now I am able to see via iwconfig that my router is being associated with the adapter.

iwconfig does not understand WPA encryption, so what it reports about your WPA-encrypted wifi connection is likely to be somewhat erroneous.

AceVentura wrote:I would assume that since I am using WPA , the mode should be restricted.

I think that "open" and "restricted" modes are relevant only to WEP encryption. Also the meaning of open/restricted can vary depending on the wifi device and driver.

AceVentura wrote:I just edited it with route and bingo, it was working.

Routing and IP assignment are the last stage of network configuration. If you can successfully run route, then a wifi connection must already be up and running.

yep, everything is working now as expected.
I had to do a bit of digging around to get it working, but finally I did it.

Wireless is orking with WPA flawlesly, no issues at all.
Thanks once again !

Yes, but what did you do differently from your first attempt that got wpa_supplicant working?
Your results could help others.

Well,

For starts, I began from scratch, deleted all the earlier files.
Then made a new configuration for wpa supplicant.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++

ctrl_interface=/var/run/wpa_supplicant
#ap_scan=1
update_config=1

network={
# scan_ssid=1
ssid="XXXXXXXXXXXXXXXX"
psk=XXXXXXXXXXXXXXXXXX
# proto=WPA
# key_mgmt=WPA-PSK
# pairwise=TKIP
# group=TKIP
}

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Note that above , I had previously used ASCII passphrase
psk="s:passphrase"
Instead this time around I converted it into hex using wpa passphrase command.
Commented all other things that I did not think were very important.

Once I ran the wpa_supplicant , I ended up having a valid eth1 interface but still pings to router were not geting any response.

Digging into this , I came across a entry in routing table like
269.192.0.0 wth netmask 255.255.0.0
This was something that I had not setup, and on a hunch I deleted this from the routing table.
After that , I was able to ping the router and access internet.

Thats all to it....
All I can say is "if you dont succeed, try again " ...thats the way I did it

Hi there, I'm having a little trouble:

So, I open rxvt and enter the following:

iwconfig wlan0 essid My_Network
iwconfig wlan0 key open My_Key
iwconfig wlan0 mode managed

My_network ist the name of my network (only letters, the first one being a cap)
My-Key ist my WEP key (consisting of letters and numbers, the first one being a capital letter)

Now, when I enter the second line I get the following error:

iwconfig: unknown command "My_Network"

What am I doing wrong?

Hi boone773,

Can post some more details ?
version of puppy u r using ?
Adapter name ?
whether your adapter is recognised ?


Cheers,
AceVentura

boone773 wrote:My-Key ist my WEP key (consisting of letters and numbers, the first one being a capital letter)

Sorry, my instructions assumed that everyone would be using the true WEP key (hexadecimal digits) and not the WEP password.
I have just updated the instructions in the first post. In short, use the s: prefix.

Thanks for your quick reply guys, I really appreciate it!

I tried with the s: prefix and got a lot further but still I can't browse.
I attached a screenshot of the commandlines.

I am currently using an ASUS WL-167G dongle.

Conncection Wizard recognizes the USB, recognizes my active network, I click on "Wireless", "Scan", click on my network, click on "WEP", enter my network key (actually the password, tried s: as prefix here but that didn't help), click "Use this profile", Wizard reports success, I click on "Acquire DHCP IP", Wizard reports success, but I cannot open any websites?!

I figured since the Wizard won't do the trick I'd try the commandline...

Any ideas?

Thanks, Boone

Edit: Attachment removed

First I would disable encryption at your wifi router and check that a wifi connection will succeed in this unencrypted mode.

If OK, I would now try with WEP encryption again, but I would pre-load all encryption-related modules before running the iwconfig commands, as explained in PART 4 of the Wifi HOWTO.

If still no success, I would try the alternative form of running dhcpcd, like this -

In my office, we have 2 desktops, 1 router, 1 USB wireless netopia ralink, rt2570. I can open puppy 3.01 on both, and access internet from the one with the router. When I try to configure on the USB connection, puppy recognizes it is rausb0, says it has a live network, but the light on the wireless device does not come on, and auto dchp cannot connect. I will try the command line instructions at the beginning of this post, but I'm not sure if I'm in the correct thread. If not, please direct me, if so please help.
Thanks
Rick

@tempestous:

No idea what the problem was with WEP, I switched to WPAPSK, used your tutorial and *bang* works perfectly fine right away!

Thanks a ton mate, you really were of great help! I could never have done this without your great howto! You're great!

pudgypup wrote:In my office, we have 2 desktops, 1 router, 1 USB wireless netopia ralink, rt2570. I can open puppy 3.01 on both, and access internet from the one with the router. When I try to configure on the USB connection, puppy recognizes it is rausb0, says it has a live network, but the light on the wireless device does not come on, and auto dchp cannot connect. I will try the command line instructions at the beginning of this post, but I'm not sure if I'm in the correct thread. If not, please direct me, if so please help.
Thanks
Rick

During a retry of config, I did a scan for the network, loaded the module, checked WEP tab, typed in the encryption key, and now I'm on!!!!

I know it looks like a "Duh" moment, but things you've seen a million times can suddenly come clear, which it did for me. Thanks All!
Rick