Ubuntu 10.4 fails to connect to linksys range expander WRE54 3.0

Bug #593377 reported by Eduardo Fracassi
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hi,

I installed ubuntu on my sister's machines runnng a wireless lan based on linksys WRTG54 and a linksys WRE54 range expander version 3.0.

In windows xp we are able to connect to the range expander receiving a 100% quality signal.

But when trying to connect to the range expander with ubuntu 10.4 , after specifying the range expander's MAC, ubuntu tries to connect to the range expander but fails and after some minutes creates a connection and connects to the router at 192.168.1.1.

BUG: Ubuntu 10.4 fails to connect to the range expander (100 % signal at that range). Ubuntu will only connect to the router (35-40 % signal at that range).

best,
Eduardo
---
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 10.04
IfupdownConfig:
 auto lo
 iface lo inet loopback
IpRoute:
 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.102 metric 2
 169.254.0.0/16 dev wlan0 scope link metric 1000
 default via 192.168.1.1 dev wlan0 proto static
Keyfiles: Error: [Errno 2] No such file or directory
NonfreeKernelModules: nvidia
Package: network-manager 0.8-0ubuntu3
PackageArchitecture: i386
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: lucid
Uname: Linux 2.6.32-22-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WpaSupplicantLog:

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't start working on it yet, because your bug report didn't include enough information.

Please include the information requested at https://wiki.ubuntu.com/DebuggingNetworkManager (capture log), and the entire files /var/log/syslog and /var/log/dmesg.

 If you have trouble, do not hesitate to ask for more assistance. Thanks in advance.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Or if you prefere open a terminal and type
apport-collect 593377

Revision history for this message
Eduardo Fracassi (eduardo-fracassi) wrote :

Hi Fabio,

thanks for helping with this bug. I run the

apport-collect 593377

command that you suggested and I hope it collected the necessary information.

I hope ti helps,

Eduardo

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Sorry i've made an error.
Can you please run in a terminal

apport-collect -p network-manager 593377

and attach too the files:

/var/log/syslog
/var/log/dmesg

Thanks in advance.

affects: ubuntu → network-manager (Ubuntu)
Revision history for this message
Eduardo Fracassi (eduardo-fracassi) wrote : Dependencies.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Eduardo Fracassi (eduardo-fracassi) wrote : Gconf.txt

apport information

Revision history for this message
Eduardo Fracassi (eduardo-fracassi) wrote : IpAddr.txt

apport information

Revision history for this message
Eduardo Fracassi (eduardo-fracassi) wrote : IwConfig.txt

apport information

Revision history for this message
Eduardo Fracassi (eduardo-fracassi) wrote : NetDevice.eth0.txt

apport information

Revision history for this message
Eduardo Fracassi (eduardo-fracassi) wrote : NetDevice.lo.txt

apport information

Revision history for this message
Eduardo Fracassi (eduardo-fracassi) wrote : NetDevice.wlan0.txt

apport information

Revision history for this message
Eduardo Fracassi (eduardo-fracassi) wrote : PciNetwork.txt

apport information

Revision history for this message
Eduardo Fracassi (eduardo-fracassi) wrote : WifiSyslog.txt

apport information

Revision history for this message
Eduardo Fracassi (eduardo-fracassi) wrote : nm-system-settings.conf.txt

apport information

Revision history for this message
Eduardo Fracassi (eduardo-fracassi) wrote : Re: [Bug 593377] Re: Ubuntu 10.4 fails to connect to linksys range expander WRE54 3.0
  • syslog Edit (2.8 KiB, application/octet-stream; name=syslog)
  • dmesg Edit (37.0 KiB, application/octet-stream; name=dmesg)

Hi Fabio,

I run the command and also send you both attached both files.

Sorry for the delay but I go to my sister's house once a week.

I hope it helps,

Eduardo

On Wed, Jul 21, 2010 at 4:26 PM, Fabio Marconi <email address hidden>wrote:

> Sorry i've made an error.
> Can you please run in a terminal
>
> apport-collect -p network-manager 593377
>
> and attach too the files:
>
> /var/log/syslog
> /var/log/dmesg
>
> Thanks in advance.
>
> --
> Ubuntu 10.4 fails to connect to linksys range expander WRE54 3.0
> https://bugs.launchpad.net/bugs/593377
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: Incomplete
>
> Bug description:
> Hi,
>
> I installed ubuntu on my sister's machines runnng a wireless lan based on
> linksys WRTG54 and a linksys WRE54 range expander version 3.0.
>
> In windows xp we are able to connect to the range expander receiving a 100%
> quality signal.
>
> But when trying to connect to the range expander with ubuntu 10.4 , after
> specifying the range expander's MAC, ubuntu tries to connect to the range
> expander but fails and after some minutes creates a connection and connects
> to the router at 192.168.1.1.
>
> BUG: Ubuntu 10.4 fails to connect to the range expander (100 % signal at
> that range). Ubuntu will only connect to the router (35-40 % signal at that
> range).
>
> best,
> Eduardo
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+bug/593377/+subscribe
>

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

requested packages are attached I mark as confirmed.
:)Fabio

Changed in network-manager (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Mohamed Amine Ilidrissi (ilidrissi.amine) wrote :

Bugs should not be marked "Confirmed" until someone else other than the bug reporter experiences the same issue.

Changed in network-manager (Ubuntu):
status: Confirmed → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.