Re: [rlug] openvpn part 2: plutorun: 104 z1 #1: STATE_MAIN_I1: initiate ...could not start conn (solved)

2007-06-18 Fir de Conversatie Alex
Daca in loc de auto=start ii scriu auto=add, gata nu mai apare mesajul ala cretin. Problema e ca nu pot scrie auto=add pe ambele routere, deci nu pot sa scap de mesaj ... Eu suspectam aici alta problema (care a picat): faptul ca routerul B nu avea IPSECUL pornit si atunci, daca dadeam pe

[rlug] openvpn part 2: plutorun: 104 z1 #1: STATE_MAIN_I1: initiate ...could not start conn

2007-06-15 Fir de Conversatie Linux User
Hello all, Am deschis zilele trecute un thread lung legat de openswan. Ceea ce m-a pus de la inceput pe un drum complet aiurea, a fost mesajul din syslog: Jun 15 14:04:22 dev13 ipsec_setup: ...Openswan IPsec started Jun 15 14:04:22 dev13 ipsec_setup: Starting Openswan IPsec 2.4.8... Jun 15

Re: [rlug] openvpn part 2: plutorun: 104 z1 #1: STATE_MAIN_I1: initiate ...could not start conn

2007-06-15 Fir de Conversatie lonely wolf
Linux User wrote: in general, for an intended-to-be-permanent connection, both ends should use *auto=start* to ensure that any reboot causes immediate renegotiation. For roadwarrior connections (*right=%any*), it is not known where the client will show up, so one has to use *auto=add OK,