There are several ways to go.......
1.) You reboot your router, but I strongly suggest don't use such a solution.
When you reboot your router by script, it can end in a continuous
rebooting device.
Sometimes it is hard to get a connection to your router.....
2.) You do just nothing - the regular fw recognise a lost connection within 5
minutes
then a new connection is established again.
3.) You can open a console on your router and enter 'killall pppd'. Wait a
minute, your router starts a new connection immediatly.
4.) You write a script to ping a website from time to time and when at least
dns connection is lost, your script kills pppd and a new connection is
established soon.
Below you find all needed files, store file address to '/tmp/etc/' and do
the appropriate entry in '/tmp/local/.files', then store script 'watch_wan'
to '/tmp/local/sbin/' and store everything with the well known commands:
'flashfs save && flashfs commit && flashfs enable && reboot'
If you want, you can change time between pings, your loglocation aso.,
just have a closer look at the file 'watch_wan', don't forget to store it
forever with flashfs....
5.) You change your gprs file. As written above, there is an automatic
detection in your koppel firmware, hence you can adjust the time where a
lost connection is recognized.
Open vi /tmp/ppp/gprs/gprs (or open gprs with any editor) and change in
the line lcp-echo-failure 5 the value '5' to '2'.
Then add to your '/tmp/local/.files' the full path of gprs
file '/tmp/ppp/gprs/gprs'.
To store your changed file, do a
'flashfs save && flashfs commit && flashfs enable && reboot'
ahhh... don't forget to remove the extensions of the files and rights!
A chmod 777 /tmp/local/sbin/watch_wan should do the trick.
Call your watch_wan just with: (post-boot or console)
'/tmp/local/sbin/watch_wan &' in order to run in background
Hope it helps...
Reply With Quote
