Originally Posted by
net-slider
UPD: /jffs/scripts/post-mount - у меня нет этого файла, там только services-start и services-stop o_O
там ного чего нет, ведь не все надо сразу и всегда.
вот список, старт которых прописан в прошивке
Code:
** User scripts **
These are shell scripts that you can create, and which will be run when
certain events occur. Those scripts must be saved in /jffs/scripts/
(so, JFFS must be enabled and formatted). Available scripts:
* dhcpc-event: Called whenever a DHCP event occurs on the WAN
interface. The type of event (bound, release, etc...)
is passed as an argument.
* firewall-start: Firewall is started (filter rules have been applied)
The WAN interface will be passed as argument (for
example. "eth0")
* init-start: Right after jffs is mounted, before any of the services
get started
* nat-start: nat rules (i.e. port forwards and such) have been applied
(nat table)
* post-mount: Just after a partition is mounted
* pre-mount: Just before a partition is mounted. Be careful with
this script. This is run in a blocking call and will
block the mounting of the partition for which it is
invoked till its execution is complete. This is done so
that it can be used for things like running e2fsck on the
partition before mounting. This script is also passed the
device path being mounted as an argument which can be
used in the script using $1.
* qos-start: Called after both the iptables rules and tc configuration
are completed for QoS.
* openvpn-event: Called whenever an OpenVPN server gets
started/stopped, or an OpenVPN client connects to a
remote server. Uses the same syntax/parameters as
the "up" and "down" scripts in OpenVPN.
* services-start: Initial service start at boot
* services-stop: Services are stopped at shutdown/reboot
* unmount: Just before unmounting a partition. This is a blocking
script, so be careful with it. The mount point is passed
as an argument to the script.
* wan-start: WAN interface just came up (includes if it went down and
back up). The WAN unit number will be passed as argument
(0 = primary WAN)
Don't forget to set them as executable:
chmod a+rx /jffs/scripts/*
And like any Linux script, they need to start with a shebang:
#!/bin/sh
Originally Posted by
Omega
эм, там стоит другой процессор
и усиленная 2T2R радиочасть
CPU Model Broadcom BCM5357 chip rev 2 pkg 8
CPU Frequency 300 MHz
а прошивка другого мнения!
Originally Posted by
lokus
Андрей, как самый большой гуру здесь, подскажите пожалуйста
Возникла идея поставить OpenVPN в JFFS, чтобы не задействовать nvram.
Как это сделать самым правильным образом?
Точнее openvpn-клиент уже есть в прошивке, значит я должен просто запускать его скриптом храня конфиг на jffs, тогда на rt-n16 будет и dual-wan и openvpn)
с начала можете скопировать конфигурацию из прошивки. т.е. сделать, скопировать файлы в JFFS. значения то хранятся в nvram, н окаждый раз при старте из этих значений формируются файлы. поправите в них пути и запустите из service-start к примеру или сделаете задачу cron.
Reply With Quote
Вылез баг
