|
|||||||||||
|
Re: linux-ipsec: 9th planet (now 8th?) review
From: Richard Guy Briggs <rgb(at)conscoop.ottawa.on.ca>
Date: Wed Jun 17 1998 - 08:41:10 EDT
I'll ignore them this time around, but they should be fixed by 0.90. > | I didn't know if the ipsec module needed to be loaded or not. It seems
Well, have a look at klips/doc/rgb_setup.txt for some ideas. The commands that I think need to be in place are: insmod ipsec, tncfg ...., and ifconfig ipsec0 ... > | It bugs me (although I am guilty myself) when I get caught by a makefile
I just said it bugged me when I forgot about this... > | I am happy to see that pluto exits with an error in debug mode when it
Ok, but I saw no obvious protest...maybe it was burried. > | Pluto will not notice if the ipsec virtual interface has not been connected
check for ipsec0 -> NULL. This will tell you that it is not wired to anything. > | With the command:
Not quite. Try: route add -host <remoteIP> dev ipsec0 This will route all the traffic that needs processing via ipsec first, otherwise it will completely bypass the module. > I've just changed Pluto to know this IFF peer == peer's client.
For examples, check the updated spi.c. > Pluto did notice that the KLIPS wasn't happy. It reported a write
I'm not entirely sure myself...I'm still trying to discover the best way to get error codes back from the kernel into user space. > | It appears pluto didn't even try to talk to klips to set the forward esp
Ah. > | It did nothing on the remote end with klips or route(8).
Ah. > | Pluto occupies /dev/ipsec, preventing any other process from writing to
Ah. Good. > Extracts from RIchard's log, with notes:
I half expected this.... > [Silly Pluto decides that since it cannot digest this packet, it will
route add -host <peer> dev ipsec0 > The second round ended unhappily with:
Most likely. > I've made a stab at splitting the keys in kernel.c (the Pluto module
I'll run it to test it before grovelling through that. I wasn't aware of any output that went somewhere else...but I may have simply lost it. > I've changed Pluto to only use stderr. The distinction between stderr
Thank you. I used the tunnel command on a separate invocation that was not spewed in the last message. If the output had been different, I would have posted it. I guess that was not clear. > This is *not* a problem. Pluto automatically assumes that tunnelling
Good. This should be the expected behaviour.
> Hugh Redelmeier
Slainte Mhath, rgb -----BEGIN PGP SIGNATURE-----
iQCVAwUBNYe5ZN+sBuIhFagtAQEIDgP/YlFCS4uxqEO6NL5EAdTOlpYn3HzJaI4e
3tQU6EdPJ8MahbAzqonir6/0dZCCWXzZ5qdTruiL4lm+J5r6hHZvL4H4C14lv7f8
hdXjcKgFR5cbpyPSkn8yhmpMD/ld54Qrf0wElN8deMbT9CPCadIUjKGaKpNyvm74
TUaLxcUIJdo=
This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 12:59:22 EDT |
||||||||||
|
|||||||||||