NTFS 3g can be compiled with current kernel 2.4.37, but nobody tested it.Quote:
Originally Posted by outkastm
HFS+ supported by kernel, we can include module binary in next snapshot in case you ready to test it.
Printable View
NTFS 3g can be compiled with current kernel 2.4.37, but nobody tested it.Quote:
Originally Posted by outkastm
HFS+ supported by kernel, we can include module binary in next snapshot in case you ready to test it.
support for DNS-O-Matic ?
Currently, we have more urgent tasks to achieve stability & bugs removal. If someone send me patch to add this functionality and it will not so huge (we have a very limited space for 520gU, 500gx and other 4M flash routers), than we can include it into the mainstream.Quote:
Originally Posted by downloadd
on dns-o-matic they say dd-wrt supports it, so maybe we can rip it from the sources and magicly put it in the oleg sources:D
http://www.dnsomatic.com/wiki/dd-wrt
but I have this weird feelin that olegs firmware also might be able to do this... since you can specify the server:
I'm sure this must be a value somewhere in olges:)Quote:
DYNDNS Server: updates.dnsomatic.com
I already like the D release, so I can't wait till the full one, keep it up;)
DD-WRT uses inadyn. Olegs firmware uses ez-ipupdate. Our firmware adds ability to use custom config /etc/ddns.conf (appendable with /usr/local/etc/ddns.conf). If someone confirm that ez-ipupdate works with dns-o-matic, we can add this parameters to predefined list in web-interface.Quote:
Originally Posted by wpte
seems like dns-o-matic uses dyndns-like update api. you can try it right now (using 1.9.2.7-d exactly)Quote:
Originally Posted by wpte
create /usr/local/etc/ddns.conf according ez-ipupdate manuals, wđich is to be append to autogenerated /etc/ddns.conf
any these params will override autogenerated ones, so you should specify server=updates.dnsomatic.com with typical ddns.org settings
so, play with it, or i could patch ez-ipupdate to suit your dns-o-matic needs... some day...
yep. someone has to try it outQuote:
Originally Posted by lly
EDIT: works for me with dyndns setted up at web interface and following /usr/local/etc/ddns.conf
Code:service-type=dyndns
server=updates.dnsomatic.com
host=all.dnsomatic.com
Hello
First of all thanks you for your hard work,I've tested a few versions of your firmware and it's very stable...but I've tried today your latest build from 24.02,and I've a problem: after I set up Wireless Mac adress filtering,puting a 5 mac adress of wireless devices to allow them to connect wireless,after saving an reboot,I can't no more to login in the web interface of the router(IE or Firefox),I mean the page doesn't appear anymore,the IP is 192.168.1.1 ,and nothing,same message:''Internet Explorer cannot display the webpage'' .I've flashed 5 times,resetting to defaults ,nvram erase ,nothing,same story.Everything is ok,until I set Mac filtering to permit for wireless access,after that,no more web interface of the router.Maybe someone could try to see if they have the same problem.
Tnx a lot
Cheers
- You have to flash firmware by wire, not by WiFi.
- Is web-interface accessible by wire? (If yes, you have mistake in your restrictions).
Tnx for your reply.
Everything I've done only by wire,using Asus firmware restauration tool...everything is ok until I'm changing Mac Wireless Filter to permit a mac adress from my laptop to access the wireless network...after that no more acces to the webpage of the router using wired access,not wireless(wireless I've not tryed at all,only wired).Right now I'm downloading the firmware again,and flashing again to see if it happens again.
Cheers
I've tried on 2 asus wl500gP v1 ,also the build from 09 february ,same story,the routers frozen,nothing works,only with hard reset can log in again...with january build,no problem,it works,so something must be changed in latest builds..I don't have enabled any kind of security on wireless,no wep,no wpa,nothing,only MAC filter with permit access for 3 mac adress,1 laptop and 2 Nokia phones.
Tnx again
Unfortunately, I can't reproduce problem. I tried both Accept/Reject modesQuote:
Originally Posted by viasat
on "Wireless - Access Control" page, adds six MAC's - all ok. If situation repeats, you should prepare testcase, step by step.
Please try one more time,I've attached an printscreen where the modification is.If I click on Finish,Save&Restart ,it will never restart,no more log in into router,only after hard reset.Believe me,I don't want to waste your time,but the problem it's there,at least for me ,on two different routers...you don't need to have internet conection,just flash the router with your latest build,go on to the option from printscreen,select Accept,add an mac adress,Finish,Save%Restart,and you will see that never restarts,,at least for me...if works for you,it's ok,I give it up,I don't know anymore what else to try,and I'll wait your next releseas...
Tnx again and excuse my bad English!
Cheers
viasat
First of all, You modify wrong page!
On this page you define MAC rules for both wire & wireless clients!
Please, read carefully that written on screen BEFORE modifying anything.
Ok,tnx a lot,my mistake,I'll search better next time!
Cheers and thanck you for your work and help!
Best Regards
Sure im ready to test it. I have an Packard Bell Store & Play 500GB that supports FAT, NTFS or HFS+ fs for connection to TV.Quote:
Originally Posted by lly
HFS+ module you can get on http://wl500g.googlecode.com/files/m...090224.tar.bz2 since 20090224 snapshot.Quote:
Originally Posted by outkastm
NTFS 3g binary - http://rapidshare.de/files/45619009/...l.tar.bz2.html
P.S. And don't forget to set up LD_LIBRARY_PATH variable
How to disable access to router configuration from wireless?
Option to disable wireless with ezsetup button?
Option to write log file to usb hdd?
WPA KEY generator ?
link on router home page to http://wl500g.info/ and http://code.google.com/p/wl500g/?
read iptables manualQuote:
Originally Posted by downloadd
search FAQ about /usr/local/sbin/ez-setup scriptQuote:
Option to disable wireless with ezsetup button?
search forum. This very hard to be realized in standart GUI due to USB hdd mounts after logging starts & in case of error - hdd never be mounted automatic.Quote:
Option to write log file to usb hdd?
Your suggestion?Quote:
WPA KEY generator ?
maybeQuote:
I made a quick generator, it's as attachment.Quote:
Originally Posted by lly
anyway, here was my feature request:D
:DQuote:
anyway... a little feature request popped up, and it's not like a big deal I think...
The problem is that the webcam daemon generates a giant cpu load. If there was an option in the webinterface to limit it to eg 1fps
there is an option -s in rcamd, that lets you set after how many seconds it'll take a frame from the webcam, when 0 it is unlimited.
like this maybe:
if there could be a box to fill that in the webinterface, my sometimes working script at boot to reduce the fps of the webcam will become unneeded, and I don't have to restart the cam daemon.Quote:
rcamd -p 7777 -s 1 -z MET-1METDST,M3.5.0/2,M10.5.0/3 -a 0 -t 0 -r 0 -f 640x480 -m 100 -c 100
what do you say?:D
There is .EXE in attachment - it useless in unix! Anyway, maybe you can explain, why you want it in main firmware?Quote:
Originally Posted by wpte
accepted, but I can't you promise exact time of realization.Quote:
anyway, here was my feature request:D
I didn't want the generator in the firmware... but because someone wanted a generator aparrently, I made a quick one in C#.Quote:
Originally Posted by lly
it doesn't work in wine either, because it's .net 3.5
I couldn't convert it back to 2.0 unfortunately, too mutch errors :(
I can give you the source if you want?:D
edit:
the webpages are written in ASP right?
then a button with this code linked to it might do the job quickly:
http://www.sashadesign.com/howto/7/
I apoligize that downloadd wants it in firmware and can't imagine, why?Quote:
Originally Posted by wpte
you don't have to apologize:confused:Quote:
Originally Posted by lly
but you said that:
and I tought "you" referred to me:pQuote:
There is .EXE in attachment - it useless in unix! Anyway, maybe you can explain, why you want it in main firmware?
just a misunderstanding I guess:)
wpte
Your FR about rcamd was much simpler than I thought :)
"Refresh Time in seconds:" field on webcam page controls unused variable "usb_webfresh_x". So, I simply change default value, as in ASUS rc internals, to "0", and made it usable.
r141 uploaded into SVN
hmm... I tought "Refresh Time in seconds:" was for the non-activeX webcam viewer page to reload itself and have to correct frame displayed:pQuote:
Originally Posted by lly
and that is the case I think...
so if you put it on 0 (no limit on the fps) you won't get a refresh in the webpage, or too mutch refreshes?:confused:
I'm going to test it out anyway;)
thanks:D
Maybe you are right, my fast solution is not so good :(Quote:
Originally Posted by wpte
But this variable means near same both in web-interface & rcamd.
rcamd:web:PHP Code:-s <seconds between frames> (default==1)
Thus, I decide do decision above.PHP Code:This field indicates the time interval in seconds that system reloads image.
well... you could do it like that I guess, but you need a little handler for the webrefresh if it isn't there yet:)
something like:
dunno how it looks like in the FW, but I guess if you put this somewhere in between it should pick up and have a proper refresh:DPHP Code:if(interval=0)
{
webrefresh=1;
}
i.e. you suggest that webrefresh always be greater than zero?Quote:
Originally Posted by wpte
Ok, I agree.
Quote:
Originally Posted by lly
great:)
btw, I noticed that the flashfs files have changed over time from the svn builds?
when I tried reflashing an old flashfs file, the router wouldn't start it's dhcp server anymore... or something else went wrong.
so I'm still sailing on the older D firmware.
I have a wl-500w btw.
One of the goals for the new firmware mentioned in the initial post was "better ipv6 support". However, it seems that IPv6 support ist currently completly disabled. :(
Is it possible to compile the firmware with IPv6 support enabled?
if you read carefully, the first post was also a sort of wishlist.
I have to report the same problem - I couldn't connect to router at all after reflashing to lastest firmware, so I had to revert back to previsous version (WL500gp-1.9.2.7-d-20090225.trx) using TFTP.Quote:
Originally Posted by wpte
did reflash finish successfully? I mean did power led turn on again?Quote:
Originally Posted by ondrejpecta
or power led was turn off and router hangs?
try to follow this steps:
1. flashfs disable && reboot
2. reflash firmware, router should be flashed and rebooted as usual
3. flashfs enable && reboot
will it hang at shutdown or at boot time?
it stops at booting for me...Quote:
Originally Posted by theMIROn
it seems, as soon as I actually even create a flashfs (like creating post-boot etc.) and save it, it's enough to make it stop working.
the boot procedure seems normal if I look at the LED's on the front, the same kinda flashing lights and 2 refreshes of the switch... nothing out of the ordinary.
Also I noticed that I received data from the router, but I couldn't send anything. how many times do you see that on your network stats?:p:D
okie. try this:
1. restore prevous firmware build (tftp maybe)
2. boot, save flashfs.tar.gz and disable it (flashfs disable)
3. reboot
4. flash r141 or newer 1.9.2.7-d firmware
5. restore flashfs.tar.gz via web interface
will it help? it'll be nice to provide console boot logs, if you have it
I also have some problems with SVN-version 140.
I flashed the firmware succesfully.
Next I noticed the new option to enable SSH in the webinterface, so I enabled that option.
After that, my clients didn't get any ip-adres from DHCP and I was unable to ping the router.
I after serveral attempt to flash the old firmware, I accidentaly discovered that via a static ip-adres I was able to login to SSH (but still no ping).
It seems that enabling SSH from the webinterface, breaks some of the firewall rules, cause if I disable the firewall with "iptables -D INPUT -j DROP" everyting is working again....
However this also leaves my unprotected.
(i'm building r144 atm, to see if that solves the problem)
Edit:
Further tests show that it has nothing to do with enabling SSH.
I went back to factory defaults, and configured the basics -> everthing is fine
Next I do a flashfs enable && reboot -> at first everything seems fine, but after a while I get 'firewalled'
I'll see tomorrow if i can find the exact moment where the firewall is enabled.
DrChair:
If you still have problem with firewall, could you show output of
PHP Code:iptables-save | grep INPUT
No, this behavior shouldn't be changed.Quote:
Originally Posted by wpte
Please, describe more detailed. My assumption:Quote:
when I tried reflashing an old flashfs file, the router wouldn't start it's dhcp server anymore... or something else went wrong.
1. You flashed new firmware. Successful?
2. reboot. router up ok? what about dhcp-server(dnsmasq)?
3. Did you try to execute "flashfs enable" & reboot?
4. Router itself starts? What is in syslog?
1. yes, successful (tried with webpage upload and asus restoration tool)Quote:
Originally Posted by lly
2. First reboot is good, and after applying the settings to the router it's also rebooting fine. Only after saving something in the flashfs memory it stops working properly.
3. I did, I always execute "flashfs save && flashfs commit && flashfs enable && reboot", I actually have it under a macro on my G15 keyboard:p
4. The router doesnt respond to anything anymore when something is in the flashfs, not even the reset button, I need to unplug the psu to make it run again.
I do want to note that sometimes the firmware is flashed, but the original memory of the old firmware is still there, even after a factory default.
I just noticed that the stable release has a tar.gz compression and it seems like the beta(or alpha, I dunno) has tar.bz2 compression.
Also I saw that the paths in the flashfs file are different in the older beta release, than the newer one.
If I have no post-firewall script, everything is working fineQuote:
Originally Posted by al37919
then the output is
:INPUT ACCEPT [288:57716]
:INPUT ACCEPT [288:57716]
If I have the following post-firewall in place:
I have a problem and the output of iptables-save |grep INPUT is:Code:#!/bin/sh
## FIREWALL
## set default policy
iptables -D INPUT -j DROP
## Allow access to webserver from WAN
iptables -A INPUT -p tcp --dport 80 -j ACCEPT
## Allow access to SSH (port24) from WAN
iptables -A INPUT -p tcp --dport 24 -j ACCEPT
iptables -t nat -A PREROUTING -i vlan1 -p tcp --dport 24 -j DNAT --to-destination 192.168.2.1:24
# Allow access to PROFTPD (port 21) from WAN
iptables -A INPUT -p tcp --dport 20 -j ACCEPT
iptables -t nat -A PREROUTING -i vlan1 -p tcp --dport 20 -j DNAT --to-destination 192.168.2.1:20
iptables -A INPUT -p tcp --dport 21 -j ACCEPT
iptables -t nat -A PREROUTING -i vlan1 -p tcp --dport 21 -j DNAT --to-destination 192.168.2.1:21
iptables -A INPUT -p tcp --dport 65530:65535 -j ACCEPT
iptables -t nat -A PREROUTING -i vlan1 -p tcp --dport 65530:65535 -j DNAT --to-destination 192.168.2.1
iptables -A INPUT -j DROP
:INPUT ACCEPT [695:224835]
:INPUT ACCEPT [36:11691]
-A INPUT -p tcp -m tcp --dport 80 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 24 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 20 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 21 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 65530:65535 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 80 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 24 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 20 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 21 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 65530:65535 -j ACCEPT
-A INPUT -j DROP
With firmware around r100 this post-firewall was still working.
I guess it has something to do with all the SNAT changes