Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[funchords]

I'm thinking Fixed channel is what's fixing it.   

As an experiment, I'll put mine back in auto and see what happens over the next day or two.

[twk3]

Hmm, I already know moving to wireless g only mode reduces my restarts. (And I'm already on fixed chan)

I also decided to see what if those authentications were actually effecting my network. I started pinging my router, and I get a timeout a couple times a minute. So the WPA seems to be having some fun with my network.

I'm getting this authentication/deauthentication problem with all devices on my network. I agree with netdevil, I don't think my phone is the cause.

My new test will be using WPA1, see what happens.

EDIT: The first thing I tried was to use WPA2 only, (AES). Both this and the TKIP for WPA2 left my devices unable to connect. (must not be able to use WPA2)

I am currently trying WPA only with AES


EDIT2: No longer having auth/deauth issues. Internet browsing load times have noticably decreased on image intense sites. The other thing I did was change the Group Key Update Interval to be a full day.

Too soon to tell if this will also fix my restart issues, but my log file is sure getting smaller and easier to read.

[funchords]

If you want to experiment between WPA/WPA2 (or WEP or None), after making that change on your DIR-655 (or any AP), then go to your wireless devices, wipe out their saved settings for your access point, reboot the wireless device, and then associate like you would with a brand-new access point. 

This advice cannot hurt, since it doesn't do anything but match the current settings at worst.  However, it won't help you connect a WPA-only or a TKIP-only network device to a WPA2-only network.

If this helps, it's because after you changed the DIR-655, the wireless device remembered the previous connection and security parameters which were no longer valid.  Following that process creates and saves a new, clean, correct set of parameters reflecting the recent change you made to your wireless network.

Note: If you do have trouble connecting up to a WPA and/or WPA2 network with these steps, its possibly because the AP has the wireless device in an 802.1X lockout or blacklist, earned by too many prior authentication failures.  To clear the lockout, repeat the above steps and remove power/restore power to the Access Point right after you reboot the wireless device.  If you don't have access to the AP's power, then leaving the affected device offline for a little over an hour or two should also expire the lockout (that's a guess, I don't know where D-Link's thresholds are set).

[twk3]

Aye, my laptop cannot connect when set to WPA2 only mode. But it can in WPA only mode. If I put it into both mode, I can connect, but my devices deauthenticate and reauthenticate every few minutes.


I also haven't fixed my wireless restart. I just got another one now, the difference this time, is that with the current settings it only happens once. Previous restarts often restarted several times back to back before any devices were authenticated.

[funchords]

Okay, to be clear --

If you're in WPA/WPA2 mode, and you've wiped out your computer's saved settings for your access point, rebooted the computer and router, and then associated like you would with a brand-new access point, you still get the authentication/deauthentication cycle? 

Which wireless NIC do you have? Are you on the latest drivers and OS updates?

[twk3]

I have an atheros super G card on a toshiba laptop. Running Windows XP SP3.

When I first got the router, I could only connect while it was open or in WEP and not in any mode that included n (including mixed modes). I updated the card firmware to the most recent, that was about a month ago. Then I was able to connect to the router while it was in WPA and while in a mixed mode with n.

And yes, after completely clearing wifi profiles for the wifi on the laptop, and resetting the router, I still get auth/deauth events as soon as I switch into WPA2 + WPA and no connection when using just WPA2. I get these events from the laptop, and from my blackberry. I have not seen a deauth on my wii though, yet. But it's not always on.

From the first day that I got my laptop working on the network, I have been seeing log events every 30sec-2min. I wasn't seeing a performance hit, so I just thought it was normal.

Now that I'm using WPA only, I'm only seeing log events every 30min - 1hr.. and they're just ICMP 8 packets being blocked, or transmission sequence errors.

[funchords]

Interesting, thanks!

[netdevil]

OK - mine works better but still not good. Yesterday my wife's laptop disconnected and would not log back on even after several reboots. I had to reboot the router, only then would the laptop be able to log back on - only to be immediately disconnected again. Another attempt to register in the network and it worked again. Here's the log from Ubuntu 7.10 - the router does NOT log any useful data...!

Code: [Select]

Dec 12 13:33:03 wika-laptop kernel: [ 9582.272000] wlan0: Initial auth_alg=0
Dec 12 13:33:03 wika-laptop kernel: [ 9582.272000] wlan0: authenticate with AP XX:XX:XX:XX:XX:XX
Dec 12 13:33:03 wika-laptop kernel: [ 9582.472000] wlan0: authenticate with AP XX:XX:XX:XX:XX:XX
Dec 12 13:33:03 wika-laptop kernel: [ 9582.672000] wlan0: authenticate with AP XX:XX:XX:XX:XX:XX
Dec 12 13:33:04 wika-laptop kernel: [ 9582.872000] wlan0: authentication with AP XX:XX:XX:XX:XX:XX timed out
Dec 12 13:33:05 wika-laptop kernel: [ 9583.872000] wlan0: RX WEP frame with unknown keyidx 2 (A1=ff:ff:ff:ff:ff:ff A2=XX:XX:XX:XX:XX:XX A3=XX:XX:XX:XX:XX:XX)
Dec 12 13:33:08 wika-laptop NetworkManager: <info>  Old device 'wlan0' activating, won't change.
Dec 12 13:33:17 wika-laptop kernel: [ 9595.868000] wlan0: RX WEP frame with unknown keyidx 2 (A1=ff:ff:ff:ff:ff:ff A2=XX:XX:XX:XX:XX:XX A3=XX:XX:XX:XX:XX:XX)
Dec 12 13:33:19 wika-laptop kernel: [ 9597.868000] wlan0: RX WEP frame with unknown keyidx 2 (A1=ff:ff:ff:ff:ff:ff A2=XX:XX:XX:XX:XX:XX A3=XX:XX:XX:XX:XX:XX)
Dec 12 13:33:19 wika-laptop NetworkManager: <info>  Old device 'wlan0' activating, won't change.
Dec 12 13:33:30 wika-laptop last message repeated 2 times
Dec 12 13:33:33 wika-laptop kernel: [ 9611.860000] wlan0: RX WEP frame with unknown keyidx 2 (A1=ff:ff:ff:ff:ff:ff A2=XX:XX:XX:XX:XX:XX A3=XX:XX:XX:XX:XX:XX)
Dec 12 13:33:34 wika-laptop NetworkManager: <info>  Activation (wlan0/wireless): association took too long (>60s), failing activation.
Dec 12 13:33:34 wika-laptop NetworkManager: <info>  Activation (wlan0) failure scheduled...
Dec 12 13:33:34 wika-laptop NetworkManager: <info>  Activation (wlan0) failed for access point (KeinZugangFuerFremde)
Dec 12 13:33:34 wika-laptop NetworkManager: <info>  Activation (wlan0) failed.
Dec 12 13:33:34 wika-laptop NetworkManager: <info>  Deactivating device wlan0.


[.... NEXT DAY .... The same. After rebooting the router the following appeared:]



Dec 13 09:38:49 wika-laptop NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Dec 13 09:38:50 wika-laptop kernel: [ 2413.800000] wlan0: Initial auth_alg=0
Dec 13 09:38:50 wika-laptop kernel: [ 2413.800000] wlan0: authenticate with AP XX:XX:XX:XX:XX:XX
Dec 13 09:38:50 wika-laptop kernel: [ 2413.800000] wlan0: RX authentication from XX:XX:XX:XX:XX:XX (alg=0 transaction=2 status=0)
Dec 13 09:38:50 wika-laptop kernel: [ 2413.800000] wlan0: authenticated
Dec 13 09:38:50 wika-laptop kernel: [ 2413.800000] wlan0: associate with AP XX:XX:XX:XX:XX:XX
Dec 13 09:38:50 wika-laptop kernel: [ 2413.804000] wlan0: RX AssocResp from XX:XX:XX:XX:XX:XX (capab=0x431 status=0 aid=1)
Dec 13 09:38:50 wika-laptop kernel: [ 2413.804000] wlan0: associated
Dec 13 09:38:50 wika-laptop kernel: [ 2413.804000] wlan0: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0
Dec 13 09:38:50 wika-laptop kernel: [ 2413.804000] wlan0: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0
Dec 13 09:38:50 wika-laptop kernel: [ 2413.804000] wlan0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30
Dec 13 09:38:50 wika-laptop kernel: [ 2413.804000] wlan0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15
Dec 13 09:38:50 wika-laptop kernel: [ 2413.808000] wlan0: association frame received from XX:XX:XX:XX:XX:XX, but not in associate state - ignored
Dec 13 09:38:50 wika-laptop kernel: [ 2413.880000] wlan0: RX WEP frame with unknown keyidx 1 (A1=ff:ff:ff:ff:ff:ff A2=XX:XX:XX:XX:XX:XX A3=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:50 wika-laptop kernel: [ 2414.032000] wlan0: CTS protection enabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:50 wika-laptop kernel: [ 2414.132000] wlan0: CTS protection disabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:50 wika-laptop kernel: [ 2414.236000] wlan0: CTS protection enabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:51 wika-laptop kernel: [ 2414.876000] wlan0: RX WEP frame with unknown keyidx 1 (A1=ff:ff:ff:ff:ff:ff A2=XX:XX:XX:XX:XX:XX A3=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:51 wika-laptop kernel: [ 2415.260000] wlan0: CTS protection disabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:51 wika-laptop NetworkManager: <debug> [1229186331.962856] nm_device_802_11_wireless_update_bssid(): Roamed from BSSID 00:00:00:00:00:00 to XX:XX:XX:XX:XX:XX on wireless network 'XXXXXXXX'
Dec 13 09:38:52 wika-laptop kernel: [ 2415.464000] wlan0: CTS protection enabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:52 wika-laptop NetworkManager: <debug> [1229186332.042796] nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless network 'KeinZugangFuerFremde'
Dec 13 09:38:52 wika-laptop NetworkManager: <info>  Old device 'wlan0' activating, won't change.
Dec 13 09:38:52 wika-laptop kernel: [ 2415.876000] wlan0: RX WEP frame with unknown keyidx 1 (A1=ff:ff:ff:ff:ff:ff A2=XX:XX:XX:XX:XX:XX A3=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:53 wika-laptop kernel: [ 2416.828000] wlan0: RX WEP frame with unknown keyidx 0 (A1=00:14:85:df:74:54 A2=XX:XX:XX:XX:XX:XX A3=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:54 wika-laptop kernel: [ 2418.132000] wlan0: CTS protection disabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:54 wika-laptop kernel: [ 2418.432000] wlan0: CTS protection enabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:55 wika-laptop NetworkManager: <info>  Old device 'wlan0' activating, won't change.
Dec 13 09:38:56 wika-laptop NetworkManager: <info>  Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to access point 'KeinZugangFuerFremde'.
Dec 13 09:38:56 wika-laptop NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Dec 13 09:38:56 wika-laptop NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Dec 13 09:38:57 wika-laptop NetworkManager: <info>  Activation (wlan0) Beginning DHCP transaction.
Dec 13 09:38:57 wika-laptop NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Dec 13 09:38:57 wika-laptop NetworkManager: <info>  DHCP daemon state is now 12 (successfully started) for interface wlan0
Dec 13 09:38:57 wika-laptop dhclient: wmaster0: unknown hardware address type 801
Dec 13 09:38:57 wika-laptop kernel: [ 2421.096000] wlan0: CTS protection disabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:58 wika-laptop kernel: [ 2421.504000] wlan0: CTS protection enabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:38:58 wika-laptop NetworkManager: <info>  DHCP daemon state is now 1 (starting) for interface wlan0
Dec 13 09:38:58 wika-laptop dhclient: wmaster0: unknown hardware address type 801
Dec 13 09:38:59 wika-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Dec 13 09:39:00 wika-laptop kernel: [ 2424.168000] wlan0: CTS protection disabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:39:00 wika-laptop kernel: [ 2424.268000] wlan0: CTS protection enabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:39:02 wika-laptop kernel: [ 2426.112000] wlan0: CTS protection disabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:39:06 wika-laptop kernel: [ 2430.108000] printk: 1 messages suppressed.
Dec 13 09:39:06 wika-laptop kernel: [ 2430.108000] wlan0: CTS protection disabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:39:07 wika-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
Dec 13 09:39:07 wika-laptop dhclient: DHCPOFFER from 192.168.0.1
Dec 13 09:39:07 wika-laptop dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Dec 13 09:39:11 wika-laptop kernel: [ 2435.124000] printk: 1 messages suppressed.
Dec 13 09:39:11 wika-laptop kernel: [ 2435.124000] wlan0: CTS protection disabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:39:13 wika-laptop dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Dec 13 09:39:16 wika-laptop kernel: [ 2440.140000] printk: 1 messages suppressed.
Dec 13 09:39:16 wika-laptop kernel: [ 2440.140000] wlan0: CTS protection disabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:39:24 wika-laptop kernel: [ 2448.128000] printk: 3 messages suppressed.
Dec 13 09:39:24 wika-laptop kernel: [ 2448.128000] wlan0: CTS protection disabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:39:25 wika-laptop kernel: [ 2449.152000] printk: 1 messages suppressed.
Dec 13 09:39:25 wika-laptop kernel: [ 2449.152000] wlan0: CTS protection disabled (BSSID=XX:XX:XX:XX:XX:XX)
Dec 13 09:39:28 wika-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Dec 13 09:39:28 wika-laptop dhclient: DHCPOFFER from 192.168.0.1
Dec 13 09:39:28 wika-laptop dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Dec 13 09:39:28 wika-laptop dhclient: DHCPACK from 192.168.0.1
Dec 13 09:39:28 wika-laptop avahi-daemon[4761]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.197.
Dec 13 09:39:28 wika-laptop avahi-daemon[4761]: New relevant interface wlan0.IPv4 for mDNS.
Dec 13 09:39:28 wika-laptop avahi-daemon[4761]: Registering new address record for 192.168.0.197 on wlan0.IPv4.
Dec 13 09:39:28 wika-laptop NetworkManager: <info>  DHCP daemon state is now 2 (bound) for interface wlan0
Dec 13 09:39:28 wika-laptop NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled...
Dec 13 09:39:28 wika-laptop NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get) started...
Dec 13 09:39:28 wika-laptop dhclient: bound to 192.168.0.197 -- renewal in 38570 seconds.
Dec 13 09:39:28 wika-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.host_name
Dec 13 09:39:28 wika-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_domain
Dec 13 09:39:28 wika-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_servers
Dec 13 09:39:28 wika-laptop NetworkManager: <info>  Retrieved the following IP4 configuration from the DHCP daemon:
Dec 13 09:39:28 wika-laptop NetworkManager: <info>    address 192.168.0.197
Dec 13 09:39:28 wika-laptop NetworkManager: <info>    netmask 255.255.255.0
Dec 13 09:39:28 wika-laptop NetworkManager: <info>    broadcast 192.168.0.255
Dec 13 09:39:28 wika-laptop NetworkManager: <info>    gateway 192.168.0.1
Dec 13 09:39:28 wika-laptop NetworkManager: <info>    nameserver 192.168.0.1
Dec 13 09:39:28 wika-laptop NetworkManager: <info>    domain name 'XX.XXXXXXXX.net'
Dec 13 09:39:28 wika-laptop NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Dec 13 09:39:28 wika-laptop NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete.
Dec 13 09:39:28 wika-laptop NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Dec 13 09:39:28 wika-laptop avahi-daemon[4761]: Withdrawing address record for 192.168.0.197 on wlan0.
Dec 13 09:39:28 wika-laptop avahi-daemon[4761]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.197.
Dec 13 09:39:28 wika-laptop avahi-daemon[4761]: Interface wlan0.IPv4 no longer relevant for mDNS.
Dec 13 09:39:28 wika-laptop avahi-daemon[4761]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.197.
Dec 13 09:39:28 wika-laptop avahi-daemon[4761]: New relevant interface wlan0.IPv4 for mDNS.
Dec 13 09:39:28 wika-laptop avahi-daemon[4761]: Registering new address record for 192.168.0.197 on wlan0.IPv4.
Dec 13 09:39:29 wika-laptop NetworkManager: <info>  Clearing nscd hosts cache.
Dec 13 09:39:29 wika-laptop 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)) 
Dec 13 09:39:29 wika-laptop NetworkManager: <info>  Activation (wlan0) successful, device activated.
Dec 13 09:39:29 wika-laptop NetworkManager: <debug> [1229186369.699975] nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless network 'XXXXXXXXXXXXXXXXXXXXXXXXXXXX'
Dec 13 09:39:29 wika-laptop NetworkManager: <info>  SWITCH: terminating current connection 'wlan0' because it's no longer valid.
Dec 13 09:39:29 wika-laptop NetworkManager: <info>  Deactivating device wlan0.
Dec 13 09:39:29 wika-laptop dhclient: There is already a pid file /var/run/dhclient.wlan0.pid with pid 6006
Dec 13 09:39:29 wika-laptop dhclient: killed old client process, removed PID file
Dec 13 09:39:29 wika-laptop dhclient: wmaster0: unknown hardware address type 801
Dec 13 09:39:29 wika-laptop dhclient: wmaster0: unknown hardware address type 801
Dec 13 09:39:29 wika-laptop NetworkManager: <info>  Activation (wlan0) Finish handler scheduled.
Dec 13 09:39:29 wika-laptop NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Dec 13 09:39:29 wika-laptop dhclient: DHCPRELEASE on wlan0 to 192.168.0.1 port 67
Dec 13 09:39:29 wika-laptop avahi-daemon[4761]: Withdrawing address record for 192.168.0.197 on wlan0.
Dec 13 09:39:29 wika-laptop avahi-daemon[4761]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.197.
Dec 13 09:39:29 wika-laptop avahi-daemon[4761]: Interface wlan0.IPv4 no longer relevant for mDNS.
Dec 13 09:39:29 wika-laptop kernel: [ 2453.356000] NET: Registered protocol family 10
Dec 13 09:39:29 wika-laptop kernel: [ 2453.356000] lo: Disabled Privacy Extensions
Dec 13 09:39:29 wika-laptop kernel: [ 2453.356000] ADDRCONF(NETDEV_UP): eth0: link is not ready
Dec 13 09:39:29 wika-laptop ntpdate[6077]: can't find host ntp.ubuntu.com
Dec 13 09:39:29 wika-laptop ntpdate[6077]: no servers can be used, exiting
Dec 13 09:39:30 wika-laptop NetworkManager: nm_device_is_802_3_ethernet: assertion `dev != NULL' failed
Dec 13 09:39:30 wika-laptop NetworkManager: nm_device_is_802_11_wireless: assertion `dev != NULL' failed
Dec 13 09:39:30 wika-laptop kernel: [ 2454.180000] wlan0: deauthenticate(reason=3)
As mentioned above, after that I registered again and it connected me.

Maybe that gives any clues?

[twk3]

Looks to me like there is something wrong with your connection manager. For one, it lies:

Dec 12 13:33:34 wika-laptop NetworkManager: <info>  Activation (wlan0/wireless): association took too long (>60s), failing activation.

^ Based on the times, network manager did not wait 60 seconds, and for authentication, network manager didn't even wait a single second before timing out. I don't think this is your problem though.

Dec 13 09:39:29 wika-laptop 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))

^ Do you have nscd installed? This shouldn't be your problem either, but it is something to check out.


Basically, I'm not smart enough to figure it out, based on those logs. One thing I would try if I were you, would be to try and use http://wicd.sourceforge.net/ instead of network manager, and see if you get the same problem.

[funchords]

OK - mine works better but still not good. Yesterday my wife's laptop disconnected and would not log back on even after several reboots. I had to reboot the router, only then would the laptop be able to log back on - only to be immediately disconnected again. Another attempt to register in the network and it worked again. Here's the log from Ubuntu 7.10 - the router does NOT log any useful data..

That's lockout behavior. Was this network WPA/WPA2 at some point and is now WEP?

[netdevil]

@twk3 - Thanks, I'll take a look at that.

@funchords: No, it's still WPA only which seems to work more stable. Haven't tried WEP yet.

I am not sure what this is. Sometimes it kicks her out of a Skype session and she'll be locked out if that's what it is.

Right now I am just waiting for OpenSuse11.1 to be available for download then I'll install that and see if it's getting any better (wanted to switch to Ubuntu 8.04 which ran fine as a LiveCD but the installation would always crash when it started to write files to the harddisk  ).

EDIT: OK, I installed WICD and the connection rate is much better, can't really say all too much about stability so far. What I noticed, however, is that my logs are filling up with 'CTS Protection enabled/disabled' messages like crazy (every 1-3 sec) and something about a 'printk message suppressed.'  I guess for more detailed analyses I'll wait for the new OpenSuse-installation.

Edit2: Still getting errors and the connection disconnects after a while (WICD reports its still up but nothing gets transferred; router log does not report anything; system log reports an error, which I will post later). For some reason I still think that the router is involved in this somehow...

[twk3]

I have been connected with fedora 8 all this week, and the restarts have still been occuring. Just eliminates my software on windows from being the cause. Though, as far as I can tell, it seems to restart when nothing is connected as well.

Whether it's the router, my laptop wireless card, or my blackberry... I still don't know.

[funchords]

I have been connected with fedora 8 all this week, and the restarts have still been occuring. Just eliminates my software on windows from being the cause. Though, as far as I can tell, it seems to restart when nothing is connected as well.

And that's still on fixed channel 1?  Have you tried 11?

[Rimtech]

I made these changes yesterday as per D-Link tech support and I havent had a wireless restart yet, and it's been almost a full 24 hours
>Make sure UPnP and Muticast streaming are disabled.
>Change wireless channel to 10
>Change beacon period to 80
>Change RTS threshold to 2100
>Change Fragmentation threshold to 2100
>Change DTIM interval to 5

[EddieZ]

Try reflashing the firmware.