Sumvision SVW322U (rt3072 chipset) ifup will not connect howerer KDE NM does

English Network/Internet
1

Hi Folks,

I have the above mentioned USB Wifi Dongle

Bus 002 Device 003: ID 148f:3072 Ralink Technology, Corp. RT3072 Wireless Adapter

It works extremely well using the KDE network manager but just will not connect using ifup traditional method through yast.

Initially it was using the RT2870 driver but this only gave wirelessg speeds (and still no ifup) but after blacklisting RT2780 and using RT5370sta driver draftn speed was achieved using KDE network manager however I still could not connect through ifup. The dongle scans and sees networks using ifup but will just not connect properly (NB security WPA2-AES).

I’m no wireless dongle guru and if there is anyone out there who knows how to get to the bottom of this one I’d really appreciate a couple of pointers.

Thanks

2

The general rule is that if NetworkManager works and ifup fails, then your ifup
configuration is defective. NM uses the same set of commands and the same driver
to control the interface that ifup does. Only the database is different, and NM
knows how to set that up.

Please post the contents of /etc/sysconfig/network/ifcfg-wlan0. If your device
has a name different than wlan0, then adjust the file name appropriately.

Wireless configuration is not rocket science, but it can be difficult, which is
why software like NM was developed.

3

Hi lwfinger

please find attached as requested with sensitive details *'d out. NB I was trying a couple of different STARTMODE settings and the last is hotplug but still no difference.


BOOTPROTO='dhcp'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR=''
MTU=''
NAME=''
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='hotplug'
USERCONTROL='no'
WIRELESS_AP=''
WIRELESS_AP_SCANMODE='1'
WIRELESS_AUTH_MODE='psk'
WIRELESS_BITRATE=''
WIRELESS_CA_CERT=''
WIRELESS_CHANNEL=''
WIRELESS_CLIENT_CERT=''
WIRELESS_CLIENT_KEY=''
WIRELESS_CLIENT_KEY_PASSWORD=''
WIRELESS_DEFAULT_KEY='0'
WIRELESS_EAP_AUTH=''
WIRELESS_EAP_MODE=''
WIRELESS_ESSID='*****'
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_KEY_0=''
WIRELESS_KEY_1=''
WIRELESS_KEY_2=''
WIRELESS_KEY_3=''
WIRELESS_KEY_LENGTH='128'
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_PEAP_VERSION=''
WIRELESS_POWER='yes'
WIRELESS_WPA_ANONID=''
WIRELESS_WPA_IDENTITY=''
WIRELESS_WPA_PASSWORD=''
WIRELESS_WPA_PSK='********'
4

STARTMODE should not be ‘hotplugged’ if you want to start ifup at boottime. The card should be activated before ifup, so ‘at boottime’ (don’t know the exact english, my Yast is in dutch). Set it in Yast.

5

I think I’m being hit by this issue:

traditional (ifup) and networkmanager problems using KDE 11.4

I have also tested my laptop out which appears to be suffering the same issue (always used NM with 11.4 so never tested ifup until now).

However when changing the eth0 on my laptop to on cable connection, viola a gateway is free for the wireless network card and all is well.

This is poor behaviour from ifup settings in yast, if there is a wlan present then the eth0 should default to this behaviour or at least there should be some release and pass to wlan.

I’ll file a bug report

6

On 09/14/2011 05:16 PM, Dragon32 wrote:
>
> I think I’m being hit by this issue:
>
> ‘traditional (ifup) and networkmanager problems using KDE 11.4’
> (http://tinyurl.com/4l2cnom)
>
> I have also tested my laptop out which appears to be suffering the same
> issue (always used NM with 11.4 so never tested ifup until now).
>
> However when changing the eth0 on my laptop to on cable connection,
> viola a gateway is free for the wireless network card and all is well.
>
> This is poor behaviour from ifup settings in yast, if there is a wlan
> present then the eth0 should default to this behaviour or at least there
> should be some release and pass to wlan.
>
> I’ll file a bug report

I do not think it is a bug. If the wire is connected, networking should use the
wire. If you tell the system to bring up the wired connection when the system is
booted, then the wire is always connected, and the wire should always be used.

As I said before, using ifup is complicated and there are a lot of details to be
kept straight.

7

Bug report submitted.

https://bugzilla.novell.com/show_bug.cgi?id=717933

8

Hi lwfinger,

I can can see where you are coming from but I feel this should be error trapped, networkmanager handles the situation where both ethernet and wireless lan are connected simultaneously. If the user sets up a wireless lan via ifup then just a simple dialogue box pop up or something to make you aware of the gotcha.

Thanks for looking at the issue.

Regards

D32

9

On 09/14/2011 05:56 PM, Dragon32 wrote:
>
> Hi lwfinger,
>
> I can can see where you are coming from but I feel this should be error
> trapped, networkmanager handles the situation where both ethernet and
> wireless lan are connected simultaneously. If the user sets up a
> wireless lan via ifup then just a simple dialogue box pop up or
> something to make you aware of the gotcha.

Did you issue the ifdown for eth0?

10

I’ve set eth0 in ifup to be on cable connect and wlan0 to be on boot and this works perfectly well all the time in respect of wlan0.

11

On 09/15/2011 03:36 AM, Dragon32 wrote:
>
> lwfinger;2384300 Wrote:
>> Did you issue the ifdown for eth0?
>
> I’ve set eth0 in ifup to be on cable connect and wlan0 to be on boot
> and this works perfectly well all the time in respect of wlan0.

I know that will work. The question was “When you had eth0 and wlan0 both set to
connect ‘on-boot’, did you down eth0 before trying to up wlan0?”. That is
essentially what NM does.