Firmware v1.9.2.7 CR4 [Oleg]

[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)
================================================== =====

[Oleg]

I could not find anything about WPA-PSK and AES+TKIP.

Did i overlooked something?

Ok, I had an impression, that we've added it to the Known Bugs. It appears, that it's missing, sorry.
Anyway, AES+TKIP option does not work with 1.9.2.7. Antiloop, am I right?

[Antiloop]

Ok, I had an impression, that we've added it to the Known Bugs. It appears, that it's missing, sorry.
Anyway, AES+TKIP option does not work with 1.9.2.7. Antiloop, am I right?

uhm..

WPA-PSK with TKIP+AES should work fine,
WDS or HYBRID MUST be disabled, also client mode does not work afaik

[nOBeLium]

Apart from the wi-fi problem, my router resets very 5 minutes or such..can I go back to a 1.8.x.x firmware? If yes, please give me a link since I can't find it on home page. Thanks,

[GJAman]

Apart from the wi-fi problem, my router resets very 5 minutes or such..can I go back to a 1.8.x.x firmware? If yes, please give me a link since I can't find it on home page. Thanks,

http://oleg.wl500g.info/1.8.1.7-3/

[nOBeLium]

Thanks! Going to downgrade it and will post results (if it fixed current problems I'm experiencing with this firmware).

[jbrbv]

uhm..

WPA-PSK with TKIP+AES should work fine,
WDS or HYBRID MUST be disabled, also client mode does not work afaik

Oleg,
Is it possible to get WPA-PSK and both AES+TKIP encryptions to work under WDS?

[Oleg]

Oleg,
Is it possible to get WPA-PSK and both AES+TKIP encryptions to work under WDS?

I've no idea, probably Antiloop tested this. If it does not work, then probably driver is buggy...

[Antiloop]

Oleg,
Is it possible to get WPA-PSK and both AES+TKIP encryptions to work under WDS?

it has been a while ago, and still waiting for some testunits to arrive

but afaik it is impossible to use WPA-PSK AES+TKIP and WDS

I believe it should work either with AES or TKIP but not at the same time

WDS + WPA-PSK AES is not working with current firmware
and for TKIP i'm not 100% sure anymore now if it did work or not..

you can test this easily, only thing you should change is to use WEP if it starts working then the combination does not work (when using firmware 1.8.1.7-3 for example this should work fine)

[jbrbv]

it has been a while ago, and still waiting for some testunits to arrive

but afaik it is impossible to use WPA-PSK AES+TKIP and WDS

I believe it should work either with AES or TKIP but not at the same time

WDS + WPA-PSK AES is not working with current firmware
and for TKIP i'm not 100% sure anymore now if it did work or not..

you can test this easily, only thing you should change is to use WEP if it starts working then the combination does not work (when using firmware 1.8.1.7-3 for example this should work fine)

Please read the report of Michael. Het got his WDS setup working with WPA-PSK and AES. My setup has been working with WPA-PSK and AES. I'm now using 1.9.3.6 and [WDS] WPA-PSK with AES is working fine.

[iog]

Previously I had Asus FW 1.9.2.7, which worked well except that it dropped connection about every two days and had to be manually reconnected (on Bigpond cable). With Oleg's custom FW 1.9.2.7-CR4, connection drops out frequently (~5-10 minutes) with timeouts on browsing or email send/receive. It does reconnect automatically after a minute or so, but meanwhile, if using a VPN connection it fails. I had no dropouts with browsing or VPN with Asus 1.9.2.7. It does not look as if CR4 is much good on bigpond. I've reverted to 1.9.2.7. At least it does the basic stuff well for ~48 hours at a time!

[Antiloop]

Please read the report of Michael. Het got his WDS setup working with WPA-PSK and AES. My setup has been working with WPA-PSK and AES. I'm now using 1.9.3.6 and [WDS] WPA-PSK with AES is working fine.

hm strange.. my WDS connection stopped working since the 1.9.x.x series haven't tested any higher 1.9.2.7 currently

but what does he mean with

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

which BOTH routers?
are we talking about 2 routers connected to eachother or 3 then?

[jbrbv]

hm strange.. my WDS connection stopped working since the 1.9.x.x series haven't tested any higher 1.9.2.7 currently

but what does he mean with
which BOTH routers?
are we talking about 2 routers connected to eachother or 3 then?

Two (2). You need to add both MAC addresses.

[Antiloop]

Two (2). You need to add both MAC addresses.

so you mean you need to add MAC address of the device itselve ?

[jbrbv]

so you mean you need to add MAC address of the device itselve ?

Yes, that's right.