<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with bulk import]]></title><description><![CDATA[A list of topics that have been tagged with bulk import]]></description><link>https://forum.netgate.com/tags/bulk import</link><generator>RSS for Node</generator><lastBuildDate>Thu, 12 Mar 2026 01:43:49 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/tags/bulk import.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[how to bulk import netblocks into an alias?]]></title><description><![CDATA[While this system of keeping an active list of a company's netblocks works great -- beware.  It can suck up memory and result in "cannot allocate memory" errors.  Example: building a list for Apple (AS6185) will give you a large list of small netblocks in 17.x.x.x.  However, "whois 17.0.0.0" shows that 17.0.0.0/8 is a direct allocation to Apple, so specifying a network alias with a /8 takes a lot less memory.  Google is even worse with 7400+ IPv4 netblocks from the whois ASN output.
]]></description><link>https://forum.netgate.com/topic/171564/how-to-bulk-import-netblocks-into-an-alias</link><guid isPermaLink="true">https://forum.netgate.com/topic/171564/how-to-bulk-import-netblocks-into-an-alias</guid><dc:creator><![CDATA[beerguzzle]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>