Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102

2012-09-14 Thread Вадим Уразаев
Ok, I will disable vlan_hwtso using ifconfig -vlanhwtso. Thanks. > Try disabling tso at the global level in the kernel. Under some > circumstances with some drives VLAN_HWTSO -> TSO. > -Garrett > ___ freebsd-net@freebsd.org mailing list http://lists.fr

Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102

2012-09-13 Thread Вадим Уразаев
I am using two lagg interfaces : lagg0: flags=8843 metric 0 mtu 1500 options=400b8 ether 00:1b:21:55:a7:c4 nd6 options=9 media: Ethernet autoselect status: active laggproto lacp laggport: igb1 flags=1c laggport: igb0 flags=1c lagg1: flags=8843 metric 0 mtu 1500 options=400b8 ether 00:1b:21:63:59:c

Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102

2012-09-13 Thread Вадим Уразаев
Then my guess is wrong. I found the message, where similiar problem was described in ipfw mailling list http://lists.freebsd.org/pipermail/freebsd-ipfw/2011-March/004582.html, with no answer. Maybe it will be usefull for somebody. ___ freebsd-net@freebsd

RE: kernel: arpresolve: can't allocate llinfo for 65.59.233.102

2012-09-13 Thread Вадим Уразаев
I have the same issue (default gateway unexpectedly changes on some random address) on FreeBSD 9.0 Box with lot of traffic going through it, I have a wild guess that it is related to libalias compilled into kernel (troubles start showing itself when I started to use ipfw nat functionality ).

Re: The problem with MTU <1500

2012-03-26 Thread Вадим Уразаев
You may use this patch to ipfw http://www.freebsd.org/cgi/query-pr.cgi?pr=103454 Or you may use ng_patch netgraph node (man ng_patch(4) should give you some examples) The simpliest way to do what you want is pf rule scrub in on em0 no-df performance of all those methods you should check by youre