Bug 9388 – Trouble staying connected to WiFi (WRT610N router)

Bug 9388 - Trouble staying connected to WiFi (WRT610N router)

Summary:

Trouble staying connected to WiFi (WRT610N router)

Status:	RESOLVED WORKSFORME

Product:	SB Controller
Classification:	Unclassified
Component:	Setup
Version:	unspecified
Platform:	PC Other

Importance:	-- major (vote)
Target Milestone:	7.3
Assigned To:	Ross Levine

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-09-03 16:30 UTC by Dan Evans
Modified:	2009-01-07 15:02 UTC (History)
CC List:	4 users (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dan Evans 2008-09-03 16:30:16 UTC

We've gotten a couple reports (that I know of) of people claiming that their Duet connects fine to this their WRT610N router, but it frequently disconnects unexpectedly... sometimes 30 mins later, sometimes 1 day later.

Truthfully, I've heard this report A LOT, and I suspect it extends beyond this particular router model.

Comment 1 Richard Titmuss 2008-09-04 00:29:02 UTC

Dan, are you sure the Controller disconnects from the WiFi, or is it a problem with the SN/SC connection. You need to confirm what color the wireless icon is, and get the information from the Settings > Advanced > Wireless Network > <Network Name> menu. In particular the State, Encryption, IP Address and SNR fields would be useful.

Also please try with wireless lan power saving disabled. Does that help?

Comment 2 Ross Levine 2008-09-24 18:45:38 UTC

I connected 3 Duet's to our WRT610N and no disconnects over 8 days. Ping Dan.

Comment 3 Ross Levine 2008-11-03 16:09:32 UTC

Please include Right Now incident numbers going forward. We've beat on this router and not seen any sort of connection issue in setup or afterward.

Comment 4 Walker LaRon 2009-01-07 15:02:51 UTC

081217-004145

Customer is having same issue.

I am sending all valid questions to place information into this bug once I receive the answers

Thanks,

LaRon