Andrey,
1. Sockets are unconnected
2. Datagrams are unicast
-Max
On Mon, Sep 5, 2016 at 6:46 AM, Andrey V. Elsukov wrote:
> On 05.09.16 15:42, Maxim Sobolev wrote:
> > Suppose we have two threads in the system both bound to a same specific
> UDP
> > port, one using
Hi,
We've just changed the network config on a box - going from a single 'em1'
adapter to a lagg failover of em0, em1.
This works - but we noticed after the machine rebooted, we couldn't ping it
from other hosts.
Checking on other machines on the LAN they still had an ARP entry for the
--On 06 September 2016 09:13 +0100 Karl Pielorz
wrote:
We've just changed the network config on a box - going from a single
'em1' adapter to a lagg failover of em0, em1.
Sorry - not enough coffee yet, I should have said this is on FreeBSD
10.3-RELEASE-p7 amd64...
Yes known issue I'm afraid.
I created a patch set to address this but there where objections so it
was removed, see the attached which is based on 10.2-RELEASE.
On 06/09/2016 09:13, Karl Pielorz wrote:
Hi,
We've just changed the network config on a box - going from a single
'em1' adapter
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212331
Mark Linimon changed:
What|Removed |Added
CC|freebsd-i...@freebsd.org|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212283
Gleb Smirnoff changed:
What|Removed |Added
Summary|network watchdog timeout|oversized IP
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212283
--- Comment #12 from Gleb Smirnoff ---
I think we shouldn't tweak the ip_len in the kernel. If userland supplies
oversized datagram, greater than interface MTU, we should just drop it
silently.
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212283
--- Comment #13 from Gleb Smirnoff ---
Not silently. Better return EFBIG to userland.
--
You are receiving this mail because:
You are the assignee for the bug.
___