You are not logged in.

#1 2008-05-30 01:02:40

JeremyTheWicked
Member
From: Poland
Registered: 2008-05-23
Posts: 193

Weird netcfg2 behavior

Hi guys.

I've been trying out the netcfg package. I cannot get my wireless to work on boot. (using NETWORKS=menu in rc.conf). The wired connection works.

I've configured the profiles alright. I was trying a lot of different things to find out where the problem comes from. To my surprise, it seems that I can connect to my wireless access point only at the second try:
the first netcfg2 name_of_profile always fails (unless I type "ifconfig wlan0 up" manually before - if I don't do it the wireless goes up after the second try).

It's a little bit frustrating that I cannot get networking on boot up. I would be very grateful for your ideas.


arch(3) adj amused because you think you understand something better than other people ;P

Offline

#2 2008-05-30 01:31:34

sa
Member
From: boston ma
Registered: 2008-05-23
Posts: 127
Website

Re: Weird netcfg2 behavior

You have to set it in rc.conf. There's a part that says NETWORKS=(), make sure the right config name is in that slot. If the wireless config is not starting up manually, then there must be something wrong with it...can you post the contents of your wireless profile?

Offline

#3 2008-05-30 11:13:48

JeremyTheWicked
Member
From: Poland
Registered: 2008-05-23
Posts: 193

Re: Weird netcfg2 behavior

Hi.

Thanks for your answer. These are my 2 profiles.

CONNECTION="wireless"
DESCRIPTION="Siec domowa Lublin"
INTERFACE=wlan0
SCAN="yes"
SECURITY="wep"
ESSID="<censored>"
KEY=<censored>
IP="dhcp"
RETRIES=2

and:

CONNECTION="ethernet"
DESCRIPTION="A very basic ethernet profile, using dhcp"
INTERFACE=eth0
IP="dhcp"
DHCP_TIMEOUT=10

In rc.conf it says:

NETWORKS=menu

Actually it doesn't anymore: I commented it out and I'm starting the wireless manually - got tired of that "FAILED" message.

Any ideas will be appreciated.

Last edited by JeremyTheWicked (2008-05-31 00:10:19)


arch(3) adj amused because you think you understand something better than other people ;P

Offline

#4 2008-05-30 15:12:49

zenlord
Member
From: Belgium
Registered: 2006-05-24
Posts: 1,223
Website

Re: Weird netcfg2 behavior

Please remove your ESSID / key - someone might take advantage of it...

Put in your rc.conf:
NETWORKS=(<ethernetProfileName> <wirelessProfileName>)

Zl.

Offline

#5 2008-05-30 15:38:52

Feynman
Member
From: Atlanta, GA, USA
Registered: 2008-05-06
Posts: 24

Re: Weird netcfg2 behavior

I have a similar problem, but only on one wireless network.  It is configured correctly, is listed in my Networks in rc.conf, and won't start at boot.  I know it's configured (at least somewhat) correctly because I can use netcfg2 -c (profile name) and it will, without fail, connect only on the second attempt.  I've tried increasing the timeout value, but it didn't help.

Edit: typo

Last edited by Feynman (2008-05-30 15:39:53)

Offline

#6 2008-05-31 00:16:58

JeremyTheWicked
Member
From: Poland
Registered: 2008-05-23
Posts: 193

Re: Weird netcfg2 behavior

zenlord wrote:

Please remove your ESSID / key - someone might take advantage of it...

Put in your rc.conf:
NETWORKS=(<ethernetProfileName> <wirelessProfileName>)

Zl.

I've tried that already. It still fails. (I removed ESSID and key although it's just my home wireless network and I doubt anybody here lives within 100 yards from my place wink )


arch(3) adj amused because you think you understand something better than other people ;P

Offline

#7 2008-06-04 17:31:11

JeremyTheWicked
Member
From: Poland
Registered: 2008-05-23
Posts: 193

Re: Weird netcfg2 behavior

Bump.

I solved the problem by running

netcfg2 essid || netcfg2 essid

in /etc/rc.local

It works but it's far from elegant. How does the netcfg tool work? Is it possible to assign a custom command to a netcfg-menu entry (like the one above)?


arch(3) adj amused because you think you understand something better than other people ;P

Offline

#8 2008-06-05 03:23:26

k_f
Member
Registered: 2008-06-05
Posts: 6

Re: Weird netcfg2 behavior

I have the same problem, plus everytime after resume from suspend to RAM, netcfg2 can not connect to my wireless access point, the message says DHCP assignment failed, I have to reboot to get wireless work again.

Offline

Board footer

Powered by FluxBB