Strange problem with IPSEC, not entirely transparent.

2005-11-22 Thread Baldur Gislason
I recently set up IPSEC communications between two hosts I have in different places. One is FreeBSD 5.4-STABLE August 22. 2005. The other is 4.11-STABLE April 18th 2005. I run a gif tunnel between them and routes for networks found on both sides are negotiated by quagga using ospf. the internet

Re: Strange problem with IPSEC, not entirely transparent.

2005-11-22 Thread Baldur Gislason
Adding: If I kill spmd on the 5.4 box, then all works fine but the comms are only encrypted in one direction. Baldur On Tue, Nov 22, 2005 at 09:52:53PM +, Baldur Gislason wrote: > I recently set up IPSEC communications between two hosts I have in different > places. > One is FreeBSD 5.4-STA

Re: Strange problem with IPSEC, not entirely transparent.

2005-11-22 Thread Baldur Gislason
And another observation, sorry for flooding the list like this. The 4.11 box is compiled with IPSEC_DEBUG but the 5.4 box isn't. Baldur On Tue, Nov 22, 2005 at 09:57:24PM +, Baldur Gislason wrote: > Adding: > If I kill spmd on the 5.4 box, then all works fine but the comms are only > encrypt

em interrupt storm

2005-11-22 Thread Kris Kennaway
I am seeing the em driver undergoing an interrupt storm whenever the amr driver receives interrupts. In this case I was running newfs on the amr array and em0 was not in use: 28 root1 -68 -187 0K 8K CPU1 1 0:32 53.98% irq16: em0 36 root1 -64 -183 0K 8K RU

RE: em interrupt storm

2005-11-22 Thread John Polstra
On 23-Nov-2005 Kris Kennaway wrote: > I am seeing the em driver undergoing an interrupt storm whenever the > amr driver receives interrupts. In this case I was running newfs on > the amr array and em0 was not in use: > >28 root1 -68 -187 0K 8K CPU1 1 0:32 53.98% irq16: em