Re: kern/177456: [tcp] [patch] An error of calculating TCP sequence number will resault in the machine to restart

2013-03-28 Thread linimon
Old Synopsis: An error of calculating TCP sequence number will resault in the machine to restart New Synopsis: [tcp] [patch] An error of calculating TCP sequence number will resault in the machine to restart Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon R

Re: igb and ALTQ in 9.1-rc3

2013-03-28 Thread Nick Rogers
On Thu, Mar 28, 2013 at 4:16 PM, Jack Vogel wrote: > Have been kept fairly busy with other matters, one thing I could do short > term is > change the defines in igb the way I did in the em driver so you could still > define > the older if_start entry. Right now those are based on OS version and so

Re: close(2) while accept(2) is blocked

2013-03-28 Thread Jilles Tjoelker
On Thu, Mar 28, 2013 at 06:54:31PM +0200, Andriy Gapon wrote: > So, this started as a simple question, but the answer was quite > unexpected to me. > Let's say we have an opened and listen-ed socket and let's assume that > we know that one thread is blocked in accept(2) and another thread is > ca

Re: igb and ALTQ in 9.1-rc3

2013-03-28 Thread Jack Vogel
Have been kept fairly busy with other matters, one thing I could do short term is change the defines in igb the way I did in the em driver so you could still define the older if_start entry. Right now those are based on OS version and so you will automatically get if_transmit, but I could change it

Re: igb and ALTQ in 9.1-rc3

2013-03-28 Thread Nick Rogers
On Tue, Dec 11, 2012 at 1:09 AM, Jack Vogel wrote: > On Mon, Dec 10, 2012 at 11:58 PM, Gleb Smirnoff wrote: > >> On Mon, Dec 10, 2012 at 03:31:19PM -0800, Jack Vogel wrote: >> J> UH, maybe asking the owner of the driver would help :) >> J> >> J> ... and no, I've never been aware of doing anything

2 vlans - setfib - kernel: arpresolve: can't allocate llinfo for x.x.x.x

2013-03-28 Thread Eduardo
Hi Folks, I have a server with a 10G intel card, X520-DA2, and it is working fine, interface shows up as ix0 On this card, I have one interface connected at 10G, and it has 2 vlans on it (no "plain" IP is on the machine or on this card, only via these vlans) I have it also configured them with s

close(2) while accept(2) is blocked

2013-03-28 Thread Andriy Gapon
So, this started as a simple question, but the answer was quite unexpected to me. Let's say we have an opened and listen-ed socket and let's assume that we know that one thread is blocked in accept(2) and another thread is calling close(2). What is going to happen? Turns out that practically no

Re: Win7 client, IPv6 network, multicast DNS equests and BIND name server?

2013-03-28 Thread Lev Serebryakov
Hello, Mattia. You wrote 28 марта 2013 г., 18:58:32: MR> And now your Win7 should be happy. I don't want to add second dhcpd (unfortunately, isc-dhcpd could not process IPv4 and IPv6 in single process), and it is not a problem to have IPv4 only DNS when dhcpd is accessible. And if dhcpd

Re: Win7 client, IPv6 network, multicast DNS equests and BIND name server?

2013-03-28 Thread Mattia Rossi
Am 28.03.2013 15:58, schrieb Mattia Rossi: Am 28.03.2013 14:49, schrieb Lev Serebryakov: Hello, Freebsd-net. This question is not very FreeBSD specific, but as my router and DNS server are FreeBSD-based, I think a could ask it here and don't subscribe do BIND-related list, Ok? When DHCPv4

Re: Win7 client, IPv6 network, multicast DNS equests and BIND name server?

2013-03-28 Thread Mattia Rossi
Am 28.03.2013 14:49, schrieb Lev Serebryakov: Hello, Freebsd-net. This question is not very FreeBSD specific, but as my router and DNS server are FreeBSD-based, I think a could ask it here and don't subscribe do BIND-related list, Ok? When DHCPv4 is not available, Win7 clients on my network

Win7 client, IPv6 network, multicast DNS equests and BIND name server?

2013-03-28 Thread Lev Serebryakov
Hello, Freebsd-net. This question is not very FreeBSD specific, but as my router and DNS server are FreeBSD-based, I think a could ask it here and don't subscribe do BIND-related list, Ok? When DHCPv4 is not available, Win7 clients on my network pick up proper IPv6 prefix, but cannot pick up DN