Ubuntu Sverige

Forum för Ubuntus svenska gemenskap
https://ubuntu-se.servebbs.org/

Hjälp med uppkoppling till trådlös router

https://ubuntu-se.servebbs.org/viewtopic.php?t=22605

Sida 1 av 2

Hjälp med uppkoppling till trådlös router

Postat: 15 jan 2008, 22:57
av babbelfisken
Hejsan,

I min förra installation av Gutsy så fick jag mitt trådlösa nätverkskort att fungera
och jag kunde koppla upp mig mot min accesspunkt som kräver WPA-PSK [TKIP] för att logga in.

Nu så var jag tvungen att göra en ominstallation och har gjort om alla steg för att få det att fungera.
Sliter mina gråa nu. Network-admin "ser" min accesspunkt men jag kan inte logga in till den.
Enable Networking och Enable Wireless är förbockat.

Värt att nämna att jag har en win vista som kan koppla upp sig mot min trådlösa router med alla inställningar.

Här kommer lite utdata som jag hoppas kan vara relevant:

daniel@BABBELFISKEN:~$ lspci | grep Broadcom
00:0a.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)

Denna har jag enablat firmware för [bcm43xx-fwcutter] och den är In Use.

daniel@BABBELFISKEN:~$ iwconfig

lo        no wireless extensions.

eth0      no wireless extensions.

eth1      IEEE 802.11b/g  ESSID:"BABBELFISKEN"  Nickname:"Broadcom 4318"
          Mode:Managed  Frequency=2.472 GHz  Access Point: 00:14:6C:D9:75:5A 
          Bit Rate=1 Mb/s  Tx-Power=18 dBm 
          RTS thr:off  Fragment thr:off
          Link Quality=70/100  Signal level=-40 dBm  Noise level=-72 dBm
          Rx invalid nwid:0  Rx invalid crypt:8648  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0  Missed beacon:0


daniel@BABBELFISKEN:~$ ifconfig

eth0      Link encap:Ethernet  HWaddr 00:03:0D:38:E2:8C 
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::203:dff:fe38:e28c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1553 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1057 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1220041 (1.1 MB)  TX bytes:148750 (145.2 KB)
          Interrupt:17 Base address:0x2400

eth1      Link encap:Ethernet  HWaddr 00:14:A5:40:BE:D4 
          inet6 addr: fe80::214:a5ff:fe40:bed4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:46 errors:0 dropped:8833 overruns:0 frame:0
          TX packets:18086 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5192 (5.0 KB)  TX bytes:1185266010 (1.1 GB)
          Interrupt:3 Base address:0x8000

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)

Jag har kört alla updates som finns och jag vet inte mer vad det är som jag skall köra.
Det har fungerat innan, det är det som är det konstiga?

Väldigt tacksam för svar då jag har googlat 2 nätter nu...

Mvh Daniel Svensson, ny ubuntist som är trött på windows...

SV: Hjälp med uppkoppling till trådlös router

Postat: 15 jan 2008, 23:16
av Lars
Hej, välkommen till Ubuntu-se :)

Får du upp frågan om lösenord? Kanske du kan testa att radera det sparade lösenordet i nyckelringshanteraren (under system/administration).

Ett annat trick är att trycka alt+F2 och köra gconf-editor. Högerklicka på varje värdet under /system/networking/wireless/networks/BABBELFISKEN och välj nollställ. Det kan hjälpa ibland.

SV: Hjälp med uppkoppling till trådlös router

Postat: 15 jan 2008, 23:24
av DeepThought
Nu slängde jag ut NetworkManager för ett tag sedan (till förmån för ett program som heter wicd), så jag minns inte exakt. Men du kan testa följande:

Klicka på NetworkManager-ikonen, och välj manuell konfiguration. Välj det trådlösa kortet och klicka på Egenskaper. Kryssa ur rutan "Roaming-läge", och du får nu möjlighet att mata in alla uppgifter manuellt. Skriv in ESSID (skall vara samma som fås om du kör sudo iwlist scan i terminalen), lösenordstyp och lösenord. Om din accesspunkt kör en DHCP-server kan du välja det, annars får du mata in en statisk IP.

Fungerar det då, så kan du testa att kryssa i roaming-rutan igen, och sedan klicka på NetworkManager-ikonen igen, och välja "Anslut till annat nätverk.." (eller vad det nu är?) och mata in ESSID och lösenord. Se om det fungerar.

EDIT: Börja med Lars förslag. Lars brukar ha koll på sakerna :)

SV: Hjälp med uppkoppling till trådlös router

Postat: 15 jan 2008, 23:53
av babbelfisken
Hej igen,

Jag vet inte om jag gjorde fel nu ;)

Nu syns ingenting i nyckelringshanteraren och när jag kör gconf-editor så finns inte /system/network/
När jag försöker logga in på min router så poppar rutan upp att skriva in lösenord och välja WPA Personal
och TKIP som vanligt.. men inget händer..

SV: Hjälp med uppkoppling till trådlös router

Postat: 16 jan 2008, 00:02
av Lars
OK, de där sakerna skapas nog första gången du lyckas koppla upp dig.

Du kan kolla på system/administration/systemlogg (/var/log/daemon.log) om NetworkManager ger några felmeddelanden som kan vara till hjälp.

SV: Hjälp med uppkoppling till trådlös router

Postat: 16 jan 2008, 00:26
av babbelfisken
Hej igen,

har kört kommandot more daemon.log | grep "NetworkManager: <WARN>" och fick detta.. Dessa raderna är bara för Jan 15

Jan 15 21:28:38 BABBELFISKEN NetworkManager: <WARN>  nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory)) 
Jan 15 21:56:45 BABBELFISKEN NetworkManager: <WARN>  nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory)) 
Jan 15 22:29:33 BABBELFISKEN NetworkManager: <WARN>  nm_dbus_get_network_data_cb(): nm_dbus_get_network_data_cb(): dbus returned an error.  (org.freedesktop.NetworkManagerInfo.InvalidArguments) nmi_dbus_get_network_properties called with invalid arguments. 
Jan 15 22:29:35 BABBELFISKEN NetworkManager: <WARN>  nm_dbus_get_network_data_cb(): nm_dbus_get_network_data_cb(): dbus returned an error.  (org.freedesktop.NetworkManagerInfo.InvalidArguments) nmi_dbus_get_network_properties called with invalid arguments. 
Jan 15 22:29:38 BABBELFISKEN NetworkManager: <WARN>  nm_dbus_get_network_data_cb(): nm_dbus_get_network_data_cb(): dbus returned an error.  (org.freedesktop.NetworkManagerInfo.InvalidArguments) nmi_dbus_get_network_properties called with invalid arguments. 
Jan 15 22:29:40 BABBELFISKEN NetworkManager: <WARN>  nm_dbus_get_network_data_cb(): nm_dbus_get_network_data_cb(): dbus returned an error.  (org.freedesktop.NetworkManagerInfo.InvalidArguments) nmi_dbus_get_network_properties called with invalid arguments. 
Jan 15 22:32:50 BABBELFISKEN NetworkManager: <WARN>  nm_dhcp_manager_get_state_for_device(): dhcdbd not running!
Jan 15 22:32:50 BABBELFISKEN NetworkManager: <WARN>  nm_dhcp_manager_begin_transaction(): dhcdbd not running!
Jan 15 22:32:51 BABBELFISKEN NetworkManager: <WARN>  nm_dhcp_manager_get_state_for_device(): dhcdbd not running!
Jan 15 22:32:51 BABBELFISKEN NetworkManager: <WARN>  nm_dhcp_manager_begin_transaction(): dhcdbd not running!
Jan 15 22:32:51 BABBELFISKEN NetworkManager: <WARN>  nm_dhcp_manager_get_state_for_device(): dhcdbd not running!
Jan 15 22:32:51 BABBELFISKEN NetworkManager: <WARN>  nm_dhcp_manager_begin_transaction(): dhcdbd not running!
Jan 15 22:32:51 BABBELFISKEN NetworkManager: <WARN>  nm_dhcp_manager_get_state_for_device(): dhcdbd not running!
Jan 15 22:32:51 BABBELFISKEN NetworkManager: <WARN>  nm_dhcp_manager_begin_transaction(): dhcdbd not running!
Jan 15 22:32:51 BABBELFISKEN NetworkManager: <WARN>  nm_dhcp_manager_get_state_for_device(): dhcdbd not running!
Jan 15 22:32:51 BABBELFISKEN NetworkManager: <WARN>  nm_dhcp_manager_begin_transaction(): dhcdbd not running!
Jan 15 22:32:52 BABBELFISKEN NetworkManager: <WARN>  nm_dhcp_manager_get_state_for_device(): dhcdbd not running!
Jan 15 22:32:52 BABBELFISKEN NetworkManager: <WARN>  nm_dhcp_manager_begin_transaction(): dhcdbd not running!
Jan 15 22:32:52 BABBELFISKEN NetworkManager: <WARN>  nm_dhcp_manager_get_state_for_device(): dhcdbd not running!
Jan 15 22:32:52 BABBELFISKEN NetworkManager: <WARN>  nm_dhcp_manager_begin_transaction(): dhcdbd not running!
Jan 15 22:32:52 BABBELFISKEN NetworkManager: <WARN>  nm_dhcp_manager_get_state_for_device(): dhcdbd not running!
Jan 15 22:32:52 BABBELFISKEN NetworkManager: <WARN>  nm_dhcp_manager_begin_transaction(): dhcdbd not running!
Jan 15 22:32:53 BABBELFISKEN NetworkManager: <WARN>  nm_dhcp_manager_get_state_for_device(): dhcdbd not running!
Jan 15 22:32:53 BABBELFISKEN NetworkManager: <WARN>  nm_dhcp_manager_begin_transaction(): dhcdbd not running!
Jan 15 22:32:53 BABBELFISKEN NetworkManager: <WARN>  nm_dhcp_manager_get_state_for_device(): dhcdbd not running!
Jan 15 22:32:53 BABBELFISKEN NetworkManager: <WARN>  nm_dhcp_manager_begin_transaction(): dhcdbd not running!
Jan 15 22:33:02 BABBELFISKEN NetworkManager: <WARN>  nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory)) 
Jan 15 22:33:49 BABBELFISKEN NetworkManager: <WARN>  nm_dbus_get_networks_cb(): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - There are no wireless networks stored..
Jan 15 22:35:38 BABBELFISKEN NetworkManager: <WARN>  nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory)) 
Jan 15 22:37:51 BABBELFISKEN NetworkManager: <WARN>  nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory)) 
Jan 15 22:38:06 BABBELFISKEN NetworkManager: <WARN>  nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory)) 
Jan 15 22:42:22 BABBELFISKEN NetworkManager: <WARN>  ifparser_init(): Error: Can't parse inet line 'inet' 
Jan 15 22:42:27 BABBELFISKEN NetworkManager: <WARN>  ifparser_init(): Error: Can't parse inet line 'inet' 
Jan 15 22:42:33 BABBELFISKEN NetworkManager: <WARN>  nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory)) 
Jan 15 22:43:03 BABBELFISKEN NetworkManager: <WARN>  nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory)) 
Jan 15 22:43:17 BABBELFISKEN NetworkManager: <WARN>  ifparser_init(): Error: Can't parse inet line 'inet' 
Jan 15 22:43:26 BABBELFISKEN NetworkManager: <WARN>  nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory)) 
Jan 15 22:43:28 BABBELFISKEN NetworkManager: <WARN>  ifparser_init(): Error: Can't parse inet line 'inet' 
Jan 15 22:43:43 BABBELFISKEN NetworkManager: <WARN>  nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory)) 
Jan 15 23:14:33 BABBELFISKEN NetworkManager: <WARN>  nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory)) 

Vet inte hur jag själv skall utröna detta.. En annan sak med, ibland när jag försökt logga in har jag sett "bars" [signalstyrkan] men den står på 0%, efter ett tag dyker inloggningsrutan upp igen för trådlösa nätverket?

SV: Hjälp med uppkoppling till trådlös router

Postat: 16 jan 2008, 00:38
av Lars
Hur ser din /etc/network/interfaces ut?

SV: Hjälp med uppkoppling till trådlös router

Postat: 16 jan 2008, 00:43
av babbelfisken
daniel@BABBELFISKEN:/etc/network$ more interfaces
auto lo
iface lo inet loopback

SV: Hjälp med uppkoppling till trådlös router

Postat: 16 jan 2008, 00:49
av Lars
Jag hittade något på nätet om att NetworkManager inte tycker om tabbar i /etc/network/interfaces, du kanske ska kolla att det bara är mellanslag.

För övrigt så får jag också det där med Failed to execute child process "/usr/sbin/nscd", fast bara en gång. Det fungerar ändå.

SV: Hjälp med uppkoppling till trådlös router

Postat: 16 jan 2008, 01:08
av babbelfisken
Hej igen Lars,

Tacksam för att du vill ta dig tid. Men jag står på samma ruta igen.
Vet inte vad det är som kan ha gått snett?

Finns det inget automagiskt kommando som typ restartar network-admin
med alla interfaces och vad det nu kan vara :)

Danne

SV: Hjälp med uppkoppling till trådlös router

Postat: 16 jan 2008, 11:42
av Lars
Något magiskt kommando känner jag inte till för just detta, men "Error: Can't parse inet line 'inet'" tyder på att något är fel i /etc/network/interfaces. Tryck alt+F2, kör "gksudo gedit /etc/network/interfaces" och ersätt innehållet med följande:

Kod: Markera allt

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
Det är kanske snarlikt det du redan har, men osynliga tecken såsom radmatningar och tabbar kan eventuellt ställa till det.

SV: Hjälp med uppkoppling till trådlös router

Postat: 16 jan 2008, 12:22
av babbelfisken
Hej Lars och övriga,

Min /etc/network/interfaces såg exakt likadan ut.
För säkerhets skull så raderade jag allt i filen, inkl möjliga "tab och radbryts tecken".
Skrev in allt igen.

Startade om datorn och det fungerar inte.
Några fler idéer ?

SV: Hjälp med uppkoppling till trådlös router

Postat: 16 jan 2008, 12:27
av Lars
Får du fortfarande samma felmeddelande (Can't parse inet line 'inet')?

SV: Hjälp med uppkoppling till trådlös router

Postat: 16 jan 2008, 21:44
av babbelfisken
Hej Lars (min guru),

Nu får jag denna utskriften, dessa är de sista raderna efter att jag försökt att logga in nätet. Tooltipen
för nm-applet sa ngt i stil med "Preparing device eth1 ...." när den försökte logga in.
Efter att den försökt fick jag dessa rader i loggen:

daniel@BABBELFISKEN:/var/log$ more daemon.log | grep "NetworkManager: <WARN>"

Jan 16 20:34:01 BABBELFISKEN NetworkManager: <WARN>  nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory)) 
Jan 16 20:34:02 BABBELFISKEN NetworkManager: <WARN>  nm_device_802_11_wireless_scan(): could not trigger wireless scan on device eth1: No such device

Mer utdata gjord efter föröket att logga in:

daniel@BABBELFISKEN:/var/log$ sudo iwlist scan
lo        Interface doesn't support scanning.

eth0      Interface doesn't support port scanning.

eth1      Interface doesn't support scanning : No such device




daniel@BABBELFISKEN:/var/log$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:03:0D:38:E2:8C 
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::203:dff:fe38:e28c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8777 errors:0 dropped:0 overruns:0 frame:0
          TX packets:637 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1144948 (1.0 MB)  TX bytes:131932 (128.8 KB)
          Interrupt:17 Base address:0x2400

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)

daniel@BABBELFISKEN:/var/log$ iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

eth1      IEEE 802.11b/g  ESSID:"BABBELFISKEN"  Nickname:"Broadcom 4318"
          Mode:Managed  Frequency=2.462 GHz  Access Point: 00:14:6C:D9:75:5A 
          RTS thr:off  Fragment thr:off
          Link Quality=0/100  Signal level=-256 dBm  Noise level=-256 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0  Missed beacon:0

Jag rullar tummarna så länge. Det verkar ju som att det e ngt galet med eth1 nu?

Danne

SV: Hjälp med uppkoppling till trådlös router

Postat: 16 jan 2008, 21:56
av Lars
Du har visst ett Broadcom-kort, har du rätt firmware under /lib/firmware? Filerna har namn som bcm43xx_microcode4.fw och liknande.

SV: Hjälp med uppkoppling till trådlös router

Postat: 16 jan 2008, 22:49
av babbelfisken
Det står bcm43xx_microcode11.fw

SV: Hjälp med uppkoppling till trådlös router

Postat: 17 jan 2008, 07:36
av babbelfisken
Hej Lars,

Här är en till output. Försökte logga in igen och hoppas att ngt magiskt hade skett med datorn under
natten men icke ;)

Nu fick jag upp signalbars vi uppkopplingsikonen men den gick över till eth0 efter ett tag.

Jan 17 06:27:23 BABBELFISKEN NetworkManager: <debug> [1200547643.308074] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'BABBELFISKEN'
Jan 17 06:27:23 BABBELFISKEN NetworkManager: <info>  User Switch: /org/freedesktop/NetworkManager/Devices/eth1 / BABBELFISKEN
Jan 17 06:27:23 BABBELFISKEN NetworkManager: <info>  Deactivating device eth1.
Jan 17 06:27:23 BABBELFISKEN NetworkManager: <info>  Device eth1 activation scheduled...
Jan 17 06:27:23 BABBELFISKEN NetworkManager: <info>  Deactivating device eth0.
Jan 17 06:27:23 BABBELFISKEN dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 5176
Jan 17 06:27:23 BABBELFISKEN dhclient: killed old client process, removed PID file
Jan 17 06:27:23 BABBELFISKEN dhclient: DHCPRELEASE on eth0 to 192.168.1.1 port 67
Jan 17 06:27:23 BABBELFISKEN avahi-daemon[4769]: Withdrawing address record for 192.168.1.2 on eth0.
Jan 17 06:27:23 BABBELFISKEN avahi-daemon[4769]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.2.
Jan 17 06:27:23 BABBELFISKEN avahi-daemon[4769]: Interface eth0.IPv4 no longer relevant for mDNS.
Jan 17 06:27:24 BABBELFISKEN NetworkManager: <info>  Activation (eth1) started...
Jan 17 06:27:24 BABBELFISKEN NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Jan 17 06:27:24 BABBELFISKEN avahi-daemon[4769]: Withdrawing address record for fe80::203:dff:fe38:e28c on eth0.
Jan 17 06:27:24 BABBELFISKEN NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Jan 17 06:27:24 BABBELFISKEN NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Jan 17 06:27:24 BABBELFISKEN NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Jan 17 06:27:24 BABBELFISKEN NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Jan 17 06:27:24 BABBELFISKEN NetworkManager: <info>  Activation (eth1/wireless): access point 'BABBELFISKEN' is encrypted, but NO valid key exists.  New key needed.
Jan 17 06:27:24 BABBELFISKEN NetworkManager: <info>  Activation (eth1) New wireless user key requested for network 'BABBELFISKEN'.
Jan 17 06:27:24 BABBELFISKEN NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Jan 17 06:27:24 BABBELFISKEN NetworkManager: <info>  Activation (eth1) New wireless user key for network 'BABBELFISKEN' received.
Jan 17 06:27:24 BABBELFISKEN NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Jan 17 06:27:24 BABBELFISKEN NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Jan 17 06:27:24 BABBELFISKEN NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Jan 17 06:27:24 BABBELFISKEN NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Jan 17 06:27:24 BABBELFISKEN NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Jan 17 06:27:24 BABBELFISKEN NetworkManager: <info>  Activation (eth1/wireless): access point 'BABBELFISKEN' is encrypted, and a key exists.  No new key needed.
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  supplicant_interface_init() - connect to global ctrl socket (0/10).
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  supplicant_interface_init() - connect to global ctrl socket (1/10).
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  SUP: sending command 'INTERFACE_ADD eth1^I^Iwext^I/var/run/wpa_supplicant4^I'
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  SUP: response was 'OK'
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  supplicant_init() - connect to device ctrl socket (1/10).
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  SUP: sending command 'AP_SCAN 1'
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  SUP: response was 'OK'
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  SUP: sending command 'ADD_NETWORK'
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  SUP: response was '0'
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 ssid 42414242454c4649534b454e'
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  SUP: response was 'OK'
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 proto WPA'
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  SUP: response was 'OK'
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK'
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  SUP: response was 'OK'
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 psk <key>'
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  SUP: response was 'OK'
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 pairwise TKIP'
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  SUP: response was 'OK'
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 group TKIP'
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  SUP: response was 'OK'
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  SUP: sending command 'ENABLE_NETWORK 0'
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  SUP: response was 'OK'
Jan 17 06:27:25 BABBELFISKEN NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Jan 17 06:27:29 BABBELFISKEN NetworkManager: <info>  Old device 'eth1' activating, won't change.
Jan 17 06:28:02 BABBELFISKEN last message repeated 3 times
Jan 17 06:28:23 BABBELFISKEN last message repeated 2 times
Jan 17 06:28:25 BABBELFISKEN NetworkManager: <info>  Activation (eth1/wireless): association took too long (>60s), failing activation.
Jan 17 06:28:25 BABBELFISKEN NetworkManager: <info>  Activation (eth1) failure scheduled...
Jan 17 06:28:26 BABBELFISKEN NetworkManager: <info>  Activation (eth1) failed for access point (BABBELFISKEN)
Jan 17 06:28:26 BABBELFISKEN NetworkManager: <info>  Activation (eth1) failed.
Jan 17 06:28:26 BABBELFISKEN NetworkManager: <info>  Deactivating device eth1.
Jan 17 06:28:26 BABBELFISKEN NetworkManager: <info>  SWITCH: no current connection, found better connection 'eth0'.
Jan 17 06:28:26 BABBELFISKEN NetworkManager: <info>  Will activate connection 'eth0'.
Jan 17 06:28:26 BABBELFISKEN NetworkManager: <info>  Device eth0 activation scheduled...
Jan 17 06:28:26 BABBELFISKEN NetworkManager: <info>  Activation (eth0) started...
Jan 17 06:28:26 BABBELFISKEN NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Jan 17 06:28:26 BABBELFISKEN NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Jan 17 06:28:26 BABBELFISKEN NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Jan 17 06:28:26 BABBELFISKEN NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Jan 17 06:28:26 BABBELFISKEN NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Jan 17 06:28:26 BABBELFISKEN NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Jan 17 06:28:26 BABBELFISKEN NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Jan 17 06:28:26 BABBELFISKEN NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Jan 17 06:28:26 BABBELFISKEN NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Jan 17 06:28:27 BABBELFISKEN NetworkManager: <info>  Activation (eth0) Beginning DHCP transaction.
Jan 17 06:28:27 BABBELFISKEN dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 0
Jan 17 06:28:27 BABBELFISKEN NetworkManager: <info>  DHCP daemon state is now 12 (successfully started) for interface eth0
Jan 17 06:28:27 BABBELFISKEN NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Jan 17 06:28:28 BABBELFISKEN NetworkManager: <info>  DHCP daemon state is now 1 (starting) for interface eth0
Jan 17 06:28:32 BABBELFISKEN dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
Jan 17 06:28:33 BABBELFISKEN dhclient: DHCPOFFER from 192.168.1.1
Jan 17 06:28:33 BABBELFISKEN dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jan 17 06:28:35 BABBELFISKEN dhclient: DHCPACK from 192.168.1.1
Jan 17 06:28:35 BABBELFISKEN avahi-daemon[4769]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.2.
Jan 17 06:28:35 BABBELFISKEN dhclient: bound to 192.168.1.2 -- renewal in 33193 seconds.
Jan 17 06:28:35 BABBELFISKEN avahi-daemon[4769]: New relevant interface eth0.IPv4 for mDNS.
Jan 17 06:28:35 BABBELFISKEN avahi-daemon[4769]: Registering new address record for 192.168.1.2 on eth0.IPv4.
Jan 17 06:28:35 BABBELFISKEN NetworkManager: <info>  DHCP daemon state is now 2 (bound) for interface eth0
Jan 17 06:28:35 BABBELFISKEN NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
Jan 17 06:28:35 BABBELFISKEN NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) started...
Jan 17 06:28:35 BABBELFISKEN NetworkManager: <info>  Retrieved the following IP4 configuration from the DHCP daemon:
Jan 17 06:28:35 BABBELFISKEN NetworkManager: <info>    address 192.168.1.2
Jan 17 06:28:35 BABBELFISKEN NetworkManager: <info>    netmask 255.255.255.0
Jan 17 06:28:35 BABBELFISKEN NetworkManager: <info>    broadcast 192.168.1.255
Jan 17 06:28:35 BABBELFISKEN NetworkManager: <info>    gateway 192.168.1.1
Jan 17 06:28:35 BABBELFISKEN NetworkManager: <info>    nameserver 192.168.1.1
Jan 17 06:28:35 BABBELFISKEN NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Jan 17 06:28:35 BABBELFISKEN NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) complete.
Jan 17 06:28:35 BABBELFISKEN NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Jan 17 06:28:35 BABBELFISKEN avahi-daemon[4769]: Withdrawing address record for 192.168.1.2 on eth0.
Jan 17 06:28:35 BABBELFISKEN avahi-daemon[4769]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.2.
Jan 17 06:28:35 BABBELFISKEN avahi-daemon[4769]: Interface eth0.IPv4 no longer relevant for mDNS.
Jan 17 06:28:35 BABBELFISKEN avahi-daemon[4769]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.2.
Jan 17 06:28:35 BABBELFISKEN avahi-daemon[4769]: New relevant interface eth0.IPv4 for mDNS.
Jan 17 06:28:35 BABBELFISKEN avahi-daemon[4769]: Registering new address record for 192.168.1.2 on eth0.IPv4.
Jan 17 06:28:36 BABBELFISKEN NetworkManager: <info>  Clearing nscd hosts cache.
Jan 17 06:28:36 BABBELFISKEN NetworkManager: <WARN>  nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory)) 
Jan 17 06:28:36 BABBELFISKEN NetworkManager: <info>  Activation (eth0) successful, device activated.
Jan 17 06:28:36 BABBELFISKEN NetworkManager: <info>  Activation (eth0) Finish handler scheduled.
Jan 17 06:28:36 BABBELFISKEN NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Jan 17 06:28:39 BABBELFISKEN ntpdate[6209]: step time server 91.189.94.4 offset 3.063706 sec
Jan 17 06:28:40 BABBELFISKEN avahi-daemon[4769]: Registering new address record for fe80::203:dff:fe38:e28c on eth0.*.

SV: Hjälp med uppkoppling till trådlös router

Postat: 17 jan 2008, 12:31
av Lars
Det är väl raden Activation (eth1/wireless): association took too long (>60s), failing activation. som är intressant, men jag vet inte riktigt vad det beror på. Jag antar att eth0 är ditt trådbundna kort, om du drar ur sladden till det så kanske du kan få datorn att försöka lite mer med eth1 innan den ger upp.

Du kanske kan testa med WEP istället, eller helt utan kryptering. Bara för att verifiera att kortet i sig fungerar som det ska.

SV: Hjälp med uppkoppling till trådlös router

Postat: 18 jan 2008, 11:52
av babbelfisken
Hej Lars och övriga,

Gjorde en ominstallation och detta är första utdatat efter att jag försökt göra en uppkoppling.
Innan ominstallationen så försökte jag med WEP och ingen kryptering alls men även detta funkade inte,
så det var därför jag beslutade mig att göra en ominstallation. I loggen nedan så har jag nu bcm43xx_microcode5.fw och innan installationen så hade jag bcm43xx_microcode11.fw? Varför olika nu? Verkar ju vara ngt fel med firmware? Min firmware
är In Use i hanteraren för properitära drivrutiner.


LOG( Editerad ):

Jan 17 23:40:56 babbelfisken firmware_helper[7161]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:00:0a.0' with driver 'bcm43xx'
Jan 17 23:40:59 babbelfisken NetworkManager: <WARN>  nm_device_802_11_wireless_scan(): could not trigger wireless scan on device eth1: No such device
Jan 17 23:41:54 babbelfisken avahi-daemon[5415]: Files changed, reloading.
Jan 17 23:41:54 babbelfisken avahi-daemon[5415]: No service file found in /etc/avahi/services.
Jan 17 23:41:55 babbelfisken avahi-daemon[5415]: Got SIGTERM, quitting.
Jan 17 23:41:55 babbelfisken avahi-daemon[5415]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.2.
Jan 17 23:42:59 babbelfisken firmware_helper[8534]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:00:0a.0' with driver 'bcm43xx'
Jan 17 23:43:03 babbelfisken NetworkManager: <WARN>  nm_device_802_11_wireless_scan(): could not trigger wireless scan on device eth1: No such device
Jan 17 23:45:03 babbelfisken firmware_helper[9746]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:00:0a.0' with driver 'bcm43xx'
Jan 17 23:45:07 babbelfisken NetworkManager: <WARN>  nm_device_802_11_wireless_scan(): could not trigger wireless scan on device eth1: No such device
Jan 17 23:47:07 babbelfisken firmware_helper[11055]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:00:0a.0' with driver 'bcm43xx'
Jan 17 23:47:11 babbelfisken NetworkManager: <WARN>  nm_device_802_11_wireless_scan(): could not trigger wireless scan on device eth1: No such device
Jan 17 23:48:11 babbelfisken avahi-daemon[15181]: Found user 'avahi' (UID 106) and group 'avahi' (GID 114).
Jan 17 23:48:11 babbelfisken avahi-daemon[15181]: Successfully dropped root privileges.
Jan 17 23:48:11 babbelfisken avahi-daemon[15181]: avahi-daemon 0.6.20 starting up.
Jan 17 23:48:11 babbelfisken avahi-daemon[15181]: Successfully called chroot().
Jan 17 23:48:11 babbelfisken avahi-daemon[15181]: Successfully dropped remaining capabilities.
Jan 17 23:48:11 babbelfisken avahi-daemon[15181]: No service file found in /etc/avahi/services.
Jan 17 23:48:11 babbelfisken avahi-daemon[15181]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.2.
Jan 17 23:48:11 babbelfisken avahi-daemon[15181]: New relevant interface eth0.IPv4 for mDNS.
Jan 17 23:48:11 babbelfisken avahi-daemon[15181]: Network interface enumeration completed.
Jan 17 23:48:11 babbelfisken avahi-daemon[15181]: Registering new address record for fe80::203:dff:fe38:e28c on eth0.*.
Jan 17 23:48:11 babbelfisken avahi-daemon[15181]: Registering new address record for 192.168.1.2 on eth0.IPv4.
Jan 17 23:48:11 babbelfisken avahi-daemon[15181]: Registering HINFO record with values 'X86_64'/'LINUX'.
Jan 17 23:48:12 babbelfisken avahi-daemon[15181]: Server startup complete. Host name is babbelfisken.local. Local service cookie is 3550654388.
Jan 17 23:49:11 babbelfisken firmware_helper[17593]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:00:0a.0' with driver 'bcm43xx'
Jan 17 23:49:14 babbelfisken NetworkManager: <WARN>  nm_device_802_11_wireless_scan(): could not trigger wireless scan on device eth1: No such device
Jan 17 23:51:14 babbelfisken firmware_helper[23557]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:00:0a.0' with driver 'bcm43xx'
Jan 17 23:51:17 babbelfisken NetworkManager: <WARN>  nm_device_802_11_wireless_scan(): could not trigger wireless scan on device eth1: No such device
Jan 17 23:52:42 babbelfisken NetworkManager: <WARN>  nm_signal_handler(): Caught signal 15, shutting down normally.
Jan 17 23:52:42 babbelfisken NetworkManager: <info>  Caught terminiation signal
Jan 17 23:52:42 babbelfisken NetworkManager: <debug> [1200610362.673684] nm_print_open_socks(): Open Sockets List:
Jan 17 23:52:42 babbelfisken NetworkManager: <debug> [1200610362.673711] nm_print_open_socks(): Open Sockets List Done.
Jan 17 23:52:42 babbelfisken NetworkManager: <info>  Deactivating device eth0.
Jan 17 23:52:42 babbelfisken dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 5562
Jan 17 23:52:42 babbelfisken dhclient: killed old client process, removed PID file
Jan 17 23:52:42 babbelfisken dhclient: DHCPRELEASE on eth0 to 192.168.1.1 port 67
Jan 17 23:52:42 babbelfisken avahi-daemon[15181]: Withdrawing address record for 192.168.1.2 on eth0.
Jan 17 23:52:42 babbelfisken avahi-daemon[15181]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.2.
Jan 17 23:52:42 babbelfisken avahi-daemon[15181]: Interface eth0.IPv4 no longer relevant for mDNS.
Jan 17 23:52:43 babbelfisken avahi-daemon[15181]: Withdrawing address record for fe80::203:dff:fe38:e28c on eth0.
Jan 17 23:52:43 babbelfisken NetworkManager: <info>  Deactivating device eth1.
Jan 17 23:52:43 babbelfisken NetworkManager: <info>  starting...
Jan 17 23:52:43 babbelfisken firmware_helper[25333]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:00:0a.0' with driver 'bcm43xx'
Jan 17 23:52:48 babbelfisken NetworkManager: <info>  eth1: Device is fully-supported using driver 'bcm43xx'.
Jan 17 23:52:48 babbelfisken NetworkManager: <info>  nm_device_init(): waiting for device's worker thread to start
Jan 17 23:52:48 babbelfisken firmware_helper[25354]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:00:0a.0' with driver 'bcm43xx'
Jan 17 23:52:48 babbelfisken NetworkManager: <info>  nm_device_init(): device's worker thread started, continuing.
Jan 17 23:52:48 babbelfisken NetworkManager: <info>  Now managing wireless (802.11) device 'eth1'.
Jan 17 23:52:48 babbelfisken NetworkManager: <info>  Deactivating device eth1.
Jan 17 23:52:48 babbelfisken NetworkManager: <info>  eth0: Device is fully-supported using driver 'r8169'.
Jan 17 23:52:48 babbelfisken NetworkManager: <info>  nm_device_init(): waiting for device's worker thread to start
Jan 17 23:52:49 babbelfisken NetworkManager: <info>  nm_device_init(): device's worker thread started, continuing.
Jan 17 23:52:49 babbelfisken NetworkManager: <info>  Now managing wired Ethernet (802.3) device 'eth0'.
Jan 17 23:52:49 babbelfisken NetworkManager: <info>  Deactivating device eth0.
Jan 17 23:52:49 babbelfisken NetworkManager: <info>  Will activate wired connection 'eth0' because it now has a link.
Jan 17 23:52:49 babbelfisken NetworkManager: <info>  Updating allowed wireless network lists.
Jan 17 23:52:49 babbelfisken NetworkManager: <WARN>  nm_dbus_get_networks_cb(): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - There are no wireless networks stored..
Jan 17 23:52:49 babbelfisken NetworkManager: <info>  SWITCH: no current connection, found better connection 'eth0'.
Jan 17 23:52:49 babbelfisken NetworkManager: <info>  Will activate connection 'eth0'.
Jan 17 23:52:49 babbelfisken NetworkManager: <info>  Device eth0 activation scheduled...
Jan 17 23:52:49 babbelfisken NetworkManager: <info>  Activation (eth0) started...
Jan 17 23:52:49 babbelfisken NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Jan 17 23:52:49 babbelfisken NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Jan 17 23:52:49 babbelfisken NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Jan 17 23:52:49 babbelfisken NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Jan 17 23:52:49 babbelfisken NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Jan 17 23:52:49 babbelfisken NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Jan 17 23:52:49 babbelfisken NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Jan 17 23:52:49 babbelfisken NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Jan 17 23:52:49 babbelfisken NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Jan 17 23:52:50 babbelfisken NetworkManager: <info>  Activation (eth0) Beginning DHCP transaction.
Jan 17 23:52:50 babbelfisken dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 0
Jan 17 23:52:50 babbelfisken NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Jan 17 23:52:50 babbelfisken NetworkManager: <info>  DHCP daemon state is now 12 (successfully started) for interface eth0
Jan 17 23:52:51 babbelfisken NetworkManager: <info>  DHCP daemon state is now 1 (starting) for interface eth0
Jan 17 23:52:52 babbelfisken dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Jan 17 23:52:52 babbelfisken NetworkManager: <WARN>  nm_device_802_11_wireless_scan(): could not trigger wireless scan on device eth1: No such device
...
...
...





daniel@babbelfisken:~$ sudo iwlist scan
[sudo] password for daniel:
lo        Interface doesn't support scanning.

eth0      Interface doesn't support scanning.

eth1      Scan completed :
          Cell 01 - Address: 00:19:5B:01:B5:E5
                    ESSID:"dlink"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
                              11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s
                    Quality=75/100  Signal level=-65 dBm  Noise level=-72 dBm
                    Extra: Last beacon: 208ms ago
          Cell 02 - Address: 00:14:6C:D9:75:5A
                    ESSID:"BABBELFISKEN"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Channel:11
                    Frequency:2.462 GHz (Channel 11)
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 9 Mb/s; 11 Mb/s
                              6 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s





daniel@babbelfisken:~$ ifconfig
  eth0      Link encap:Ethernet  HWaddr 00:03:0D:38:E2:8C 
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::203:dff:fe38:e28c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:879 errors:0 dropped:0 overruns:0 frame:0
          TX packets:457 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:588728 (574.9 KB)  TX bytes:56557 (55.2 KB)
          Interrupt:17 Base address:0x2400

eth1      Link encap:Ethernet  HWaddr 00:14:A5:40:BE:D4 
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:276 overruns:0 frame:0
          TX packets:117 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:7667595 (7.3 MB)
          Interrupt:3 Base address:0x8000

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)
                Quality=89/100  Signal level=-32 dBm  Noise level=-72 dBm
                    IE: WPA Version 1
                        Group Cipher : WEP-40
                        Pairwise Ciphers (1) : WEP-40
                        Authentication Suites (1) : PSK
                    Extra: Last beacon: 112ms ago



daniel@babbelfisken:~$ more /etc/network/interfaces
auto lo
iface lo inet loopback


Hoppas att detta kan hjälpa ngn att förstå vad det är som är knas?
Windows burken kan koppla upp sig mot routern fortfarande så det känns inte som att
jag skall reseta routern..

Alla tankar och funderingar är välkomna..

Danne

SV: Hjälp med uppkoppling till trådlös router

Postat: 18 jan 2008, 16:09
av Lars
Det kanske är fel firmware? Hur fick du tag i de filerna, med bcm43xx-fwcutter?
Alla tidsangivelser är UTC+02:00 UTC+2
Sida 1 av 2

Powered by phpBB® Forum Software © phpBB Limited

Swedish translation by phpBB Sweden © 2006-2015