On Tue, Dec 27, 2005 at 02:38:18AM +0600, mitrohin a.s. wrote:
> helo.
>
> i have strangle problem with forward rule.
>
> isp1 +--+
> <-[fxp0:x.x.x.1/24] router_1 [re0:10.200.1.1/24]+
>| [xl2:10.4.2.1/24]---+ |
>
On Mon, Dec 26, 2005 at 05:56:31PM +0200, Oleg Tarasov wrote:
O> Further analysis brought me to a conclusion that the problem is in MTU
O> values. Changing MTU on client machines made everything work fine -
O> but as I know this is not right. If packets are routed between
O> different MTU interface
helo.
i have strangle problem with forward rule.
isp1 +--+
<-[fxp0:x.x.x.1/24] router_1 [re0:10.200.1.1/24]+
| [xl2:10.4.2.1/24]---+ |
+--+ | |
++
While doing some network stress-tests from a dual-CPU x86 FreeBSD 5.4
server, I noticed that a "ping -f" drives dhcpd's CPU usage way up. I
put dhcpd into debug mode and didn't get any error messages. I then ran
dhcpd with strace, and saw loads of these messages when I started the
ping flood:
Hello,
Further analysis brought me to a conclusion that the problem is in MTU
values. Changing MTU on client machines made everything work fine -
but as I know this is not right. If packets are routed between
different MTU interfaces they have to be fragmented or something. If
fragmentation is imp
Current FreeBSD problem reports
Critical problems
Serious problems
Non-critical problems
S Submitted Tracker Resp. Description
---
o [2003/07/11] kern/54383 net [nfs] [patch] NFS root configurations w
