alpha rt-n firmware releases

Printable View

Show 40 post(s) from this thread on one page

22-03-2010, 18:34
ofverstedt

Quote:

Originally Posted by wpte

I just compile them, so you should thanks the developers;)

this svn change: http://code.google.com/p/wl500g/source/detail?r=1339
sort of says that the printer should be working or close to working.
Have you tried with other asus routers? or is the rt-n16 your first one?:)

for the WL series the printer functionality works, not for all printers though.
What printer do you have?

It's my first ASUS! :)
I think it could be the printer, it is a budget printer, OKI B2200. It does almost its job and it was cheap! :p Maybe I have to live with the printer attached to one of the computers instead. :)

I think lly read this thread sometimes so it was a thanks to him aswell.

I think it could be the printer, it is a budget printer, OKI B2200. It does amost its job and it was cheap! ;) Maybe I have to live with the printer attched to one of the computer insted. :)
24-03-2010, 00:40
s1za

1 Attachment(s)

error

After my last post saying that everything was up and running an error just came out :(

after using the raid (2 1Tb usb disks on a USB Hub that worked flawlessly on the 500gp for 2 years) on the RT-N16 for a while (noticed some delays in saving files first but assumed that was from wifi) and the raid was broken and one disk was removed :confused:

1. tried to mount the raid and it began resync. Every time a issued 'cat /proc/mdstat' the speed of resyng dropped until 20Kb/s and finally stopped resync (exited from mdadm);

2. recompiled several firmwares again with some combinations options
Always with this options:
* Multi-device support (RAID and LVM)
*
Multiple devices driver support (RAID and LVM) (MD) [Y/n/?]
RAID support (BLK_DEV_MD) [Y/n/m/?]
RAID-1 (mirroring) mode (MD_RAID1) [Y/n/m/?]

With and without this options:
* SCSI device support
*
SCSI device support (SCSI) [Y/m/n/?]
SCSI target support (SCSI_TGT) [Y/m/n/?]
*
* SCSI support type (disk, tape, CD-ROM)
*
SCSI disk support (BLK_DEV_SD) [Y/m/n/?]

with the same results;

3. Tried to compile new version of mdadm (3.1.2 with no success). Managed to run 2.6.7-1 (compiled with build-root on a ubuntu vm) instead of 2.6.1 that is on the ipkg and with the same result;

4. Simulated everything on 2 1GB USB sticks with the same results (it stop resync). Manage to resync everything on ubuntu (with mdadm 2.6.7) re-tested on the router and after copy some files the same disk errors and disk removal from raid (please see attached syslog.log file);

5. For me hardware is excluded (everything works connected to a ubuntu machine). I think mdadm is excluded as well. So I'm stuck with some options in the firmware that I missed or some bug? on the scsi drivers?

I appreciate any help. Thank's in advance...
24-03-2010, 06:04
al37919

Quote:

Originally Posted by ofverstedt

Does the printer work for anyone?
My doesnt work, but i dont know if it is because of the printer itself or the FW.

are you familiar with this tutorial: http://oleg.wl500g.info/printing/
24-03-2010, 08:39
lly

Quote:

Originally Posted by s1za

1. tried to mount the raid and it began resync. Every time a issued 'cat /proc/mdstat' the speed of resyng dropped until 20Kb/s and finally stopped resync (exited from mdadm);
...
5. For me hardware is excluded (everything works connected to a ubuntu machine). I think mdadm is excluded as well. So I'm stuck with some options in the firmware that I missed or some bug? on the scsi drivers?

Are you ubuntu runs on 2.6.22 kernel? ;)
I apologize that problem caused by obsolete md/scsi drivers. Solution is not simple - backport from newer kernels of some parts md/scsi needed.
24-03-2010, 11:34
s1za

Quote:

Originally Posted by lly

Are you ubuntu runs on 2.6.22 kernel? ;)
I apologize that problem caused by obsolete md/scsi drivers. Solution is not simple - backport from newer kernels of some parts md/scsi needed.

Ubuntu 9.10 runs on the latest kernel (for this version) 2.6.30 if I'm not mistaken (I'm away from the laptop)

I've just used the laptop to check the hardware (disks and hub). Also installed mdadm on the ubuntu (which is the same version that on the router 2.6.7) so excluded problems from ipkg package and new kernel. Mdadm on the ubuntu recognized the raid and was able to do the recync with no problem.

Please tell if you need extra info.
24-03-2010, 11:44
lly

Quote:

Originally Posted by s1za

Please tell if you need extra info.

Sorry, I can't promise you anything since I haven't enough time to drill down this problem at this time. Moreover, it is very hard to solve such problems remotely, since we are not a kernel maintainers.

Best of all will be if you can seek kernel mailing list for patches or similar problem reports yourself.
24-03-2010, 23:21
ofverstedt

Quote:

Originally Posted by al37919

are you familiar with this tutorial: http://oleg.wl500g.info/printing/

Yes, i have tested that one. I get this in the syslog when i try to print:

Quote:

Mar 22 17:03:45 p9100d[331]: Connection from 192.168.1.11 port 59297 accepted
Mar 22 17:03:45 kernel: drivers/usb/class/usblp.c: usblp0 Device ID string [101/max 1552]='MANUFACTURER:OKI DATA CORP;CO'
Mar 22 17:03:45 kernel: drivers/usb/class/usblp.c: Parsing USBLPID...

And this when i turn off the printer:

Quote:

Mar 22 17:30:54 p9100d[331]: Finished job: 0 bytes received
Mar 22 17:30:57 kernel: usb 2-2.1: USB disconnect, address 4
25-03-2010, 06:54
al37919

your output show that there is no problem with usb connection. However, according to this: http://www.openprinting.org/printers/manufacturer/Oki your printer will probably not work with linux. I have to admit that this database is not exactly our case, however, such status may mean that some firmware should be loaded into the printer before printing which is not publicly available.
02-04-2010, 23:41
wpte

Hey,

I've found out that my brute-force prevention isn't working anymore

it sort of blocks now and then when I try portscanning with an online port scanner (http://www.t1shopper.com/tools/port-scan/)

but after 2 blocks or so the ssh becomes visible again.

Code:

Apr 2 23:25:39 kernel: SSH ACCEPT IN=vlan2 OUT= MAC=00:26:18:a1:3c:fb:00:60:4c:e3:66:3c:08:00:45:00:00:3c SRC=208.64.252.230 DST=192.168.1.11 LEN=60 TOS=0x00 PREC=0x00 TTL=46 ID=65460 DF PROTO=TCP SPT=45575 DPT=22 SEQ=3832370418 ACK=0 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (020405B40402080ABCE9AB460000000001030307) Apr 2 23:25:39 /opt/sbin/sshd[819]: Did not receive identification string from 208.64.252.230 Apr 2 23:25:55 kernel: SSH ACCEPT IN=vlan2 OUT= MAC=00:26:18:a1:3c:fb:00:60:4c:e3:66:3c:08:00:45:00:00:3c SRC=208.64.252.230 DST=192.168.1.11 LEN=60 TOS=0x00 PREC=0x00 TTL=46 ID=25408 DF PROTO=TCP SPT=45624 DPT=22 SEQ=3845884720 ACK=0 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (020405B40402080ABCE9E8700000000001030307) Apr 2 23:25:55 /opt/sbin/sshd[820]: Did not receive identification string from 208.64.252.230 Apr 2 23:26:25 kernel: SSH ACCEPT IN=vlan2 OUT= MAC=00:26:18:a1:3c:fb:00:60:4c:e3:66:3c:08:00:45:00:00:3c SRC=208.64.252.230 DST=192.168.1.11 LEN=60 TOS=0x00 PREC=0x00 TTL=46 ID=46836 DF PROTO=TCP SPT=45729 DPT=22 SEQ=3882735177 ACK=0 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (020405B40402080ABCEA60BD0000000001030307) Apr 2 23:26:26 /opt/sbin/sshd[824]: Did not receive identification string from 208.64.252.230 Apr 2 23:26:35 kernel: SSH ACCEPT IN=vlan2 OUT= MAC=00:26:18:a1:3c:fb:00:60:4c:e3:66:3c:08:00:45:00:00:3c SRC=208.64.252.230 DST=192.168.1.11 LEN=60 TOS=0x00 PREC=0x00 TTL=46 ID=18665 DF PROTO=TCP SPT=45765 DPT=22 SEQ=3886140901 ACK=0 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (020405B40402080ABCEA850C0000000001030307) Apr 2 23:26:35 /opt/sbin/sshd[825]: Did not receive identification string from 208.64.252.230

also the ip get listed in the /proc/net/ipt_recent/BRUTE file

Quote:

src=208.64.252.230 ttl: 46 last_seen: 4294823209 oldest_pkt: 4 4294799437, 4294818572, 4294821275, 4294823209

dunno if it's meant to work like this, since I remembered it to work with older versions:D
03-04-2010, 08:02
lly

Quote:

Originally Posted by wpte

I've found out that my brute-force prevention isn't working anymore

dunno if it's meant to work like this, since I remembered it to work with older versions:D

Which older version exactly? Can you provide your rule, just for information?

P.S. ipt_recent was modified in r1393
03-04-2010, 16:41
s1za

1 Attachment(s)

Hi,

Things got worst :(

Now with only one drive connected directly to the usb (no raid) I've got the writing errors to the drive (read seems ok since it was mounted for 2 days and I've got no error).

Drive was mounted as ext3.
Firmware 1.9.2.7-rtn-r1395

Bug on the scsi drivers?
03-04-2010, 23:51
wpte

Quote:

Originally Posted by lly

Which older version exactly? Can you provide your rule, just for information?

P.S. ipt_recent was modified in r1393

I haven't tested out which revision worked yet

I did test some different setups with iptables now though, but all with the same result.
Also... portforwarding to eth1 or vlan2 doesn't seem to matter:confused:
I should start working on that a little earlier than 23:30 tomorrow :D

anyway, I've also found out that 3 wlan devices that did not work with the RT-N16 did work as soon as I turned off Regulatory Mode. and that while they worked with the same settings on my wl-500w with 802.11d enabled:confused: Including an old 802.11g card which usually had 14Mb/s now reaching 54Mb/s.

Also enabling WMM can double the max speed on some cards, while they don't have negative effects on the other cards.
I have 9 different cards of different brands so it's a pretty solid result I'd say:p

seems like some settigs are made for these wlan drivers, or is this just coincidence?
03-04-2010, 23:54
wpte

Quote:

Originally Posted by s1za

Hi,

Things got worst :(

Now with only one drive connected directly to the usb (no raid) I've got the writing errors to the drive (read seems ok since it was mounted for 2 days and I've got no error).

Drive was mounted as ext3.
Firmware 1.9.2.7-rtn-r1395

Bug on the scsi drivers?

What brand and type drives do you have?
do you connect them via usb hub?

in cases like that I usually reset the settings after making a backup, to make sure no left-over settings are stored.:)
04-04-2010, 04:17
s1za

Quote:

Originally Posted by wpte

What brand and type drives do you have?
do you connect them via usb hub?

in cases like that I usually reset the settings after making a backup, to make sure no left-over settings are stored.:)

Now the drive (Iomega 1Tb) is connected directly to the usb port, since I got a similar problem using both drives (I've got two) in raid1 (post #77).

Trouble started with RT-N16. I had this system (2 Iomega 1Tb connected to a hub in raid1) working for 2 years on a 500gp without any problem. Now I'm afraid of losing data...

You mean doing a reset to the memory of the router?
04-04-2010, 13:07
wpte

Quote:

Originally Posted by s1za

Now the drive (Iomega 1Tb) is connected directly to the usb port, since I got a similar problem using both drives (I've got two) in raid1 (post #77).

Trouble started with RT-N16. I had this system (2 Iomega 1Tb connected to a hub in raid1) working for 2 years on a 500gp without any problem. Now I'm afraid of losing data...

You mean doing a reset to the memory of the router?

the drives should be alright according to the iomega website: http://www.iomega.com/europe/support...ts/10657e.html

Yes, the memory of the router.
Just back up the settings when it doesn't change anything of course:)

Show 40 post(s) from this thread on one page