Em 01/12/2008 11:40, Ivan Voras escreveu:
Paulo Fragoso wrote:
Using other hardware whit FreeBSD 7.1-PRERELEASE running
apache-worker-2.2.9_5 + mysql, we have a poor result:
{client}$ ab -n 2000 -c 1000 http://system_using_7.1-PRERELEASE
...
Test aborted after 10 failures
apr_connect(): I
Hello,
I'm interested in the information of further development of Subject. I have
a bottleneck: swi_net limited by one CPU core time. There was a thread
http://lists.freebsd.org/pipermail/freebsd-net/2008-March/017447.html .
Patch http://people.freebsd.org/~mav/netgraph.threads.patch is not avail
On Mon, Dec 01, 2008 at 12:27:58AM -0800, Jonathan Feally wrote:
> Sorry for the cross-post, but this could be either lists problem.
>
> I have 2 boxes running 7-STABLE as of 20081130, both i386 SMP. One is
> running ISC DHCPD 3.0.x from recent ports, and the other dhclient from make
> world.
>
> Can someone please confirm or rule out my issue with dhclient sending
> bad IP checksum packets. It would really suck if 7.1 was released with a
> broken DHCP client.
>
I've had many problems lately, but none involved checksum nor the dhcpd
(btw, I assume that you are seeing bad checksum on th
I will try another em card in that server to confirm/rule out the nic
driver. I am seeing the same checksum number on both the source machine,
the dhcp server machine, and a 3rd windows xp machine sniffing the
traffic with etherreal/wireshark. The windows xp box is running an intel
nic as well,
Jonathan Feally wrote:
I will try another em card in that server to confirm/rule out the nic
driver. I am seeing the same checksum number on both the source
machine, the dhcp server machine, and a 3rd windows xp machine
sniffing the traffic with etherreal/wireshark. The windows xp box is
runni
Hi
I have a weird issue to report, and I am not sure if it's a bug or
some other configuration problem.
Server is a dual NICed FreeBSD 6.2 system. For example, one NIC is em0
= 192.168.0.1, and the other one is em1 = 192.168.0.2.
I have an Apache server listening on 80 and 443 on both IP address
wang_jiabo <[EMAIL PROTECTED]> wrote:
> following is my setkey configration. I can get SAD and SPD. but when I
> run " ping6 -I rl0 3ffe:501::103:20a:ebff:fe85:9e56 " on FreeBSD
> FreeBSD report: kernel: esp_aesctr_decrypt aes-ctr:payload length must
> be multiple of 16
>
Christian Weisgerber wrote:
wang_jiabo <[EMAIL PROTECTED]> wrote:
following is my setkey configration. I can get SAD and SPD. but when I
run " ping6 -I rl0 3ffe:501::103:20a:ebff:fe85:9e56 " on FreeBSD
FreeBSD report: kernel: esp_aesctr_decrypt aes-ctr:payload length must
be multiple o
OK, so I installed a different PE1750 with BETA2 and then updated the
source via cvsup RELENG_7 from cvsup3 and all is ok now on that box.
Went back the first box and cvsup'ed the src again into an empty
directory and it compiled and worked fine. Looks like my updating of the
source along the w
Ok, I managed to cause it again.
dhclient was the problem.
My source tree was fine. Turns out that it is my make.conf CFLAGS=-O3
setting.
When compiled with -O3 it will generate packets with bad checksums.
Simply recompiling it with -O2 did not cause this issue and dhclient
works fine.
So th
Christian, good day.
Tue, Dec 02, 2008 at 08:12:28PM +, Christian Weisgerber wrote:
> wang_jiabo <[EMAIL PROTECTED]> wrote:
> > add 3ffe:501::103:20a:ebff:fe85:9e56
> > 3ffe:501::104:21d:fff:fe19:59fc esp 0x1000 -m tunnel -E aes-ctr
> > "ipv6readylogoaes2to1" -A hmac-sha1 "ipv6readylo
12 matches
Mail list logo
