Quote:
Originally Posted by jimmy
Code:nvram set bootCmd0="sed \"s/WORKGROUP/MSHOME/\" /ramfs/etc/smb.conf > /etc/smb.conf"
Printable View
Quote:
Originally Posted by jimmy
Code:nvram set bootCmd0="sed \"s/WORKGROUP/MSHOME/\" /ramfs/etc/smb.conf > /etc/smb.conf"
Is there a maximum drive size which will be supported ?
Don't know hard figures, but there are several ppl here who have 160Gb HD with one big FAT32 partition working just fine. Because 160Gb is beyond most common limits for drive sizes, I guess a 300Gb should work as well.Quote:
Originally Posted by Lionking
I hope this is the right place to place my problem in here. I am currently using fw 1.6.5.3 on WL-500b, everything works fine, but I tried to update it to the latest fw from Oleg (tried the previous versions as well) and have problem getting it to work. In telnet 192.168.1.1 I log into telnet, but if i input wl status or wl join 'AP' it stops responding and freezes. Currently I am using USB flask disk with wl_apsta.o file to get it to work and to connect wirelessly to AP in client mode. What am I doing wrong? Can anyone help?
Oleg,Quote:
Originally Posted by Oleg
I have just fixed the /init/firewall_change script to handle WLAN-WAN and WLAN-LAN rules (also called Wireless firewall or Dmz in scripts) and I think it is ready to be included in new cust. firmware release. (Changes inspired by /init/firewall script.)
Also I added support for custom (bootCmd) firewall rules in FORWARD chain(which is flushed & reset by this script otherwise):
Now file /var/tmp/firewall_custom is executed at the end of firewall_change script so it can be used like this:
Note, that it needs an empty file /var/tmp/firewall_custom to be present and have execute permissions. Can you create this file in new customized firmware release as well? I think it should go to /ramfs/var/tmp.Code:nvram set bootCmd5="echo '/usr/sbin/iptables -I FORWARD blablbabla' >> /var/tmp/firewall_custom" # -- for firewall refresh
nvram set bootCmd6="/var/tmp/firewall_custom" # -- execute once after boot
Thank you
Yato
I have found, that bootCmd command are not neccessarily executed in sequence indicated by their numbers. This occured in my case, when I use numbers with more than one digit. When I am looking into rc.nvram it is clear to me why - the commands are not sorted at all.
Currently I use this workaround:
YatoCode:nvram set bootCmd0="nvram show | grep '^myBootCmd' | sort | sed 's/^[^=]*=//' > /tmp/myBootCmd 2>> /tmp/myBootCmd.log && chmod +x /tmp/myBootCmd && /tmp/myBootCmd 2>&1 >> /tmp/myBootCmd.log"
nvram set myBootCmd00="cmd1"
nvram set myBootCmd01="cmd2"
nvram set myBootCmd10="cmd11"
In fact I've deleted firewall_change script completely in the 1.7.5.9, so /init/firewall handles everything... As for custom rules - I'm thinking of another solution with no nvram at all. :)Quote:
Originally Posted by yato
Thanks, will be fixed...Quote:
Originally Posted by yato
Ok, definitely better sollution ;) . Looking forward for new release! Man I am curious! :)Quote:
Originally Posted by Oleg
Hi, I have a problem with CR5, my router reboot continously 2-3*/day. When I downgraded, run correctly.
Tibor