startup and networking

heathen · 2007-03-19 01:51:38

when booting my computer networking hangs then fails to load...
this is my error

Error for wireless request "Set Encode" (8B2A)
set failed on eth1: operation not supported

when It finally boots i can run #/etc/rc.d/network restart and it works every time.

What am I doing wrong??

skottish · 2007-03-19 02:01:29

Something like this?

http://www.knoppix.net/forum/viewtopic.php?p=15585

heathen · 2007-03-19 02:05:47

i dont understand that. what am I supposed to do?

sorry, I'm still the noob.

junglepeanut · 2007-03-19 02:12:56

Before reading below realize I know nothing and this is me just guessing.

Also post your config files (you can comment out the keys if you like etc.

Is this every time or intermittent?
This happens most of the time here but sometimes it works...

This error comes from a lot of things. (at least in my experience i.e. not root, bad essid, etc.) I have found some fixes like splitting the commands that go to iwconfig to two lines and this fixes it every time that it is not a simple error.

What I mean is-- if essid is one line and the key is the next, mine works everytime, but combined they fail. (Combined (network restart) does work if the boot failed sometimes otherwise it freezes my computer so I don't mess with it much.) So I am changing the netcfg script to make it work for me...but I am still learning and have my own work to do so it will be finished tomorrow or the next day hopefully.

Should be enough in here for you to make changes to your own as well if you want.

Last edited by junglepeanut (2007-03-19 02:13:35)

heathen · 2007-03-19 02:29:14

this does happen at every start...
this started happening after i added the network key..

/etc/conf.d/wireless

wlan_eth1="eth1 essid lostsanity key (128bit wepkey)"
WLAN_INTERFACES=(eth1)

/etc/rc.conf

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
TIMEZONE="United States/Eastern"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

#
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=()
#
# Modules to load at boot-up (in this order)
#   - prefix a module with a ! to blacklist it
#
MODULES=(sky2 ipw2200 acpi-cpufreq cpufreq-ondemand) 
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="laptop"
#
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available
# interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
lo="lo 127.0.0.1"
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
eth1="dhcp"
INTERFACES=(lo !eth0 eth1)
#
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
#
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network-profiles
#
#NET_PROFILES=(main)

#
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng network netfs crond alsa acpid cpufreq)


# End of file

anything else that might be helpfull?

junglepeanut · 2007-03-19 09:35:55

Ok, I am no network guru. Just going to add some stuff I found useful. I also have the ipw-2200 and I think a lot of this has to do with it in specific, like it needs time to do each command or something.

If you run lsmod and see eth1394 loaded at boot, try blacklisting it, (I noticed when I did connect it happened much faster with this blacklisted.)

Next the etc/conf.d/wireless method does not work for me.
I found that if you do it this way (thanks to someone for making me see the menu option too) things work better...not much. So I just have the comments in there right now.

Under /etc/network-profiles/ you will find a template. Make a few copies (or one if you only need one) calling them the names of the places you connect wirelessly or whatever.

An example template that I have saved as /etc/network-profiles/mywlan is:

#
# Network Profile
#

DESCRIPTION="MyWLAN"

# Network Settings
INTERFACE=eth1
HOSTNAME=XXX

# Interface Settings (use IFOPTS="dhcp" for DHCP)
IFOPTS="dhcp"
#GATEWAY=192.168.0.1

# DNS Settings (optional)
#DOMAIN=localdomain
#DNS1=
#DNS2=

# Wireless Settings (optional)
ESSID="MyWLAN"
KEY="ababababababababababababab"
IWOPTS="essid $ESSID key $KEY"

#WIFI_INTERFACE=wlan0   # use this if you have a special wireless interface
                        # that is linked to the real $INTERFACE

#WIFI_WAIT=5            # seconds to wait for the wireless card to
                        # associate before bringing the interface up
#USEWPA="yes"           # start wpa_supplicant with the profile
#WPAOPTS=""             # use "" for normal operation or specify additional
                        # options (eg, "-D ipw")
                        # see /etc/wpa_supplicant.conf for configuration
#AUTOWPA="yes"          # automatically configure WPA
#PASSKEY=""             # wpa passkey/phrase. for use with AUTOWPA

The above only works intermittently (my two liner is still in testing lol seriously I don't want to mess up anyones pc ... yet).

Now so you can choose which wireless access point you are near on boot change the NET_PROFILES=(main) to NET_PROFILES=(menu) ...(or just the file you want if you only have one...) in /etc/rc.conf

This should work...sometimes maybe even most of the time.

Two more things I would like to add:

For a longer menu time:
http://bbs.archlinux.org/viewtopic.php?id=30811

And consider adding ifplugd to daemons in rc.conf (you may need to install it.) That way you have auto-detect when eth0 is plugged in.

Let me know if this is enough for yours to get working (I might have changed a few other config files...)
if it is let me know if you get the intermittent hiccup. Thanks

Last edited by junglepeanut (2007-03-19 09:37:20)

heathen · 2007-03-19 22:04:19

this is beginning to hurt my head
/etc/conf.d/wireless worked fine untill I added the key in. As long as there is no key, it works every time.
/etc/network-profiles/main hangs and fails but the normal boot starting network works...

if i disable network-profiles. i have a hang period of atleast a minute before starting network fails.
if I enable network-profiles. it hangs at boot for about a minute, then fails. BUT starting network works.

either way I have a hang period... I'm so confused... lol

junglepeanut · 2007-03-19 22:12:54

OK, I am not sure what could be yours, maybe yours needs the two liner.

main is the name of your file in network-profiles right?

Worst case scenario you could right a script that is run as soon as you login.

Also could you give an example of how you insert your key ... and does it have any special symbols. Might be a router setting as well.

junglepeanut · 2007-03-19 22:16:50

Could you post content of those files now? You know all the wireless ones. Maybe there are conflicts from switching so many times.

heathen · 2007-03-19 23:21:22

sorry, i was eating dinner.... yay for salmon
by the way, thanks for the help...

my /etc/conf.d/wireless hasnt changed
/etc/network-profiles/main

#
# Network Profile
#

DESCRIPTION="Default Network Profile"

# Network Settings
INTERFACE=eth1
HOSTNAME=myhost

# Interface Settings (use IFOPTS="dhcp" for DHCP)
#IFOPTS="192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
IFOPTS="dhcp"
#GATEWAY=192.168.0.1

# DNS Settings (optional)
#DOMAIN=localdomain
#DNS1=192.168.0.1
#DNS2=

# Wireless Settings (optional)
ESSID=lostsanity
KEY=1........................4
#IWOPTS="mode managed essid $ESSID channel 6 key restricted $KEY"
IWOPTS="essid $ESSID key $KEY"

#WIFI_INTERFACE=wlan0   # use this if you have a special wireless interface
                                        # that is linked to the real $INTERFACE

#WIFI_WAIT=5                 # seconds to wait for the wireless card to
                                       # associate before bringing the interface up
#USEWPA="yes"               # start wpa_supplicant with the profile
#WPAOPTS=""                 # use "" for normal operation or specify additional
                                      # options (eg, "-D ipw")
                                      # see /etc/wpa_supplicant.conf for configuration
#AUTOWPA="yes"          # automatically configure WPA
#PASSKEY=""                # wpa passkey/phrase. for use with AUTOWP

I tried the essid both with and without quotes around them... no diffrence

I dont particularly need the network-profiles bit... as my laptop rarely leaves my house (battery life of 7 minutes kinda blows)... when it does leave, it's a wired connection anyway... then i just blacklist eth1 and enable eth0

junglepeanut · 2007-03-20 00:26:52

I am guessing you also did not have the eth1394 mod to blackout.

OK, comment out everything in /etc/conf.d/wireless that way you can put it back if you like.

Try putting quotes around like below. I think they both need to be in quotes.

ESSID="lostsanity"
KEY="26thingies"

Hmm, another idea after above, check after boot (if it fails) before network restart

iwconfig

If it says your
1.)essid correctly
2.) key correctly

If 2 is blank then you have the same issue I have and the second command is hitting it too quick or something such that the second time it normally gets it.

If that is the case I will post the two liner ... which I haven't edited more, yet, because unconceivably mine has not failed in 24 hours...

Last edited by junglepeanut (2007-03-20 00:27:31)

heathen · 2007-03-20 01:12:47

i tried the essid and key in quotes and out of quotes... no diffrence

output of iwconfig

lo        no wireless extensions.

eth0      no wireless extensions.

eth1      IEEE 802.11b  ESSID:"lostsanity"  
          Mode:Managed  Frequency:2.447 GHz  Access Point: 00:06:25:7D:76:95   
          Bit Rate:11 Mb/s   Tx-Power=20 dBm   Sensitivity=8/0  
          Retry limit:7   RTS thr:off   Fragment thr:off
          Encryption key:1...-....-....-....-....-....-.4   Security mode:open
          Power Management:off
          Link Quality=68/100  Signal level=-32 dBm  Noise level=-87 dBm
          Rx invalid nwid:0  Rx invalid crypt:33  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:30

Last edited by heathen (2007-03-20 01:13:52)

junglepeanut · 2007-03-20 13:51:59

I am at a loss since yours looks like it is nows the device and key etc. Maybe someone else will chime in, this is different than my issue.

One more thing is your device supposed to be mode:open or is it supposed to be mode:managed. Since restart works I bet this doesn't need to be changed.

Also you have the wrong hostname in main.

Good luck, I have am at a loss but will keep reading posts.

heathen · 2007-03-20 21:04:07

heh, thanks for telling me about my hostname... just to be sure i tried it. It still doesnt work.

All of this started when I added the key in. I dont really want to run an unsecured wireless network. I just need to figure out what I need to do to make the key work properly.

junglepeanut · 2007-03-20 21:31:52

Also the key is hex right? If it is ascii are you doing like posted above by scottish. (Doubt it is this since restart works.)

Another thing you could do (reading from "man iwconfig") is append commit to your iwopts as it says this makes things take effect as of the command instead of when brought up, or something like that. Lastly it says that commit can be useful for debugging.

You might want to try taking eth1 out of rc.conf also per Judd (I don't need to do this though)
http://www.archlinux.org/pipermail/arch … 04855.html

Last edited by junglepeanut (2007-03-20 21:37:00)

heathen · 2007-03-20 21:44:46

when i run iwconfig right after boot this comes up

$ iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

eth1      unassociated  ESSID:"lostsanity"  
          Mode:Managed  Channel=0  Access Point: Not-Associated   
          Bit Rate:0 kb/s   Tx-Power=20 dBm   Sensitivity=8/0  
          Retry limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

no key...

junglepeanut · 2007-03-20 23:59:00

OK, that is my issue the two seem to hit to fast, but mine is only intermittent. I am going to try booting under my old script and see if it works still then I will post it. Funny now two days in a row mine has not done the above with the stock script.

OK, it is not working, maybe something changed in the last few days and that is why mine is now working better. Hmm, I work on getting the other working but no guarantees as I spent two months getting it to work the way it did before. (I am not a good programmer.)

Have you set your hostname in dhclient.conf?

Last edited by junglepeanut (2007-03-21 00:09:25)

heathen · 2007-03-21 00:25:40

i dont appear to have that file anywhere...

heathen · 2007-03-21 00:54:57

out of curiosity, i checked dmesg

ieee80211_crypt: registered algorithm 'WEP'
ieee80211_crypt_wep: could not allocate crypto API arc4
eth1: could not initialize WEP: load module ieee80211_crypt_wep
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
Mobile IPv6
eth1: no IPv6 routers present

any ideas?

junglepeanut · 2007-03-21 11:32:32

The problem has to be the

ieee80211_crypt_wep: could not allocate crypto API arc4
eth1: could not initialize WEP: load module ieee80211_crypt_wep

as I have the rest of that stuff.

We could try doing like it says and load the module in rc.conf (lsmod shows it loaded for me but I do not have it in rc.conf).

$ lsmod | grep ipw
ipw2200               141768  0 
ieee80211              30536  1 ipw2200
$ lsmod | grep ieee
ieee80211_crypt_wep     4480  1 
ieee1394               84056  1 ohci1394
ieee80211              30536  1 ipw2200
ieee80211_crypt         4992  2 ieee80211_crypt_wep,ieee80211

Searching google I have found loads of that error even someone like me who it seems to have had it just vanish on its own using Arch.

http://bbs.archlinux.org/viewtopic.php?pid=228771

This guy had to recompile his kernel but I don't think you need that as after boot yours works.

http://www.lastlog.de/wiki/index.php/IB … encryption

This thread points to it first being a intel bug but later a kernel bug as the above states. But it is interesting to note from reading it that there seem to be three fixes. First, try reinstalling ipw2200 and ipw2200-fw (apparently there is also an intel patch but I could not find a link to it anywhere.). Second if this doesn't work try a newer HAL, or reinstall it. Lastly, patch the kernel with ARC4 or wait for Linus T. to fix it in the kernel.

http://www.gossamer-threads.com/lists/l … nel/739985

The HAL thing is interesting, maybe you could add that to your daemons to make it go away. ( I have these daemons.)

DAEMONS=(syslog-ng network netfs crond ifplugd hal acpid)

Maybe even put hal close to the front so it is on first??? Like after syslog-ng but before network? I don't know anything.

Last edited by junglepeanut (2007-03-21 12:03:20)

junglepeanut · 2007-03-21 11:57:55

As far as dhclient.conf, I forgot I went through the headache of this not working and tried installing many different internet connecting tools. i.e.

 pacman -Qs dhc
local/dhcdbd 1.14-4
    DHCP D-BUS daemon (dhcdbd) controls dhclient sessions with D-BUS, stores and
    presents DHCP options
local/dhclient 3.0.4-1
    dhclient is standalone client from the dhcp package
local/dhcpcd 1.3.22pl4-4
    A DHCP client daemon

None of them fixed the boot issue...I think.

One other thing you could do, I did this for a while then would turn it back when I was ready to work on it, is in rc.conf also !eth1 this way you get speedy boot. And then just start it manually.

heathen · 2007-03-21 21:29:16

installing hal made no diffrenece...

i could mac filter, but it's really even less secure than wep... i dunno...

I'm totally lost.. I wonder if part of it is that I use an old router...

junglepeanut · 2007-03-21 22:22:50

.....mine is an old discontinued because of bugs router as well.(No other computers on the network report errors though.) It may be the router.

junglepeanut · 2007-03-25 10:55:48

So I just went to another location for the last three days. Everything is set-up the same as before and... I am in your boat. Nothing works trying to do it at boot. This is a new wireless device.

This may need to be turned into a bug.

junglepeanut · 2007-04-04 01:33:31

I've noticed with mine now. It fails every time I switch routers. If it is the second (sometimes third time) connecting to the same router it works fine on boot.

Still trying to play with netcfg to have it work cleanly. i.e. if I run the commands individually it never happens but currently I am busy with school stuff not time to even look into it.

Last edited by junglepeanut (2007-04-04 01:33:53)

Arch Linux

#1 2007-03-19 01:51:38

startup and networking

#2 2007-03-19 02:01:29

Re: startup and networking

#3 2007-03-19 02:05:47

Re: startup and networking

#4 2007-03-19 02:12:56

Re: startup and networking

#5 2007-03-19 02:29:14

Re: startup and networking

#6 2007-03-19 09:35:55

Re: startup and networking

#7 2007-03-19 22:04:19

Re: startup and networking

#8 2007-03-19 22:12:54

Re: startup and networking

#9 2007-03-19 22:16:50

Re: startup and networking

#10 2007-03-19 23:21:22

Re: startup and networking

#11 2007-03-20 00:26:52

Re: startup and networking

#12 2007-03-20 01:12:47

Re: startup and networking

#13 2007-03-20 13:51:59

Re: startup and networking

#14 2007-03-20 21:04:07

Re: startup and networking

#15 2007-03-20 21:31:52

Re: startup and networking

#16 2007-03-20 21:44:46

Re: startup and networking

#17 2007-03-20 23:59:00

Re: startup and networking

#18 2007-03-21 00:25:40

Re: startup and networking

#19 2007-03-21 00:54:57

Re: startup and networking

#20 2007-03-21 11:32:32

Re: startup and networking

#21 2007-03-21 11:57:55

Re: startup and networking

#22 2007-03-21 21:29:16

Re: startup and networking

#23 2007-03-21 22:22:50

Re: startup and networking

#24 2007-03-25 10:55:48

Re: startup and networking

#25 2007-04-04 01:33:31

Re: startup and networking

Board footer