rt2561/rt61 COMPATIBLE to create wireless access point ???

Live forum: http://rt2x00.serialmonkey.com/viewtopic.php?t=4409

axotolys

04-11-2007 17:20:33

hello,
my question is simple.
I know it's possible to create a wireless access point with a card with chipset atheros > http//www.linux.com/articles/55617
but is it possible to make the same with the ralink card (rt2561/rt61) ??
I installed the driver from ralink website "2007_1003_RT61_Linux_STA_v1.1.1.0.tgz"
> http//www.ralinktech.com/ralink/Home/S ... Linux.html

and if yes, is there some difference or something special to do ?
thanks

axotolys

[code38sh8fz6]root@server:~# cat /etc/lsb-release

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.10
DISTRIB_CODENAME=gutsy
DISTRIB_DESCRIPTION="Ubuntu 7.10"


root@server:~#lspci
00:00.0 Host bridge: Intel Corporation 82815 815 Chipset Host Bridge and Memory Controller Hub (rev 04)
00:01.0 PCI bridge: Intel Corporation 82815 815 Chipset AGP Bridge (rev 04)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 11)
00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 11)
00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 Controller (rev 11)
00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 11)
00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 11)
01:00.0 VGA compatible controller: nVidia Corporation NV36 [GeForce FX 5700LE] (rev a1)
02:01.0 Network controller: RaLink RT2561/RT61 802.11g PCI
02:02.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02)
02:03.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 50)
02:03.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 50)
02:03.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 51)
02:04.0 Ethernet controller: Intel Corporation 82557/8/9 Ethernet Pro 100 (rev 08)
02:05.0 SCSI storage controller: Adaptec AHA-7850 (rev 01)
root@server:~#sudo lshw -C network
*-network:0
description: Wireless interface
product: RT2561/RT61 802.11g PCI
vendor: RaLink
physical id: 1
bus info: pci@0000:02:01.0
logical name: wmaster0
version: 00
serial: 00:08:d3:28:4e:0f
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=rt61pci latency=32 module=rt61pci multicast=yes wireless=IEEE 802.11g
*-network:1
description: Ethernet interface
product: 82557/8/9 Ethernet Pro 100
vendor: Intel Corporation
physical id: 4
bus info: pci@0000:02:04.0
logical name: eth0
version: 08
serial: 00:04:ac:e3:f2:9e
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.17-k4-NAPI duplex=full firmware=N/A ip=192.168.0.161 latency=32 link=yes maxlatency=56 mingnt=8 module=e100 multicast=yes port=MII speed=100MB/s
*-network DISABLED
description: Ethernet interface
physical id: 1
logical name: br0
serial: 00:04:ac:e3:f2:9e
capabilities: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes
root@server:~# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

br0 no wireless extensions.

root@server:~#ifconfig
eth0 Link encap:Ethernet HWaddr 00:04:AC:E3:F2:9E
inet addr:192.168.0.161 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::204:acff:fee3:f29e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4516144 errors:0 dropped:0 overruns:0 frame:0
TX packets:4676329 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3343258882 (3.1 GB) TX bytes:959705203 (915.2 MB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:3680 errors:0 dropped:0 overruns:0 frame:0
TX packets:3680 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:458469 (447.7 KB) TX bytes:458469 (447.7 KB)

wlan0 Link encap:Ethernet HWaddr 00:08:D3:28:4E:0F
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wmaster0 Link encap:UNSPEC HWaddr 00-08-D3-28-4E-0F-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:13:F7:33:66:53
ESSID:"jeremiouch"
Mode:Master
Channel:6
Frequency:2.437 GHz
Signal level=-58 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=0000013c08b2a35b
Cell 02 - Address: 00:19:5B:DF:8F:EC
ESSID:"AppartH"
Mode:Master
Channel:11
Frequency:2.462 GHz
Signal level=-76 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=00000a24335ae273
Cell 03 - Address: 00:1A:2A:9E:4A:51
ESSID:"PPF"
Mode:Master
Channel:3
Frequency:2.422 GHz
Signal level=-76 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:tsf=0000000aa812fbd9

br0 Interface doesn't support scanning.
root@server:~# cat /etc/network/interfaces
#auto lo
#iface lo inet loopback

#iface eth0 inet dhcp

#auto eth0



auto wlan0 br0

iface wlan0 inet manual
pre-up wlanconfig wlan0 destroy
pre-up wlanconfig wlan0 create wlandev wifi0 wlanmode ap
post-down wlanconfig wlan0 destroy
wireless-mode master

iface br0 inet manual
bridge_ports eth0 wlan0

ifconfig >
eth0 Link encap:Ethernet HWaddr 00:04:AC:E3:F2:9E
inet addr:192.168.0.161 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::204:acff:fee3:f29e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4507049 errors:0 dropped:0 overruns:0 frame:0
TX packets:4673714 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3342617398 (3.1 GB) TX bytes:959595369 (915.1 MB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1950 errors:0 dropped:0 overruns:0 frame:0
TX packets:1950 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:227628 (222.2 KB) TX bytes:227628 (222.2 KB)

wlan0 Link encap:Ethernet HWaddr 00:08:D3:28:4E:0F
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wmaster0 Link encap:UNSPEC HWaddr 00-08-D3-28-4E-0F-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
et pour le pont > root@server:~# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.0004ace3f29e no eth0
wlan0

donc le pont à l'air de marcher
ensuite pour la config du hostapd.conf

interface=wlan0
bridge=br0
driver=rx2500.o
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
debug=0
dump_file=/tmp/hostapd.dump
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
ssid=UBUNTUSERVER
#macaddr_acl=1
#accept_mac_file=/etc/hostapd/accept
auth_algs=3
eapol_key_index_workaround=0
eap_server=0
wpa=3
wpa_psk_file=/etc/hostapd/wpa_psk
wpa_key_mgmt=WPA-PSK
wpa_pairwise=CCMP
stakey=0

ensuite démarrage > /etc/init.d/hostapd start
mais > failed[/code38sh8fz6]

Spy84464

10-11-2007 10:43:16

Hello,
There are many things here.
First, we don't support drivers downloaded from ralinktech.com, please use our releases instead.
To answer your question, here is a small outline of existing drivers
"rt61", from Ralink tech website, which we don't support, and cannot run in master mode (what you're looking for).
"rt61", from us, this is an improved version of the above driver, it doesn't support master mode either.
"rt61pci", also known as "rt2x00", from us, a completely new driver written from scratch, which will support master mode the future.
So basically, you cannot use rt61 as an access point yet.

Now, according to the output you provided you are running rt2x00 (NOT Ralink's driver), which is shipped with Ubuntu by default. Take care of using only one driver, you may get into trouble if both rt61 and rt61pci are loaded at the same time.

Regards,
Romain

Vern

10-11-2007 18:47:17

Hi axotolys,

Ralink hardware allows it, but the legacy rt61 driver does not have AP capability.

axotolys

13-11-2007 12:21:28

thanks you very much
but I don't really understand.

[code2b4oaqr2]"Ralink hardware allows it, but the legacy rt61 driver does not have AP capability."[/code2b4oaqr2]
> it's possible but there isn't any driver yet (from Ralink) ?

[code2b4oaqr2]""rt61pci", also known as "rt2x00", from us, a completely new driver written from scratch, which will support master mode the future. "[/code2b4oaqr2]
> it 'll be possible with the "rt61pci" driver that is under development ?

Is that right ?
Axotolys

Spy84464

13-11-2007 19:00:39

> it's possible but there isn't any driver yet (from Ralink) ?[/quote2g6s1y8d]
Yes, but I don't know if Ralink plans to ever release a driver with this feature.

> it 'll be possible with the "rt61pci" driver that is under development ?[/quote2g6s1y8d]
Yes, there are often discussions about this in the rt2x00 section.

buliwoof

28-01-2008 14:25:09

Hi, at this time is somebody succed to make work Ralink rt61 as Acess Point ?

Spy84464

29-01-2008 21:27:34

Maybe, master mode has been enabled again in rt2x00, and should hopefully be working. Check the rt2x00 section for success (or failure) story.