Firmware v1.9.2.7 CR4 [Oleg]

[Oleg]

Thanks Oleg! Great work as usual, lots of fixes and new stuff.

Would there be enough free space available with the current use of LZMA compression for exchanging stupid-ftp with vsftpd?

Well, actually this space is now used by nfs and ipv6 stuff. Anyway, we still have free space and vsftpd could fit to it. The only problem is that vsftpd requires slightly different users concept, which does not applies very well with current stupid-ftpd...

[Styno]

The only problem is that vsftpd requires slightly different users concept, which does not applies very well with current stupid-ftpd...

This could be overcome by replacing the FTP config page in the webinterface with a new one specifically for vsftpd, right? How much efford would that take?

[Oleg]

This could be overcome by replacing the FTP config page in the webinterface with a new one specifically for vsftpd, right? How much efford would that take?

I have no idea, as I have not checked this carefully yet.

[hugo]

Does this mean we can use any openwrt package on the wl-hdd? This is the greatest news of the day then!

[Oleg]

Does this mean we can use any openwrt package on the wl-hdd? This is the greatest news of the day then!

No, as they use different fs layout. I've compiled several packages from the nslu2-linux.org site, they've them in the unslung firmware.

[hugo]

So basicaly we still have a binary/lib difference between the packages, and we still have to compile them? or can we run the binary directly if set up on correct folders?

[Oleg]

So basicaly we still have a binary/lib difference between the packages, and we still have to compile them? or can we run the binary directly if set up on correct folders?

You could run openwrt binaries as well. For this to work you need to make chroot environment, i.e. mount openwrt rootfs and chroot to it. That's all. You should be able to use most of the openwrt packages after that.

[hugo]

maybe a small bug?

[admin@wl-hdd bin]$ ipkg.sh update
mkdir: Cannot create directory `/opt/lib/': Read-only file system

[Aiwan]

Summary of problem:
Asus is setup as WiFi client,attaches to ISP’s AP, but is not able to send or receive any IP packets on WiFi interface.
LAN ethernet ports are isolated from router inside Asus.
----------------------
Hi,
I tried to setup Asus 500g Deluxe as Wifi client to connect my home LAN to ISP using WiFi. It looks like there is either some bug in gx version or (more probably) there is problem in my setup (typical problem between keyboard and chair). I have some networking experience (Cisco CCIE,CCNP,CCDP) but Asus is new for me. I tested real life connection to ISP and later (after long hours of fight with ASUS) I built testing lab environment to limit ISP's complications (MAC filtering, security filters etc..). My ASUS worked in lab same way as in real life - WiFi connection has been built (my ASUS attached to AP) but there is no possibility to get DHCP reply, there is 0 packets received on WiFi interface from air. Another (very similar) behaviour is on LAN (eth 0.1) ports, it seems that they are only unidirectional ports.

I am sorry if I made some stupid error in setup but I spent long hours with Asus and I am desperate now. I tried almost everything (different setups, tried all HOWTOs I was able to find) and it does not work as expected.

I described my setup (pictures, screenshots, listings) and my tests as a Word file at http://www.tenzor.cz/surfer/asus/ASUSproblem.doc and I am attaching it to this post.

Could you give me some hint how to make this great router with Oleg's firmware (I like it, really) working in my setup?
Thanks
Ivan

[Antiloop]

Summary of problem:
Asus is setup as WiFi client,attaches to ISP’s AP, but is not able to send or receive any IP packets on WiFi interface.
LAN ethernet ports are isolated from router inside Asus.
----------------------
Hi,
I tried to setup Asus 500g Deluxe as Wifi client to connect my home LAN to ISP using WiFi. It looks like there is either some bug in gx version or (more probably) there is problem in my setup (typical problem between keyboard and chair). I have some networking experience (Cisco CCIE,CCNP,CCDP) but Asus is new for me. I tested real life connection to ISP and later (after long hours of fight with ASUS) I built testing lab environment to limit ISP's complications (MAC filtering, security filters etc..). My ASUS worked in lab same way as in real life - WiFi connection has been built (my ASUS attached to AP) but there is no possibility to get DHCP reply, there is 0 packets received on WiFi interface from air. Another (very similar) behaviour is on LAN (eth 0.1) ports, it seems that they are only unidirectional ports.

I am sorry if I made some stupid error in setup but I spent long hours with Asus and I am desperate now. I tried almost everything (different setups, tried all HOWTOs I was able to find) and it does not work as expected.

I described my setup (pictures, screenshots, listings) and my tests as a Word file at http://www.tenzor.cz/surfer/asus/ASUSproblem.doc and I am attaching it to this post.

Could you give me some hint how to make this great router with Oleg's firmware (I like it, really) working in my setup?
Thanks
Ivan

i've not read your .doc file yet
and I'm also not sure if WL500g.Deluxe as Wireless Client works
I will try this asap when I find some time..
(I have the same setup with WL-HDD/WL-500g and 1.9.2.7-3c firmware which works flawless only no encryption is used, so please try 1.9.2.7-3c too if you use no encryption)

[Oleg]

Could you give me some hint how to make this great router with Oleg's firmware (I like it, really) working in my setup?
Thanks
Ivan

Where are you from? If you're from Russia, then PM me. To be honest, client mode was never tested with wl500gx, so LAN port problems could be there.
As for WLAN problem - do you use hex wep keys or passphrases? Passphrases are know to cause problems (as they're mostly vendor specific, unlike WPA-PSK keys), use hex keys only. Also, have you tried using it without WEP at all?
Also, dependening on the peer software it could require either "Shared Key" authentication (like you've specified) or "Open System / Shared Key" (this way key is used for data encryption only).

[Aiwan]

Where are you from? If you're from Russia, then PM me. To be honest, client mode was never tested with wl500gx, so LAN port problems could be there.
As for WLAN problem - do you use hex wep keys or passphrases? Passphrases are know to cause problems (as they're mostly vendor specific, unlike WPA-PSK keys), use hex keys only. Also, have you tried using it without WEP at all?
Also, dependening on the peer software it could require either "Shared Key" authentication (like you've specified) or "Open System / Shared Key" (this way key is used for data encryption only).

Thanks for reply Oleg, I am from Czech Republic (I have studied russian language 11 years but my technichal russian is bad ). I am using passphrase, but I assume that if wl status shows that I am connected, it means that WEP encryption works well and data should go through. I'll test all possibilities recommended and let you know.
LAN ports (eth0.1) is solvable by hack using crossover cable between WAN and LAN ethernet port (3 remaining ports are enough for now). This is low priority issue.
WiFi isssue is much more serious.
Thanks for hints Oleg. I appreciate it.

[Aiwan]

Where are you from? If you're from Russia, then PM me. To be honest, client mode was never tested with wl500gx, so LAN port problems could be there.
As for WLAN problem - do you use hex wep keys or passphrases? Passphrases are know to cause problems (as they're mostly vendor specific, unlike WPA-PSK keys), use hex keys only. Also, have you tried using it without WEP at all?
Also, dependening on the peer software it could require either "Shared Key" authentication (like you've specified) or "Open System / Shared Key" (this way key is used for data encryption only).

500gx seems to work OK as WiFi client with 1.9.2.7-4 with no encryption.
500gx seems to work OK as WiFi client with 1.9.2.7-4 with shared key WEP encryption, but key must be input in Hexadecimal form, not passphrase.

Bug in firmware is, that Asus wrongly (or at least differently from Cisco Aironet 350 PCMCIA card, Orinoco AP, Intel Centrino chipset WiFi card and my ISP's D-link AP) translates passphrase WEP key into Hexadecimal form (which is probably used for encryption process). When I used table below (from Orinoco AP Help) and translated passphrase manualy into Hexadecimal key, it started to work.

There was no difference between "Open System / Shared Key" and "Shared Key" option, after translation of passphrase, both worked well with my ISP's D-link AP.

My fault was that I missunderstood wl status output
[admin@ASUS500GX root]$ wl status
SSID: "pokus"
Mode: Managed RSSI: -28 dBm noise: -99 dBm Channel: 1
BSSID: 00:02:2D:2D:10:AD Capability: ESS WEP
Supported Rates: [ 1(b) 2(b) 5.5 11 ]
I understood that WEP keys were compared and encryption works well. It is not true. The output above is probably radio interface status with no connection with encryption.

Problem with strange behaviour of LAN ports is not solved and I will have to investigate it.

Ivan

----------------------------------------
Translation from passphrase to hexadecimal equivalent (thanks Orinoco AP for intellectual property, I am not breaching their copyright too much ).

Encryption Key strings are case-sensitive!
Example: If your Encryption Key reads: "Key2Z" the hexadecimal equivalent would be: "4B657932A"

Alphanumeric Hex Alphanumeric Hex
A 41 a 61
B 42 b 62
C 43 c 63
D 44 d 64
E 45 e 65
F 46 f 66
G 47 g 67
H 48 h 68
I 49 i 69
J 4A j 6A
K 4B k 6B
L 4C l 6C
M 4D m 6D
N 4E n 6E
O 4F o 6F
P 50 p 70
Q 51 q 71
R 52 r 72
S 53 s 73
T 54 t 74
U 55 u 75
V 56 v 76
W 57 w 77
X 58 x 78
Y 59 y 79
Z A z 7A
Spacebar 20 0 30
! 21 1 31
" 22 2 32
# 23 3 33
$ 24 4 34
% 25 5 35
& 26 6 36
' 27 7 37
( 28 8 38
) 29 9 39
* 2A : 3A
+ 2B ; 3B
, 2C < 3C
- 2D = 3D
. 2E > 3E
/ 2F ? 3F
[ 5B @ 40
5C
] 5D
^ 5E
_ 5F
` 60
7B
| 7C
7D
~ 7E
Del. 7F

[Oleg]

In fact there is no WEP hex key - passphrase translation schemes, so every vendor uses it's own implementation. Agere/Orinoco drivers supports really weak scheme, which only uses ASCII translation (this reduces key strength), also at some point I had problems interacting Orinoco Gold Card with Orinoco AP - they've translated passphrases differently (this was driver bug).
So, as I've suggested several times - do not use WEP passphrases, use hex keys.

[ManfredK2]

Oleg, is there a chance to get a shutdown-function for the WL-HDD implemented in a further version of your excellent firmware ?