Re: 1M routes or 1M arp entries
On 2017/08/14 16:48, Simon Mages wrote: > Hi, > > you may want to take a look into /etc/login.conf > login.conf(5), cap_mkdb(1) I wouldn't normally recommend cap_mkdb for the login.conf file, it's too easy to forget to update the db after making a change. I'd just edit the text file. You will need to fully logout for changes to take effect (with ssh multiplexing, the master needs to exit; with X, you need a new session).
Re: 1M routes or 1M arp entries
On 14.8.2017. 16:48, Simon Mages wrote: > Hi, > > you may want to take a look into /etc/login.conf > login.conf(5), cap_mkdb(1) > > In this file you can fiddle with you limit maxima > for login classes. > > BR > Simon > Thank you, i will do that ...
Re: 1M routes or 1M arp entries
Hi, you may want to take a look into /etc/login.conf login.conf(5), cap_mkdb(1) In this file you can fiddle with you limit maxima for login classes. BR Simon 2017-08-14 16:28 GMT+02:00, Hrvoje Popovski: > On 14.8.2017. 16:03, Alexander Bluhm wrote: >> On Mon, Aug 14, 2017 at 03:52:56PM +0200, Hrvoje Popovski wrote: >>> # netstat -rnf inet >>> netstat: Cannot allocate memory >> >> Have you tried to increase ulimit -d ? > > it seems that i can decrease it but not increase it, or i don't know how > to do it properly :) > > # ulimit -d > 33554432 > > # ulimit -d 33554433 > > # ulimit -d > 33554432 > >
Re: 1M routes or 1M arp entries
On 14.8.2017. 16:03, Alexander Bluhm wrote: > On Mon, Aug 14, 2017 at 03:52:56PM +0200, Hrvoje Popovski wrote: >> # netstat -rnf inet >> netstat: Cannot allocate memory > > Have you tried to increase ulimit -d ? it seems that i can decrease it but not increase it, or i don't know how to do it properly :) # ulimit -d 33554432 # ulimit -d 33554433 # ulimit -d 33554432
Re: 1M routes or 1M arp entries
On Mon, Aug 14, 2017 at 03:52:56PM +0200, Hrvoje Popovski wrote: > # netstat -rnf inet > netstat: Cannot allocate memory Have you tried to increase ulimit -d ? bluhm
1M routes or 1M arp entries
Hi all, when openbsd imports cca 1M routes or more and if i want to see them with "netstat -rn" i'm getting "Cannot allocate memory". bgpd can see all routes. i don't think that this is real problem but full bgp table is cca 700K routes. # bgpctl show ip bgp mem RDE memory statistics 1245184 IPv4 unicast network entries using 47.5M of memory 2490368 rib entries using 152M of memory 2490368 prefix entries using 152M of memory 1 BGP path attribute entries using 120B of memory 1 BGP AS-PATH attribute entries using 37B of memory, and holding 1 references 0 BGP attributes entries using 0B of memory and holding 0 references 0 BGP attributes using 0B of memory RIB using 352M of memory # bgpctl show ip bgp | wc -l 1245188 # netstat -rnf inet netstat: Cannot allocate memory same happens with arp. if cca 1M arp entries are injected with "arp" and "netstat -rn" i'm getting "Cannot allocate memory". of course that this is extremely ridiculous example, but i would be good if i can a least delete arp entries. # vmstat -m | egrep "Name|arp" NameSize Requests FailInUse Pgreq Pgrel Npage Hiwat Minpg Maxpg Idle arp 56 14819030 983053 13950 104 13846 13846 0 80 # arp -an HostEthernet AddressNetif ExpireFlags arp: malloc: Cannot allocate memory # arp -ad arp: malloc: Cannot allocate memory # netstat -rnf inet netstat: Cannot allocate memory