Damn Small Linux (DSL) Forums
Welcome, Guest. Please login or register.
Did you miss your activation email?
October 23, 2014, 05:59:45 PM

Login with username, password and session length
News
The new DSL forums are now open.
Stats
297752 Posts in 294154 Topics by 210 Members
Latest Member: stojanov
Search:     Advanced search
* Home Help Search Login Register
Get The Official Damn Small Linux Book. Great VPS hosting provided by Tektonic

+  Damn Small Linux (DSL) Forums
|-+  Damn Small Linux
| |-+  HD Install
| | |-+  How to save iwconfig (network) settings?
« previous next »
Pages: [1] Print
Author Topic: How to save iwconfig (network) settings?  (Read 1425 times)
pcm2a
Newbie
*
Posts: 16


View Profile Email
« on: August 15, 2013, 11:04:25 PM »

I have DSL 4.11rc2 installed to a Compaq LTE Elite 4/75 mhz laptop and I have an Orinoco prism wifi card.

I can execute the following commands from the prompt and have working wifi:
> iwconfig
- Shows my wifi card as eth0
> iwconfig eth0 essid NETGEAR-2.4-G
> iwconfig eth0 key myhexkeyhere
> iwconfig eth0 commit
- SET Failed on device eth0 ; Operation not supported.
> pump -i eth0

What is the proper way to save the network settings so it connects on startup?
Logged
CNK
Full Member
***
Posts: 151


View Profile
« Reply #1 on: August 16, 2013, 08:09:55 AM »

You can put all the commands in the file "/opt/bootlocal.sh". Open a root terminal and use nano or another text editor to insert your commands.

Also, all the iwconfig commands (well at least the first two, I don't know what lead to you using the "commit" command) can be placed in the one line. eg. "iwconfig eth0 essid NETGEAR-2.4-G key myhexkeyhere".
Logged
pcm2a
Newbie
*
Posts: 16


View Profile Email
« Reply #2 on: August 16, 2013, 01:09:29 PM »

When I ran iwconfig --help 'commit' was one of the options.  I wonder what it does.
Logged
CNK
Full Member
***
Posts: 151


View Profile
« Reply #3 on: August 17, 2013, 12:52:21 AM »

From the man Page (http://linux.die.net/man/8/iwconfig):

Quote
commit

Some cards may not apply changes done through Wireless Extensions immediately (they may wait to aggregate the changes or apply it only when the card is brought up via ifconfig). This command (when available) forces the card to apply all pending changes.
This is normally not needed, because the card will eventually apply the changes, but can be useful for debugging.

I'd try starting the wifi without the "commit" command and if it still works, leave it out of the bootlocal.sh command. The "essid" and "key" commands are often all you need to connect with iwconfig (followed by "pump", of course).
Logged
pcm2a
Newbie
*
Posts: 16


View Profile Email
« Reply #4 on: August 17, 2013, 06:47:42 PM »

Thanks for that info. The commit command definitely isn't needed, I stopped using it after it failed.

On a positive note, I also popped in a Cisco Aironet 340 card and it works out of the box too.
Logged
Pages: [1] Print 
« previous next »
Jump to:  

Powered by SMF 1.1.19 | SMF © 2013, Simple Machines
Mercury design by Bloc