Firmware 1.9.2.7 CR9

Printable View

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

15-03-2008, 14:02
Oleg

Firmware 1.9.2.7 CR9
Changes since 1.9.2.7-8:
- Added RTC support for the WL-HDD/WL-700g boards
- Fixed a bug causing lockups during reboot
- SNMP: uptime values no longer depends on the system time
- UPnP: it's now possible to select interface for which interface address reported back to clients (IP Config - Misc), port-forwards are working just like other virtual servers
- UPnP: additionally protected by built-in firewall in case when multicast forwards enabled
- IPTV: added udpxy (check IP Config - Miscellaneous: IPTV UDP Multicast to HTTP Proxy Port) to enable-disable it
- Added Get IP automatically option to the WAN & LAN page
- DHCP: added support for some broken DHCP servers (e.g. Golden Telecom)
- Manual DNS server entries are no longer added to routing table
- Fixed Redirects in the web-iface (it should no longer redirect to internal address);
- Enabled Idle Disconnect functionality for PPPoE/PPTP. It's recomended to turn this feature off by typing zero in this field.
- L2TP speed increase (up to 2.5 times compared to previous versions) and correct tunnel termination
- PPTP sync option is now correctly handled and enabled by default, improved overall stability, cleared up logs;
- Updated QuickSetup to recent PPPoE, PPTP and L2TP changes
- Added fine grained WPA control on the Wireless page: added separate WPA Enterprise, WPA2 Enterprise, WPA Personal, WPA2 Personal and WPA-Auto-Personal (which is wpa-psk + wpa2-psk for TKIP+AES, wpa-psk for TKIP and wpa2-psk for AES).
- Added Regulatory Mode field (802.11d/802.11h/off) to the Wireless - Advanced page. This should fix some problems with Intel WiFi cards (select 802.11d mode).
- Virtual Servers has now separate default action in the WAN to LAN firewall.
- Added Host Name field to the Manual DHCP MAC list.
- Added Comment field to Wireless - Access list.
- FTP: switched to vsftpd, reworked web-iface.
- Samba: extended web-iface, new share modes - all partitions, manual share list.
- Samba: Windows Vista support, W2K3SP1 compatibility
- Added utf8 as default encoding of the hard/flash drive (enabled by default).
- NFS: fixed some /etc/exports problems
Other changes:
- Kernel modules are now stored in single directory
- Added ftdi_sio usb to serial converter module
- Some other modules are now available as separate download (modules-1.9.2.7-9.tgz), includes HID, input, Bluetooth. Unpack them to /opt
- Added modprobe, which is looking for /opt/lib/modules/... by default.
- USB updates
- VLAN support fixes, updated robocfg
- dropbear 0.50 (credits to lly), enabled inetd support
- busybox_httpd fixes: new cgi environment vars (HTTP_HOST, CGI_*)
- Changed a way how automount works: everything is mounted to /tmp/mnt now, while /tmp/harddisk is just a symbolic link to first partition
- Samba/FTP/NFS relative paths are against /tmp/harddisk
- Added /usr/local/sbin/pre-mount to be called before automount (suitable to manual mounts, disk checks, etc).
- Added Enable USB Storage selection to the System Setup - Services page to enable usb storage modules to load automatically
- Added filesystem type autodetection to automount portition
Grab it here
15-03-2008, 21:00
tarosk

CR9 PPPoE Issue, FTP issue

I have PPPoE problem in this release.

After upgrade from CR8 to CR9 everything worked fine, until next restart.

After restart PPPoE stoped working. I seems pppd don't even try to authorize with only this lines in log:

Code:

Jan 1 01:00:10 pppd[92]: Plugin rp-pppoe.so loaded. Jan 1 01:00:10 pppd[92]: RP-PPPoE plugin version 3.3 compiled against pppd 2.4.2 Jan 1 01:00:10 pppd[93]: pppd 2.4.2 started by admin, uid 0 Jan 1 01:00:10 pppd[93]: Using interface ppp0 Jan 1 01:00:10 pppd[93]: local IP address 10.64.64.64 Jan 1 01:00:10 pppd[93]: remote IP address 10.112.112.112

Get IP address automaticaly was not enabled by default, so I enabled it, reboot with no success.

Next I tried factory reset - PPPoE does not work after performing quick setup or manual config.

Went back to CR8. Here is pppd syslog with correct PPPoE initialization (from CR8)

Code:

Jan 1 01:00:18 pppd[93]: Plugin rp-pppoe.so loaded. Jan 1 01:00:18 pppd[93]: RP-PPPoE plugin version 3.3 compiled against pppd 2.4.2 Jan 1 01:00:19 pppd[95]: pppd 2.4.2 started by admin, uid 0 Jan 1 01:00:19 pppd[95]: PPP session is 1892 Jan 1 01:00:19 pppd[95]: Using interface ppp0 Jan 1 01:00:19 pppd[95]: Connect: ppp0 <--> eth1 Jan 1 01:00:19 pppd[95]: PAP authentication succeeded Jan 1 01:00:19 pppd[95]: peer from calling number 00:90:1A:A0:01:AA authorized Jan 1 01:00:19 pppd[95]: local IP address 85.135.130.109 Jan 1 01:00:19 pppd[95]: remote IP address 212.55.224.33 Jan 1 01:00:19 pppd[95]: primary DNS address 195.28.64.99 Jan 1 01:00:19 pppd[95]: secondary DNS address 195.80.171.4

Another issue: ftp server freezes after login (success is logged in syslog) on sending directory listing.

Contact me if you need more logs or information.

Anyway thanks for great work on this custom firmware Oleg!
16-03-2008, 07:44
Oleg

Have you read release notes?

Quote:

Enabled Idle Disconnect functionality for PPPoE/PPTP. It's recomended to turn this feature off by typing zero in this field.
16-03-2008, 18:54
tarosk

Thanks for help, after setting "Idle Disconnect" PPPoE works fine. May be u could make this default :)

Anyway what about the FTP issue? accounts with "Read/Write" access to ftp_pub work OK, but for accounts with "Private" access does not work - connection "freezes" after sending password. Both ftp_pub and ftp_pvt exist and have same access control.

system log:

Code:

Mar 16 19:46:07 vsftpd[163]: CONNECT: Client "192.168.1.116" Mar 16 19:46:07 vsftpd[162]: [guest] OK LOGIN: Client "192.168.1.116" Mar 16 19:46:12 vsftpd[166]: CONNECT: Client "192.168.1.116" Mar 16 19:46:12 vsftpd[165]: [taro] OK LOGIN: Client "192.168.1.116"

ftp client:

Code:

ftp> o my.router Systém je připojen k my.router. 220 (vsFTPd 2.0.6) Uživatel (my.router:(none)): guest 331 Please specify the password. Heslo: 230 Login successful. ftp> ftp> o my.router Systém je připojen k my.router. 220 (vsFTPd 2.0.6) Uživatel (my.router:(none)): taro 331 Please specify the password. Heslo:

after typing password, there's no response (even if log says login is successful)

I tried to turn off passive mode, but with no luck.
17-03-2008, 06:23
jimmy_cr

Some problems after upgrade to CR9

Just FYI (asap I'll have some time I'll upgrade again and paste the errors from system log for you Oleg)

Upgraded from 1.9.2.7-7g to CR9. I've saved my old settings and FlashFS. After flashing CR9 I had to reboot WL500g manually (pwr off/pwr on). Power led was off, AIR+WAN+LAN leds showed activity before. After reboot I found some kernel errors in console - saying something about memory allocation with some memory/register dump. I tried reloading settings+flashfs from backup. I had to reboot manually again (pwr off/pwr on). Result was that OpenVPN was not working. So I reverted back to 1.9.2.7-7g, again reloaded settings+FlashFS from backup and everything works like a charm again.
17-03-2008, 18:15
jimmy_cr

Here is a part of log what I get after upgrade to CR9

Code:

Jan 1 01:00:14 kernel: lp driver: get device ID Jan 1 01:00:14 kernel: neg fail Jan 1 01:00:14 kernel: neg fail Jan 1 01:00:20 kernel: invalidate: busy buffer Jan 1 01:00:20 kernel: invalidate: busy buffer Jan 1 01:00:20 kernel: invalidate: busy buffer Jan 1 01:00:20 kernel: invalidate: busy buffer Jan 1 01:00:20 kernel: invalidate: busy buffer Jan 1 01:00:20 kernel: invalidate: busy buffer Jan 1 01:00:20 kernel: invalidate: busy buffer Jan 1 01:00:20 kernel: invalidate: busy buffer Jan 1 01:00:20 kernel: invalidate: busy buffer Jan 1 01:00:20 kernel: invalidate: busy buffer Jan 1 01:00:20 kernel: invalidate: busy buffer Jan 1 01:00:20 kernel: invalidate: busy buffer Jan 1 01:00:20 kernel: Unable to find swap-space signature Jan 1 01:01:01 /opt/sbin/cron[137]: (admin) CMD (run-parts /opt/etc/cron.hourly) Jan 1 01:01:33 kernel: kernel BUG at ll_rw_blk.c:934! Jan 1 01:01:33 kernel: Unable to handle kernel paging request at virtual address 00000000, epc == 800be894, ra == 800be894 Jan 1 01:01:33 kernel: Oops in fault.c::do_page_fault, line 192: Jan 1 01:01:33 kernel: $0 : 00000000 1000dc00 0000001f 00000001 00000020 802de000 803b63a0 0000001f Jan 1 01:01:33 kernel: $8 : 801f39c8 8020d31d 00000000 00000000 fffffff9 ffffffff 0000000a 00000002 Jan 1 01:01:33 kernel: $16: 00000001 00000002 0006bd9c 80a01694 00000001 8074a900 80a016bc 00000000 Jan 1 01:01:33 kernel: $24: 802dfcca 00000002 802de000 802dfe00 00000002 800be894 Jan 1 01:01:33 kernel: Hi : 00000000 Jan 1 01:01:33 kernel: Lo : 00000002 Jan 1 01:01:33 kernel: epc : 800be894 Tainted: P Jan 1 01:01:33 kernel: Status: 1000dc03 Jan 1 01:01:33 kernel: Cause : 8000000c Jan 1 01:01:33 kernel: Process kupdated (pid: 6, stackpage=802de000) Jan 1 01:01:33 kernel: Stack: 801b57ec 801b5804 000003a6 80a016a0 00000001 00000400 80817de0 Jan 1 01:01:33 kernel: 00000002 00002000 00000400 8074a900 00000002 0006bd9c 00000002 00000001 Jan 1 01:01:33 kernel: 00000006 00000001 00000010 807efd28 800be9f0 00000000 00000000 00000000 Jan 1 01:01:33 kernel: 00000000 00000000 00000000 8074a900 00000002 00000001 00000001 00000000 Jan 1 01:01:33 kernel: 800beb2c 00000000 800ee768 800ee828 80119210 00000003 802dfee0 80037e28 Jan 1 01:01:33 kernel: 00000004 ... Jan 1 01:01:33 kernel: Call Trace: [<801b57ec>] [<801b5804>] [<800be9f0>] [<800beb2c>] [<800ee768>] Jan 1 01:01:33 kernel: [<800ee828>] [<80119210>] [<80037e28>] [<80037ed8>] [<800395b0>] [<80037fa4>] Jan 1 01:01:33 kernel: [<80074058>] [<8000cea8>] [<8004f188>] [<8003c768>] [<8003c738>] [<8003cc1c>] Jan 1 01:01:33 kernel: [<8003cb2c>] [<8003ca0c>] [<8003ca0c>] [<80003304>] [<8000f5c4>] [<800111cc>] Jan 1 01:01:33 kernel: [<800032f4>] Jan 1 01:01:33 kernel: Jan 1 01:01:33 kernel: Code: 24a55804 0c0043f5 240603a6 <0802f8a2> aee00000 27bdffd0 afb40028 afb20020 afb1001c

I'm using FLASHDISK with OpenVpn and of course I have
/usr/local/sbin/post-mount

Code:

#!/bin/sh swapon /dev/discs/disc0/part2

/usr/local/sbin/post-boot

Code:

#!/bin/sh insmod /lib/modules/2.4.20/kernel/drivers/scsi/scsi_mod.o insmod /lib/modules/2.4.20/kernel/drivers/scsi/sd_mod.o insmod /lib/modules/2.4.20/kernel/drivers/usb/storage/usb-storage.o mount /dev/discs/disc0/part1 /opt i=0 while [ $i -le 30 ] do if [ -d /opt/etc ] then break fi sleep 1 i=`expr $i + 1` done # Activate swap swapon /dev/discs/disc0/part2 # Run all active services - active means starts with S /opt/etc/init.d/rc.unslung

/usr/local/sbin/post-firewall

Code:

#!/bin/sh #OpenVPN access from WAN iptables -D INPUT -j DROP iptables -A INPUT -p tcp --dport 1194 -j ACCEPT iptables -t nat -A PREROUTING -i vlan1 -p tcp --dport 1194 -j DNAT --to-destinat ion $4:1194 iptables -A INPUT -j DROP iptables -D INPUT -j DROP # Allow TUN interface connections to OpenVPN server iptables -A INPUT -i tun+ -j ACCEPT # Allow TUN interface connections to be forwarded through other interfaces iptables -A FORWARD -i tun+ -j ACCEPT iptables -A INPUT -j DROP
18-03-2008, 16:19
wiz

CR9 breaks scanner

I've succesfully updated from cr8 to cr9, now my scanner refuses to work. If I downgrade to cr8 again scanner works like a charm.

I've updated the sane backends to the newest version, then it says following:

Code:

08/3/18@17:10:06: DEBUG: 351 {cnf_start_services} Started service: saned 08/3/18@17:10:06: DEBUG: 351 {cnf_start_services} mask_max = 6, services_started = 1 08/3/18@17:10:06: NOTICE: 351 {main} xinetd Version 2.3.14 started with no options compiled in. 08/3/18@17:10:06: NOTICE: 351 {main} Started working: 1 available service 08/3/18@17:10:06: DEBUG: 351 {main_loop} active_services = 1 08/3/18@17:10:15: DEBUG: 351 {main_loop} select returned 1 08/3/18@17:10:15: DEBUG: 351 {server_start} Starting service saned 08/3/18@17:10:15: DEBUG: 352 {exec_server} duping 7 08/3/18@17:10:15: DEBUG: 351 {main_loop} active_services = 1 08/3/18@17:10:15: ERROR: 352 {exec_server} execv( /opt/sbin/saned ) failed: No such file or directory (errno = 2)

Off course there is a /opt/sbin/saned present but that won't work

putting sane backends back to 1.0.18+cvs20061127-1

Code:

08/3/18@17:15:54: NOTICE: 393 {main} xinetd Version 2.3.14 started with no options compiled in. 08/3/18@17:15:54: NOTICE: 393 {main} Started working: 1 available service 08/3/18@17:15:54: DEBUG: 393 {main_loop} active_services = 1 08/3/18@17:16:01: DEBUG: 393 {main_loop} select returned 1 08/3/18@17:16:01: DEBUG: 393 {server_start} Starting service saned 08/3/18@17:16:01: DEBUG: 394 {exec_server} duping 7 08/3/18@17:16:01: DEBUG: 393 {main_loop} active_services = 1 08/3/18@17:16:01: DEBUG: 393 {main_loop} active_services = 1 08/3/18@17:16:01: DEBUG: 393 {main_loop} select returned 1 08/3/18@17:16:01: DEBUG: 393 {check_pipe} Got signal 18 (Continued) 08/3/18@17:16:01: DEBUG: 393 {child_exit} waitpid returned = 394 08/3/18@17:16:01: DEBUG: 393 {server_end} saned server 394 exited 08/3/18@17:16:01: INFO: 393 {conn_free} freeing connection 08/3/18@17:16:01: DEBUG: 393 {child_exit} waitpid returned = -1 08/3/18@17:16:01: DEBUG: 393 {main_loop} active_services = 1

Anyone an idea why sane don't work with cr9?

Seems it is related to scanner.o. It does load, but sane-find-scanner does not find any scanner. IN cr8 it works flawlessly...
20-03-2008, 10:27
sebw

I see that the separate download modules include scsi_mod, sd_mod and usb-storage.

It may be a silly question, but, I presume the modules are also still part of the main firmware, since without them how can one mount a drive to opt? Is this a bit of unnecessary duplication or am I missing the point?
20-03-2008, 10:52
al37919

Yes it is a bit of unnecessary duplication
20-03-2008, 11:14
Oleg

Quote:

Originally Posted by wiz

Seems it is related to scanner.o. It does load, but sane-find-scanner does not find any scanner. IN cr8 it works flawlessly...

There are was huge number of kernel updated, so most likely scanner.o should be recompiled with current kernel.
20-03-2008, 11:17
Oleg

Quote:

Originally Posted by jimmy_cr

Here is a part of log what I get after upgrade to CR9

Why do you activate swap twice?

Why do you load scsi stuff manually? This is no longer needed (check release notes). If you want to do this on your own - disable usb storage in the web iface.

You've to fix this first, before blaming if something does not work.

BTW, I've OpenVPN running on my router and "it works like a charm".
20-03-2008, 11:22
Oleg

Quote:

Originally Posted by tarosk

Thanks for help, after setting "Idle Disconnect" PPPoE works fine. May be u could make this default :)

It should be 0 by default, but looks like you've not resetted your router to default or used old config, right?

Quote:

Anyway what about the FTP issue? accounts with "Read/Write" access to ftp_pub work OK, but for accounts with "Private" access does not work - connection "freezes" after sending password. Both ftp_pub and ftp_pvt exist and have same access control.

Private directories should be created manually (just like home directories in real unixes). So you've to create ftp_pvt/taro first.
20-03-2008, 18:44
jimmy_cr

Quote:

Originally Posted by Oleg

Why do you activate swap twice?

Why do you load scsi stuff manually? This is no longer needed (check release notes). If you want to do this on your own - disable usb storage in the web iface.

You've to fix this first, before blaming if something does not work.

BTW, I've OpenVPN running on my router and "it works like a charm".

Oleg thanks for kicking my ass "the right way". I've never said, that your firmware sucks or something similar against it. All I need was some advice and you gave it to me - so thanks, now everything works as expected ;)

Maybe I should ask directly ;)
20-03-2008, 19:14
Oleg

Quote:

Originally Posted by Oleg

There are was huge number of kernel updated, so most likely scanner.o should be recompiled with current kernel.

BTW, newer scanner.o is included in the modules-1.9.2.7-9.tgz .
21-03-2008, 10:11
wiz

Quote:

Originally Posted by Oleg

There are was huge number of kernel updated, so most likely scanner.o should be recompiled with current kernel.

thanks Oleg, I'll give it a go to try to build it myself. If I get it working I'll put a posting in the sane thread and attach the new scanner.o.

regards,

Wiz

Hmmz, just read yr posting about it being available already in the modules gz. I'll give it a go tonight, am using the connection at the moment to work, so once I am done I will give it a go.
21-03-2008, 13:29
akbor

Hi,

I discovered following minor bugs with my WL-HDD and FW release 1.9.2.7-9. Sorry that I post to the wrong sub-forum, but I'm pretty sure, there is no way to get an answer in the WL-HDD sub-forum...

1. The RTC works with 1.9.2.7-9 on WL-HDD well, but I didn't found a way to eliminate following error message from the system log:

Code:

Mar 21 13:59:12 kernel: ***RTC BATTERY FAILURE***

the battery is definitely OK and not faulty, 3,2 V measured

2. The behaviour of the reset button has changed. I wanted to shut down my WL-HDD, but I couldn't. After pressing the reset button down and waiting a couple of seconds, till the power LED is off and releasing the button WL-HDD didn't go in OFF state - it made a restart!

P.S./EDIT: On my other device WL-500gP the behaviour of the reset button is different, but either not like described in the 1.9.2.7-6 (last change of the reset behaviour) release note

Code:

Restore to defaults/shutdown are now called using RESTORE/RESET button as follows: first 3 seconds - power LED on: release button to do nothing next 5 seconds - power LED off: release button to "shutdown" next 5 seconds - power LED blinking: release button to reset to defaults start over

the power LED starts to blink immediately (approx. 1 sec) after pressing the reset button down. Of course I didn't want to set my device to default, so I waited several seconds till the power LED stopped blinking. There was no way to shut down the device with the reset button.

P.P.S./EDIT2: ok, I must be blind, have not seen "Disabled "power off" for all units except WL-HDD" statement in the 1.9.2.7-7g release note. So please forget the WL-500gP issue, but WL-HDD does definitely restart instead of shut down.

That's just my feedback to the new FW release.

Regards

Robert
21-03-2008, 15:38
Oleg

Quote:

Originally Posted by akbor

the battery is definitely OK and not faulty, 3,2 V measured

Well, this is just what RTC chip reports.

Quote:

2. The behaviour of the reset button has changed. I wanted to shut down my WL-HDD, but I couldn't. After pressing the reset button down and waiting a couple of seconds, till the power LED is off and releasing the button WL-HDD didn't go in OFF state - it made a restart!

This is strange. Just checked with WL-700g: it halts using same code. Unfortunately I've no idea how to debug this. :( Nothing is changed in this path... Perhaps something is crashing during halt, causing a reboot... Someone should recompile my firmware and play with shutdown stuff. Personally I do not have wl-hdd, so I could not play with it.

Actually I could prepare some test versions, but I need "interactive answers". If someone is ready to do the testing today - let me know.

BTW, this is the last firmware which supports WL-HDD. In newer sources broadcom removed support for BCM4702 CPU.
21-03-2008, 16:15
wiz

Quote:

Originally Posted by Oleg

BTW, newer scanner.o is included in the modules-1.9.2.7-9.tgz .

replaced scanner.o with the one from modules, works like a charm again. Thanks Oleg for the update of the firmware.

cheers,

Wiz
21-03-2008, 16:42
Oleg

So, WL-HDD owners.

I've built 11 test versions: http://oleg.wl500g.info/wlhdd/

Test one by one: flash, issue halt command and check if it really halts your unit or reboots. At first try 9.1.1 and 9.1.12. If both reboots, let me know and don't flash other firmwares...

Find out which versions work and which does not and let me know your findings.
21-03-2008, 17:42
akbor

Hello Oleg,

thank you for fast reaction and for support! I'm ready to test the FW files and to give you answers due to power down issue.

I tested the first two firmwares 9.1.1 and 9.1.2 (I think 9.1.12 was a typo?)

9.1.1 doesn't reboot but it doesn't go in power down either. After holding the reset button down for a couple of seconds the power LED goes off, but the WLAN LED stays on and WL-HDD stays in this state (power LED = off, WLAN LED = on) and doesn't do anything else. I've tested it twice.

9.1.2 has the same behaviour. Also tested twice.

Should I go on with 9.1.3 - 9.1.11?

Regards

Robert
21-03-2008, 17:57
Oleg

Yes, try all firmwares.
21-03-2008, 18:01
Oleg

Actually device halts, but does not turn some of the features off.

We've to figure out which one is causing reboot.
21-03-2008, 18:06
akbor

1.9.3 - same behaviour (no reboot, power LED = off, WLAN LED = on), flashing 1.9.4 ...

1.9.4 - same behaviour (no reboot, power LED = off, WLAN LED = on), flashing 1.9.5 ...

1.9.5 - same behaviour (no reboot, WLAN LED stays on), trying 1.9.6 ...

1.9.6 - same behaviour (no reboot, WLAN LED stays on), trying 1.9.7 ...

1.9.7 - same behaviour (no reboot, WLAN LED stays on), trying 1.9.8 ...

1.9.8 - same behaviour (no reboot, WLAN LED stays on), trying 1.9.9 ...

1.9.9 - same behaviour (no reboot, WLAN LED stays on), trying 1.9.10 ...
21-03-2008, 18:47
akbor

Yes, I think, I've got it! 1.9.10 makes reboot. Which feature could make problems in this version?
21-03-2008, 19:04
Oleg

Bringing WiFi interface down.

Try new image 9.1.12.
21-03-2008, 19:08
akbor

on the way
21-03-2008, 19:14
akbor

yes, 9.1.12 makes shut down, all LEDs are off!
21-03-2008, 19:15
Oleg

ok, wait for yet another (final attempt). :)
21-03-2008, 19:21
Oleg

well, let's leave 9.1.12 solution for now.
21-03-2008, 19:27
akbor

OK, thank you very much! ñïàñèáî ;)

Regards

Robert
21-03-2008, 19:29
Oleg

In the mean time I would release 1.9.2.7-9a with this fix, plus some minor fixes. This would be the last firmware with WL-HDD support.
21-03-2008, 19:45
akbor

Would you mind, if I'll post this information in the German part of the forum? Maybe somebody else has noticed some other bugs. If 1.9.2.7-9a will be defenitely the last version supporting WL-HDD it makes absolutely sense - you could improve the last version. What do you think?

Regards

Robert
21-03-2008, 20:11
Oleg

ok, no problems.
22-03-2008, 08:50
wiz

wan disconnects / udhcpc question

since I am running with cr9 I get disconnected from the internet again. I use automatic ip config, so if I go to the webpages and do a disconnect and then a reconnect every thing goes again.

In the previous firmwares in the logfiles I did see dhcp renewals, I have not seen this in the cr9 release. So I am thinking I do not get a dhcp renewall. Anyone else with auto ip config running with cr9 that sees similar behavior?

When I do a manual release I see the following in the syslog:

Code:

Mar 22 09:34:27 udhcpc[100]: Unicasting a release of MY.IP.ADDRESS to 84.245.2.1 Mar 22 09:34:27 udhcpc[100]: Entering released state Mar 22 09:34:31 udhcpc[100]: Performing a DHCP renew Mar 22 09:34:31 udhcpc[100]: Lease of MY.IP.ADDRESS obtained, lease time 14400

So this makes me think there's nothing wrong with the firewall settings, else a manual renew would fail too.
22-03-2008, 11:59
Oleg

This firmware was tested by number of guys here in Russia before it was released. 99% are using dhcp in different flavors and has not reported any problems... So, I beleive this is not a firmware problem.

You could try flashing old firmware and compare the output: it's the same.
22-03-2008, 12:29
wiz

I have no doubts it has been tested Oleg, I just don't see any renewall statements in my syslog anymore after the update.

I will put cr8 back to see if that helps.
22-03-2008, 15:48
wiz

I've put cr8 back and left the asus for a while.

Code:

Mar 22 15:32:12 udhcpc[105]: Lease of MY.IP.ADDRESS obtained, lease time 14400

Asus was booted around 13:30, so this is roughly half way through the lease time it renewed the ip address. Seems it works correctly with cr8. I'll stick to that release for now.
22-03-2008, 15:51
Oleg

Well, give me complete cr9 log then.
22-03-2008, 16:30
ericguo

NTFS support is broken in CR9?

I have a USB harddrive formated in NTFS filesystem. the CR9's kernel couldnn't support to read/write it. the CR8 can.
22-03-2008, 17:00
Oleg

NTFS never was writable. As for CR9 - it still works fine:

[root@WL-0018F33285EF root]$ 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/part1 on /tmp/mnt/disc0_1 type ntfs (ro)

Mar 22 19:52:04 kernel: hub.c: new USB device 01:03.0-1, assigned address 2
Mar 22 19:52:04 kernel: scsi0 : SCSI emulation for USB Mass Storage devices
Mar 22 19:52:04 kernel: Vendor: Model: Rev:
Mar 22 19:52:04 kernel: Type: Direct-Access ANSI SCSI revision: 02
Mar 22 19:52:04 kernel: Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
Mar 22 19:52:04 kernel: SCSI device sda: 1013000 512-byte hdwr sectors (519 MB)
Mar 22 19:52:04 kernel: sda: Write Protect is off
Mar 22 19:52:04 kernel: Partition check:
Mar 22 19:52:04 kernel: p1
Mar 22 19:52:04 kernel: WARNING: USB Mass Storage data integrity not assured
Mar 22 19:52:04 kernel: USB Mass Storage device found at 2
Mar 22 19:52:08 USB storage: ntfs(ro) fs at /dev/discs/disc0/part1 mounted to /tmp/mnt/disc0_1
Mar 22 19:54:39 vsftpd[245]: CONNECT: Client "192.168.0.4"
Mar 22 19:54:39 vsftpd[244]: [ftp] OK LOGIN: Client "192.168.0.4", anon password "?"
Mar 22 19:54:41 vsftpd[246]: [ftp] OK DOWNLOAD: Client "192.168.0.4", "/IMG_4599.jpg", 732289 bytes, 5019.34Kbyte/sec

If does not work for you - post system log then.

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