Sitecom WL-115 ( Ralink RT2500 ) does not work with network-manager

Bug #95828 reported by mcgyver
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Incomplete
Undecided
Brian Murray

Bug Description

After starting up I get this message In Ubuntu Feisty:

" Network service discovery disabled.

Your current network has a .local domain which is not recommended and incompatible with the avahi network service discovery. The service has been disabled. "

I think I reported this problem earlier but did not get any reaction. I would like to know what to do to correct this problem. In Dapper and Edgy this pci card had an excellent performance.

ProblemType: Bug
Architecture: i386
Date: Sun Mar 25 11:06:38 2007
DistroRelease: Ubuntu 7.04
Uname: Linux Lubuntu 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 i686 GNU/Linux

mcgyver (lucien-midete)
description: updated
mcgyver (lucien-midete)
description: updated
Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. That error message is not about the functionality of your network card but rather about the avahi service. Is your network card not functioning? Thanks in advance.

Revision history for this message
mcgyver (lucien-midete) wrote : Re: [Bug 95828] Re: Sitecom WL-115 ( Ralink RT2500 ) does not work with network-manager

Hi Brian,

No my card is not working. However, it did work fine in Edgy. Although
network manager sees my card, it is not able to go online.

Thanks for your reply,

Lucien Gesser

Op woensdag 04-04-2007 om 00:01 uur [tijdzone +0000], schreef Brian
Murray:
> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. That error message is not about the functionality of your
> network card but rather about the avahi service. Is your network card
> not functioning? Thanks in advance.
>
> ** Changed in: Ubuntu
> Assignee: (unassigned) => Brian Murray
> Status: Unconfirmed => Needs Info
>

Revision history for this message
Brian Murray (brian-murray) wrote :

Could you please post the contents of your '/etc/network/interfaces' file? Thanks again.

Revision history for this message
mcgyver (lucien-midete) wrote :

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface

iface eth0 inet dhcp

auto eth0

Revision history for this message
wilderness wanderer (jdmfilter-spam) wrote :

Same problem here. rt2500 pci card worked fine under Edgy. Upgraded via alt CD and no network. Numerous attempts at getting network manager to sort it out failed. I uninstalled network manager and it still will not connect via the Gnome network GUI. Note that this is with WEP encryption.

I _am_ able to connect via the command line:

sudo ifconfig ra0 down
sudo iwconfig ra0 essid blahblahblah key hexblahblah
sudo dhclient ra0

I found this at https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/37120

Syntax to manually configure in /etc/network/interfaces

iface ra0 inet dhcp
        pre-up ifconfig ra0 up
        pre-up ifconfig ra0 down
        pre-up ifconfig ra0 up
        pre-up ifconfig ra0 down
        pre-up iwconfig ra0 essid "MyRouterName"
        pre-up iwconfig ra0 mode Managed
        pre-up iwpriv ra0 set AuthMode=WPAPSK
        pre-up iwpriv ra0 set EncrypType=TKIP
        pre-up iwpriv ra0 set WPAPSK="MySecretPassword
        pre-up ifconfig ra0 up
auto ra0

Since I am only using WEP, modified to:

iface ra0 inet dhcp
        pre-up ifconfig ra0 up
        pre-up ifconfig ra0 down
        pre-up ifconfig ra0 up
        pre-up ifconfig ra0 down
        pre-up iwconfig ra0 essid "MyRouterName"
        pre-up iwconfig ra0 key "MyKeyInHex"
        pre-up iwconfig ra0 mode Managed
        pre-up ifconfig ra0 up
auto ra0

Now I have wireless connectivity which survives a reboot.

See also bugs 107555 and 78037

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.