[Differential] D8904: inet: Fix routing issue by calling if_up()

2016-12-25 Thread sepherosa_gmail.com (Sepherosa Ziehau)
sepherosa_gmail.com added a comment. In https://reviews.freebsd.org/D8904#184430, @hrs wrote: > The cause is that the prefix route was removed by in_scrubprefix() in the PRC_IFDOWN handler and never reinstalled upon PRC_IFUP because the reinstallation is done only for ifa passed to SIOC

[Differential] D8904: inet: Fix routing issue by calling if_up()

2016-12-25 Thread hrs (Hiroki Sato)
hrs added a comment. The cause is that the prefix route was removed by in_scrubprefix() in the PRC_IFDOWN handler and never reinstalled upon PRC_IFUP because the reinstallation is done only for ifa passed to SIOCAIFADDR. Just calling if_up(ifp) looks too heavy to me because it causes extra

[Differential] D8905: if: Defer the if_up until the ifnet.if_ioctl is called.

2016-12-25 Thread sepherosa_gmail.com (Sepherosa Ziehau)
sepherosa_gmail.com created this revision. sepherosa_gmail.com added reviewers: delphij, royger, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com, adrian, hiren, bz, gnn, glebius, karels. sepherosa_gmail.com added a subscriber: freebsd-net-list. REVISION SUMMARY So if_{down,up}

[Differential] D8904: inet: Fix routing issue by calling if_up()

2016-12-25 Thread sepherosa_gmail.com (Sepherosa Ziehau)
sepherosa_gmail.com created this revision. sepherosa_gmail.com added reviewers: delphij, royger, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com, adrian, bz, gnn, hiren, glebius, rwatson, karels. sepherosa_gmail.com added a subscriber: freebsd-net-list. REVISION SUMMARY This

Problem reports for freebsd-net@FreeBSD.org that need special attention

2016-12-25 Thread bugzilla-noreply
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

Re: How to configure another loopback device?

2016-12-25 Thread Hiroki Sato
John Dison wrote in <788296467.1718144.1482676705...@mail.yahoo.com>: jd> Also one more thing which looks strange: if I use jd> ifconfig_lo1_ipv6="inet6 auto_linklocal", then ipv6 aliases on lo1 are jd> configured correctly, but there is no link-local address. If I jd> exclude this line from r

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

2016-12-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215513 Michael Tuexen changed: What|Removed |Added Assignee|freebsd-net@FreeBSD.org |tue...@freebsd.org -- You are re

Fw: How to configure another loopback device?

2016-12-25 Thread John Dison via freebsd-net
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 ::1/128 will be on lo1. If I do not add that line, it will be on lo0. jd>

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

2016-12-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215513 --- Comment #7 from Peter Holm --- (In reply to Peter Holm from comment #6) No problems seen in four hours. LGTM. -- You are receiving this mail because: You are the assignee for the bug. ___ fr

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

2016-12-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215513 --- Comment #6 from Peter Holm --- (In reply to Michael Tuexen from comment #5) Looks promising. I'll let the test run a bit longer, just to be sure. -- You are receiving this mail because: You are the assignee for the bug. __

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

2016-12-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215513 --- Comment #5 from Michael Tuexen --- By looking at your Details, your system is low on memory when the problem occurs. Can you just remove the KASSERT http://fxr.watson.org/fxr/source/netinet/tcp_sack.c#L474 and retest? I think if tcp_sac

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

2016-12-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215513 --- Comment #4 from Peter Holm --- (In reply to Michael Tuexen from comment #2) Michael, the panic is very easy to reproduce on my hardware. What do I need to do? -- You are receiving this mail because: You are the assignee for the bug.

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

2016-12-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215513 --- Comment #3 from Peter Holm --- (In reply to Hiren Panchasara from comment #1) Sure: OK set hw.physmem=6g : $ svnlite checkout -q svn://svn.freebsd.org/base/user/pho/stress2 $ cd stress2 $ make > /dev/null $ echo "testuser=stress" > `