Re: question about fopen fd limit

2016-12-24 Thread Alfred Perlstein
Hello 盛慧华 Here's another trick that may work. Use funopen(3) and provide your own read/write/seek and close functions for the high fds. You can basically make "cookie" a struct that contains your "int sized" fds. FILE * funopen(const void *cookie, int (*readfn)(void *, char *, int)

[Bug 215513] panic: SACK scoreboard must not be empty

2016-12-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215513 Michael Tuexen changed: What|Removed |Added CC||tue...@freebsd.org --- Comment #2

Re: How to configure another loopback device?

2016-12-24 Thread Hiroki Sato
John Dison wrote in <252311393.1502179.1482604113...@mail.yahoo.com>: jd> > Does adding ifconfig_lo0="inet 127.0.0.1/8" to /etc/rc.conf work? jd> jd> Yes, adding ifconfig_lo0="inet 127.0.0.1/8" helps indeed. jd> jd> Interesting is that if I also add ifconfig_lo0_ipv6="inet6 ::1/128" jd> then ::

[Bug 215513] panic: SACK scoreboard must not be empty

2016-12-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215513 Hiren Panchasara changed: What|Removed |Added Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org

RE: How to configure another loopback device?

2016-12-24 Thread John Dison via freebsd-net
Resending, for some reason my reply is not in ML archives... probably everyone hates Yahoo Mail... - Forwarded Message - From: John Dison To: Hiroki Sato ; "freebsd-net@freebsd.org" Cc: "m...@sentex.net" Sent: Saturday, December 24, 2016 5:25 PM Subject: Re: How to configure another

[Bug 205592] TCP processing in IPSec causes kernel panic

2016-12-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205592 Eugene Grosbein changed: What|Removed |Added CC||po...@grosbein.net --- Comment #

[Bug 205592] TCP processing in IPSec causes kernel panic

2016-12-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205592 --- Comment #4 from and...@rinet.ru --- (In reply to Hiren Panchasara from comment #3) Unfortunately, no: I don't see 11-R being ready for production yet. -- You are receiving this mail because: You are the assignee for the bug. __

[Bug 215122] Try to change route default to IP out of range lock the system

2016-12-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215122 guy...@gmail.com changed: What|Removed |Added CC||guy...@gmail.com --- Comment #4

[Bug 211602] route change command for ipv6 route with bad gateway leads to deadlock/panic

2016-12-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211602 guy...@gmail.com changed: What|Removed |Added Resolution|--- |DUPLICATE Status|New

Re: How to configure another loopback device?

2016-12-24 Thread Hiroki Sato
John Dison via freebsd-net wrote in <1404669989.1370681.1482573468...@mail.yahoo.com>: fr> > if your first IPs are say 192.168.1.1-2/32 and 2001:550:2:8::1e-f fr> fr> > Try without an alias0 for the first set of IPs fr> fr> > ifconfig_lo1="inet 192.168.1.1/32" fr> > ifconfig_lo1_ipv6="inet6 200

Re: How to configure another loopback device?

2016-12-24 Thread John Dison via freebsd-net
> if your first IPs are say 192.168.1.1-2/32 and 2001:550:2:8::1e-f > Try without an alias0 for the first set of IPs > ifconfig_lo1="inet 192.168.1.1/32" > ifconfig_lo1_ipv6="inet6 2001:550:2:8::1e prefixlen 126" > ifconfig_lo1_alias0="inet 192.168.1.2/32" > ifconfig_lo1_ipv6_alias0="inet6 2

Re: IPV6 LRO in FreeBSD7.4 or Stable_7

2016-12-24 Thread hiren panchasara
On 12/23/16 at 09:45P, David Somayajulu wrote: > Hi, > Is IPv6 LRO support available in FreeBSD7.4 or Stable_7 ? Examining > tcp_input() in netinet/tcp_input.c, it appears that it is not. Just want to > make sure I didn't miss anything. > As far as I can tell, you are right. Cheers, Hiren pgp

[Bug 138046] [tcp] tcp sockets stay in SYN_SENT even after receiving RST. never time out as well.

2016-12-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=138046 Hiren Panchasara changed: What|Removed |Added Status|In Progress |Closed Resolution|---