netcfg2 is now in [testing]

Driadan · 2008-02-09 12:40:56

Tigertailz wrote:

Mine doesnt really work I get Wireless association failed.
If I do
$iwconfig ath0 essid krika nick T21
$dhcpcd ath0
i get connected just fine.
Here ar my settings
-------------------------rc.conf-------------------------------------------
lo="lo 127.0.0.1"
eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.255.255"
WLAN_INTERFACEC=(ath0)
#eth1="dhcp"
INTERFACES=(lo eth0)
#NET_PROFILES=(main)
NETWORKS=(auto-wireless $interface)
-----------------------------------------------------------------------------------------------------
------------------network.d/krika--------------------------------------------
DESCRIPTION="Default Network Profile"
CONNECTION="wireless"
INTERFACE=ath0
HOSTNAME=myhost
IFOPTS="dhcp"
DHCP_TIMEOUT=15
SCAN="yes"
ESSID="krika"
SECURITY="none"
IWOPTAS="mode managed essid $ESSID"
IP="dhcp"

Im using the madwifi-ng drivers patched to support packet injection

I also use the madwifi drivers (although I think it isn't patched, it is just use the package from arch). And I don't know why but using SECURITY="None" got me to the "Wireless asociation failed", if I instead use SECURITY="open" it connects without problems.

Tigertailz · 2008-02-09 13:08:22

Tigertailz wrote:

Mine doesnt really work I get Wireless association failed.
If I do
$iwconfig ath0 essid krika nick T21
$dhcpcd ath0
i get connected just fine.
Here ar my settings
-------------------------rc.conf-------------------------------------------
lo="lo 127.0.0.1"
eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.255.255"
WLAN_INTERFACEC=(ath0)
#eth1="dhcp"
INTERFACES=(lo eth0)
#NET_PROFILES=(main)
NETWORKS=(auto-wireless $interface)
-----------------------------------------------------------------------------------------------------
------------------network.d/krika--------------------------------------------
DESCRIPTION="Default Network Profile"
CONNECTION="wireless"
INTERFACE=ath0
HOSTNAME=myhost
IFOPTS="dhcp"
DHCP_TIMEOUT=15
SCAN="yes"
ESSID="krika"
SECURITY="none"
IWOPTAS="mode managed essid $ESSID"
IP="dhcp"

Im using the madwifi-ng drivers patched to support packet injection

bump

b9anders · 2008-02-11 10:21:24

I set netcfg last week and it worked fine for my wireless network. Something seems to have gone wrong at some point in the last few days (upgrade?) because it doesn't work anymore. When I try to connect with 'netcfg2 <my network> I get:

/usr/lib/network//wireless.subr: line 113: ifconfig: command not found
/usr/lib/network//wireless.subr: line 116: iwconfig: command not found
/usr/lib/network//wireless.subr: line 49: iwlist: command not found
/usr/lib/network//wireless.subr: line 49: iwlist: command not found
/usr/lib/network//wireless.subr: line 49: iwlist: command not found
/usr/lib/network//wireless.subr: line 49: iwlist: command not found

running ifconfig gives me

bash: ifconfig: command not found

and likewise running 'iwlist scan'

bash: iwlist: command not found

what happened? How do I fix this?

Driadan · 2008-02-11 12:44:49

1 - check you path
2 - check you have the net-tools and wireless_tools packages

b9anders · 2008-02-11 14:28:46

Driadan wrote:

1 - check you path

thanks. I have been trying out qingy instead of agetty and realised this messes up the path for root. back to agetty for me.

masinick · 2008-02-12 04:21:23

Please forgive the intrusion - and possibly redirect my inquiry to another section if more appropriate.

I am running Arch Linux using a wireless interface and I am confused about the various options, some of which appear to be mutually exclusive.

I have wireless working, just not the way I want it to work.

I've been logging in as root and starting up knetworkmanager, selecting the wireless access point I want to use, and then activating it. That works, but it is not automatic. What I would really like is to have it all set up during the boot up sequence.

Therefore, I am guessing that I may have to comment out certain things and add or enable others, and possibly edit a configuration file, but not sure what is needed, what is not, and what conflicts.

Background: I have a Intel Pro Wireless network, so I use the ipw configuration for starters. That is fine, and seems to work as desired.

I have some stuff in /etc/rc.conf, but possibly too much and possibly conflicting. I put in the following settings:

more wpa
#
# Network Profile
#

DESCRIPTION="Brian Masinick Home Network"

# Network Settings
INTERFACE=eth1
HOSTNAME=masinickbox

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

# DNS Settings (optional)
DOMAIN=comcast.net
DNS1=
DNS2=

# Wireless Settings (optional)
ESSID=TheMasNET
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 AUTOWPA

I have these settings in /etc/rc.conf

lo="lo 127.0.0.1"
eth1="dhcp"
INTERFACES=(lo eth1)
wlan_eth1="eth1 essid TheMasNET key s:s:wpa-text-key-from-Belkin-router"
#
# 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.2.1"
ROUTES=(!gateway)

and lower down...

NET_PROFILES=(wpa)

I have these daemons:

DAEMONS=(syslog-ng network dhcdbd networkmanager @netfs @hal @crond @openntpd @sshd !httpd !mysqld !webmin !portmap !fam !postfix !cups)

Again, what I want by default is to set up wireless on my home account. I would like the flexibility that when I am roaming i can change, so I'd like to understand how this all comes together. I have read the Wiki but I seem to be confused on some points, so perhaps some help with this specific setup would work - and an explanation of what gets added, what gets removed, and why. Eventually I will understand it myself, but I would sure appreciate any jump start that any of you can kindly offer. Thanks!

zenlord · 2008-02-12 08:56:04

masinick wrote:

I am running Arch Linux using a wireless interface and I am confused about the various options, some of which appear to be mutually exclusive.

At the moment, there is indeed room for confusion in the wiki, but that'll be fixed after netcfg2 has been added to the core-repo. Take a look here: http://wiki.archlinux.org/index.php/Network_Profiles - it has all you need.

In short: You don't need 'network', 'dhcdbd' or 'networkmanager' in DAEMONS(), only 'net-profiles', and in INTERFACES() you can leave out everything except 'lo'. Add a 'NETWORKS()'-section with in it 'auto-wireless <devicename>' to connect automatically using the specified device and the profiles you set up in /etc/network.d/ (mine says 'NETWORKS(auto-wireless wlan0 wired)' to search for wireless networks using the wlan0-interface and the profiles I set up, including a failsafe-profile to connect to a non-secure wlan if available and to connect using the 'wired'-profile, my profile for connecting through eth0.

There are some requests to change the behaviour of netcfg2 to stop connecting to profiles after the first succeeded connection (and even to automatically scan for profiles after a device has been taken down), but I don't know it Iphitus has plans to take these on.

Some (wireless?) drivers don't bring the device automatically up, and then you need to re-add the device to INTERFACES() or alter the netcfg2-script as explained in this thread (which holds a lot of information).

Zl.

Last edited by zenlord (2008-02-12 08:58:43)

masinick · 2008-02-12 13:12:08

Zenlord, thank you so much for that explanation. I finally ended up figuring out a solution that works for an ordinary user by doing something very close to what you suggest, except using the current toolset. I deactivated the interfaces except for lo, got rid of the 'network' daemon, but kept the 'dhcdbd' and 'networkmanager' daemons.

The key part for me was to add the 'knetworkmanager' program to the sudoers file using visudo. That way, from the masinick account, when I login, I can activate (or change) wireless network cells. That is one acceptable solution for me.

I will, however, look into using the new tool for future use and see if it may be even more useful to me. Thank you very much for your explanation, I greatly appreciate it!

patroclo7 · 2008-02-12 13:46:05

I think that one could simply comment out the INTERFACES line, for two reasons: 1) if the service network is not started, that line is not used; 2) the loopback interface is activated by default by the arch initscripts (recent releases).

buddabrod · 2008-02-12 17:08:33

What about parsing the wpa keys correctly? If it contains a ` or a " or other expressions, it doesn't parse them as characters being part of the key anymore.. wpa_supplicant can do that directly by itself.

Driadan · 2008-02-12 19:56:46

have you tried with \' and \" ? I'm not sure it'll work, but you can always try it

iphitus · 2008-02-13 08:49:08

Not ignoring you, just been busy. Don't worry.

jbromley: Probably the $ in the key. I'll be making some changes to how keys are handled, so that should be fixed in the next release.

kirolima: Odd. Maybe the driver wasnt ready at boot. As for removing network, yes, you can safely and easily use net-profiles only. I do

kant1:
1 - This will replace NET_PROFILES. The existing INTERFACES=() will remain.
2 - Whatever layout you like. You can abandon interfaces and routes if you wish. Keep hostname though, netcfg scripts dont set the hostname.
3 - The directory is limited.
4 - Kirolima above had that association issue too. What driver?
5 - Best way to explore netcfg2 is to open it and read it - bash is pretty simple. netcfg-auto looks for wireless networks, and then checks if there's a profile with a matching SSID.

PPP changes: Thank you, they'll definitely be merged in the next release.

Tigertailz, Driadan: Looks like something with security=none... I'll see what I can do.

SpookyET:
NetworkManager is:
[*] buggy and unreliable.
[*] primarily aimed at making wireless "friendly" on Linux
[*] dependent on GUI front ends. When netcfg2 was started, the Google SoC project had not been started.

Further, we already had profiles, but they were fairly weak, buggy and surprisingly little known. I wanted something that would work, and be implemented fairly easily. I'll be the first to admit, netcfg2 is far from an ideal solution, it does work, it was created easily, and is far better than what we already have.

See the distro independent netconf for an ideal solution: http://netconf.alioth.debian.org/

stylopath
Menu: Yes, a menu option is already implemented, though I separated it from the main netcfg. It's poorly documented but it does work. I'll add some more documentation to the wiki for the next release.
Auto not bringing up interface: Known bug, will be fixed next release
Profile Down before new one: I'll look at a 'tidy' way of doing this. I don't want to force people into a certain configuration like NetworkManager does, but I do want to make it possible for what you want. Next release

raul_nds: Probably better in a separate thread. It really depends on what your network requires. Post as much information as you can. If you've got a working wpa_supplicant.conf, then you can use that with the wpa-config option.

masinick: You're using the existing network profiles, they suck. Grab 'netcfg' from [testing]. It's the one documented here and on the wiki page linked at the start.

buddabrod: Yeah. wpa key parsing sucks. I'll see what I can do for the next release.

jbromley · 2008-02-13 09:38:17

iphitus wrote:

jbromley: Probably the $ in the key. I'll be making some changes to how keys are handled, so that should be fixed in the next release.

I believe this is the case. When I changed my WPA key to avoid the '$', it worked great.

Regards,
j

iphitus · 2008-02-13 10:12:11

Please keep any future posts in the v2.0.6 thread unless they directly to an existing post/problem here:
http://bbs.archlinux.org/viewtopic.php?id=43863

sash · 2008-02-25 03:33:22

sash wrote:

Does anyone else have a problem using netcfg2 with the latest kernel and ndiswrapper packages?
I have to revert back to kernel26 2.6.23.8-1 and ndiswrapper 1.49-3, or else I am getting continuous "DHCP request failed" messages (or something along that line").
When I revert to older packages, things work normally--I can connect from the 1st time just fine.

OK things are working again with the ndiswrapper driver--specifying a value for WPA_CONF seems to do the trick.

Linuturk · 2008-03-09 00:22:39

I've got a chip running the madwifi driver, and netcfg2 isn't working for me.

ath0      Link encap:Ethernet  HWaddr 00:16:E3:EC:3D:18  
          inet addr:192.168.0.22  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::216:e3ff:feec:3d18/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6538 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3869 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:3331676 (3.1 Mb)  TX bytes:453130 (442.5 Kb)

eth0      Link encap:Ethernet  HWaddr 00:16:D4:97:19:F2  
          inet addr:169.254.71.49  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:18 Base address:0x4000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wifi0     Link encap:UNSPEC  HWaddr 00-16-E3-EC-3D-18-00-00-00-00-00-00-00-00-00-00  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:45730 errors:0 dropped:0 overruns:0 frame:141
          TX packets:4190 errors:4 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:199 
          RX bytes:7281134 (6.9 Mb)  TX bytes:585135 (571.4 Kb)
          Interrupt:16

iwlist works fine, and I can manually connect fine.

netcfg2 worked fine before I migrated to this new machine. My wifi device was eth1 and is now ath0. I think that wifi0 is a firewire port, for some strange reason, and I'd like to knock it out. Let me know what else you need.

iphitus · 2008-03-09 10:06:37

Linuturk wrote:

I've got a chip running the madwifi driver, and netcfg2 isn't working for me.
<snip>
netcfg2 worked fine before I migrated to this new machine. My wifi device was eth1 and is now ath0. I think that wifi0 is a firewire port, for some strange reason, and I'd like to knock it out. Let me know what else you need.

Some information. "doesnt work" tells me nothing whatsoever.

http://wiki.archlinux.org/index.php/Net … nt_work.3F

iphitus wrote:

Please keep any future posts in the v2.0.6 thread unless they directly to an existing post/problem here:
http://bbs.archlinux.org/viewtopic.php?id=43863

pestilence · 2008-03-17 12:27:42

I have a laptop with 3 network interfaces (eth0, eth2 wired and eth1 wireless). Allthough wired connections work ok, the wireless configuration fails:

[pestilence@pestilence-laptop network.d]$ sudo netcfg2 eth2
:: eth2 up                                                                                                    [DONE] 
[pestilence@pestilence-laptop network.d]$
[pestilence@pestilence-laptop network.d]$ sudo netcfg2 eth1-work
:: eth1-work up                                                                                               [BUSY] iwconfig: unknown command "<censored>"
                 - Could not set wireless configuration                                                       [FAIL]

<censored> in the output refers to my WEP configured key:

[pestilence@pestilence-laptop network.d]$ cat eth1-work 
CONNECTION="wireless"
DESCRIPTION="Work wireless"
INTERFACE=eth1
SCAN="no"
SECURITY="wep"
ESSID="IPdept"
KEY="<censored>"
IP="dhcp"

Last edited by pestilence (2008-03-17 12:28:31)

steve-e · 2008-03-17 13:21:41

Do you have unescaped chars in your KEY like !, & or $? Try to prefix them with \.

pestilence · 2008-03-17 13:33:46

steve-e wrote:

Do you have unescaped chars in your KEY like !, & or $? Try to prefix them with \.

Nope, and i think I found what is happening

iwconfig eth1 set essid "myessid" key open "<censored>"

does not work...it needs:

iwconfig eth1 set essid "myessid" key open "s:<censored>"

So I believe I would have to modify the /usr/lib/network/wireless.subr

Line 205:

WEP_OPTS="mode managed essid \"$ESSID\" key open $KEY"

Last edited by pestilence (2008-03-17 13:47:27)

pestilence · 2008-03-17 13:57:06

Changing line 205 of wireless.subr to:

WEP_OPTS="mode managed essid \"$ESSID\" key open \"s:$KEY\""

Did the trick for me (I now use a passphrase as my wep key) hex key still wouldn't work (tryed it manually).
Wireless module: ipw2200

Stalafin · 2008-03-21 19:46:49

I am kinda confused about how netcfg actually works now.

It is not in testing anymore, and I have the options netcfg and netcfg2 now, yet one is dependent on network.d and the other on network-profiles. At the same time there is only one netcfg installed (2.0.6-1)...

Why is that so?

rson451 · 2008-03-21 21:25:34

netcfg (not v2) is part of the initscripts package. check out the output of "pacman -Qo $(which netcfg)".

sfabius · 2008-03-22 00:28:32

Uh, but a pacman -Syu gives me a message that netcfg is NOT any longer part of initscripts!

So I installed netcfg. Upon searching the forums I see there is this netcfg2 (I didn't know about it -- my previous setup served me just fine thank you). But there is only one netcfg in pacman. So I'm a bit confused. My main question is this: Will my current setup work, or do I have to spend an hour rewriting or renaming all of my profiles?

I currently start up my laptop with the NETWORK=(menu) in /etc/rc.conf. Profiles are currently located in /etc/network-profiles. After installing netcfg from core, I now also have a directory /etc/network.d with only "examples" in it.

abhidg · 2008-03-22 17:22:14

if you see the version of netcfg is 2.0.6, so it is actually netcfg2.
NET_PROFILES will become NETWORKS=(...)
You can also check the page in the wiki for more details.

Arch Linux

#126 2008-02-09 12:40:56

Re: netcfg2 is now in [testing]

#127 2008-02-09 13:08:22

Re: netcfg2 is now in [testing]

#128 2008-02-11 10:21:24

Re: netcfg2 is now in [testing]

#129 2008-02-11 12:44:49

Re: netcfg2 is now in [testing]

#130 2008-02-11 14:28:46

Re: netcfg2 is now in [testing]

#131 2008-02-12 04:21:23

Re: netcfg2 is now in [testing]

#132 2008-02-12 08:56:04

Re: netcfg2 is now in [testing]

#133 2008-02-12 13:12:08

Re: netcfg2 is now in [testing]

#134 2008-02-12 13:46:05

Re: netcfg2 is now in [testing]

#135 2008-02-12 17:08:33

Re: netcfg2 is now in [testing]

#136 2008-02-12 19:56:46

Re: netcfg2 is now in [testing]

#137 2008-02-13 08:49:08

Re: netcfg2 is now in [testing]

#138 2008-02-13 09:38:17

Re: netcfg2 is now in [testing]

#139 2008-02-13 10:12:11

Re: netcfg2 is now in [testing]

#140 2008-02-25 03:33:22

Re: netcfg2 is now in [testing]

#141 2008-03-09 00:22:39

Re: netcfg2 is now in [testing]

#142 2008-03-09 10:06:37

Re: netcfg2 is now in [testing]

#143 2008-03-17 12:27:42

Re: netcfg2 is now in [testing]

#144 2008-03-17 13:21:41

Re: netcfg2 is now in [testing]

#145 2008-03-17 13:33:46

Re: netcfg2 is now in [testing]

#146 2008-03-17 13:57:06

Re: netcfg2 is now in [testing]

#147 2008-03-21 19:46:49

Re: netcfg2 is now in [testing]

#148 2008-03-21 21:25:34

Re: netcfg2 is now in [testing]

#149 2008-03-22 00:28:32

Re: netcfg2 is now in [testing]

#150 2008-03-22 17:22:14

Re: netcfg2 is now in [testing]

Board footer