[ previous ] [ next ] [ threads ]
 
 From:  Vincent Fleuranceau <v dot fleuranceau at gmail dot com>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] IPSec woes
 Date:  Mon, 25 Apr 2005 17:44:34 +0200
Hi,

I don't see what's wrong in your config.

I cant just tell you what I do to to trigger the link at boot time :

Download your config.xml file, then add the following lines to the
<system> ... </system> section and finally upload the config.xml file
(m0n0 will restart right away).

<shellcmd>echo &gt;/tmp/pinger.sh sleep 10</shellcmd>
<shellcmd>echo &gt;&gt;/tmp/pinger.sh ping -i 10 -c 6 -S '$1' '$2'</shellcmd>
<shellcmd>echo &gt;&gt;/tmp/pinger.sh exec ping -i 600 -S '$1' '$2'</shellcmd>
<shellcmd>sh /tmp/pinger.sh 10.0.0.1 192.168.1.0 &gt;/dev/null
2&gt;/dev/null&amp;</shellcmd>

where 10.0.0.1 = "local" m0n0wall IP (LAN interface) and 192.168.1.0 =
remote *network* address (no need to actually reach something, we just
want to "stimulate" IPsec a bit)

Adapt it with your own IP adressing scheme and don't forget to invert
the IP settings for the other router!

Cheers,

-- Vincent

PS: this pinger.sh idea is (c) Fred Wright ;-)