PDA

Bekijk de volledige versie : Firmware v1.9.2.7 CR1 [Oleg]



Oleg
19-12-2004, 14:17
New firmware, as well as sources are available for download (http://wl500g.dyndns.org/1.9.2.7-1/). Please visit this (http://wl500g.dyndns.org/) page if you need further information.

Changes are:

Used GPL 1.9.2.7 sources, WPA2 & WME disabled for now
WL-500gx support
Hopefully, dnsmasq-"starcraft" issue fixed (in fact it looks like race condition)
Syslog is now also running in AP mode
Fixed 1.8.1.7-3 samba problems
Added new busybox applet: crond
Web interface shows decoded uptime now
Changed PPPoE behaviour to be compatible with stock firmware, added 2 new nvram variables:
* wan0_pppoe_maxfail - terminate after wan0_pppoe_maxfail consecutive failed connection attempts. A value of 0 means no limit. The default value is 10.
* wan0_pppoe_holdoff - specifies how many seconds to wait before re-initiating the link after it terminates.
Removed PPPoE mru/mtu 1500 warnings
Several new USB HP OfficeJet printers are supported now

WlanMan
19-12-2004, 14:24
Hi

Again, nice Firmware. Crond is cool :).
All working fine here.

What can this "ating" come from ?

Jan 1 01:00:01 kernel: br0: port 2(eth2) entering forwarding state
Jan 1 01:00:01 kernel: ating
Jan 1 01:00:01 kernel: br0: port 1(eth0) entering forwarding state

Greets

Oleg
19-12-2004, 14:29
I've no idea. Please post complete log.

WlanMan
19-12-2004, 15:31
I've no idea. Please post complete log.
OK, here is syslog. The interresing part is around the bridge setup.

Jan 1 01:00:01 syslogd started: BusyBox v1.00 (2004.12.15-20:26+0000)
Jan 1 01:00:01 kernel: klogd started: BusyBox v1.00 (2004.12.15-20:26+0000)
Jan 1 01:00:01 kernel: cpu probe
Jan 1 01:00:01 dnsmasq[51]: started, version 2.17 cachesize 150
Jan 1 01:00:01 dnsmasq[51]: DHCP, IP range 192.168.1.200 -- 192.168.1.254, lease time 24h
Jan 1 01:00:01 dnsmasq[51]: DHCP, /tmp/dnsmasq.log will be written every 28800s
Jan 1 01:00:01 dnsmasq[51]: read /etc/hosts - 5 addresses
Jan 1 01:00:01 dnsmasq[51]: reading /tmp/resolv.conf
Jan 1 01:00:01 kernel: prom init
Jan 1 01:00:01 kernel: cpu report
Jan 1 01:00:01 kernel: CPU revision is: 00024000
Jan 1 01:00:01 kernel: Loading BCM4710 MMU routines.
Jan 1 01:00:01 kernel: Primary instruction cache 8kb, linesize 16 bytes (2 ways)
Jan 1 01:00:01 kernel: Primary data cache 4kb, linesize 16 bytes (2 ways)
Jan 1 01:00:01 kernel: Linux version 2.4.20 (root@omnibook) (gcc version 3.2.3 with Broadcom modifications) #4 Thu Dec 16 23:32:43 MSK 20
[...]
Jan 1 01:00:01 kernel: Checking for 'wait' instruction... unavailable.
Jan 1 01:00:01 kernel: POSIX conformance testing by UNIFIX
Jan 1 01:00:01 kernel: PCI: Fixing up bus 0
Jan 1 01:00:01 kernel: PCI: Fixing up bridge
Jan 1 01:00:01 kernel: PCI: Fixing up bus 1
Jan 1 01:00:01 kernel: Linux NET4.0 for Linux 2.4
Jan 1 01:00:01 kernel: Based upon Swansea University Computer Society NET3.039
Jan 1 01:00:01 kernel: Initializing RT netlink socket
Jan 1 01:00:01 kernel: Starting kswapd
Jan 1 01:00:01 kernel: Journalled Block Device driver loaded
Jan 1 01:00:01 kernel: devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
Jan 1 01:00:01 kernel: devfs: boot_options: 0x1
Jan 1 01:00:01 kernel: NTFS driver v1.1.22 [Flags: R/O]
Jan 1 01:00:01 kernel: pty: 256 Unix98 ptys configured
Jan 1 01:00:01 kernel: Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
Jan 1 01:00:01 kernel: PPP generic driver version 2.4.2
Jan 1 01:00:01 kernel: PPP Deflate Compression module registered
Jan 1 01:00:01 kernel: PPP BSD Compression module registered
Jan 1 01:00:01 kernel: Amd/Fujitsu Extended Query Table v1.0 at 0x0040
Jan 1 01:00:01 kernel: Physically mapped flash: JEDEC Device ID is 0xCA. Assuming broken CFI table.
Jan 1 01:00:01 kernel: Physically mapped flash: Swapping erase regions for broken CFI table.
Jan 1 01:00:01 kernel: number of CFI chips: 1
Jan 1 01:00:01 kernel: Flash device: 0x400000 at 0x1fc00000
Jan 1 01:00:01 kernel: Physically mapped flash: squashfs filesystem found at block 1087
Jan 1 01:00:01 kernel: Creating 5 MTD partitions on "Physically mapped flash":
Jan 1 01:00:01 kernel: 0x00000000-0x00040000 : "pmon"
Jan 1 01:00:01 kernel: 0x00040000-0x003e0000 : "linux"
Jan 1 01:00:01 kernel: 0x0010fd24-0x003e0000 : "rootfs"
Jan 1 01:00:01 kernel: 0x003f0000-0x00400000 : "nvram"
Jan 1 01:00:01 kernel: 0x003e0000-0x003f0000 : "config"
Jan 1 01:00:01 kernel: sflash: chipcommon not found
Jan 1 01:00:01 kernel: NET4: Linux TCP/IP 1.0 for NET4.0
Jan 1 01:00:01 kernel: IP Protocols: ICMP, UDP, TCP
Jan 1 01:00:01 kernel: IP: routing cache hash table of 512 buckets, 4Kbytes
Jan 1 01:00:01 kernel: TCP: Hash tables configured (established 1024 bind 2048)
Jan 1 01:00:01 kernel: ip_conntrack version 2.1 (128 buckets, 1024 max) - 344 bytes per conntrack
Jan 1 01:00:01 kernel: ip_conntrack_pptp.c:init: ip_conntrack_pptp.c: registering helper
Jan 1 01:00:01 kernel: ip_conntrack_pptp version 1.9 loaded
Jan 1 01:00:01 kernel: ip_nat_pptp version 1.5 loaded
Jan 1 01:00:01 kernel: ip_tables: (C) 2000-2002 Netfilter core team
Jan 1 01:00:01 kernel: ipt_time loading
Jan 1 01:00:01 kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Jan 1 01:00:01 kernel: NET4: Ethernet Bridge 008 for NET4.0
Jan 1 01:00:01 kernel: 802.1Q VLAN Support v1.7 Ben Greear <greearb@candelatech.com>
Jan 1 01:00:01 kernel: All bugs added by David S. Miller <davem@redhat.com>
Jan 1 01:00:01 kernel: FAT: bogus logical sector size 34816
Jan 1 01:00:01 kernel: FAT: bogus logical sector size 34816
Jan 1 01:00:01 kernel: NTFS: Unable to set blocksize 512.
Jan 1 01:00:01 kernel: VFS: Mounted root (squashfs filesystem) readonly.
Jan 1 01:00:01 kernel: Mounted devfs on /dev
Jan 1 01:00:01 kernel: Freeing unused kernel memory: 68k freed
Jan 1 01:00:01 kernel: Warning: unable to open an initial console.
Jan 1 01:00:01 kernel: Algorithmics/MIPS FPU Emulator v1.5
Jan 1 01:00:01 kernel: eth0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.90.7.0
Jan 1 01:00:01 kernel: eth1: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.90.7.0
Jan 1 01:00:01 kernel: PCI: Enabling device 01:02.0 (0004 -> 0006)
Jan 1 01:00:01 kernel: eth2: Broadcom BCM4320 802.11 Wireless Controller 3.90.7.0
Jan 1 01:00:01 kernel: device eth0 entered promiscuous mode
Jan 1 01:00:01 kernel: device eth2 entered promiscuous mode
Jan 1 01:00:01 kernel: br0: port 2(eth2) entering listening state
Jan 1 01:00:01 kernel: br0: port 1(eth0) entering listening state
Jan 1 01:00:01 kernel: br0: port 2(eth2) entering learning state
Jan 1 01:00:01 kernel: br0: port 1(eth0) entering learning state
Jan 1 01:00:01 kernel: br0: port 2(eth2) entering forwarding state
Jan 1 01:00:01 kernel: ating
Jan 1 01:00:01 kernel: br0: port 1(eth0) entering forwarding state
Jan 1 01:00:01 kernel: br0: topology change detected, propagating
Jan 1 01:00:01 kernel: usb.c: registered new driver usbdevfs
Jan 1 01:00:01 kernel: usb.c: registered new driver hub
Jan 1 01:00:01 kernel: usb-ohci.c: USB OHCI at membase 0xb8004000, IRQ 2
Jan 1 01:00:01 kernel: usb-ohci.c: usb-00:04.0, PCI device 14e4:4715
Jan 1 01:00:01 kernel: usb.c: new USB bus registered, assigned bus number 1
Jan 1 01:00:01 kernel: hub.c: USB hub found
Jan 1 01:00:01 kernel: hub.c: 2 ports detected
Jan 1 01:00:02 kernel: lp0: using parport0 (polling).
Jan 1 01:00:02 kernel: hub.c: new USB device 00:04.0-1, assigned address 2
Jan 1 01:00:02 kernel: usb.c: registered new driver usblp
Jan 1 01:00:02 kernel: printer.c: v0.13: USB Printer Device Class driver
Jan 1 01:00:02 kernel: hub.c: USB hub found
Jan 1 01:00:02 kernel: hub.c: 4 ports detected
Jan 1 01:00:03 kernel: hub.c: new USB device 00:04.0-1.1, assigned address 3
Jan 1 01:00:03 kernel: usb.c: USB device 3 (vend/prod 0xea0/0x2168) is not claimed by any active driver.
Jan 1 01:00:04 kernel: usb.c: registered new driver audio
Jan 1 01:00:04 kernel: audio.c: v1.0.0:USB Audio Class driver
Jan 1 01:00:04 kernel: SCSI subsystem driver Revision: 1.00
Jan 1 01:00:04 kernel: Initializing USB Mass Storage driver...
Jan 1 01:00:04 kernel: usb.c: registered new driver usb-storage
Jan 1 01:00:04 kernel: scsi0 : SCSI emulation for USB Mass Storage devices
Jan 1 01:00:04 kernel: Vendor: KINGMAX Model: USB Flash Disk Rev: 2.00
Jan 1 01:00:04 kernel: Type: Direct-Access ANSI SCSI revision: 02
Jan 1 01:00:04 kernel: Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
Jan 1 01:00:04 kernel: SCSI device sda: 256000 512-byte hdwr sectors (131 MB)
Jan 1 01:00:04 kernel: sda: Write Protect is off
Jan 1 01:00:04 kernel: Partition check:
Jan 1 01:00:04 kernel: p1
Jan 1 01:00:04 kernel: WARNING: USB Mass Storage data integrity not assured
Jan 1 01:00:04 kernel: USB Mass Storage device found at 3
Jan 1 01:00:04 kernel: USB Mass Storage support registered.
[...]
Jan 1 01:00:15 kernel: VFS: Can't find ext3 filesystem on dev sd(8,1).
Jan 1 01:00:15 kernel: MSDOS FS: Using codepage 950
Jan 1 01:00:15 kernel: MSDOS FS: IO charset cp950
Dec 18 20:57:17 USB storage: vfat fs mounted to /tmp/harddisk
Dec 18 20:57:17 FTP server: daemon is started
Dec 18 20:57:26 ntp client: time is synchronized to 129.217.131.21
Dec 19 00:48:56 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: ctinfo = 2, skipping
Dec 19 00:48:59 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: ctinfo = 2, skipping
Dec 19 00:49:05 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: ctinfo = 2, skipping
Dec 19 03:42:46 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: ctinfo = 2, skipping
Dec 19 03:42:48 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: ctinfo = 2, skipping
Dec 19 03:42:49 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: ctinfo = 2, skipping
Dec 19 03:42:55 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: ctinfo = 2, skipping
Dec 19 03:42:55 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: ctinfo = 2, skipping
Dec 19 12:58:03 ntp client: time is synchronized to 129.217.131.21
[...]

Greets

Oleg
19-12-2004, 16:08
Mine logs:


Jan 1 03:00:02 kernel: br0: port 2(eth2) entering forwarding state
Jan 1 03:00:02 kernel: br0: topology change detected, propagating
Jan 1 03:00:02 kernel: br0: port 1(eth0) entering forwarding state
Jan 1 03:00:02 kernel: br0: topology change detected, propagating

So, looks like this a part of propag-ating.

Try dmesg, it should show kernel messages untouched.

piri
19-12-2004, 17:29
oleg, you're the greatest, this firmware fixed the dnsmasq/starcraft problem for me :)

loadsa cheers, thomas.

Dante_
19-12-2004, 17:46
What do you mean for USB officejet support?
Will the built-in scanner work?
If not, can't you put a deamon to serve direct acess to the USB port?
I've found a project that we should pay attencion...
http://usbip.naist.jp/

This is the solution! We can attach ANY USB device.. printer-scanner combo, serial port converters, anything... RAW access to the USB port...

Oleg
19-12-2004, 18:16
What do you mean for USB officejet support?
Will the built-in scanner work?

No, but some models now supports printing via USB.


If not, can't you put a deamon to serve direct acess to the USB port?
I've found a project that we should pay attencion...
http://usbip.naist.jp/

This is the solution! We can attach ANY USB device.. printer-scanner combo, serial port converters, anything... RAW access to the USB port...
Yes, but for now it requires linux on the other side.

Dante_
20-12-2004, 02:38
Yes, and it's in alpha stage yet...
I'll try to find other projects...

piri
20-12-2004, 14:13
since the firmware upgrade my wireless connection in ap mode with wpa-psk (tkip+aes) encryption won't come up anymore.
only wep is working correctly....

cheers, thomas.

Oleg
20-12-2004, 19:11
since the firmware upgrade my wireless connection in ap mode with wpa-psk (tkip+aes) encryption won't come up anymore.
only wep is working correctly....

cheers, thomas.
Please try ASUS 1.9.2.7 firmware and let me know if it works.

i-beast-a
20-12-2004, 19:16
Hi,

Great firmware but there is one issue that I had never before.
When i listen to webradio, the router crashes completely after about 10 minutes. It has a complete reset.
Computer is connected by wire, so no wireless issues or so.

The asus 1.9.2.7. has exactly the same issue.

In previous versions this worked all fine.

Any ideas????

Blackfire
20-12-2004, 20:06
(1 days, 5 hours, 34 minutes, 46 seconds since boot)
without dropping my connection on wire and wirless @ same time ;)

Great work

Oleg
20-12-2004, 20:37
When i listen to webradio, the router crashes completely after about 10 minutes. It has a complete reset.

Any ideas????
Yes, buy FM radio. :D
In fact - no ideas, seems like something is changed in the kernel. Is it RA translation?

i-beast-a
20-12-2004, 23:18
Yes, buy FM radio. :D
In fact - no ideas, seems like something is changed in the kernel. Is it RA translation?

:D

What the F*** is RA translation??

I've tried several stations but it keeps on chrashing...

Few examples:
http://ms.stream.garnierprojects.com/radio538
http://62.250.12.54:8000/listen.pls
http://www.c-dance.be/cdance-high.asx

The rest works great for me...

Styno
20-12-2004, 23:39
I've tried several stations but it keeps on chrashing...

Few examples:
http://ms.stream.garnierprojects.com/radio538
http://62.250.12.54:8000/listen.pls
http://www.c-dance.be/cdance-high.asx

The rest works great for me...
I can understand why its crashing all the time: The music you are listening to is crap. No wonder...

Choose another channel which does not broadcasts 'scooter' or 'BrEzAh' noise and all will be well.
..
..
..
I think :p

i-beast-a
21-12-2004, 10:57
I can understand why its crashing all the time: The music you are listening to is crap. No wonder...

Choose another channel which does not broadcasts 'scooter' or 'BrEzAh' noise and all will be well.
..
..
..
I think :p

I've tried listening to different channels.......BUT THEN I CHRASH MYSELF!! :D
After 1 hour of sky-radio I will kill myself....

(please help)

piri
21-12-2004, 13:58
Please try ASUS 1.9.2.7 firmware and let me know if it works.

tried official asus 1.9.2.7. fw and didn't work either.

sorry for blaming you oleg :-/

Oleg
21-12-2004, 14:00
switch to aes or tkip only, looks like aes+tkip is broken.

piri
21-12-2004, 16:01
switch to aes or tkip only, looks like aes+tkip is broken.

hmmm, tried both tkip and aes only, but didn't work....
only when unhiding SSID with those settings you can connect, but without a password (i.e. no encryption at all!!!) - seems that the whole wpa encryption is broken....

strangs that only I seem to have this problem - no other people out there using wpa-psk? :confused:

cheers, thomas.

jup
21-12-2004, 20:11
I've been using 500bv2 version of this firmware for a while now, and everything seems to work like a charm so far. I run it with WPA-PSK and TKIP. You're much faster then Asus itself, Oleg, since they haven't even released this version for 500b yet. ;)

Great work, thanks!

Phantome
21-12-2004, 22:03
I'm getting this message when i'm trying to run wshaper on this firmware :

wshaper start "eth1" 680 90
RTNETLINK answers: Invalid argument
.
.
.

Have search for this error and i only find answares that something is missing in the kernel config.

Oleg
21-12-2004, 22:12
I'm getting this message when i'm trying to run wshaper on this firmware :

wshaper start "eth1" 680 90
RTNETLINK answers: Invalid argument
.
.
.

Have search for this error and i only find answares that something is missing in the kernel config.
Yes, something is broken... I will check on that. Thank you for your report.

cZip
22-12-2004, 00:23
Howto setup wl-500g 1.9.2.7 to Wifi client?

THX cZip

ropmip
22-12-2004, 00:41
I've tried versions 1.8.x.x and now this version and I can't connect to this IP adress (newsserver):
194.65.14.158

In version 1.7.9.x it was working fine...
Is this a known problem?
I don't know if it happens on Asus official releases also... (I'm using Oleg's)

Oleg
22-12-2004, 09:37
Howto setup wl-500g 1.9.2.7 to Wifi client?

THX cZip
You mean client mode? If so, then the answer - it's not possible at this time. Use 1.7.5.9-5 instead, but this will require telneting tp the router and setting two nvram variables manually:



nvram set 13_x_ClientMode=1
nvram set 13_x_IBSS=1
nvram commit
reboot


If you've further questions - use search.

Oleg
22-12-2004, 09:39
I've tried versions 1.8.x.x and now this version and I can't connect to this IP adress (newsserver):
194.65.14.158

In version 1.7.9.x it was working fine...
Is this a known problem?
I don't know if it happens on Asus official releases also... (I'm using Oleg's)
Have you checked this server with 1.7.5.9-5 recently? Does it still works. It's unlikely, that new firmware could cause such problems... Check your PC firewall...

Zerveza
22-12-2004, 13:15
I wish to create a HTTP tunnel, where can I find how to set / adjust the default firewall settings to accept external SSH requests? I wouldn`t mind if it were a step by step description... my linux scills are a bit rusty. ;)

Is this the best firmware up till now (stable/functionality)?

Styno
22-12-2004, 13:45
I wish to create a HTTP tunnel, where can I find how to set / adjust the default firewall settings to accept external SSH requests? I wouldn`t mind if it were a step by step description... my linux scills are a bit rusty. ;)

Is this the best firmware up till now (stable/functionality)?
Search this forum for 'proxy', I think you'll find an anwer there....

The most stable and functional firmware until now is probably 1.7.5.9 CR5.

cZip
22-12-2004, 14:15
You mean client mode? If so, then the answer - it's not possible at this time. Use 1.7.5.9-5 instead, but this will require telneting tp the router and setting two nvram variables manually:



nvram set 13_x_ClientMode=1
nvram set 13_x_IBSS=1
nvram commit
reboot


If you've further questions - use search.

Thank you for your answer. I have got firmware 1.7.5.6.-5 - it works well as a client.

But I donīt have any Bandwidth Management and that’s why I would like to firmware 1.9.2.7

Will be the client mod implement into the firmware 1.9.2.7?

If yes, when..? approximately...?

Oleg
22-12-2004, 14:58
Thank you for your answer. I have got firmware 1.7.5.6.-5 - it works well as a client.

But I donīt have any Bandwidth Management and that’s why I would like to firmware 1.9.2.7

Will be the client mod implement into the firmware 1.9.2.7?

If yes, when..? approximately...?
I've no idea. It's like a puzzle. :D

wfleck
22-12-2004, 15:15
I tried to compile your firmware but it cannot find the 'addver' command. This is neither available in the custom firmware tree nor on my system (Debian GNU/Linux testing).

Could you please tell me what 'addver' is?

Thank you,
Werner

Oleg
22-12-2004, 16:13
This program should be in the ASUS GPL sources. Is it missing?
I'm attaching it just in case.

Phantome
22-12-2004, 22:13
Firmware v.1.9.2.7 CR1 [Oleg]

I have got a problem with my wireless connection.
It gets disconnected every short while.
The wireless computer got a static ip.

This is som of the output from the syslog.

Dec 22 17:00:21 udhcpc[127]: Sending renew...
Dec 22 17:00:21 udhcpc[127]: Lease of 10.0.0.2 obtained, lease time 7200
Dec 22 17:00:22 dnsmasq[71]: read /etc/hosts - 5 addresses
Dec 22 17:00:22 dnsmasq[71]: read /etc/ethers - 4 addresses
Dec 22 17:00:22 dnsmasq[71]: reading /tmp/resolv.conf
Dec 22 17:00:22 dnsmasq[71]: using nameserver 10.0.0.138#53
Dec 22 17:00:22 dhcp client: renew IP : 10.0.0.2 from 10.0.0.138

Dec 22 16:05:28 dnsmasq[71]: DHCPREQUEST(br0) 192.168.1.5 xx:xx:xx:xx:xx:xx
Dec 22 16:05:28 dnsmasq[71]: DHCPACK(br0) 192.168.1.5 xx:xx:xx:xx:xx:xx blade
Dec 22 16:05:38 dnsmasq[71]: DHCPREQUEST(br0) 192.168.1.5 xx:xx:xx:xx:xx:xx
Dec 22 16:05:38 dnsmasq[71]: DHCPACK(br0) 192.168.1.5 xx:xx:xx:xx:xx:xx blade
Dec 22 16:05:41 dnsmasq[71]: DHCPREQUEST(br0) 192.168.1.5 xx:xx:xx:xx:xx:xx
Dec 22 16:06:13 dnsmasq[71]: DHCPDISCOVER(br0) 192.168.1.5 xx:xx:xx:xx:xx:xx
Dec 22 16:06:13 dnsmasq[71]: DHCPOFFER(br0) 192.168.1.5 xx:xx:xx:xx:xx:xx

This keeps repeating it selfs.
Any clues what's wrong ?

Oleg
22-12-2004, 22:29
This keeps repeating it selfs.
Any clues what's wrong ?
Nothing wrong with wl500g. It just issues IP address in request for it.
Probably windows wireless problems, wpa or something...

Phantome
22-12-2004, 23:34
:rolleyes: Sorry about that, something is disturbing the signal, changed the channel and everything is ok for now. Even the speed changed from 150kbyte/s to 2500kbyte/s :)

wfleck
22-12-2004, 23:49
This program should be in the ASUS GPL sources. Is it missing?
I'm attaching it just in case.

Thank you very much! It is in the 1817 GPL sources, but it is missing in 1927.

Werner

cardoso
23-12-2004, 12:54
Hello
I now that this is a silly question, but I've just updated from ASUS 1.9.2.7 to
Firmware v.1.9.2.7 CR1 [Oleg]
and which username and password should I use to telnet the router ?

thanx

Oleg
23-12-2004, 13:00
same as used by webinterface.

cardoso
23-12-2004, 13:03
the webinterface as no user... only password

Styno
23-12-2004, 14:11
the webinterface as no user... only password
That means that you didn't upgrade to 1.9.2.7 properly.

Push the reset button on the back of the router for at least 10 seconds while power is applied. That resets your router to its default factory settings. After that you'll have logon with default username/password and reconfigure your router. Then your router is correctly upgraded.

You can login to telnet with the same username/password as the webinterface.

Oleg
23-12-2004, 15:18
I'm also suggesting to reset to defaults. Empty user name indicates, that you've upgraded from older (pre 1.8.x.x firmware) and has not reseted to defaults. This could cause problems, due to the fact, that firmware is seriously changed and some of the options supported earlier could cause problems with new firmware. BTW, it's still possible to telnet to your router - firmware defaults to root if username is empty.

int
24-12-2004, 15:59
Hello people!!

Add Portugal to the Time Zone! :(

Portugal are like (GMT) England !

thks for this forum :)

Merry Christmas and good programing!

Viper_Rus
26-12-2004, 08:33
on 1.9.2.7-1 (2004-12-17) not work WPA in WDS

on 1.8.1.7-3 (2004-11-15) work fine

Oleg
26-12-2004, 10:54
on 1.9.2.7-1 (2004-12-17) not work WPA in WDS

on 1.8.1.7-3 (2004-11-15) work fine
You need to specify WPA mode, which you are trying to use. There was already reported, that TKIP+AES does not work. Unfortunatly, this code could not be fixed, due to the fact that it's binary only, so I'm suggesting you to use 1.8.1.7-3 or 1.8.1.9.

int
26-12-2004, 13:18
hmmm, tried both tkip and aes only, but didn't work....
only when unhiding SSID with those settings you can connect, but without a password (i.e. no encryption at all!!!) - seems that the whole wpa encryption is broken....

strangs that only I seem to have this problem - no other people out there using wpa-psk? :confused:


I have this problem to!! with the whole wpa

chupra
27-12-2004, 02:04
Strange thing..it appears that scp is present in the firmware, but ssh lacks. So because scp cannot work without ssh, it is a waste of space to hold it, but it would also be nice if it worked too :).

Oleg
27-12-2004, 11:26
Strange thing..it appears that scp is present in the firmware, but ssh lacks. So because scp cannot work without ssh, it is a waste of space to hold it, but it would also be nice if it worked too :).
You just need to start scp from the PC, not from the wl500g itself.

pekr
10-04-2005, 13:01
Mine logs:


Jan 1 03:00:02 kernel: br0: port 2(eth2) entering forwarding state
Jan 1 03:00:02 kernel: br0: topology change detected, propagating
Jan 1 03:00:02 kernel: br0: port 1(eth0) entering forwarding state
Jan 1 03:00:02 kernel: br0: topology change detected, propagating

So, looks like this a part of propag-ating.



Hello Oleg,

since I upgrade FW to 1.9.2.7-3b, my syslog is filling with these messages from Bridge:



Jan 17 11:57:03 kernel: br0: received tcn bpdu on port 1(eth0)
Jan 17 11:57:03 kernel: br0: topology change detected, sending tcn bpdu
Jan 17 11:57:05 kernel: br0: received tcn bpdu on port 1(eth0)
Jan 17 11:57:05 kernel: br0: topology change detected, sending tcn bpdu
Jan 17 11:57:07 kernel: br0: retransmitting tcn bpdu
Jan 17 11:57:07 kernel: br0: received tcn bpdu on port 1(eth0)
Jan 17 11:57:07 kernel: br0: topology change detected
Jan 17 11:57:09 kernel: br0: retransmitting tcn bpdu
Jan 17 11:57:11 kernel: br0: retransmitting tcn bpdu
Jan 17 11:57:13 kernel: br0: retransmitting tcn bpdu
Jan 17 11:57:15 kernel: br0: retransmitting tcn bpdu
Jan 17 11:57:17 kernel: br0: retransmitting tcn bpdu
Jan 17 11:57:19 kernel: br0: retransmitting tcn bpdu
Jan 17 11:57:21 kernel: br0: retransmitting tcn bpdu
Jan 17 11:57:23 kernel: br0: retransmitting tcn bpdu
Jan 17 11:57:25 kernel: br0: retransmitting tcn bpdu
Jan 17 11:57:28 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 11:57:28 kernel: br0: topology change detected, sending tcn bpdu
Jan 17 11:57:30 kernel: br0: retransmitting tcn bpdu
Jan 17 11:57:31 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 11:57:31 kernel: br0: topology change detected
Jan 17 11:57:32 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 11:57:32 kernel: br0: topology change detected
Jan 17 11:57:32 kernel: br0: retransmitting tcn bpdu
Jan 17 11:57:34 kernel: br0: retransmitting tcn bpdu
Jan 17 11:57:35 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 11:57:35 kernel: br0: topology change detected
Jan 17 11:57:36 kernel: br0: retransmitting tcn bpdu
Jan 17 11:57:38 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 11:57:38 kernel: br0: topology change detected
Jan 17 11:57:38 kernel: br0: retransmitting tcn bpdu
Jan 17 11:57:40 kernel: br0: retransmitting tcn bpdu
Jan 17 11:57:41 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 11:57:41 kernel: br0: topology change detected
Jan 17 11:57:42 kernel: br0: retransmitting tcn bpdu
Jan 17 11:57:44 kernel: br0: retransmitting tcn bpdu
Jan 17 11:57:46 kernel: br0: retransmitting tcn bpdu
Jan 17 11:58:10 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 11:58:10 kernel: br0: topology change detected, sending tcn bpdu
Jan 17 12:45:43 kernel: br0: received tcn bpdu on port 1(eth0)
Jan 17 12:45:43 kernel: br0: topology change detected, sending tcn bpdu
Jan 17 12:45:45 kernel: br0: retransmitting tcn bpdu
Jan 17 12:45:47 kernel: br0: retransmitting tcn bpdu
Jan 17 12:46:12 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 12:46:12 kernel: br0: topology change detected, sending tcn bpdu
Jan 17 12:46:13 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 12:46:13 kernel: br0: topology change detected, sending tcn bpdu
Jan 17 12:46:15 kernel: br0: retransmitting tcn bpdu
Jan 17 12:46:15 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 12:46:15 kernel: br0: topology change detected
Jan 17 12:46:17 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 12:46:17 kernel: br0: topology change detected, sending tcn bpdu
Jan 17 12:46:19 kernel: br0: retransmitting tcn bpdu
Jan 17 12:46:19 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 12:46:19 kernel: br0: topology change detected
Jan 17 12:46:21 kernel: br0: retransmitting tcn bpdu
Jan 17 12:46:23 kernel: br0: retransmitting tcn bpdu
Jan 17 12:46:24 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 12:46:24 kernel: br0: topology change detected
Jan 17 12:46:25 kernel: br0: retransmitting tcn bpdu
Jan 17 12:46:26 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 12:46:26 kernel: br0: topology change detected
Jan 17 12:46:27 kernel: br0: retransmitting tcn bpdu
Jan 17 12:46:29 kernel: br0: retransmitting tcn bpdu
Jan 17 12:46:29 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 12:46:29 kernel: br0: topology change detected
Jan 17 12:46:31 kernel: br0: retransmitting tcn bpdu
Jan 17 12:46:32 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 12:46:32 kernel: br0: topology change detected
Jan 17 12:46:33 kernel: br0: retransmitting tcn bpdu
Jan 17 12:46:34 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 12:46:34 kernel: br0: topology change detected
Jan 17 12:46:35 kernel: br0: retransmitting tcn bpdu
Jan 17 12:46:36 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 12:46:36 kernel: br0: topology change detected
Jan 17 12:46:37 kernel: br0: retransmitting tcn bpdu
Jan 17 12:46:37 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 12:46:37 kernel: br0: topology change detected
Jan 17 12:46:39 kernel: br0: retransmitting tcn bpdu
Jan 17 12:46:40 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 12:46:40 kernel: br0: topology change detected
Jan 17 12:46:41 kernel: br0: retransmitting tcn bpdu
Jan 17 12:46:43 kernel: br0: retransmitting tcn bpdu
Jan 17 12:46:45 kernel: br0: retransmitting tcn bpdu
Jan 17 12:46:47 kernel: br0: retransmitting tcn bpdu
Jan 17 12:47:12 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 12:47:12 kernel: br0: topology change detected, sending tcn bpdu
Jan 17 12:47:13 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 12:47:13 kernel: br0: topology change detected, sending tcn bpdu
Jan 17 12:47:14 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 12:47:14 kernel: br0: topology change detected
Jan 17 12:47:15 kernel: br0: retransmitting tcn bpdu
Jan 17 12:47:16 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 12:47:16 kernel: br0: topology change detected
Jan 17 12:47:17 kernel: br0: retransmitting tcn bpdu
Jan 17 12:47:18 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 12:47:18 kernel: br0: topology change detected
Jan 17 12:47:19 kernel: br0: retransmitting tcn bpdu
Jan 17 12:47:21 kernel: br0: retransmitting tcn bpdu
Jan 17 12:47:43 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 12:47:43 kernel: br0: topology change detected, sending tcn bpdu
Jan 17 21:25:31 kernel: br0: received tcn bpdu on port 1(eth0)
Jan 17 21:25:31 kernel: br0: topology change detected, sending tcn bpdu
Jan 17 21:25:33 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:02 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 21:26:02 kernel: br0: topology change detected, sending tcn bpdu
Jan 17 21:26:02 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 21:26:02 kernel: br0: topology change detected
Jan 17 21:26:04 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:06 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:08 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:10 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:12 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:14 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:16 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:18 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:20 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:22 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:24 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:26 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:28 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 21:26:28 kernel: br0: topology change detected, sending tcn bpdu
Jan 17 21:26:30 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:31 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 21:26:31 kernel: br0: topology change detected
Jan 17 21:26:32 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:33 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 21:26:33 kernel: br0: topology change detected
Jan 17 21:26:34 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:37 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 21:26:37 kernel: br0: topology change detected, sending tcn bpdu
Jan 17 21:26:39 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:39 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 21:26:39 kernel: br0: topology change detected
Jan 17 21:26:41 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:41 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 21:26:41 kernel: br0: topology change detected
Jan 17 21:26:43 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:43 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 21:26:43 kernel: br0: topology change detected
Jan 17 21:26:45 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:45 kernel: br0: received tcn bpdu on port 3(wds0.49156)
Jan 17 21:26:45 kernel: br0: topology change detected
Jan 17 21:26:47 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:49 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:51 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:53 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:55 kernel: br0: retransmitting tcn bpdu
Jan 17 21:26:57 kernel: br0: retransmitting tcn bpdu


There is several WL500g connected to this one in WDS mode.
Operation mode is set to Router, but no routing is currently used (WAN interface isn't connected).
During this, WLAN hardly respond to ping for about 2 minutes. After then, everything works well (as before).

I have also several WL500g running FW 1.7.5.9-5 in similar setup and there is no such messages in the syslog as there are no blackouts with continuous ping.

What's wrong?

pekr
10-04-2005, 13:03
Forgot to add bridge configuration:



brctl showbr br0
br0
bridge id 8000.00112fde2120
designated root 8000.00112f90e834
root port 5 path cost 100
max age 20.00 bridge max age 20.00
hello time 2.00 bridge hello time 2.00
forward delay 0.00 bridge forward delay 0.00
ageing time 42.30 gc interval 4.00
hello timer 0.00 tcn timer 0.00
topology change timer 0.00 gc timer 3.74
flags


eth0 (1)
port id 8001 state forwarding
designated root 8000.00112f90e834 path cost 100
designated bridge 8000.00112fde2120 message age timer 0.00
designated port 8001 forward delay timer 0.00
designated cost 100 hold timer 0.66
flags

eth2 (2)
port id 8002 state forwarding
designated root 8000.00112f90e834 path cost 100
designated bridge 8000.00112fde2120 message age timer 0.00
designated port 8002 forward delay timer 0.00
designated cost 100 hold timer 0.66
flags

wds0.49156 (3)
port id 8003 state forwarding
designated root 8000.00112f90e834 path cost 100
designated bridge 8000.00112fde2120 message age timer 0.00
designated port 8003 forward delay timer 0.00
designated cost 100 hold timer 0.66
flags

wds0.49154 (4)
port id 8004 state forwarding
designated root 8000.00112f90e834 path cost 100
designated bridge 8000.00112fde2120 message age timer 0.00
designated port 8004 forward delay timer 0.00
designated cost 100 hold timer 0.66
flags

wds0.49155 (5)
port id 8005 state forwarding
designated root 8000.00112f90e834 path cost 100
designated bridge 8000.00112f90e834 message age timer 0.66
designated port 8004 forward delay timer 0.00
designated cost 0 hold timer 0.00
flags

wds0.49153 (6)
port id 8006 state forwarding
designated root 8000.00112f90e834 path cost 100
designated bridge 8000.00112fde2120 message age timer 0.00
designated port 8006 forward delay timer 0.00
designated cost 100 hold timer 0.66
flags

tomilius
10-04-2005, 21:40
Pekr--try a more recent firmware, like 1.9.2.7-3c or 1.9.2.7-4. I think I read something previously about there being annoying debug messages in one of the earlier firmwares, and this might be one of them.

pekr
10-04-2005, 22:24
tomilius:
Thanks for tip, I will try.

To be more specific - I haven't problem with these messages but with link unavailability during these 'topology changes'. Last time it took about 15 minutes.

Now I've try to disable STP:



brctl stp br0 disable

Seems to help so far...

Oleg
11-04-2005, 09:58
nvram set lan_stp=0
nvram commit

pekr
13-04-2005, 23:26
nvram set lan_stp=0
nvram commit


After few days with:


brctl stp br0 disable

everything looks good (no error at any AP).

Thanks for nvram setting Oleg!