[quagga-dev 1028] Re: Linux and netlink

Hasso Tepper hasso at estpak.ee
Thu Apr 8 12:25:52 BST 2004


Paul Jakma wrote:
> On Thu, 8 Apr 2004, Hasso Tepper wrote:
> > It's not so easy. From man 7 socket:
> >
> > SO_RCVBUF
> > Sets  or  gets  the maximum socket receive buffer in bytes. The
> > default value is set by the rmem_default sysctl and the maximum
> > allowed value is set by the rmem_max sysctl.
> >
> > hasso at test3:/proc/sys$ cat /proc/sys/net/core/rmem_default
> > 65535
> > hasso at test3:/proc/sys$ cat /proc/sys/net/core/rmem_max
> > 65535
>
> ah dear, yes.
>
> > I got my router working with 524280. Btw, it depends what
> > features you have enabled in router. Enabled multicast and ipv6
> > make things worse of course (more routes are added when interface
> > is upped).
>
> yes.
>
> > It wasn't so bad with older zebra, btw and I have feeling that
> > one patch
> > (http://marc.theaimsgroup.com/?l=zebra&m=102379207214720&w=2)
> > made things worse.
>
> Quite possibly.
>
> Could we then just document the rmem_max sysctl and make the rcvbuf
> configurable? (we cant twiddle the sysctl because the kernel doesnt
> honour CAP_NET_ADMIN for net related sysctl's) (and grr #2, iirc
> zebra reads the routing table before it parses the config file).

Maybe documenting rmem_max and rmem_default in enough? In case of 
incereased rmem_default every created socket will have this receive 
buffer size though.

-- 
Hasso Tepper
Elion Enterprises Ltd.
WAN administrator



More information about the Quagga-dev mailing list