>> From now on , I know uclinux may not run script correctly?(disvantage of
>> mash)
>> I have compiled the freeswan into my uclinux-system . when I start ipsec
>> manually as follows:
>> tncfg --attach --virtual ipsec0 --physical eth0
>> ifconfig ipsec0 192.168.1.2
>> pluto &
>> some imformation as follows:
>> an 1 01:33:11 Pluto[106]: Starting Pluto (FreeS/WAN Version )
>> Jan 1 01:33:11 Pluto[106]: including X.509 patch (Version 0.9.13)
>> Jan 1 01:33:11 Pluto[106]: including NAT-Traversal patch (Version 0.3)
>> [disab
>> led]
>> Jan 1 01:33:11 Pluto[106]: ike_alg_register_enc: Activating OAKLEY_AES_CBC:
>> Ok
>> (ret=0)
>> Jan 1 01:33:11 Pluto[106]: Changing to directory '/etc/config'
>>
>> pluto stop here....who know why?
>You probably need to run some "whack" commands to tell pluto about your
>tunnels, unless you want to use manually keyed tunnels.
>It's fairly simple to work out the whack commands you need it you
>install freeswan on a desktop system and then look at all the whack
>commands used to start a tunnel.
I have opened the document to found how to use whack command, it says"whack is
an auxiliary program to allow requests to be made to a running pluto. "
dose it mean we should run pluto firstly?then use whack command?
but how to start pluto firstly? I met the problem above.
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
