RouterTech Firmware 2.93 Discussion

All about firmwares for routers. Support for RouterTech firmwares is here too.
Post Reply
User avatar
Kieran
RouterTech Team
RouterTech Team
Posts: 2675
Joined: Fri Jan 20, 2006 11:30 am
Location: London
Contact:

RouterTech Firmware 2.93 Discussion

Post by Kieran » Mon Apr 12, 2010 1:27 pm

This is the place to discuss (thanks, suggestions, criticisms etc.) the v2.93 release of the RouterTech firmware, available for download here

For support, problems, bugs or other such firmware related questions or issues, please start a new thread
Kieran
"Indeed!"
Invaluable links: Forum Rules | Networking Guides | FAQ | Site Search | Forum Search <-- Use it or feel my wrath!
No support via PM, please ask your questions in the forum!
Thunderbird60
Newbie
Newbie
Posts: 9
Joined: Wed Mar 24, 2010 12:16 pm

Re: RouterTech Firmware 2.93 Discussion

Post by Thunderbird60 » Tue Apr 13, 2010 7:30 am

Unfortunately, this release is as unstable, mainly under p2p load, as release 2.92. After days of nightmare I had to come back to original firmware of my Acorp 420M.
User avatar
thechief
RouterTech Team
RouterTech Team
Posts: 12067
Joined: Wed Feb 01, 2006 10:22 pm
Location: England, the Centre of Africa
Contact:

Re: RouterTech Firmware 2.93 Discussion

Post by thechief » Tue Apr 13, 2010 8:19 am

Thunderbird60 wrote:Unfortunately, this release is as unstable, mainly under p2p load, as release 2.92.
Such wide generalisations are wholly unhelpful. Care to give some details?
Thunderbird60 wrote:After days of nightmare ...
For a firmware that was only released yesterday?

To provide an alternative factual analysis, mine has been running non-stop for days (from the final test 3 days before the release), and on a very poor line too.
RouterTech firmware release: 2.93
Linux version 2.4.17_mvl21-malta-mips_fp_le (developers@RouterTech.Org) #1 Wed Apr 7 21:08:17 BST 2010
BUILD=RouterTech_3.6.0D_20100407_2.93
VERSION=3.6.0D-RouterTech-PSBL
BOARD=AR7WRD
TARGET=psbl
FSSTAMP=20100407211146
Ethernet ports: 4
Core logic version: 3.6.0D
Boot Loader: 1.4.0.8
ATM Driver version:[7.05.01.00]
DSL HAL version: [7.05.01.00]
DSP Datapump version: [7.05.01.00] Annex A
SAR HAL version: [01.07.2c]
PDSP Firmware version:[0.54]
Chipset ID: [7300/7300A]
Upstream rate (kbps): 606
Downstream rate (kbps): 2724
Trained Modulation: ADSL_G.dmt.bis
Path Mode: Interleaved
System uptime: 96 hr 19 min - 4 day(s), 0 hour(s), 19 minute(s), and 19 second(s) (system 99% idle)
WAN uptime: 96hr 18min 4sec
WAN IP address: 90.xx.xx.xx
Bandwidth usage:
Downloads : 1271.3241 MB
Uploads : 257.2241 MB
Line attenuation:
DS Line Attenuation: 58 DS Margin: 7
US Line Attenuation: 36 US Margin: 13
Memory usage:
In active use : 83% of 14216 kb
Available : 17% (2528 kb) of 14216 kb
Environment fragmentation:
The environment does not seem to be fragmented.
Connection information: connection0 mux0 encaps0 quickstart 0:38 pppoa
The Chief: :afro: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
Thunderbird60
Newbie
Newbie
Posts: 9
Joined: Wed Mar 24, 2010 12:16 pm

Re: RouterTech Firmware 2.93 Discussion

Post by Thunderbird60 » Tue Apr 13, 2010 8:44 am

thechief wrote:Such wide generalisations are wholly unhelpful. Care to give some details?
router hangs - I have the same symptoms. The router keeps p2p-connections. But DNS fails. I can't connect to the router. If to close uTorrent, after some time I can connect to the router. But it become more and more unstable till the next reboot. Everything I noticed, these lines in a log: "Connection reset by peer". Here what I wrote down some days ago:
ROUTERTECH SYSTEM DIAGNOSTICS

Operating system version
Linux version 2.4.17_mvl21-malta-mips_fp_le (developers@RouterTech.Org) #1 Tue Jan 5 15:06:46 GMT 2010

Firmware version information
BUILD=RouterTech_3.6.0D_20100105_2.92
VERSION=3.6.0D-RouterTech-4P-PSBL
BOARD=AR7RD
TARGET=psbl
FSSTAMP=20100105150919

PSP version information

Linux OS DSL-PSPOhioL version 4.5.0.5 Best and Final on BasePSP Version 5.7.6.12 Jan 5 2010 15:07:43
Avalanche SOC Version: 0x11002b operating in cached, write back, write allocate mode
Cpu Frequency:211 MHZ
System Bus frequency: 105 MHZ


Driver version information
Core Logic version: 3.6.0D
Texas Instruments CPMAC driver version: 1.5
Texas Instruments CPMAC HAL version: CPMAC 01.07.08 Jan 5 2010 15:06:57
ATM Driver version:[7.05.01.00]
DSL HAL version: [7.05.01.00]
DSP Datapump version: [7.05.01.00] Annex A
SAR HAL version: [01.07.2c]
PDSP Firmware version:[0.54]
Chipset ID: [Ohio250(7200/7100A2)]

Modem Modulation Information
NO_MODE 0x0
ADSL_G.dmt 0x2
ADSL_G.lite 0x4
ADSL_G.dmt.bis 0x8
ADSL_G.dmt.bis_DELT 0x9
ADSL_2plus 0x10
ADSL_2plus_DELT 0x11
ADSL_re-adsl 0x20
ADSL_re-adsl_DELT 0x21
ADSL_ANSI_T1.413 0x80
MULTI_MODE 0xff
ADSL_G.dmt.bis_AnxI 0x0
ADSL_G.dmt.bis_AnxJ 0x0
ADSL_G.dmt.bis_AnxM 0x400
ADSL_2plus_AnxI 0x0
ADSL_2plus_AnxJ 0x0
ADSL_2plus_AnxM 0x2000
G.shdsl 0x0
IDSL 0x0
HDSL 0x0
SDSL 0x0
VDSL 0x0

System environment (/proc/ticfg/env)
BUILD_OPS 0x301
bootloaderVersion 1.4.0.4
ProductID Sprinter@ADSL LAN420M
HWRevision Unknown
SerialNumber none
mtd2 0x90000000,0x90010000
mtd3 0x90010000,0x90020000
mtd4 0x90020000,0x90200000
MAC_PORT 1
IPA 192.168.1.1
BOOTCFG m:f:"mtd1"
MEMSZ 0x00800000
FLASHSZ 0x00200000
MODETTY0 9600,n,8,1,hw
MODETTY1 9600,n,8,1,hw
PROMPT (psbl)
CPUFREQ 211968000
MIPSFREQ 211968000
SYSFREQ 105984000
StaticBuffer 128
vcc_encaps0 0.0
vcc_encaps1 0.0
vcc_encaps2 0.0
vcc_encaps3 0.0
vcc_encaps4 0.0
vcc_encaps5 0.0
vcc_encaps6 0.0
vcc_encaps7 0.0
HWA_0 00:14:2B:0B:24:4E
HWA_3 00:14:2B:0B:24:4F
DSL_BIT_TMODE 1
mtd1 0x90020090,0x90099000
mtd0 0x90099000,0x90200000
modulation 0xff
connection0 0xd60a


CPU information
processor : 0
cpu model : MIPS 4KEc V4.8
BogoMIPS : 211.35
wait instruction : no
microsecond timers : yes
extra interrupt vector : yes
hardware watchpoint : yes
VCED exceptions : not available
VCEI exceptions : not available

Memory (RAM) information
total: used: free: shared: buffers: cached:
Mem: 6397952 6295552 102400 0 143360 876544
Swap: 0 0 0
MemTotal: 6248 kB
MemFree: 100 kB
MemShared: 0 kB
Buffers: 140 kB
Cached: 856 kB
SwapCached: 0 kB
Active: 652 kB
Inactive: 1916 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 6248 kB
LowFree: 100 kB
SwapTotal: 0 kB
SwapFree: 0 kB

Flash memory (chip) information
Flash type: AMD; Manufacturer=Unknown!.
Manufacturer_ID=0x007F; Chip_ID=0x0049; Chip_Size=0x400000; Erase_Regions=0x0004

Mount points
/dev/mtdblock/0 / squashfs ro 0 0
none /dev devfs rw 0 0
proc /proc proc rw 0 0
ramfs /var ramfs rw 0 0

Filesystems
nodev rootfs
nodev bdev
nodev proc
nodev sockfs
nodev tmpfs
nodev shm
nodev pipefs
nodev ramfs
nodev devfs
squashfs

MTD
dev: size erasesize name
mtd0: 00167000 00010000 "mtd0"
mtd1: 00078f70 00010000 "mtd1"
mtd2: 00010000 00008000 "mtd2"
mtd3: 00010000 00010000 "mtd3"
mtd4: 001e0000 00010000 "mtd4"

Kernel modules
tiatm 138672 1

Interrupts
7: 69275 R4000 timer/counter [MIPS interrupt]
8: 0 unified secondary [hw0 (Avalanche Primary)]
15: 340 serial [hw0 (Avalanche Primary)]
23: 46427 + SAR [hw0 (Avalanche Primary)]
27: 45528 + Cpmac Driver, + Cpmac Driver, + Cpmac Driver, + Cpmac Driver [hw0 (Avalanche Primary)]
31: 47 + DSL [hw0 (Avalanche Primary)]

Devices
Character devices:
1 mem
2 pty/m%d
3 pty/s%d
4 tts/%d
5 cua/%d
10 misc
108 ppp
128 ptm
136 pts/%d
162 raw

Block devices:
7 loop
31 mtdblock

Processes
PID USER VSZ STAT COMMAND
1 root 976 S init
2 root 0 SW [keventd]
3 root 0 SWN [ksoftirqd_CPU0]
4 root 0 SW [kswapd]
5 root 0 SW [bdflush]
6 root 0 SW [kupdated]
7 root 0 SW [mtdblockd]
185 root 1180 S /usr/sbin/thttpd -d /usr/www -u root -p 80 -c /cgi-bi
186 root 2112 S /usr/bin/cm_pc
188 root 3460 S /usr/bin/cm_logic -m /dev/ticfg -c /etc/config.xml
207 root 744 S /sbin/dproxy -c /etc/resolv.conf -d
305 root 976 S init
400 root 2392 S /usr/sbin/pppd plugin pppoe nas0 user sl80802 passwor
421 root 920 S /sbin/msntp -r 2 -t 5 -p 30 -s time-a.nist.gov time-b
424 root 684 S /usr/sbin/udhcpd /var/tmp/udhcpd.conf
655 root 984 S N /bin/sh diagnostics.cgi
656 root 1180 S /usr/sbin/thttpd -d /usr/www -u root -p 80 -c /cgi-bi
660 root 608 S N /usr/local/bin/diagnostics
661 root 976 S N sh -c /usr/local/bin/diagnostics.sh
662 root 984 S N /bin/sh /usr/local/bin/diagnostics.sh
684 root 976 R N /bin/ps

ADSL Modem information

AR7 DSL Modem Statistics:
--------------------------------
[DSL Modem Stats]
US Connection Rate: 892 DS Connection Rate: 8154
DS Line Attenuation: 0 DS Margin: 17
US Line Attenuation: 11 US Margin: 33
US Payload : 15580272 DS Payload: 8279088
US Superframe Cnt : 38157 DS Superframe Cnt: 38157
US Transmit Power : 15 DS Transmit Power: 22
LOS errors: 0 SEF errors: 0
Errored Seconds: 2 Severely Err Secs: 0
Frame mode: 0 Max Frame mode: 0
Trained Path: 1 US Peak Cell Rate: 2103
Trained Mode: 8192 Selected Mode: 65535
ATUC Vendor Code: 4753504E ATUC Revision: 3
Hybrid Selected: 1 Trellis: 1
Showtime Count: 1 DS Max Attainable Bit Rate: 16832 kbps
BitSwap: 1 US Max Attainable Bit Rate: 992000 bps
Annex: AnxM psd_mask_qualifier: 0x001c
ATUC ghsVid: ff b5 47 53 50 4e 02 0b
T1413Vid: 00 00 T1413Rev: 00 VendorRev: 00
ATUR ghsVid: b5 00 54 53 54 43 00 00
T1413Vid: 00 00 T1413Rev: 00 VendorRev: 00

[Upstream (TX) Interleave path]
CRC: 0 FEC: 0 NCD: 0
LCD: 0 HEC: 0

[Downstream (RX) Interleave path]
CRC: 3 FEC: 178 NCD: 0
LCD: 0 HEC: 0

[Upstream (TX) Fast path]
CRC: 2 FEC: 0 NCD: 0
LCD: 0 HEC: 0

[Downstream (RX) Fast path]
CRC: 0 FEC: 0 NCD: 0
LCD: 0 HEC: 0

[ATM Stats]
[Upstream/TX]
Good Cell Cnt: 324589
Idle Cell Cnt: 1041287


[Downstream/RX)]
Good Cell Cnt: 172481
Idle Cell Cnt: 12302725
Bad Hec Cell Cnt: 2
Overflow Dropped Cell Cnt: 0

[SAR AAL5 Stats]
Tx PDU's: 27487
Rx PDU's: 19847
Tx Total Bytes: 14677756
Rx Total Bytes: 7718266
Tx Total Error Counts: 0
Rx Total Error Counts: 0


[OAM Stats]
Near End F5 Loop Back Count: 0
Near End F4 Loop Back Count: 0
Far End F5 Loop Back Count: 0
Far End F4 Loop Back Count: 0
SAR OAM Ping Response Drop Count=15

Trained modulation:
ADSL_2plus_AnxM

Path mode:
Interleaved

Network statistics
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:www 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:domain 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:ftp 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:ssh 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:telnet 0.0.0.0:* LISTEN
tcp 0 0 mygateway1.AR7RD:www 192.168.10.2:3958 ESTABLISHED
tcp 0 0 mygateway1.AR7RD:www 192.168.10.2:3695 TIME_WAIT
tcp 0 0 mygateway1.AR7RD:www 192.168.10.2:3937 TIME_WAIT
tcp 0 0 mygateway1.AR7RD:www 192.168.10.2:3870 TIME_WAIT
tcp 0 0 mygateway1.AR7RD:www 192.168.10.2:3883 TIME_WAIT
tcp 0 0 mygateway1.AR7RD:www 192.168.10.2:3809 TIME_WAIT
udp 0 0 0.0.0.0:domain 0.0.0.0:*
udp 0 0 0.0.0.0:bootps 0.0.0.0:*
udp 0 0 0.0.0.0:tftp 0.0.0.0:*
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ] DGRAM 258 /var/tmp/cm_logic.ctl
unix 5 [ ] DGRAM 272 /dev/log
unix 2 [ ] DGRAM 274 /dev/klog
unix 2 [ ] DGRAM 244 /var/tmp/cm_pc.ctl
unix 2 [ ] DGRAM 1026
unix 2 [ ] DGRAM 640
unix 2 [ ] DGRAM 625
unix 2 [ ] STREAM 230
unix 2 [ ] DGRAM 229
unix 2 [ ] DGRAM 29
unix 2 [ ] DGRAM 23

Iptables chains
Chain INPUT (policy ACCEPT 2202 packets, 119K bytes)
pkts bytes target prot opt in out source destination
196 30199 ACCEPT all -- ppp0 any anywhere anywhere state RELATED,ESTABLISHED
1281 95198 DROP all -- ppp0 any anywhere anywhere

Chain FORWARD (policy ACCEPT 33605 packets, 17M bytes)
pkts bytes target prot opt in out source destination
22726 9210K ACCEPT all -- ppp0 any anywhere anywhere state RELATED,ESTABLISHED
1359 65232 TCPMSS tcp -- any ppp0 anywhere anywhere tcp flags:SYN,RST/SYN TCPMSS clamp to PMTU
0 0 DROP all -- ppp0 any anywhere anywhere

Chain OUTPUT (policy ACCEPT 2593 packets, 503K bytes)
pkts bytes target prot opt in out source destination
11 2392 DROP icmp -- any ppp0 anywhere anywhere icmp destination-unreachable
0 0 DROP icmp -- any ppp0 anywhere anywhere state INVALID

Network interface details
br0 Link encap:Ethernet HWaddr 00:14:2B:0B:24:4E
inet addr:192.168.10.1 Bcast:192.168.10.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:36571 errors:0 dropped:0 overruns:0 frame:0
TX packets:25269 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:17043714 (16.2 MiB) TX bytes:10101466 (9.6 MiB)

br1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
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)

br2 Link encap:Ethernet HWaddr 00:00:00:00:00:00
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)

eth0 Link encap:Ethernet HWaddr 00:14:2B:0B:24:4E
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:36555 errors:0 dropped:0 overruns:0 frame:0
TX packets:25254 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:17545960 (16.7 MiB) TX bytes:10096478 (9.6 MiB)

eth1 Link encap:Ethernet HWaddr 82:14:2B:0B:24:4E
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:36555 errors:0 dropped:0 overruns:0 frame:0
TX packets:25275 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:17545960 (16.7 MiB) TX bytes:10102356 (9.6 MiB)

eth2 Link encap:Ethernet HWaddr 92:14:2B:0B:24:4E
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:36574 errors:0 dropped:0 overruns:0 frame:0
TX packets:25275 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:17556478 (16.7 MiB) TX bytes:10102356 (9.6 MiB)

eth3 Link encap:Ethernet HWaddr A2:14:2B:0B:24:4E
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:36574 errors:0 dropped:0 overruns:0 frame:0
TX packets:25275 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:17556478 (16.7 MiB) TX bytes:10102356 (9.6 MiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 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)

nas0 Link encap:Ethernet HWaddr 00:14:2B:0B:24:4F
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:24494 errors:0 dropped:0 overruns:0 frame:0
TX packets:34231 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:9585799 (9.1 MiB) TX bytes:18001227 (17.1 MiB)

ppp0 Link encap:Point-to-Point Protocol
inet addr:<censored> P-t-P:<censored> Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:24449 errors:0 dropped:0 overruns:0 frame:0
TX packets:34214 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9385862 (8.9 MiB) TX bytes:16905646 (16.1 MiB)


System Log
Jan 5 15:09:09 | Valid Configuration Tree
Jan 5 15:09:09 | NTP Polling Timer for DHCP Started succesfully.
Jan 5 15:09:09 | DSL Polling Timer Started succesfully.
Jan 5 15:09:09 | PSP Boot environment Modem Modulation Change: 0xff
Jan 5 15:09:09 | Firewall NAT service started
Jan 5 15:09:10 | Bridge Created: br0
Jan 5 15:09:11 | Bridge VLAN0 add eth0
Jan 5 15:09:11 | Bridge VLAN AUTO OFF.
Jan 5 15:09:11 | Bridge VLAN0 add eth1
Jan 5 15:09:11 | Bridge VLAN AUTO OFF.
Jan 5 15:09:11 | Bridge VLAN0 add eth2
Jan 5 15:09:11 | Bridge VLAN AUTO OFF.
Jan 5 15:09:11 | Bridge VLAN0 add eth3
Jan 5 15:09:11 | Bridge VLAN AUTO OFF.
Jan 5 15:09:11 | Bridge Created: br1
Jan 5 15:09:12 | Bridge Created: br2
Jan 5 15:09:14 | Bridge Interface Added: eth0
Jan 5 15:09:16 | Bridge Interface Added: eth1
Jan 5 15:09:18 | Bridge Interface Added: eth2
Jan 5 15:09:19 | Bridge Interface Added: eth3
Jan 5 15:09:21 | USB is disabled
Jan 5 15:09:21 | DSL Carrier is down
Jan 5 15:09:41 | DSL Carrier is up
Jan 5 15:09:41 | sar read trained mode (16)(ADSL_2plus_AnxM)
Jan 5 15:09:42 | ---}}} Start of connection delayed for 6 sec
Jan 5 15:09:48 | PPPoE Launch after conn delay timeout ...
Jan 5 15:09:49 | pppd 2.4.4 started by root, uid 0
Jan 5 15:09:49 | Unexpected packet: Ether addr: 00:90:1a:a2:04:d7 (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x07 sid=0x0000 length=0x002d (PADO) PPPoE tag: type=0102 length=0009 (AC Name) data (UTF-8): KSK-BBAR2 PPPoE tag: type=0103 length=0004 (Host Uniq) dat
Jan 5 15:09:49 | Got connection: d60a
Jan 5 15:09:49 | New PPP_ID: 0xd60a
Jan 5 15:09:49 | Saved Session ID: 0
Jan 5 15:09:49 | AC MAC address: <censored>
Jan 5 15:09:49 | Connect: ppp0 {--} nas0
Jan 5 15:09:50 | PAP authentication succeeded
Jan 5 15:09:50 | local IP address <censored>
Jan 5 15:09:50 | remote IP address <censored>
Jan 5 15:09:50 | PPPoE Connect with IP Address <censored>
Jan 5 15:09:50 | PPPoE Connection Successfully Established
Jan 5 15:09:50 | Renew PPPoE Session ID: 0xd60a
Jan 5 15:09:50 | PPPoE Connect with Gateway IP Address: <censored>
Jan 5 22:10:02 | onconnectWAN: cron has been disabled in the bootloader environment.

Miscellaneous information
Linux version 2.4.17_mvl21-malta-mips_fp_le (developers@RouterTech.Org) #1 Tue Jan 5 15:06:46 GMT 2010
BUILD=RouterTech_3.6.0D_20100105_2.92
VERSION=3.6.0D-RouterTech-4P-PSBL
BOARD=AR7RD
TARGET=psbl
FSSTAMP=20100105150919
Core logic version: 3.6.0D
Boot Loader: 1.4.0.4
ATM Driver version:[7.05.01.00]
DSL HAL version: [7.05.01.00]
DSP Datapump version: [7.05.01.00] Annex A
SAR HAL version: [01.07.2c]
PDSP Firmware version:[0.54]
Chipset ID: [Ohio250(7200/7100A2)]
Upstream rate (kbps): 892
Downstream rate (kbps): 8154
Trained Modulation:
Path Mode: sh: 1: unknown operand
FastPath
System uptime: 0 hr 12 min - 0 day(s), 0 hour(s), 12 minute(s), and 56 second(s) (system 84% idle)
WAN uptime: error: error_code=-1, err_msg=There is no container 'connection2'
Bandwidth usage:
Downloads : 17.3479 MB
Uploads : 0 MB
Line attenuation:
DS Line Attenuation: 0 DS Margin: 16
US Line Attenuation: 11 US Margin: 32
Memory usage:
In active use : 69% of 6248 kb
Available : 31% (1980 kb) of 6248 kb
Connection information: connection0
thechief wrote:For a firmware that was only released yesterday?
I mean the same problems exist at least since v2.92.
thechief wrote:To provide an alternative factual analysis...
As I can see, the difference is that I use pppoe. I don't know if it's important.
User avatar
thechief
RouterTech Team
RouterTech Team
Posts: 12067
Joined: Wed Feb 01, 2006 10:22 pm
Location: England, the Centre of Africa
Contact:

Re: RouterTech Firmware 2.93 Discussion

Post by thechief » Tue Apr 13, 2010 9:29 am

There have been some problems with pppoe. These are by no means universal, but where it is the only significant difference, then it must be a prime suspect. Before looking closer at the issue, post the output of these - from your Acorp firmware

Code: Select all

cat /proc/sys/net/ipv4/netfilter/ip_conntrack_buckets
cat /proc/sys/net/ipv4/netfilter/ip_conntrack_max
cat /proc/sys/net/ipv4/netfilter/ip_conntrack_generic_timeout
cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established
cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_close_wait
cat /proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeout
cat /proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeout_stream
The Chief: :afro: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
Thunderbird60
Newbie
Newbie
Posts: 9
Joined: Wed Mar 24, 2010 12:16 pm

Re: RouterTech Firmware 2.93 Discussion

Post by Thunderbird60 » Tue Apr 13, 2010 9:44 am

*********************************************************
* ADSL ROUTER ACORP LAN420M LAN 4-PORT (Annex A) *
*********************************************************
BusyBox v0.61.pre (2007.10.23-19:20+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

# cat /proc/sys/net/ipv4/netfilter/ip_conntrack_buckets
cat: /proc/sys/net/ipv4/netfilter/ip_conntrack_buckets: No such file or directory
# cat /proc/sys/net/ipv4/netfilter/ip_conntrack_max
1024
# cat /proc/sys/net/ipv4/netfilter/ip_conntrack_generic_timeout
60
# cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established
1200
# cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_close_wait
60
# cat /proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeout
30
# cat /proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeout_stream
180
#
User avatar
thechief
RouterTech Team
RouterTech Team
Posts: 12067
Joined: Wed Feb 01, 2006 10:22 pm
Location: England, the Centre of Africa
Contact:

Re: RouterTech Firmware 2.93 Discussion

Post by thechief » Tue Apr 13, 2010 10:04 am

Ok, I can see two significant differences from the RT settings. What about these

Code: Select all

cat /proc/sys/net/ipv4/netfilter/ip_conntrack_icmp_timeout
cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_be_liberal
cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_loose
cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_max_retrans
cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_close
cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_fin_wait
cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_last_ack
cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_max_retrans
cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_syn_recv
cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_syn_sent
cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_time_wait
The Chief: :afro: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
mstombs
RouterTech Team
RouterTech Team
Posts: 3753
Joined: Wed Jan 10, 2007 11:54 pm

Re: RouterTech Firmware 2.93 Discussion

Post by mstombs » Tue Apr 13, 2010 10:13 am

What does your Acorp report for DSL stats

This
DS Line Attenuation: 0 DS Margin: 16
US Line Attenuation: 11 US Margin: 32
Suggests something is wrong with the DSL / DSP drivers, I don't believe 0 DS Line attenuation, and the Upstream margin is the maximum possible to report 32. This suggests poor communication with the ISPs DSLAM.
j13mk
Newbie
Newbie
Posts: 6
Joined: Sat Feb 06, 2010 8:15 pm

Re: RouterTech Firmware 2.93 Discussion

Post by j13mk » Tue Apr 13, 2010 11:21 am

Hi, I can't upgrade to ver. 2.93 from 2.92. After upgrade is successful my G604T keep saying that I have v2.92. I was trying to upgrade few times now, and still have the same problem.
User avatar
thechief
RouterTech Team
RouterTech Team
Posts: 12067
Joined: Wed Feb 01, 2006 10:22 pm
Location: England, the Centre of Africa
Contact:

Re: RouterTech Firmware 2.93 Discussion

Post by thechief » Tue Apr 13, 2010 11:55 am

There are any number of reasons why that may be so, ranging from fragmentation of the environment, to not first unmounting minix or cifs or ftpfs partitions. Unless you provide more details, we will all be left guessing.

And see this: firmware-faq/#Adam2-upgrade-problems
The Chief: :afro: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
Thunderbird60
Newbie
Newbie
Posts: 9
Joined: Wed Mar 24, 2010 12:16 pm

Re: RouterTech Firmware 2.93 Discussion

Post by Thunderbird60 » Tue Apr 13, 2010 2:43 pm

thechief wrote:What about these

Code: Select all

# cat /proc/sys/net/ipv4/netfilter/ip_conntrack_icmp_timeout
30
# cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_be_liberal
1
# cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_loose
3
# cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_max_retrans
3
# cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_close
5
# cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_fin_wait
120
# cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_last_ack
30
# cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_max_retrans
300
# cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_syn_recv
60
# cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_syn_sent
120
# cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_time_wait
60
#
mstombs wrote:What does your Acorp report for DSL stats

Code: Select all

Modem Status
	
Connection Status 	  	Connected
Us Rate (Kbps) 	  	892
Ds Rate (Kbps) 	  	8154
US Margin 	  	30
DS Margin 	  	10
Trained Modulation 	  	ADSL_2plus_AnxM
LOS Errors 	  	5
DS Line Attenuation 	  	0
US Line Attenuation 	  	11
Peak Cell Rate 	  	2103 cells per sec
CRC Rx Fast 	  	0
CRC Tx Fast 	  	16
CRC Rx Interleaved 	  	156
CRC Tx Interleaved 	  	0
Path Mode 	  	Interleaved
DSL Statistics
	
Near End F4 Loop Back Count 	  	0
Near End F5 Loop Back Count 	  	0
mstombs wrote:Suggests something is wrong with the DSL / DSP drivers, I don't believe 0 DS Line attenuation, and the Upstream margin is the maximum possible to report 32. This suggests poor communication with the ISPs DSLAM.
I don't know if I can do anything here. Especially with the line. But as I can see, connection is stable. Up to 8Mbit/s.
Here is what I found out about this question:
Image
According to this, my line is fairly good.
User avatar
thechief
RouterTech Team
RouterTech Team
Posts: 12067
Joined: Wed Feb 01, 2006 10:22 pm
Location: England, the Centre of Africa
Contact:

Re: RouterTech Firmware 2.93 Discussion

Post by thechief » Tue Apr 13, 2010 4:14 pm

Ok, these are the different tcp settings:

Acorp firmware:
Acorp wrote: cat /proc/sys/net/ipv4/netfilter/ip_conntrack_max=1024
cat /proc/sys/net/ipv4/netfilter/ip_conntrack_generic_timeout=60
cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_be_liberal=1
RT firmware:
RT wrote: cat /proc/sys/net/ipv4/netfilter/ip_conntrack_max=6151 (or a lower number for ram-challenged routers)
cat /proc/sys/net/ipv4/netfilter/ip_conntrack_generic_timeout=120
cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_be_liberal=0
The only one that looks likely to cause significant differences in outcomes is "ip_conntrack_tcp_be_liberal". Opinion is divided as to whether and when it should be set to zero or one. However, to test the RT firmware on your router on the same basis as Acorp, you run do the following in the RT firmware (from a telnet/ssh login session)

Code: Select all

echo 1024 > /proc/sys/net/ipv4/netfilter/ip_conntrack_max
echo 60 > /proc/sys/net/ipv4/netfilter/ip_conntrack_generic_timeout
echo 1 > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_be_liberal
And then start your p2p sessions, and see if it makes any difference.

With regard to attenuations, a DS attenuation of 0 cannot be right. So there is definitely a problem there.

PS: you may also want to try manually setting the modulation to ADSL_G.dmt - it may be that the AnnexM or Adsl2 stuff is getting in the way.
The Chief: :afro: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
rseiler
Regular
Regular
Posts: 77
Joined: Tue Apr 28, 2009 8:54 pm

Re: RouterTech Firmware 2.93 Discussion

Post by rseiler » Tue Apr 13, 2010 6:03 pm

chief, thanks for the release, it has a number of interesting changes. I look forward to trying it. BTW, what command gives you what you quoted in your first post above? It looks a bit like a best-of RUC.
User avatar
thechief
RouterTech Team
RouterTech Team
Posts: 12067
Joined: Wed Feb 01, 2006 10:22 pm
Location: England, the Centre of Africa
Contact:

Re: RouterTech Firmware 2.93 Discussion

Post by thechief » Tue Apr 13, 2010 6:34 pm

rseiler wrote:chief, thanks for the release
You're welcome :)
rseiler wrote:BTW, what command gives you what you quoted in your first post above?
"ver" - best run from a telnet/ssh login session.
The Chief: :afro: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
cb
Novice
Novice
Posts: 30
Joined: Sat Apr 12, 2008 9:40 pm
Location: Newcastle-under-Lyme

Re: RouterTech Firmware 2.93 Discussion

Post by cb » Tue Apr 13, 2010 9:59 pm

RT Team,

Thanks for this latest release, not only have you fixed the problem with "ver" when not using encaps0, it has even more detail in it!

I can understand rationalising the dsp drivers to a low and high version, but was curious why for 1350A modems the high version is dsp71A instead of the dsp72A from RT 2.92.

Also, has something changed in the way chksync works - I had the "1 20" setting and saw a message in the log every 20mins with RT 2.92, but see nothing in RT 2.93 logs. Is it somehow not running now or just not logging?

Cheers.
Post Reply