Firmware v1.9.2.7 CR4 [Oleg]

[jbrbv]

To share my experiences with you:
On my set of two WL-500g's WDS does work with WPS-PSK and AES (on Channel 11).
Both are in AP mode and one of them is connected to a router.

[Wesleyrpg]

Have to say that bigpond "heartbeat" is 100% stable.

Now if only asus could import olegs fixes into their firmware.

thanks oleg


P.S. In upcoming firmware.....i'd like to see the following things.....i'm sure this isn't the right place to post it....but here it is anyway! Do you think any of these things is likely/possible???

1.. OoB packets support (Currently the WL500g ignores them)
2.. QoS support...im about to get VOIP (so this would be helpful)
3.. UPnP ports never closed bug fixed....annoying and a security hole

[michael]

To share my experiences with you:
On my set of two WL-500g's WDS does work with WPS-PSK and AES (on Channel 11).
Both are in AP mode and one of them is connected to a router.

jbrbv : I'm trying to get the same setup working, and have both my WL-500g's set up as you have said above, but still cant get bridging working - could you please give more information on your wireless settings that you used to getthis to work - my WL-500g's are on v1.9.2.7 CR4 and the other details are in the attached pdf - any help you could give would be very much appreciated

[guch79]

Hey Oleg

I´ve just updated to this new firmware, and i must say it runs more smoothly then the ASUS Unmodded firmware.

I have read thru this thred and i cant find enybody with the same problem as i.

Problem:

I want to upload all my mp3 music to my FTP, so i want to make a subfolder i a folder. There is no problem with making the folder in flash fxp, but when i try to upload enything to the subfolder i get an error.
If i manualy make the folder, there is no problem uploading files to it.

Exampel:
I make a folder path: Psytrance \ -Artist \ -2003-\
And then i try to upload a folder with the album in, and then i fails.
But if i creat the subfolder manualy and then upload the mp3 files to it, there is no problems.

I use a maxtor ide hardrive, with fat 32 format on it.

Would it help if i make it a linux partiton??

Sorry english is not my first language (",) so i hope this makes sense.

-Gustav

[michael]

jbrbv : I'm trying to get the same setup working, and have both my WL-500g's set up as you have said above, but still cant get bridging working - could you please give more information on your wireless settings that you used to getthis to work - my WL-500g's are on v1.9.2.7 CR4 and the other details are in the attached pdf - any help you could give would be very much appreciated

just an update to this - I've tried running the two WL500g's in router mode and AP mode, tried with the same SSID and different SSID's (not that it should matter), tried specifying both WEP and WPA-PSK keys, as well as just WPA-PSK alone, tried setting both WL-500G's to pure WDS more with no AP, but nothing I do gets WDS working over WPA-PSK. I understand that WDS wont work over WPA due to the changing keys, but theres numerous posts here that people have WDS running OK over WPA-PSK, and I just cant get it to work.

Again, if anybody out there has a step by step howto on this it would be very much appreciated, but also if there are any tips on how to debug this that would also be good - I've looked at the wl command but cant get very far with it - for instance : is there some way it can tell me if a WDS connection has been attempted, or to force one?

[jbrbv]

just an update to this - I've tried running the two WL500g's in router mode and AP mode, tried with the same SSID and different SSID's (not that it should matter), tried specifying both WEP and WPA-PSK keys, as well as just WPA-PSK alone, tried setting both WL-500G's to pure WDS more with no AP, but nothing I do gets WDS working over WPA-PSK. I understand that WDS wont work over WPA due to the changing keys, but theres numerous posts here that people have WDS running OK over WPA-PSK, and I just cant get it to work.

Again, if anybody out there has a step by step howto on this it would be very much appreciated, but also if there are any tips on how to debug this that would also be good - I've looked at the wl command but cant get very far with it - for instance : is there some way it can tell me if a WDS connection has been attempted, or to force one?

Michael,

I'm comparing the settings from your PDF with the settings from my WL-500g's directly and post the differences.
First of all, my WL-500g's are in AP mode. Both use DHCP for the IP-addresses. The first Wl-500g is connected hardwired to a router (which is connected to the internet and is acting as DHCP server). The second WL-500g is only connected to the power-mains. Not hardwired to the network. It gets the IP-address by DHCP via the first WL-500g.
At the moment i'm using 1.9.3.6 BETA as it runs smoother in WDS mode than 1.9.2.7 CR4 (= my opinion), both firmwares work in WDS mode!
There are a few things that need to be the same (read i have the same):
- mode
- SSID
- channel
- WPA Pre-Shared Key
- password (and name on the CR4)
- have the settings on wireless-interface and wireless-advanced be the same as much as possible

The differences
On the wireless-interface page:
I have 54g protection checked
I have network Key rotation interval of 86400
The key has a length of nine characters.

In the remote bridge list i have the mac addresses of both the routers. As a minimum you need the mac address of the other WL-500g

In the Access Control List you have the mac address of the other WL-500g. Remove it. Here you only need the MAC addresses of the clients (=PC's, portables, PDA's) if you wish.

In Wireless - Advanced i have Hide SSID on Yes, Enable Frame bursting on Enabled and Radio Power on 38. I don't think these setting do really matter as long as the first two settings are the same on both WL-500g's.

Suc6

[michael]

Michael,

I'm comparing the settings from your PDF with the settings from my WL-500g's directly and post the differences.
First of all, my WL-500g's are in AP mode. Both use DHCP for the IP-addresses. The first Wl-500g is connected hardwired to a router (which is connected to the internet and is acting as DHCP server). The second WL-500g is only connected to the power-mains. Not hardwired to the network. It gets the IP-address by DHCP via the first WL-500g.
At the moment i'm using 1.9.3.6 BETA as it runs smoother in WDS mode than 1.9.2.7 CR4 (= my opinion), both firmwares work in WDS mode!
There are a few things that need to be the same (read i have the same):
- mode
- SSID
- channel
- WPA Pre-Shared Key
- password (and name on the CR4)
- have the settings on wireless-interface and wireless-advanced be the same as much as possible

The differences
On the wireless-interface page:
I have 54g protection checked
I have network Key rotation interval of 86400
The key has a length of nine characters.

In the remote bridge list i have the mac addresses of both the routers. As a minimum you need the mac address of the other WL-500g

In the Access Control List you have the mac address of the other WL-500g. Remove it. Here you only need the MAC addresses of the clients (=PC's, portables, PDA's) if you wish.

In Wireless - Advanced i have Hide SSID on Yes, Enable Frame bursting on Enabled and Radio Power on 38. I don't think these setting do really matter as long as the first two settings are the same on both WL-500g's.

Suc6

many, many thanks - I will review and test these and see if I can get it going

[michael]

many, many thanks - I will review and test these and see if I can get it going

It Works!

the key seems to be when you said:

"In the remote bridge list i have the mac addresses of both the routers."

In all the other combinations I tried, including running WDS over WEP, I've only had the MAC address of the other router... but when I tried putting both MACs in both routers bridge address lists it worked with WPA-PSK/AES. I tried other things in your list as well, but this was the last change I made before it worked.

In summary, I have these things the same on both routers now:

- hostname
- bridge MAC access list
- encryption options
- wireless options

but I still have differing admin passwords for both, and the 26 character AES WPA-PSK I used originally is working on both - I changed it for a shorter key thinking that might be the problem, but happily its not.

Interestingly enough, now that its working, the boot log and the output of "ifconfig -a" shows more lines, and more network interfaces inthe bridge, than it had before. I include them below from one of the units in case it helps anyone else.

Many thanks again for taking the time to help me with this.

================================================== =====
Jan 1 11:00:02 kernel: eth0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.90.7.0
Jan 1 11:00:02 kernel: eth1: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.90.7.0
Jan 1 11:00:02 kernel: PCI: Enabling device 01:02.0 (0004 -> 0006)
Jan 1 11:00:02 kernel: eth2: Broadcom BCM4320 802.11 Wireless Controller 3.90.7.0
Jan 1 11:00:02 kernel: device eth0 entered promiscuous mode
Jan 1 11:00:02 kernel: device eth2 entered promiscuous mode
Jan 1 11:00:02 kernel: device wds0.49153 entered promiscuous mode
Jan 1 11:00:02 kernel: device wds0.49154 entered promiscuous mode
Jan 1 11:00:02 kernel: device eth1 entered promiscuous mode
Jan 1 11:00:02 kernel: br0: port 5(eth1) entering learning state
Jan 1 11:00:03 kernel: ds0.49154) entering learning state
Jan 1 11:00:03 kernel: br0: port 3(wds0.49153) entering learning state
Jan 1 11:00:03 kernel: br0: port 2(eth2) entering learning state
Jan 1 11:00:03 kernel: br0: port 1(eth0) entering learning state
Jan 1 11:00:03 kernel: br0: port 5(eth1) entering forwarding state
Jan 1 11:00:03 kernel: br0: topology change detected, propagating
Jan 1 11:00:03 kernel: br0: port 4(wds0.49154) entering forwarding state
Jan 1 11:00:03 kernel: br0: topology change detected, propagating
Jan 1 11:00:03 kernel: br0: port 3(wds0.49153) entering forwarding state
Jan 1 11:00:03 kernel: br0: topology change detected, propagating
Jan 1 11:00:03 kernel: br0: port 2(eth2) entering forwarding state
Jan 1 11:00:03 kernel: br0: topology change detected, propagating
Jan 1 11:00:03 kernel: br0: port 1(eth0) entering forwarding state
Jan 1 11:00:03 kernel: br0: topology change detected, propagating
================================================== =====
br0 Link encap:Ethernet HWaddr 00:11:2F:4E:74:65
inet addr:10.33.33.3 Bcast:10.33.33.255 Mask:255.255.255.0
inet6 addr: fe80::211:2fff:fe4e:7465/10 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:288 errors:0 dropped:0 overruns:0 frame:0
TX packets:285 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:26498 (25.8 KiB) TX bytes:73831 (72.1 KiB)

eth0 Link encap:Ethernet HWaddr 00:11:2F:4E:74:65
inet6 addr: fe80::211:2fff:fe4e:7465/10 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:5297 (5.1 KiB)
Interrupt:3 Base address:0x2000

eth1 Link encap:Ethernet HWaddr 00:11:2F:4E:74:65
inet6 addr: fe80::211:2fff:fe4e:7465/10 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:5297 (5.1 KiB)
Interrupt:4 Base address:0x8000

eth2 Link encap:Ethernet HWaddr 00:11:2F:4E:74:65
inet6 addr: fe80::211:2fff:fe4e:7465/10 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:546 errors:0 dropped:0 overruns:0 frame:353
TX packets:290 errors:15 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:225456 (220.1 KiB) TX bytes:77117 (75.3 KiB)
Interrupt:6 Base address:0x2000

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 MULTICAST MTU:16436 Metric:1
RX packets:467 errors:0 dropped:0 overruns:0 frame:0
TX packets:467 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:41364 (40.3 KiB) TX bytes:41364 (40.3 KiB)

sit0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:1480 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:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wds0.4915 Link encap:Ethernet HWaddr 00:11:2F:4E:74:65
inet6 addr: fe80::211:2fff:fe4e:7465/10 Scope:Link
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:100
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wds0.4915 Link encap:Ethernet HWaddr 00:11:2F:4E:74:65
inet6 addr: fe80::211:2fff:fe4e:7465/10 Scope:Link
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:100
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
================================================== =====