On 2015-03-15 16:29:02 (+0300), Andrey V. Elsukov wrote:
> This is very rare case, I think, but plen can be zero in case, when
> jumbo payload option is present. Probably this is the reason why this
> check is done after hop-by-hop options parsing.
>
You're right, I missed that. The proposed patc
On 2015-03-16 09:51:55 (-0400), Eric van Gyzen wrote:
> Here is a brainstorm that might give the best of both: Return the
> reassembled packet from PFIL_IN, but with the original fragment chain
> stashed in metadata. Most of the stack operates on the single,
> reassembled packet. ip6_output() s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=138782
Hiren Panchasara changed:
What|Removed |Added
Version|8.0-BETA4 |10.1-STABLE
CC|
On 16.03.2015 at 19:40 wrote Andrey V. Elsukov:
Hi,
I already have implemented generic IPv6 support for gre(4) in r274246.
But if you want to add something, there are some missing features, e.g.
GRE keepalives (1), IPv6 tunnel encapsulation limit option (2).
Hi Andrey,
Great work! I will tak
On 16.03.2015 17:29, Julian Kornberger wrote:
> Hi,
>
> is anyone interested in implementing gre(4) over IPv6?
> It seems that there has not been any progress since 2012:
> https://wiki.freebsd.org/IPv6TODO#gre.284.29_over_IPv6
Hi,
I already have implemented generic IPv6 support for gre(4) in r2
if_igb and ixgbe iirc don't set the full flowid unless you're using
RSS. They're just setting the CPU/MSIX id.
-a
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-ne
Hi,
is anyone interested in implementing gre(4) over IPv6?
It seems that there has not been any progress since 2012:
https://wiki.freebsd.org/IPv6TODO#gre.284.29_over_IPv6
Kind Regards
Julian
___
freebsd-net@freebsd.org mailing list
http://lists.freebs
On 03/13/2015 22:05, Kristof Provost wrote:
> At that point we run into the packet size check, which in ip6_forward()
> is done before the pfil(PFIL_OUT) hook. That means that we'll send an
> ICMP6_PACKET_TOO_BIG error rather than forwarding the packet.
>
> The proposed fix in D1815 is to simply m
On Thu, Mar 12, 2015 at 12:01:13PM -0400, John Baldwin wrote:
J> On Thursday, March 12, 2015 04:07:54 PM Hans Petter Selasky wrote:
J> > On 02/28/15 13:28, John Baldwin wrote:
J> > > On Friday, February 27, 2015 10:23:10 PM Gleb Smirnoff wrote:
J> > >> On Thu, Feb 26, 2015 at 08:25:59PM -0800, Adri
On 03/16/15 10:37, Vitalii Duk wrote:
I've changed use_flowid to 0 and it helped! But isn't it setting
significant? In a description it says "Shift flowid bits to prevent
multiqueue collisions".
Hi,
Maybe your ethernet hardware is not properly setting the m_flowid ...
--HPS
__
I've changed use_flowid to 0 and it helped! But isn't it setting
significant? In a description it says "Shift flowid bits to prevent
multiqueue collisions".
On 16 March 2015 at 09:50, Konstantin Kulikov wrote:
> Hello, Vitalii.
>
> Make sure following sysctl are set to zero:
> sysctl net.link.la
Hello, Vitalii.
Make sure following sysctl are set to zero:
sysctl net.link.lagg.default_use_flowid=0
sysctl net.link.lagg.0.use_flowid=0
sysctl net.link.lagg.1.use_flowid=0
Then adjust lagghash depending on your configuration.
For example if you freebsd machine acts as router with single, defaul
12 matches
Mail list logo