Printable View
I even don't know in which circumstances this happens on you router, how you achieve it, was this works on alternative firmwares, etc. So I can't help without such information.Quote:
Originally Posted by cichy
Either you should explain problem in detail, or only somebody who use NFS/RPC exactly same as you can help.
P.S. NFS is not enabled by default.
1. Very good indeed! :D
2. Yes, you would think that "reboot" would work from Putty but the problem is when is it not :p I've tried "reboot", rebooting from the webinterface etc. but now I've reseted (by removing the electricity cord) and restored the whole shit. But I'll definitively download the latest compiled version and flash and re-do everything when I find the time =)
Thanks a lot for the answers! :cool:
PS. Love the smileys on this forum
Quote:
Originally Posted by wpte
Regarding last issue i've posted here, well it's all gone there's no more such error. But now i've noticed something else, that wasn't there.
Code:Jun 27 12:16:03 smbd[222]: [2009/06/27 12:16:03, 0] lib/util_sock.c:read_socket_data(477)
Jun 27 12:16:03 smbd[222]: read_socket_data: recv failure for 4. Error = No route to host
Quote:
Originally Posted by cichy
- "error" from your first post means that something send bad RPC request to NFS server on router, nothing more. I can't imagine what program on which host it can be.
- "error" from your next post means either bad record in routing table or lost link to specific host. This is not a firmware bug too.
Glad to hear this, so i'll try to find whatever causes these errors.
P.S. Is there any thread about using NTFS-3G on oleg's firmware?
As I know, dedicated thread is absent, since NTFS-3G is not supported on stock kernels 2.4.20. Some volunteers from Russian thread perform tests of NTFS-3g on our beta firmware, and found it working, but transfer speed is ugly small ~1.5 Mb/s due to CPU limitation.Quote:
Originally Posted by cichy
So i'll stay with ext3. Thanx lly
Just wondering, is it possible to turn on asynchronous io?
or get it compiled for olegs?
since I believe this means it's turned off?
I guess it might optimize disk speeds a lot:)Quote:
cat /proc/slabinfo | grep kio
kiobuf 0 0 64 0 0 1
and ibm says it's available in patches for 2.4:
http://www.ibm.com/developerworks/li...brary/l-async/
there's no aio support in 2.4 vanila kernel, and the latest andrea's patch is from 05-Oct-2003
http://www.kernel.org/pub/linux/kern.../2.4.23aa1.bz2
so that's a no go then?Quote:
Originally Posted by theMIROn
that means if someone would prepare patches for 2.4.37.2 kernel, it'll be includedQuote:
Originally Posted by wpte
I guess the effect will be minimal. Some days I included epoll patch since some people ask me to do that. Unfortunately, nobody done performance tests (including people who promise that to me), and I ever not sure that epoll working 100% correctly :(Quote:
Originally Posted by wpte
So, without serious reasons or any performance tests on our platform (not on x86!), I don't want to include aio into firmware.
P.S. There is no aio support for our platform in uClibc 0.9.29
yeh... it doesn't always give a performance boosts on IOQuote:
Originally Posted by lly
but the idea that it lowers the cpu usage, wich comes quite handy, or at least giving other processes processor time so that the cpu is used better is quite a good thing. Especially when you consider that most routers here use swap (wich is io) to have enough memory, this might actually work even if it's only working for the cpu performance.
yeh, it's still theory:o
You don't mind if I try to program a good patch for olegs I hope?
maybe my c programming skillzz are good enough already:p
If you really decide to spend a lot of time on this task, than I expect definite results :) i.e. we will know amount of performance boost on our platform, at least.Quote:
Originally Posted by wpte
P.S. Unfortunately, 2.4 kernels are very old :(
Well I can't promise you that I will get it working since it will be my first linux programming... I've only done embedded c so far.Quote:
Originally Posted by lly
but since there are so many linux source codes out there, I guess I can make it trough:p
hi all,
i'm using hyuwei e220 umts modem and koppel fw to connect to the internet
but i'd like to switch to this evolving fw.
does anybody knows if this modem is supported in precompiled version or by
additional module? sorry, but i'm unable to compile it from svn.
as i remember i've tried to implement driver in original Oleg firmware but give
up as even with proper module the modem was initialised to flash disk by
default and no chance to switch to its serial interface [that modem is build from
two interfaces, small flash disk where win drivers are stored and modem
device. unfortunately that first is by default initiated by driver. koppel uses
some script with module load parameters but it was not working for me on Oleg
fw].
does anybody seen any how-to with "manual" set up of dial script and pppd on
wl500?
thanks in advance
piotr
Hi piotr ,
I rencently asked the same question!
I'm using this new Firmware now for half a year, runs pretty stable, has more basic functionallity and Samba transfers from USB harddisks are much faster than in other firmwares!
But .... in the web-if there's no USB modem option
As I could see in the blog entries, all the drivers are already included!
The reply to my question concerning UMTS-modem was, to take the init-scripts from koppel firmware and put them in the same directory stucture on the current firmware.
But I've never tried it so far.
Regards, Thomas
Transferring koppel scripts one-to-one wouldn't bring positive result. We already has plans to add support of USB modems via web-GUI, but this task is really big.Quote:
Originally Posted by preacher@wl500g
Any real help (patches, corrected scripts) will be accepted with pleasure.
Well, as I could see somebody found a solution.
in the german forum someone wrote an answer to my question concerning ppp scripts on your firmware:
http://wl500g.info/showpost.php?p=142506&postcount=238
He suggested to copy settings and scripts form koppel firmware and execute the script mentioned.
It seemed to me, that this worked for him.
But i didn't try so far as I am happy with the features of your firmware and other people to whom I suggested an ASUS router come along with the features of koppel firmware.
thank you preacher! what i see the script deals with initialisation of modem toQuote:
Originally Posted by preacher@wl500g
second interface [serial modem]. i'll try to set it up that way and inform about results.
regards
piotr
Your're welcome!Quote:
Originally Posted by dzebrys
I'm used to Linux, but no crack in script programming, so I didn't know.
I think we are all interested in good functionallity, so if I found something interesting in another language forum, I will post it here.
Regards
Thomas
I'm trying to compile and run a program that needs libusb.
(libk8055 from sourceforge)
When I just try to compile it (native), it fails on:
error: usb.h: No such file or directory
If I include "usb.h" from libusb-compat-0.1.3 and try to compile it, it fails on:
/opt/bin/ld: warning: libusb-1.0.so.0, needed by /usr/lib/libusb.so, not found (try using -rpath or -rpath-link)
/usr/lib/libusb.so: undefined reference to `libusb_release_interface'
/usr/lib/libusb.so: undefined reference to `libusb_get_device_descriptor'
/usr/lib/libusb.so: undefined reference to `libusb_control_transfer'
/usr/lib/libusb.so: undefined reference to `libusb_claim_interface'
/usr/lib/libusb.so: undefined reference to `libusb_set_configuration'
If I first make and install libusb-1.0.2 and libusb-compat-0.1.3 to /opt, followed by trying to compile the program, fails on:
/opt/bin/../lib/libusb-1.0.so.0: undefined reference to `pthread_mutex_trylock'
collect2: ld returned 1 exit status
However, on old oleg-firmware it compiles and runs fine (after installing ipkg libusb), but that is libusb-0.1.12.
If I try to use the binary compiled against libusb-0.1.12 on the new firmware, it gives:
can't load library 'libusb-0.1.so.4'
If I install the ipkg libusb on the new firmware, and try the binary compiled against libusb.0.1.12, it begins to run, but then reboots the router...
Any idea's how to solve this?
I remember using this one here: http://libusb.wiki.sourceforge.net/
worked out perfectly fine for me:confused:
I wasn't compiling libk8055 tho;)
In the meantime I solved the pthead error, by adding -lpthread to libs in the Makefile.
And I found out, the libk8055 isn't functioning with libusb-compat.
But on old oleg it gives an error, while on new oleg it just cold-boots the router ;(
Quite off-topic, but many thanks for this great firmware!
since the libk8055 doesn't work with libusb-compat and doesnt work with libusb-0.1.12 on new oleg, I ported it to libusb1.0.
I tested the ported source on i368 ubuntu -> here it works with libusb-1.0
However on the asus it doesn't work. Enabling debug mode, gives me the error: [calculate_timeout] failed to read monotonic clock.
So I patched io.c from libusb-1.0 and changed all occurences of usbi_backend->clock_gettime in to clock get_time. (like it used to be)
This solves the error. However now running the program again cold boots my router.
Reverting to old oleg and the program now gives the error:
libusb:warning [handle_bulk_completion] unrecognised urb status -130
libusb:warning [do_sync_bulk_transfer] unrecognised status code 1
intr error -99
I'm starting to get lost on this one :(
HI I'm using lastest oleg's firmware and I tried to run passive ftp over vsftpd. Everythink is O.K. but I have to open one specific port for this connestion forever. But I think that firewall could open this port automaticly without hard wite rule in iptables. i think it depend on any module
modprobe ip_tables
modprobe ip_conntrack
modprobe ip_conntrack_ftp
modprobe ip_conntrack_irc
modprobe iptable_nat
modprobe ip_nat_ftp
Do you know how to run this?Is possible to run it?
thanks a lot
This should sounds like "works with libusb-1.0 + kernel 2.6"!Quote:
Originally Posted by DrChair
Since r379 bundled libusb-1.0 already has similar patchQuote:
However on the asus it doesn't work. Enabling debug mode, gives me the error: [calculate_timeout] failed to read monotonic clock.
Probably, bug in kernel. Which firmware build you use? Can problem be reproduced without specific hardware? If yes, please provide modified sources of libk8055 & simple test case, we will try to fix it.Quote:
However now running the program again cold boots my router.
You enabled IMQ in newest revision.
Is it possible to do some QoS with it?
It is under tests now, but I hope, yes. Unfortunately, there will no web-GUI until someone contribute it.Quote:
Originally Posted by Lesiuk
is there any chance that a ppp_mppe module can be added to the kernel?:)
I do not need webui, i like do everything in console.Quote:
Originally Posted by lly
It's great news.
Maybe you need some help?
Do you use jabber/xmpp ?
CONFIG_PPP_MPPE_MPPC=y is set for years in Oleg-based firmwares...Quote:
Originally Posted by wpte
Maybe I understand your wrong?
sorry, I didn't knew it was enabled already:)Quote:
Originally Posted by lly
Oke, for now I assume libusb-1.0 (and compat-libusb) isn't full compatible with the current kernel.Quote:
Originally Posted by lly
So let's try to find out why the the libusb-0.1 version crashes the router.
If I remove the USB device, the program doesn't crash the router. So I guess you need the specific hardware.
However I can reproduce the problem with an usb-mouse (with also uses interrupt transfers)
I'll PM you the details...
Anyway, I spend the whole day compiling different revisions of the firmware.
R334 is the last one that works (with the libusb-0.1 version)
R335 and R336 don't compile
R337 has the problem.
So the problem is caused by "Add missed urb->interval initialization for usbdevfs"
Problem reproduced, thanks to report.Quote:
Originally Posted by DrChair
As workaround you simply can exclude kernel/242-usb-devio.patch from custom build process. This patch repairs EHCI(2.0), but broke UHCI(1.1) drivers interface via usbdevfs ioctl calls. It will take some time to find proper solution.
Great FW with great options :)
I wonder if there's a possibility to add a file called version in /etc/ directory with actual firmware version and a name of OS the router is running (i know there's a .version in / dir but it's read-only). I'm asking that coz i found something like that http://phpsysinfo.sourceforge.net/ and it gives great info about router (i added nslu icon and it's being recognized as Oleg's Firmware after finding /etc/version file). I know that this is something stupid but i think it's quite useful :)
/etc directory is writeable, as in all Oleg FW. File "/.version" must be read-only. OS version you can get from uname utility or from /proc/versionQuote:
Originally Posted by cichy
In r461 we add experimental accel-pptp kernel driver, which should significantly improve PPTP speed. Please help us to test it.
To turn it on you have to do:
nvram commit is superfluous, since there is not needed that driver will start after reboot or crash.Code:nvram set wan0_pptp_kernel=1
After this, push "Disconnect", wait 10 sec, push "Connect" in web-GUI.
Syslog should have lines like below:
p.s automatic reconnect don't work for now.Code:Aug 18 08:39:26 wan: connected manually
Aug 18 08:39:29 kernel: vlan1: Setting MAC address to xx xx xx xx xx xx.
Aug 18 08:39:29 post-firewall: started [ppp0 0.0.0.0 br0 192.168.0.1 vlan1 xxx.xxx.xxx.xxx]
Aug 18 08:39:30 pptp[258]: Plugin pptp.so loaded.
Aug 18 08:39:30 pptp[258]: PPTP plugin version 0.8.3 compiled for pppd-2.4.5, linux-2.4.37.5
Aug 18 08:39:30 pptp[259]: pppd 2.4.5 started by admin, uid 0
Aug 18 08:39:30 pptp[259]: PPTP: failed to setsockopt PPTP_SO_TIMEOUT (Operation not supported)
Aug 18 08:39:30 pptp[260]: anon log[callmgr_main:pptp_callmgr.c:132]: IP: xxx.xxx.xxx.xxx
Aug 18 08:39:30 pptp[260]: anon log[callmgr_main:pptp_callmgr.c:136]: control connection
Aug 18 08:39:30 pptp[260]: anon log[callmgr_main:pptp_callmgr.c:140]: unix_sock
Aug 18 08:39:30 pptp[261]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 'Start-Control-Connection-Request'
Aug 18 08:39:30 pptp[261]: anon log[ctrlp_disp:pptp_ctrl.c:737]: Received Start Control Connection Reply
Aug 18 08:39:30 pptp[261]: anon log[ctrlp_disp:pptp_ctrl.c:771]: Client connection established.
Aug 18 08:39:31 pptp[261]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 'Outgoing-Call-Request'
Aug 18 08:39:31 pptp[261]: anon log[ctrlp_disp:pptp_ctrl.c:856]: Received Outgoing Call Reply.
Aug 18 08:39:31 pptp[261]: anon log[ctrlp_disp:pptp_ctrl.c:895]: Outgoing call established (call ID 2, peer's call ID 22850).
Aug 18 08:39:31 pptp[259]: Using interface ppp0
Aug 18 08:39:31 pptp[259]: Connect: ppp0 <--> pptp (xxx.xxx.xxx.xxx)
Aug 18 08:39:33 pptp[259]: CHAP authentication succeeded
Aug 18 08:39:33 pptp[259]: local IP address xxx.xxx.xxx.xxx
Aug 18 08:39:33 pptp[259]: remote IP address xxx.xxx.xxx.xxx
Aug 18 08:39:33 post-firewall: started [ppp0 xxx.xxx.xxx.xxx br0 192.168.0.1 vlan1 xxx.xxx.xxx.xxx]
Aug 18 08:39:33 ddns: IP address has not changed since the last update
Aug 18 08:39:33 PPTP: connected to ISP
New firmware already in place but now i'm getting this error:
Although settings were the same as in earlier version and worked fine. What could be the problem?Code:Aug 20 21:07:28 ddns update: ez-ipupdate Version 3.0.11b7, Copyright (C) 1998-2001 Angus Mackay.
Aug 20 21:07:28 ddns update: ez-ipupdate started for interface vlan1 host cichy.ath.cx using server members.dyndns.org and service dyndns-static
Aug 20 21:07:28 ddns update: connected to members.dyndns.org (204.13.248.112) on port 80.
Aug 20 21:07:28 ddns update: authentication failure
Aug 20 21:07:28 ddns update: failure to update vlan1->xx.xx.xx.xx (domain.ath.cx)
Aug 20 21:07:28 ddns update: shutting down updater for domain.ath.cx due to fatal error