You are not logged in.

Pages: 1 2 3 4 5 6

#101 2006-04-05 06:02:02

tor
Member
From: Sweden
Registered: 2004-08-02
Posts: 80

Re: NetworkManager

nightfrost wrote:

Thanks for the tip. Here's part of the output before NM gives up:

NetworkManager: <information>   Activation (eth1/wireless): association took too long (>20s), failing activation.
NetworkManager: <information>   Activation (eth1) failure scheduled...
NetworkManager: <information>   Activation (eth1) failed for access point (voodoo)
NetworkManager: <information>   Activation (eth1) failed.
NetworkManager: <information>   Deactivating device eth1.
sendmsg(CTRL_IFACE monitor): No such file or directory
NetworkManager: <WARNING>        nm_signal_handler (): Caught signal 2, shutting down normally.
NetworkManager: <information>   Caught terminiation signal
NetworkManager: <debug info>    [1144089661.715488] nm_print_open_socks (): Open Sockets List:
NetworkManager: <debug info>    [1144089661.715549] nm_print_open_socks (): Open Sockets List Done.
NetworkManager: <information>   Deactivating device eth0.
NetworkManager: <information>   Deactivating device eth1.

It seams like NM times out after trying ~20s. How do your relevant parts of /etc/rc.conf look like?   

I don't understand the whole wpa-business. It's just a wep encryption so why is wpa_supplicant evoked?

I think wpa_supplicant is also capable of scan and key configuration of wep networks and because of that is the way NM interacts with wireless cards all together.

Offline

#102 2006-04-05 10:58:57

nightfrost
Member
From: Sweden
Registered: 2005-04-16
Posts: 647

Re: NetworkManager

This is how rc.conf looks like. I've commented out everything that could be in NMs way. And the network-profiles are all disabled (with !). 

# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="dionysos"

#
# 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
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
lo="lo 127.0.0.1"
#eth0=""
INTERFACES=(lo)
#eth1="dhcp"

#
# 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
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network-profiles
#
NET_PROFILES=(!bobo-wifi !home-wifi !home-fixed !jimbo-fixed)

I think wpa_supplicant is also capable of scan and key configuration of wep networks and because of that is the way NM interacts with wireless cards all together.

Ah, alright. Thanks smile

Offline

#103 2006-04-05 11:13:10

tor
Member
From: Sweden
Registered: 2004-08-02
Posts: 80

Re: NetworkManager

You should keep the network lines, eth0 and eth1, with dhcp. Ie:

eth0="dhcp"
eth1="dhcp"

Because otherwise im not sure how NM would interpret them. We parse the rc.conf file to look if we should use a static ip or not.

I dont think this will fix your problem but please try.

Other than that, how long does it take for you to bring up your wireless network without NM? Just wondering since it seems like you are experiencing a timeout when using NM.

Offline

#104 2006-04-05 11:29:29

nightfrost
Member
From: Sweden
Registered: 2005-04-16
Posts: 647

Re: NetworkManager

I uncommented the lines proposed, but the problem is still there.

Bringing up my network without NM is a pretty fast business: 

time sudo /etc/rc.d/network start
:: Starting network profile: home-wifi                                                                                                                [DONE]
:: Starting Network                                                                                                                                   [DONE]

real    0m4.633s
user    0m0.121s
sys     0m0.054s

I've no clue of what else I can do to get at the problem...

Offline

#105 2006-04-05 14:47:15

jfryman
Member
From: Newport News, VA
Registered: 2006-03-17
Posts: 29

Re: NetworkManager

It looks like it's an association problem with wpa_supplicant... can you paste more debug here?

What version of wpa_supplicant are you running now?

James Fryman

Offline

#106 2006-04-05 19:05:54

nightfrost
Member
From: Sweden
Registered: 2005-04-16
Posts: 647

Re: NetworkManager

Unfortunately, I'm not at home any longer and I will be drifting around for a couple of weeks... so I can't post more of the debug. (I can't find a log file either, otherwise I could post that)

the wpa_supplicant version, however, is 0.5.2. I haven't changed anything in /etc/wpa_supplicant.conf. Should I?

Offline

#107 2006-04-05 19:13:11

jfryman
Member
From: Newport News, VA
Registered: 2006-03-17
Posts: 29

Re: NetworkManager

Nope... NM passes the necessary arguments via a socket to wpa_supplicant... the config for /etc/wpa_supplicant.conf should not be needed.

Maybe you could blank it out... just to be sure. I know there are some interesting code examples in the default that may cause problems.

James Fryman

Offline

#108 2006-04-08 16:44:28

Blaasvis
Member
Registered: 2003-01-17
Posts: 467

Re: NetworkManager

well, just tried 0.6.2.

i got 2 network cards, it works somewhat.

madwifi doesn't do anything when the driver is unpatch, i will talk to iphitus about this. after patch it only does wpa, wep still hits its timeout while associating. 
[edit] well wep works now too, forgotten an patch[/edit]

the next one was the atmel wifi card, it only does wep. which isn't strange due to the fact the atmel driver doesn't support wireless extensions 19 wink

Freedom is what i love

Offline

#109 2006-04-19 20:32:24

nightfrost
Member
From: Sweden
Registered: 2005-04-16
Posts: 647

Re: NetworkManager

jfryman wrote:

It looks like it's an association problem with wpa_supplicant... can you paste more debug here?

What version of wpa_supplicant are you running now?

I've updated to the latest CVS, but I'm still having the same problem. This is everything NM spits out when I run it from the command line:

NetworkManager: <information>   starting...
NetworkManager: <information>   eth0: Device is fully-supported using driver '8139too'.
NetworkManager: <information>   nm_device_init(): waiting for device's worker thread to start
NetworkManager: <information>   nm_device_init(): device's worker thread started, continuing.
NetworkManager: <information>   Now managing wired Ethernet (802.3) device 'eth0'.
NetworkManager: <information>   Deactivating device eth0.
NetworkManager: <information>   eth1: Device is fully-supported using driver 'ipw2200'.
NetworkManager: <information>   nm_device_init(): waiting for device's worker thread to start
NetworkManager: <information>   nm_device_init(): device's worker thread started, continuing.
NetworkManager: <information>   Now managing wireless (802.11) device 'eth1'.
NetworkManager: <information>   Deactivating device eth1.
NetworkManager: <information>   Updating allowed wireless network lists.
NetworkManager: <debug>    [1145478343.253242] nm_device_802_11_wireless_get_activation_ap (): Forcing AP 'voodoo'
NetworkManager: <information>   User Switch: /org/freedesktop/NetworkManager/Devices/eth1 / voodoo
NetworkManager: <information>   Deactivating device eth1.
NetworkManager: <information>   Device eth1 activation scheduled...
NetworkManager: <information>   Activation (eth1) started...
NetworkManager: <information>   Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager: <information>   Activation (eth1) Stage 1 of 5 (Device Prepare) started...
NetworkManager: <information>   Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager: <information>   Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
NetworkManager: <information>   Activation (eth1) Stage 2 of 5 (Device Configure) starting...
NetworkManager: <information>   Activation (eth1/wireless): access point 'voodoo' is encrypted, but NO valid key exists.  New key needed.
NetworkManager: <information>   Activation (eth1) New wireless user key requested for network 'voodoo'.
NetworkManager: <information>   Activation (eth1) Stage 2 of 5 (Device Configure) complete.
NetworkManager: <information>   Activation (eth1) New wireless user key for network 'voodoo' received.
NetworkManager: <information>   Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager: <information>   Activation (eth1) Stage 1 of 5 (Device Prepare) started...
NetworkManager: <information>   Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager: <information>   Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
NetworkManager: <information>   Activation (eth1) Stage 2 of 5 (Device Configure) starting...
NetworkManager: <information>   Activation (eth1/wireless): access point 'voodoo' is encrypted, and a key exists.  No new key needed.
NetworkManager: <information>   SUP: sending command 'INTERFACE_ADD eth1                wext    /opt/gnome/var/run/wpa_supplicant       '
NetworkManager: <information>   SUP: response was 'OK'
NetworkManager: <information>   SUP: sending command 'AP_SCAN 1'
NetworkManager: <information>   SUP: response was 'OK'
NetworkManager: <information>   SUP: sending command 'ADD_NETWORK'
NetworkManager: <information>   SUP: response was '0'
NetworkManager: <information>   SUP: sending command 'SET_NETWORK 0 ssid 766f6f646f6f'
NetworkManager: <information>   SUP: response was 'OK'
NetworkManager: <information>   SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
NetworkManager: <information>   SUP: response was 'OK'
NetworkManager: <information>   SUP: sending command 'SET_NETWORK 0 wep_key0 <key>'
NetworkManager: <information>   SUP: response was 'OK'
NetworkManager: <information>   SUP: sending command 'SET_NETWORK 0 wep_tx_keyidx 0'
NetworkManager: <information>   SUP: response was 'OK'
NetworkManager: <information>   SUP: sending command 'ENABLE_NETWORK 0'
NetworkManager: <information>   SUP: response was 'OK'
NetworkManager: <information>   Activation (eth1) Stage 2 of 5 (Device Configure) complete.
NetworkManager: <information>   Activation (eth1/wireless): association took too long (>20s), failing activation.
NetworkManager: <information>   Activation (eth1) failure scheduled...
NetworkManager: <information>   Activation (eth1) failed for access point (voodoo)
NetworkManager: <information>   Activation (eth1) failed.
NetworkManager: <information>   Deactivating device eth1.
NetworkManager: <information>   wpa_supplicant(2303): Global control interface '/opt/gnome/var/run/wpa_supplicant-global'
NetworkManager: <information>   wpa_supplicant(2303): RX global ctrl_iface - hexdump_ascii(len=59):
NetworkManager: <information>   wpa_supplicant(2303):      49 4e 54 45 52 46 41 43 45 5f 41 44 44 20 65 74   INTERFACE_ADD et
NetworkManager: <information>   wpa_supplicant(2303):      68 31 09 09 77 65 78 74 09 2f 6f 70 74 2f 67 6e   h1__wext_/opt/gn
NetworkManager: <information>   wpa_supplicant(2303):      6f 6d 65 2f 76 61 72 2f 72 75 6e 2f 77 70 61 5f   ome/var/run/wpa_
NetworkManager: <information>   wpa_supplicant(2303):      73 75 70 70 6c 69 63 61 6e 74 09                  supplicant_
NetworkManager: <information>   wpa_supplicant(2303): CTRL_IFACE GLOBAL INTERFACE_ADD 'eth1             wext    /opt/gnome/var/run/wpa_supplicant       '
NetworkManager: <information>   wpa_supplicant(2303): Initializing interface 'eth1' conf 'N/A' driver 'wext' ctrl_interface '/opt/gnome/var/run/wpa_supplicant' bridge 'N/A'
NetworkManager: <information>   wpa_supplicant(2303): Initializing interface (2) 'eth1'
NetworkManager: <information>   wpa_supplicant(2303): EAPOL: SUPP_PAE entering state DISCONNECTED
NetworkManager: <information>   wpa_supplicant(2303): EAPOL: KEY_RX entering state NO_KEY_RECEIVE
NetworkManager: <information>   wpa_supplicant(2303): EAPOL: SUPP_BE entering state INITIALIZE
NetworkManager: <information>   wpa_supplicant(2303): EAP: EAP entering state DISABLED
NetworkManager: <information>   wpa_supplicant(2303): EAPOL: External notification - portEnabled=0
NetworkManager: <information>   wpa_supplicant(2303): EAPOL: External notification - portValid=0
NetworkManager: <information>   wpa_supplicant(2303): SIOCGIWRANGE: WE(compiled)=19 WE(source)=18 enc_capa=0xf
NetworkManager: <information>   wpa_supplicant(2303):   capabilities: key_mgmt 0xf enc 0xf
NetworkManager: <information>   wpa_supplicant(2303): Own MAC address: 00:12:f0:0f:5b:15
NetworkManager: <information>   wpa_supplicant(2303): r_wext_set_wpa
NetworkManager: <information>   wpa_supplicant(2303): wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
NetworkManager: <information>   wpa_supplicant(2303): wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
NetworkManager: <information>   wpa_supplicant(2303): wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
NetworkManager: <information>   wpa_supplicant(2303): wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
NetworkManager: <information>   wpa_supplicant(2303): wpa_driver_wext_set_countermeasures
NetworkManager: <information>   wpa_supplicant(2303): wpa_driver_wext_set_drop_unencrypted
NetworkManager: <information>   wpa_supplicant(2303): Setting scan request: 0 sec 100000 usec
NetworkManager: <information>   wpa_supplicant(2303): Added interface eth1
NetworkManager: <information>   wpa_supplicant(2303): Wireless event: cmd=0x8b06 len=8
NetworkManager: <information>   wpa_supplicant(2303): RX ctrl_iface - hexdump_ascii(len=9):
NetworkManager: <information>   wpa_supplicant(2303):      41 50 5f 53 43 41 4e 20 31                        AP_SCAN 1
NetworkManager: <information>   wpa_supplicant(2303): RX ctrl_iface - hexdump_ascii(len=11):
NetworkManager: <information>   wpa_supplicant(2303):      41 44 44 5f 4e 45 54 57 4f 52 4b                  ADD_NETWORK
NetworkManager: <information>   wpa_supplicant(2303): CTRL_IFACE: ADD_NETWORK
NetworkManager: <information>   wpa_supplicant(2303): RX ctrl_iface - hexdump_ascii(len=31): [REMOVED]
NetworkManager: <information>   wpa_supplicant(2303): CTRL_IFACE: SET_NETWORK id=0 name='ssid'
NetworkManager: <information>   wpa_supplicant(2303): CTRL_IFACE: value - hexdump_ascii(len=12): [REMOVED]
NetworkManager: <information>   wpa_supplicant(2303): ssid - hexdump_ascii(len=6):
NetworkManager: <information>   wpa_supplicant(2303):      76 6f 6f 64 6f 6f                                 voodoo
NetworkManager: <information>   wpa_supplicant(2303): RX ctrl_iface - hexdump_ascii(len=27): [REMOVED]
NetworkManager: <information>   wpa_supplicant(2303):  id=0 name='key_mgmt'
NetworkManager: <information>   wpa_supplicant(2303): CTRL_IFACE: value - hexdump_ascii(len=4): [REMOVED]
NetworkManager: <information>   wpa_supplicant(2303): key_mgmt: 0x4
NetworkManager: <information>   wpa_supplicant(2303): RX ctrl_iface - hexdump_ascii(len=49): [REMOVED]
NetworkManager: <information>   wpa_supplicant(2303): CTRL_IFACE: SET_NETWORK id=0 name='wep_key0'
NetworkManager: <information>   wpa_supplicant(2303): CTRL_IFACE: value - hexdump_ascii(len=26): [REMOVED]
NetworkManager: <information>   wpa_supplicant(2303): wep_key0 - hexdump(len=13): [REMOVED]
NetworkManager: <information>   wpa_supplicant(2303): RX ctrl_iface - hexdump_ascii(len=29): [REMOVED]
NetworkManager: <information>   wpa_supplicant(2303): CTRL_IFACE: SET_NETWORK id=0 name='wep_tx_keyidx'
NetworkManager: <information>   wpa_supplicant(2303): CTRL_IFACE: value - hexdump_ascii(len=1): [REMOVED]
NetworkManager: <information>   wpa_supplicant(2303): wep_tx_keyidx=0 (0x0)
NetworkManager: <information>   wpa_supplicant(2303): RX ctrl_iface - hexdump_ascii(len=16):
NetworkManager: <information>   wpa_supplicant(2303):      45 4e 41 42 4c 45 5f 4e 45 54 57 4f 52 4b 20 30   ENABLE_NETWORK 0
NetworkManager: <information>   wpa_supplicant(2303): CTRL_IFACE: ENABLE_NETWORK id=0
NetworkManager: <information>   wpa_supplicant(2303): Setting scan request: 0 sec 0 usec
NetworkManager: <information>   wpa_supplicant(2303): State: DISCONNECTED -> SCANNING
NetworkManager: <information>   wpa_supplicant(2303): Starting AP scan (broadcast SSID)
NetworkManager: <information>   wpa_supplicant(2303): Trying to get current scan results first without requesting a new scan to speed up initial association
NetworkManager: <information>   wpa_supplicant(2303): Received 0 bytes of scan results (0 BSSes)
NetworkManager: <information>   wpa_supplicant(2303): Scan results: 0
NetworkManager: <information>   wpa_supplicant(2303): Selecting BSS from priority group 0
NetworkManager: <information>   wpa_supplicant(2303): No suitable AP found.
NetworkManager: <information>   wpa_supplicant(2303): Setting scan request: 0 sec 0 usec
NetworkManager: <information>   wpa_supplicant(2303): f 76 61 72 2f 72 75 6e 2f 4e 65 74 77 6f 72 6b 4d 61 6e 61 67 65 72 2f 77 70 61 5f 63 74 72 6c 5f 32 32 38 30 2d 31 00
NetworkManager: <information>   wpa_supplicant(2303): Starting AP scan (broadcast SSID)
NetworkManager: <information>   wpa_supplicant(2303): Scan timeout - try to get results
NetworkManager: <information>   wpa_supplicant(2303): Received 0 bytes of scan results (0 BSSes)
NetworkManager: <information>   wpa_supplicant(2303): Scan results: 0
NetworkManager: <information>   wpa_supplicant(2303): Selecting BSS from priority group 0
NetworkManager: <information>   wpa_supplicant(2303): No suitable AP found.
NetworkManager: <information>   wpa_supplicant(2303): Setting scan request: 5 sec 0 usec
NetworkManager: <information>   wpa_supplicant(2303): Starting AP scan (broadcast SSID)
NetworkManager: <information>   wpa_supplicant(2303): Scan timeout - try to get results
NetworkManager: <information>   wpa_supplicant(2303): Received 0 bytes of scan results (0 BSSes)
NetworkManager: <information>   wpa_supplicant(2303): Scan results: 0
NetworkManager: <information>   wpa_supplicant(2303): Selecting BSS from priority group 0
NetworkManager: <information>   wpa_supplicant(2303): No suitable AP found.
NetworkManager: <information>   wpa_supplicant(2303): Setting scan request: 5 sec 0 usec
NetworkManager: <information>   wpa_supplicant(2303): Starting AP scan (broadcast SSID)
NetworkManager: <information>   wpa_supplicant(2303): Scan timeout - try to get results
NetworkManager: <information>   wpa_supplicant(2303): Received 0 bytes of scan results (0 BSSes)
NetworkManager: <information>   wpa_supplicant(2303): Scan results: 0
NetworkManager: <information>   wpa_supplicant(2303): Selecting BSS from priority group 0
NetworkManager: <information>   wpa_supplicant(2303): No suitable AP found.
NetworkManager: <information>   wpa_supplicant(2303): Setting scan request: 5 sec 0 usec
NetworkManager: <information>   wpa_supplicant(2303): CTRL-EVENT-TERMINATING - signal 15 received
NetworkManager: <information>   wpa_supplicant(2303): CTRL_IFACE monitor send - hexdump(len=50): 2f 6f 70 74 2f 67 6e 6f 6d 65 2f 76 61 72 2f 72 75 6e 2f 4e 65 74 77 6f 72 6b 4d 61 6e 61 67 65 72 2f 77 70 61 5f 63 74 72 6c 5f 32 32 38 30 2d 31 00

Before the latest update, however, it spat out alot more. Any ideas?

Offline

#110 2006-04-20 00:01:30

nightfrost
Member
From: Sweden
Registered: 2005-04-16
Posts: 647

Re: NetworkManager

by the way tor, are you planning to split gnome-network-manager into a desktop independent core-part and a gnome-applet? This way, we could add knetworkmanager in AUR, for KDE integration...

Offline

#111 2006-04-20 17:16:40

tor
Member
From: Sweden
Registered: 2004-08-02
Posts: 80

Re: NetworkManager

nightfrost: thats a good idea to split up the package. Im not sure if im the one who will do it though. I know that blaasvis had plans to incorporate it into unstable. And if thats the case i think its up to him.

About your problems with NM i have to say that im not much help there. By looking at your log i must say that i think it almost gets it but then gets interrupted by a timeout. Then why it takes that long is a mystery for me.

ovihc_again: How do you use/try to use NM. I assume that you at least have a name on your network? Does it show up in the list, in nm-applet,  or do you "connect to other network"? NM should work on a none encrypted network as well.

Offline

#112 2006-05-07 22:36:42

_Gandalf_
Member
Registered: 2006-01-12
Posts: 735

Re: NetworkManager

The latest cvs needs a patch to get built... here's a patch
http://arch.pastebin.com/704373

Sorry for posting at pastebin but the forum is somehow parsing what's in the code tag, damn phpBB

[My Blog] | [My Repo] | [My AUR Packages]

Offline

#113 2006-05-08 07:28:47

nightfrost
Member
From: Sweden
Registered: 2005-04-16
Posts: 647

Re: NetworkManager

thanks for this. I've been wondering why it fails.

By the way, I'm using networkmanager with wpa nowadays, and it works like a charm...

Offline

#114 2006-06-08 23:39:54

meanimal
Member
Registered: 2006-01-06
Posts: 9

Re: NetworkManager

In case this is useful to anyone, here are some (rather unintuitive) steps I had to follow in order to get my WEP network working.

- Make sure that the dbus, hal, avahi-*, and dhcpbd services are started (you can launch them from /etc/rc.d)

- Install wpa_supplicant > 0.5.3. I had wpa_supplicant 0.5.2 from AUR (doesn't seem to exist anymore), which was having problems setting up the WEP key. installing wpa_supplicant-svn fixed the problem.

Offline

#115 2006-06-14 00:03:35

jordz
Member
Registered: 2006-02-01
Posts: 248

Re: NetworkManager

I tried NetworkManager for the 1st time on Arch, works good smile (ipw2200)
But I got a problem with my router, the dhcp gives the dns of my router's dns server itself, but that one doesn't work with Linux (its a linux router strange thing ..) but normally i put the ip adres in /etc/resolv.conf and chattr it. And i change when i go to school with my laptop. Is there a way to let the networkmanager know that i wanna use a different dns then the dhcp only at home, with a specials essid?

thx! smile

Offline

#116 2006-06-15 19:53:46

tor
Member
From: Sweden
Registered: 2004-08-02
Posts: 80

Re: NetworkManager

I have now updated the AUR version of NetworkManager.

This time there are some big changes. We have splitted up the NetworkManager package. The networkmanager package now only contains the daemon part.

To be of any use you also have to install either gnome-network-manager or knetworkmanager-svn to be able to use this.

Further more NetworkManager seems not to start dhcdbd any more so you have to add this to DAEMONS in your /etc/rc.conf

Offline

#117 2006-06-19 19:29:54

joshuaheretic
Member
Registered: 2006-03-17
Posts: 7

Re: NetworkManager

I've gotten the newest version of networkmanager and gnome-network-manager to work perfectly. I was wondering if VPN support is something that needs to be enabled through ./configure, or something that needs to be compiled in separately, or if it just doesn't work under Arch at the moment? I haven't been able to find anything specific on the NM mailing-list. Likewise for dial-up, although I understand that that just hasn't been implemented for Arch yet. I might look into tinkering with the dial-up stuff, but I can't even find where the VPN plugins are.

Offline

#118 2006-06-19 19:40:35

tor
Member
From: Sweden
Registered: 2004-08-02
Posts: 80

Re: NetworkManager

Regarding VPN. These aren't shipped with the regular NM releases. They however are in the NM CVS. I have not gotten around to package them. Mostly due to me not having any VPN to try them on. I however think that they should be possible to package separately and i think that perhaps WillySilly took a look at it.

Regarding dial up this is not yet ported in the Arch NM adaption. Same story there. I have no, easy,way of testing it.

Offline

#119 2006-06-25 13:14:17

Ryujin
Forum Fellow
From: Centerville, Utah
Registered: 2005-05-12
Posts: 246
Website

Re: NetworkManager

Great job with network manager, it sure makes life easier!  I just have one question, how do you get it to work as a regular user and not just as root?

http://red45.wordpress.com
http://saltstack.org
https://github.com/thatch45

Offline

#120 2006-06-25 14:47:06

Ryujin
Forum Fellow
From: Centerville, Utah
Registered: 2005-05-12
Posts: 246
Website

Re: NetworkManager

OK, scratch that quetion, I updated my sytem pacman -Syu with the big tesing move and network manager stopped working, can anyone tell me what gives?

http://red45.wordpress.com
http://saltstack.org
https://github.com/thatch45

Offline

#121 2006-06-27 22:15:37

Ryujin
Forum Fellow
From: Centerville, Utah
Registered: 2005-05-12
Posts: 246
Website

Re: NetworkManager

I fixed it, although I am not enterly sure what did it.

http://red45.wordpress.com
http://saltstack.org
https://github.com/thatch45

Offline

#122 2006-06-30 13:09:43

jordz
Member
Registered: 2006-02-01
Posts: 248

Re: NetworkManager

I also can't connect with networkmanager.
When i try to restart it i get this error:

:: Starting NetworkManager                                               [BUSY]
/opt/gnome/sbin/NetworkManager: error while loading shared libraries:
libiw.so.28: cannot open shared object file: No such file or directory                                                                         [FAIL]

Somebody fixed it yet ?

Offline

#123 2006-06-30 13:25:44

Blaasvis
Member
Registered: 2003-01-17
Posts: 467

Re: NetworkManager

pacman -Suy  or pacman -S wireless_tools

it is a dep of it... do not know where it went wrong.

Freedom is what i love

Offline

#124 2006-06-30 13:34:00

jordz
Member
Registered: 2006-02-01
Posts: 248

Re: NetworkManager

It's not the problem that i can't use my wireless. But the gnome-applet sees the wireless networks but i can't connect anymore. I tries to connect for a few seconds and then stops. But manually i can connect. I just upgraded to the newest version on AUR.

Offline

#125 2006-06-30 14:02:18

iphitus
Forum Fellow
From: Melbourne, Australia
Registered: 2004-10-09
Posts: 4,927

Re: NetworkManager

jordz wrote:

I also can't connect with networkmanager.
When i try to restart it i get this error:

:: Starting NetworkManager                                               [BUSY]
/opt/gnome/sbin/NetworkManager: error while loading shared libraries:
libiw.so.28: cannot open shared object file: No such file or directory                                                                         [FAIL]

Somebody fixed it yet ?

rebuild it, wireless tools was updated to 0.29

Offline

Pages: 1 2 3 4 5 6

Board footer

Powered by FluxBB