em(4): sending ARP regardless of NOARP flag

2009-08-03 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Jack, I have observed that, even if -arp is specified when adding an IP address to the em(4) interface, an ARP request is still being sent. Here is a tcpdump from my network environment: 11:15:01.370256 00:13:72:66:b5:d7 > ff:ff:ff:ff:ff:ff, ethe

net.inet.tcp.keepidle and friends

2009-08-03 Thread Brian A. Seklecki
All: The description on this sysctl was just recently added in -CURRENT. It was missing during all of RELENG_6 and RELENG_7? Do we not trust it entirely, ergo the two hour initial threshold and lack of documentation? It also seems like the description could be bit more insightful; looks like it

Re: kern/137392: [ip] [panic] crash in ip_nat.c line 2577

2009-08-03 Thread linimon
Old Synopsis: crash in ip_nat.c line 2577 New Synopsis: [ip] [panic] crash in ip_nat.c line 2577 Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Mon Aug 3 15:21:16 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www

net/haproxy - some ideas

2009-08-03 Thread Vladimir Grebenschikov
Hi Recently I've looked into net/haproxy port on FreeBSD. Contrary to recent Linux there is no splice() functionality, so all data move between sockets is done through user-space. First idea - to use ksocket netgraph node to accept connections, and send data to both directions, theoretically it

Current problem reports assigned to freebsd-net@FreeBSD.org

2009-08-03 Thread FreeBSD bugmaster
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker