I try to keep a track of the small linux distros and most, if not all, are still on 2.4 kernels. As I have a IBM t41 with built in wlan cisco aironet, now supported by post 2.6.5 kernels, Well I was delighted to see the new release from Puppy.
OK, so it saw the t41's wlan, because it lit up the icon on the panel. However, I couldn't automatically generate myself an ip from my wireless router, which was a pain as none of the usual suspects pump nor dhclient seemed to be available.
does the distro have some commandline way of getting an ip address?
Otherwise it seemed a cool distro with gxine working quite well (except for full screen, but I expected that).
I'd probably try and get some sort of temporary file storage on a USB stick and use the live CD with it, without touching the HD. Still experiemnting though.
And those are my first impressions. Well done Puppy Master!
I
IBM t41 with Cisco Aironet wireless: how to get working?
Would not describe myself as an expert, but I do have wireless working on Puppy, so here goes.
1. Open an RXVT window and check that Puppy really sees your wireless card with the command iwconfig (no params). That should show your wireless connection with name - typically wlan0.
2. Assuming you have an access point or router to talk to, you will then need to customise the wireless configuration with a command along the lines of:
iwconfig wlan0 channel 7 essid pupppplaypen mode managed key s:puppy
Of course you have to know the channel, SSID, mode and WEP key for this command to work. Italics used for the items you need to customise.
3. Once you are connected to the wireless network, you need to set the IP address (ignoring the use of DHCP for the time being) with a command looking like:
ifconfig wlan0 192.168.1.41 netmask 255.255.255.0
The above assumes that your local net has an address range of 192.168.1.xxx - commonly the case.
4. Now for a route command to tell Puppy the way to other kennels:
route add -net default gw 192.168.1.254 netmask 0.0.0.0
The gateway (gw) is the router gateway on your managed network.
5. Now open ROX and find /etc/resolv.conf; use Open as Text
Enter the DNS name server addresses given by your ISP, e.g.
nameserver 202.63.39.130
nameserver 202.63.43.130
Save the file and exit ROX.
6. Test that the connection works via Ping, e.g.
ping www.google.com
Use ctrl+c to exit from ping.
7. If that works, you can open your browser and sift the puppy litter on the internet.
8. The commands can be put into a script once they work.
Apologies if some of this is very basic. Hope it yelps - er - helps.
1. Open an RXVT window and check that Puppy really sees your wireless card with the command iwconfig (no params). That should show your wireless connection with name - typically wlan0.
2. Assuming you have an access point or router to talk to, you will then need to customise the wireless configuration with a command along the lines of:
iwconfig wlan0 channel 7 essid pupppplaypen mode managed key s:puppy
Of course you have to know the channel, SSID, mode and WEP key for this command to work. Italics used for the items you need to customise.
3. Once you are connected to the wireless network, you need to set the IP address (ignoring the use of DHCP for the time being) with a command looking like:
ifconfig wlan0 192.168.1.41 netmask 255.255.255.0
The above assumes that your local net has an address range of 192.168.1.xxx - commonly the case.
4. Now for a route command to tell Puppy the way to other kennels:
route add -net default gw 192.168.1.254 netmask 0.0.0.0
The gateway (gw) is the router gateway on your managed network.
5. Now open ROX and find /etc/resolv.conf; use Open as Text
Enter the DNS name server addresses given by your ISP, e.g.
nameserver 202.63.39.130
nameserver 202.63.43.130
Save the file and exit ROX.
6. Test that the connection works via Ping, e.g.
ping www.google.com
Use ctrl+c to exit from ping.
7. If that works, you can open your browser and sift the puppy litter on the internet.
8. The commands can be put into a script once they work.
Apologies if some of this is very basic. Hope it yelps - er - helps.
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
Wifi Info
any one with further info can add it here:
http://www.goosee.com/puppy/wikka/WiFi
(click on edit - bottom of screen - use the edit commands and save
or just add to comments for someone to add
- to register on the Wiki use a CamelCase name as it says on the front page
http://www.goosee.com/puppy/wikka/WiFi
(click on edit - bottom of screen - use the edit commands and save
or just add to comments for someone to add
- to register on the Wiki use a CamelCase name as it says on the front page
Last edited by Lobster on Fri 03 Jun 2005, 03:45, edited 1 time in total.
wireless
Just for info, I have Puppy running on a Dell Inspiron 1000 laptop with a Netgear MA401 Wireless PCMCIA card. Puppy sees this card as a standard ethernet card and I configured it from the ethernet/network wizard, no problem. These cards are fairly cheap on eBay if your in a pinch.
Dusty
d957@yahoo.com
Dusty
d957@yahoo.com
Re: IBM t41 with Cisco Aironet wireless: how to get working?
Puppy has gone back to the 2.4 kernels, but I'd guess that your wireless card can still work. If it's a G card look at the madwifi drivers here:stabu wrote: OK, so it saw the t41's wlan, because it lit up the icon on the panel. However, I couldn't automatically generate myself an ip from my wireless router, which was a pain as none of the usual suspects pump nor dhclient seemed to be available.
does the distro have some commandline way of getting an ip address?
http://mymirrors.homelinux.org/puppy/wireless/
If it's a B card this post might help:
http://www.murga.org/~puppy/viewtopic.php?p=28188
No internet on HP DV2100
HP DV2100, Celeron 1.6 GHz with 1 GB RAM.
I could connect to open wireless networks with 4.1.1, but not to my own WEP secured router!
Now the 4.2.0 doesn't even connect to open routers. Here it goes:
I try to scan for networks and :
error! Failed to raise interface eth1.
Failed command was: ifconfig eth1 up
error returned was: ifconfig: SIOCSIFFLAGS: no such file or directory
Any idea?
I could connect to open wireless networks with 4.1.1, but not to my own WEP secured router!
Now the 4.2.0 doesn't even connect to open routers. Here it goes:
I try to scan for networks and :
error! Failed to raise interface eth1.
Failed command was: ifconfig eth1 up
error returned was: ifconfig: SIOCSIFFLAGS: no such file or directory
Any idea?
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia