Printable View
Hi,Quote:
Originally Posted by Hoorna
your network behaviour is same as if PC on 500g LAN port has no route to other subnet than connected LAN. Check if you have default route on PC on 500g LAN port with next hop 500g's LAN interface. Of course I can not be sure only from your decription, checking route tables from all PCs and Asuses might help. Also firewall settings may confuse things.
Hope it may help
Aiwan
Hi all,
recently I bought the Asus 500g to connect another remote LAN to my wireless network. I wanted to use the WDS function but so far i am not succesfull in it.
I loaded the newest release of the firmware (1.9.2.7-4) and configured the 500g via the web panels. (IP-address, WEP-key, MAC filtering etc.)
Computers connected to the already existing LAN are now able to ping/ configre the new Asus 500g via the WDS (so no cables!) It's even possible to ping from a telnet session on the asus over WDS via the other AP to the already existing LAN and even Internet. (e.g. www.chupa.nl)
But now the problem:
Computers connected to the Asus 500g AP. Can ping to the Asus 500g via Wireless connection and via LAN connection but they are not allowed to ping the remote Access Point (already existing LAN) at all . When i take al look at the log via telnet tot the 500g I notice the message duplicate IP-address which comes from the eth0 and eth2 combination (same HW address for wireless and LAN connection)
First I thought it was a routing problem but somewhere I read the WirelessLAN adapter and LAN adapter ought to be in the same subnet. This is why they are bridged together....
I tried to change the ip address with ifconfig but I lose my connection several times and gave up.
(where to store the settings via telnet session?)
Is someone succesfull in connecting two LANS via ASUS 500g with this firmware?
Keywords: bridge,stp,gateway,wds,route,metric, midnight commander mc,ifconfig
additional question: Has someone a compiled binary for midnight commander to use on the asus?
Is anyone else experiencing instabilities with the latest 1.9.2.7-4 release of Oleg's firmware?
It seems my unit regurarly looses wireless (wl down; wl up re-enables it). Also it seems to do spontaneous reboots. I usually have a USB stick mounted on /mnt but it gone after a while (seems to indicate reboot). Also the logfile (/tmp/syslog.log) indicates a reboot. Ofcourse there is no clue why this happens because the old log is gone. Usually the issue occurs somewhere between 12 and 24 hours after boot.
I am using an IPV6 tunnel, that may make a difference. Maybe I should try without it for a while (also not loading ipv6 module).
Regarding IPV6, the firmware seems to be imcomplete with regard to busybox. There is no ping6 and the available ping only understands ipv4. The same is true for traceroute. Anyway, IPV6 addresses result in 'host unknown'.
I have the same issue, and I don't run IPV6. I have only experienced the reboots (but maybe the wl down occurs just before that and I don't notice).Quote:
Originally Posted by Feico de Boer
I haven't taken the time to characterise the problem yet, so I have no better data on it than you do.
-- Rod
Do you use WPA? This could keying problem - try to isolate this by using WEP. If this still occures - try playing with other wl options.Quote:
Originally Posted by Feico de Boer
The reboots problem is seems to be wl.o module related and it's common for 1.9.2.7 series. 1.9.3.6 includes an updated wl.o, so once ASUS release sources for the 1.9.3.x I will switch to it.Quote:
Also it seems to do spontaneous reboots. I usually have a USB stick mounted on /mnt but it gone after a while (seems to indicate reboot). Also the logfile (/tmp/syslog.log) indicates a reboot. Ofcourse there is no clue why this happens because the old log is gone. Usually the issue occurs somewhere between 12 and 24 hours after boot.
I will add ping6 and traceroute6. As for dns problem - have no idea, I do not use ipv6 at all. Ask phedny - I've included his work to the firmware, but it seems to be incomplete at the moment.Quote:
I am using an IPV6 tunnel, that may make a difference. Maybe I should try without it for a while (also not loading ipv6 module).
Regarding IPV6, the firmware seems to be imcomplete with regard to busybox. There is no ping6 and the available ping only understands ipv4. The same is true for traceroute. Anyway, IPV6 addresses result in 'host unknown'.
I have the same issue, and I do not use IPV6.Quote:
Originally Posted by rwhitby
I use the WPA-TKIP kryptering
I have down gradet to 1.9.2.7-3c it works fine.
/Esben S. Nielsen
As far as I know I do use the WEP stuff but I will check when I have access to the router again. That won't be until I'm back home. I have not changed anything when I upgraded from 1.9.2.7-3c and that version was stable as a rock. Maybe I should hard reset the unit once and try again with clean settings.Quote:
Originally Posted by Oleg
As I mentioned, I never had problems with the previous firmwares. When I was not playing around with it, it was simple up day after day 24/7. Got home and had wireless, now I have to walk upstairs first and reboot the thing (every day) to get connection. Not really the idea behind wireless.Quote:
Originally Posted by Oleg
Actually I think there is not a DNS issue. I have been tracing the stuff before with ping6 on older firmware (1.9.2.7-3c) with the not ipv6 enable ulibc. There it was a library thing (if I recall correctly ntoh() like stuff), so just enabling IPV6 in busybox might fix things. I guess ping and traceroute just don't understand the ipv6 format and interprete these as hostnames instead of 128 bit ipv6 addresses.Quote:
Originally Posted by Oleg
Still, thanks for the efforts Oleg, I really appreciate your work.
My guess is that somebody near you just installed wireless equipment. Nothing changed in the wireless stuff in the -4, as it's available as precompiled binary only. The problem is that I've never experienced reboots, etc., so I could not even try to catch this.Quote:
Originally Posted by Feico de Boer
As for stability - this one runs in the AP mode - no reboots, etc:
Code:[root@wl500g-1 root]$ uptime
18:08:19 up 21 days, 25 min, load average: 0.08, 0.01, 0.00
[root@wl500g-1 root]$ cat /.version
1.9.2.7-4
Ok, I see now.Quote:
Actually I think there is not a DNS issue. I have been tracing the stuff before with ping6 on older firmware (1.9.2.7-3c) with the not ipv6 enable ulibc. There it was a library thing (if I recall correctly ntoh() like stuff), so just enabling IPV6 in busybox might fix things. I guess ping and traceroute just don't understand the ipv6 format and interprete these as hostnames instead of 128 bit ipv6 addresses.
Still, thanks for the efforts Oleg, I really appreciate your work.
500gx seems to work OK as WiFi client with 1.9.2.7-4 with no encryption.Quote:
Originally Posted by Oleg
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. :confused:
Ivan
----------------------------------------
Translation from passphrase to hexadecimal equivalent (thanks Orinoco AP for intellectual property, I am not breaching their copyright too much :o ).
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
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.
Oleg, is there a chance to get a shutdown-function for the WL-HDD implemented in a further version of your excellent firmware ?
Well, as I do not have wlhdd, I could not even check how this should work. Does it really turns off (i.e. all LEDs are turned off and HDD is stoped)?Quote:
Originally Posted by ManfredK2
To test WebTools on WL-500g I dug up an old 40 Gb HDD and created 2 partitions on it:
- 64 Mb Swap ( /dev/scsi/host0/bus0/target0/lun0/part5)
- the rest ext3 ( /dev/scsi/host0/bus0/target0/lun0/part6)
When I boot the router there's a `/opt` directory, but I can't write to it: If I do `mkdir /opt/test` I get:this is some config on my WL-500g:Code:mkdir: Cannot create directory `/opt/test': Read-only file system
proc:
mount:Code:cd /dev/scsi/host0/bus0/target0/lun0/
$ ls
disc part1 part5 part6
How can I get /proc to be read-write?Code:mount
/dev/root on / type squashfs (ro)
none on /dev type devfs (rw)
proc on /proc type proc (rw)
ramfs on /tmp type ramfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/discs/disc0/part6 on /tmp/harddisk type ext3 (rw,noatime)
Styno, I'm wonder: have you read this thread from the begining? Also, try using search, as read-only /opt is discussed several times already. :)
Hint: you need to mount /opt first or to switch to the external rootfs. :)
Dear Oleg, thank you for replying so quickly.
- Yes, I've read the entire thread -> It has only hints for people using FAT, rootfs or NFS. I'm using native ext3 partition without rootfs.
- Yes, I've searched (the search button is a big friend of mine remember? :p) on `/opt` and read all topics (about 14 of them) but could only find pointers to this topic, no solution.
Please can you help me?
Edit: Ok, I've tried every option in the mount man page and voila, the following works:
Thanks for your patience.Code:mount -obind /tmp/harddisk /opt