Re: Does FreeBSD do proactive ARP refresh?
> 18.03.2018, 03:31, "Rodney W. Grimes" : > >> ?17.03.2018, 21:23, "Rodney W. Grimes" > >> : > >> ?>> ?16.03.2018, 14:50, "sth...@nethelp.no" : > >> ?>> ?.. > >> ?>> ?>> ?And thank you for that suggestion! The packet loss during ARP > >> refresh > >> ?>> ?>> ?(of the destination address connected to the output interface) > >> does > >> ?>> ?>> ?*not* happen when the box is forwarding! It only happens with > >> locally > >> ?>> ?>> ?generated traffic. > >> ?>> ?Should be fixed by r331098. > >> ?> > >> ?> Thanks for the quick fix, do we know about when this breakage started? > >> ?I guess it's something like r297225. > > > > SO 2 years ago, meaning it effects stable/11, > > and may of been merged to stable/10? > Side note: if one has monitoring which does ICMP checks, it will mask the > issue because icmp replies don't use route caching. > Typical story when the observer changes the state of an observed object :-). Also perhaps why it has not been reported before, as other side effects have caused it to be a pretty invisible issue. > IIRC it was not merged to stable/10. > > > > Do you plan to MFC your fix? > Yes, I do :-) For some reason the MFC: 2 weeks did not register when I read the commit. -- Rod Grimes rgri...@freebsd.org ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Does FreeBSD do proactive ARP refresh?
> > Side note: if one has monitoring which does ICMP checks, it will mask the > > issue because icmp replies don't use route caching. > > Typical story when the observer changes the state of an observed object > > :-). > > Also perhaps why it has not been reported before, as other side effects > have caused it to be a pretty invisible issue. The reason I discovered this is because I was running longer (1 hour or more) iperf3 sessions, and I got some small but regular packet loss that I couldn't remember having seen before. Which may be because my previous longer iperf3 sessions had been with FreeBSD 9.3-STABLE. Steinar Haug, Nethelp consulting, sth...@nethelp.no ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Does FreeBSD do proactive ARP refresh?
18.03.2018, 03:31, "Rodney W. Grimes" : > [ Charset UTF-8 unsupported, converting... ] >> 17.03.2018, 21:23, "Rodney W. Grimes" : >> >> ?16.03.2018, 14:50, "sth...@nethelp.no" : >> >> ?.. >> >> ?>> ?And thank you for that suggestion! The packet loss during ARP >> refresh >> >> ?>> ?(of the destination address connected to the output interface) does >> >> ?>> ?*not* happen when the box is forwarding! It only happens with >> locally >> >> ?>> ?generated traffic. >> >> ?Should be fixed by r331098. >> > >> > Thanks for the quick fix, do we know about when this breakage started? >> I guess it's something like r297225. > > SO 2 years ago, meaning it effects stable/11, > and may of been merged to stable/10? Side note: if one has monitoring which does ICMP checks, it will mask the issue because icmp replies don't use route caching. Typical story when the observer changes the state of an observed object :-). IIRC it was not merged to stable/10. > > Do you plan to MFC your fix? Yes, I do :-) > > -- > Rod Grimes rgri...@freebsd.org > ___ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Problem reports for freebsd-net@FreeBSD.org that need special attention
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 obsolete releases. Status |Bug Id | Description +---+--- In Progress |165622 | [ndis][panic][patch] Unregistered use of FPU in k In Progress |206581 | bxe_ioctl_nvram handler is faulty In Progress |221146 | [ixgbe] Problem with second laggport New |204438 | setsockopt() handling of kern.ipc.maxsockbuf limi New |205592 | TCP processing in IPSec causes kernel panic New |206053 | kqueue support code of netmap causes panic New |209682 | [panic] [netinet] arptimer race New |213410 | [carp] service netif restart causes hang only whe New |217748 | sys/dev/ixgbe/if_ix.c: PVS-Studio: Assignment to Open|193452 | Dell PowerEdge 210 II -- Kernel panic bce (broadc Open|194485 | Userland cannot add IPv6 prefix routes Open|194515 | Fatal Trap 12 Kernel with vimage Open|199136 | [if_tap] Added down_on_close sysctl variable to t Open|202510 | [CARP] advertisements sourced from CARP IP cause Open|206544 | sendmsg(2) (sendto(2) too?) can fail with EINVAL; Open|211962 | bxe driver queue soft hangs and flooding tx_soft_ Open|213814 | AWS/EC2: no egress traffic stats on ixv(4) Open|73 | igb(4): Kernel panic (fatal trap 12) due to netwo 18 problems total for which you should take action. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 206721] FreeBSDs DHCP client(dhclient) does not support the interface-mtu option(option 26).
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206721 --- Comment #7 from commit-h...@freebsd.org --- A commit references this bug: Author: eadler Date: Mon Mar 19 04:16:38 UTC 2018 New revision: 331179 URL: https://svnweb.freebsd.org/changeset/base/331179 Log: MFC r305306: dhclient: add support for interface-mtu (26) Make dhclient set interface MTU if it was provided. This version implements MTU setting in dhclient itself before it runs dhclient-script. PR: 206721 Changes: _U stable/11/ stable/11/sbin/dhclient/clparse.c stable/11/sbin/dhclient/dhclient.c stable/11/sbin/dhclient/dhcpd.h stable/11/sbin/dhclient/dispatch.c stable/11/sbin/dhclient/privsep.c stable/11/sbin/dhclient/privsep.h -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 199136] [if_tap] Added down_on_close sysctl variable to tap(4)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199136 Eugene Grosbein changed: What|Removed |Added Resolution|--- |DUPLICATE Status|Open|Closed --- Comment #11 from Eugene Grosbein --- Just use ifconfig_tap0="inet 192.168.0.1/29 link0" *** This bug has been marked as a duplicate of bug 165174 *** -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 165174] [patch] [tap] allow tap(4) to keep its address on close
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165174 Eugene Grosbein changed: What|Removed |Added CC||y...@freebsd.org --- Comment #4 from Eugene Grosbein --- *** Bug 199136 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
