NM problems on fedora core 3
- From: Ivan Blagdan <ivan elipsa-it hr>
- To: networkmanager-list gnome org
- Subject: NM problems on fedora core 3
- Date: Tue, 29 Mar 2005 19:12:39 +0200
Greetings to the list!
First of all i want to say that NM is really a great piece of software,
that IMHO, does the right thing in getting linux closer to the average
user. I searched for a decent way of managing connections to the ever
growing number of APs that i might user with my laptop, and of all the
numerous apps Linux has to offer, NM looks to be the right way for me, a
proper example how things should be designed to work on a OS that aims
to be userfriendly.
Having said that, having it work in most situations would be a welcomed
thing :) Here is my problem:
Currently i use neat to connect to my home AP trough a configured eth1
interface, using wep... no problems connecting.
Using NetworkManager to get a connection doesn't work, connection dosn't
go past the 'connectiong to wireless network' part. Having looked trough
logs it looks like NM is not getting a DHCP response. Ill put up some
log entries below.
Ill just say thanks and keep up the good work now, in case you dont make
it to the end of the message :)
Im running a 2.6.10-1.770_FC3 kernel on Fedora core 3, humming away ever
so happily on a older Gericom Overdose 3 (sis630 chipset) laptop. I
managed to get my WLAN adapter running, Gigaset USBadapter 54, using
ndiswrapper 1.1-1. The AP is Gigaset SE515dsl, a dsl modem/router/ap,
just like the majority of APs i want to connect to. The AP is configured
to allow/block access based on client MAC adress. Im mentioning the AP
explicitly because once i got an connection with NM to a network of the
WLAN service provider that was around at the time, i could see the
signal was weak so i didnt poke around much, altough i could ping their
hosts and access them trough web.
I installed network manager trough yum, here are the package versions:
NetworkManager-0.3.4-1.1.0.fc3.i386.rpm
NetworkManager-gnome-0.3.4-1.1.0.fc3.i386.rpm
Here are some log entries from the time NM starts up (using
/sbin/service NetworkManager start as root and starting NetworkManager
as a regular user) untill it tries to connect to the AP again.
Mar 29 18:38:51 progeny NetworkManager: starting...
Mar 29 18:38:51 progeny NetworkManager: NetworkManager startup succeeded
Mar 29 18:38:53 progeny NetworkManager: eth0: Driver support level for
'sis900' is fully-supported
Mar 29 18:38:53 progeny NetworkManager: nm_device_new(): waiting for
device's worker thread to start.
Mar 29 18:38:54 progeny NetworkManager: nm_device_new(): device's worker
thread started, continuing.
Mar 29 18:38:54 progeny NetworkManager: Now managing wired device 'eth0'.
Mar 29 18:38:55 progeny NetworkManager: eth1: Driver support level for
'ndiswrapper' is fully-supported
Mar 29 18:38:58 progeny NetworkManager: nm_device_new(): waiting for
device's worker thread to start.
Mar 29 18:38:59 progeny NetworkManager: nm_device_new(): device's worker
thread started, continuing.
Mar 29 18:38:59 progeny NetworkManager: Now managing wireless device 'eth1'.
Mar 29 18:38:59 progeny nscd: nscd shutdown failed
Mar 29 18:38:59 progeny nscd: nscd startup succeeded
Mar 29 18:38:59 progeny NetworkManager: Clearing nscd hosts cache.
Mar 29 18:38:59 progeny NetworkManager: SWITCH: best device changed
Mar 29 18:39:00 progeny nscd: 15232 Access Vector Cache (AVC) started
Mar 29 18:39:02 progeny NetworkManager: Activation (eth1) started...
Mar 29 18:39:03 progeny NetworkManager: Activation (eth1/wireless):
waiting for an access point.
Mar 29 18:39:10 progeny su(pam_unix)[10794]: session closed for user root
Mar 29 18:39:17 progeny NetworkManager: Updating allowed wireless
network lists.
Mar 29 18:39:19 progeny NetworkManager: Activation (eth1/wireless):
found access point 'done_wlan' to use.
Mar 29 18:39:19 progeny NetworkManager: Activation (eth1/wireless):
access point 'done_wlan' is encrypted, and a key exists. No new key needed.
Mar 29 18:39:24 progeny NetworkManager: Activation (eth1/wireless):
using essid 'done_wlan', with Open System authentication.
Mar 29 18:39:27 progeny nmbd[4055]: [2005/03/29 18:39:27, 0]
libsmb/nmblib.c:send_udp(790)
Mar 29 18:39:28 progeny nmbd[4055]: Packet send failed to
192.168.1.255(137) ERRNO=Network is unreachable
Mar 29 18:39:28 progeny nmbd[4055]: [2005/03/29 18:39:28, 0]
nmbd/nmbd_packets.c:send_netbios_packet(163)
Mar 29 18:39:28 progeny nmbd[4055]: send_netbios_packet: send_packet()
to IP 192.168.1.255 port 137 failed
Mar 29 18:39:28 progeny nmbd[4055]: [2005/03/29 18:39:28, 0]
nmbd/nmbd_namequery.c:query_name(237)
Mar 29 18:39:28 progeny nmbd[4055]: query_name: Failed to send packet
trying to query name PRESUDST<1d>
Mar 29 18:39:28 progeny nmbd[4055]: [2005/03/29 18:39:28, 0]
nmbd/nmbd.c:reload_interfaces(265)
Mar 29 18:39:28 progeny nmbd[4055]: reload_interfaces: No subnets to
listen to. Shutting down...
Mar 29 18:39:31 progeny NetworkManager: dhcp_interface_init: MAC address
= 00:30:f1:dd:e0:1c
Mar 29 18:39:31 progeny NetworkManager: Broadcasting DHCP_DISCOVER
Mar 29 18:39:31 progeny NetworkManager: DHCP: Starting request loop,
overall start_time = {1112114371s, 404819us}
Mar 29 18:39:31 progeny NetworkManager: DHCP: Request sent, waiting for
reply...
Mar 29 18:39:48 progeny last message repeated 2 times
Mar 29 18:40:01 progeny crond(pam_unix)[15445]: session opened for user
root by (uid=0)
Mar 29 18:40:03 progeny crond(pam_unix)[15445]: session closed for user root
Mar 29 18:40:06 progeny NetworkManager: Activation (eth1/wireless):
using essid 'done_wlan', with Shared Key authentication.
Mar 29 18:40:13 progeny NetworkManager: Activation (eth1/wireless):
found access point 'ConnectionPoint' to use.
Mar 29 18:40:13 progeny NetworkManager: Activation (eth1/wireless):
access point 'ConnectionPoint' is unencrypted, no key needed.
Mar 29 18:40:17 progeny NetworkManager: Activation (eth1/wireless):
using essid 'ConnectionPoint', with no authentication.
Shutting down NM and using neat is fine:
Mar 29 18:47:58 progeny NetworkManager: Caught SIGINT/SIGTERM
Mar 29 18:47:58 progeny NetworkManager: Caught terminiation signal
Mar 29 18:47:58 progeny NetworkManager: NetworkManager -TERM succeeded
Mar 29 18:48:41 progeny kernel: parport0: PC-style at 0x378 [PCSPP,EPP]
Mar 29 18:48:52 progeny dhclient: DHCPREQUEST on eth1 to 255.255.255.255
port 67
Mar 29 18:48:52 progeny dhclient: DHCPACK from 192.168.1.1
Mar 29 18:48:52 progeny NET: /sbin/dhclient-script : updated
/etc/resolv.conf
Mar 29 18:48:52 progeny kernel: audit(1112114932.949:0): avc: denied {
read } for pid=17424 exe=/usr/sbin/nscd path=/tmp/tmpdev-17101
(deleted) dev=hda1 ino=554209 scontext=root:system_r:nscd_t
tcontext=root:object_r:tmp_t tclass=chr_file
Mar 29 18:48:56 progeny dhclient: bound to 192.168.1.5 -- renewal in
33215 seconds.
running dhclient manualy:
[root progeny done]# /sbin/dhclient
Internet Systems Consortium DHCP Client V3.0.1
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
Listening on LPF/eth0/00:90:f5:08:96:d7
Sending on LPF/eth0/00:90:f5:08:96:d7
Listening on LPF/eth1/00:30:f1:dd:e0:1c
Sending on LPF/eth1/00:30:f1:dd:e0:1c
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
DHCPOFFER from 192.168.1.1
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.5 -- renewal in 39212 seconds.
Scanning for APs with iwlist, both of these networks should be on the
same AP hardware that i mentioned above:
[root progeny done]# /sbin/iwlist eth1 scan
eth1 Scan completed :
Cell 01 - Address: 00:01:E3:49:BD:CF
ESSID:"done_wlan"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462GHz (Channel 11)
Quality:0/100 Signal level:-72 dBm Noise
level:-256 dBm
Encryption key:on
Bit Rate:1Mb/s
Bit Rate:2Mb/s
Bit Rate:5.5Mb/s
Bit Rate:11Mb/s
Bit Rate:6Mb/s
Bit Rate:9Mb/s
Bit Rate:12Mb/s
Bit Rate:18Mb/s
Bit Rate:24Mb/s
Bit Rate:36Mb/s
Bit Rate:48Mb/s
Bit Rate:54Mb/s
Extra:bcn_int=100
Extra:atim=3
Cell 02 - Address: 00:01:E3:41:FB:57
ESSID:"ConnectionPoint"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462GHz (Channel 11)
Quality:0/100 Signal level:-77 dBm Noise
level:-256 dBm
Encryption key:off
Bit Rate:1Mb/s
Bit Rate:2Mb/s
Bit Rate:5.5Mb/s
Bit Rate:11Mb/s
Bit Rate:6Mb/s
Bit Rate:9Mb/s
Bit Rate:12Mb/s
Bit Rate:18Mb/s
Bit Rate:24Mb/s
Bit Rate:36Mb/s
Bit Rate:48Mb/s
Bit Rate:54Mb/s
Extra:bcn_int=100
Extra:atim=3
Here is my eth1 configuration that works with neat. WEP key is stroed in
a seperate file. Id like to mention that neither Neat worked until i
edited the file myself, changing some configuration options that were
unsettable in neat.
[root progeny done]# cat /etc/sysconfig/network-scripts/ifcfg-eth1
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
IPV6INIT=no
ONBOOT=no
USERCTL=no
PEERDNS=yes
GATEWAY=192.168.1.1
TYPE=Wireless
DEVICE=eth1
HWADDR=00:30:f1:dd:e0:1c
BOOTPROTO=dhcp
NETMASK=255.255.255.0
DHCP_HOSTNAME=progeny
IPADDR=
DOMAIN=
ESSID=done_wlan
CHANNEL=11
MODE=Managed
RATE=Auto
Thanks,
Ivan
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]