Assets
Use GeoSite and GeoIP records as reusable routing material.
Updated
Assets are reusable lists of destination records. GeoSite records describe domain groups. GeoIP records describe IP ranges. After adding assets, the Rule editor can search their records and attach them to routing rules.
When assets help
GeoSite
A maintained group of domain records.
Good fit You want to route or block a site family, country list, category, or provider-maintained domain set.
Not ideal One exact domain is enough.
GeoIP
A maintained group of IP ranges.
Good fit You need rules for country, provider, private, or network ranges.
Not ideal The destination is better identified by domain.
Add and use an asset
Add Predefined fetches the first records
Add Predefined is a bootstrap action for an empty asset setup. It creates GeoSite and GeoIP entries and immediately fetches both over the network. The GeoSite entry uses the geosite.dat source and starts with Minification off. The GeoIP entry uses the geoip.dat source and starts with Minification on. If a matching predefined source already exists, Tunna skips the duplicate instead of adding it again.
Asset edit fields
General settings
Name controls the row label. Type chooses GeoSite or GeoIP. Minification changes how records are stored the next time the asset is processed.
Name
Use a readable label such as GeoSite, GeoIP, Ads, or Private Ranges.
Type
Choose GeoSite for domain groups or GeoIP for IP ranges.
Minification
Keep it on when you want Tunna to reduce redundant records during processing. For GeoSite it can reduce repeated domain entries; for GeoIP it can merge overlapping or adjacent CIDR blocks.
Source and details
The Source section holds the URL and shows the current status. Paste fills the Source URL and starts a fetch after a valid URL is submitted and the network is available. After a successful fetch, Asset Details shows Records, File Size, and Last Update for remote assets.
Source URL
Enter the remote .dat URL and submit or save it. Tunna needs network access before it can fetch or update remote assets.
Update
Refreshes the remote file and reprocesses records.
Delete
Removes the asset and its stored records. Local assets have no update option, and deleting any asset can remove matching chips from routing rules.
Reading asset rows
Rows show a status dot and text. Fetching data and Processing data rows show progress. Other rows show record count and file size after processing has finished. Ready to fetch means the source is saved but has not fetched yet. Active means records are available. Failed shows an error when Tunna has one. Expired means the last successful update is older than one month.
List actions and disabled states
The toolbar Update button refreshes all remote assets. It is disabled when the list is empty, when every asset is local, or while any asset is fetching or processing. Swipe an asset row to Delete it. Remote rows also have their own Update action, disabled while that asset is fetching or processing. After an update or deletion, Tunna keeps routing-rule chips only for records that still exist.
How rule Asset search uses records
In a routing rule, an empty Asset search shows only records already attached to that rule. Typing searches installed GeoSite and GeoIP records case-insensitively, shows up to 20 new matches, prefers prefix matches, and adds the first found match when you press Return. If any asset is fetching or processing, the Asset tab shows progress rows instead of the search field. If no assets exist yet, the tab shows compact asset setup with Add Predefined.
Use trusted asset sources
Assets can influence many routing rules at once. Add remote assets only from sources you trust, and expect large lists to take time, storage, and network data to fetch and process.