Text Generation
PEFT
Safetensors
GGUF
English
lora
cisco
networking
security
wazuh
incident-response
network-automation
restconf
ospf
bgp
conversational
Instructions to use JoeiBanana/ai-network-llms with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- PEFT
How to use JoeiBanana/ai-network-llms with PEFT:
Task type is invalid.
- Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- llama.cpp
How to use JoeiBanana/ai-network-llms with llama.cpp:
Install (macOS, Linux)
curl -LsSf https://llama.app/install.sh | sh # Start a local OpenAI-compatible server with a web UI: llama serve -hf JoeiBanana/ai-network-llms:Q4_K_M # Run inference directly in the terminal: llama cli -hf JoeiBanana/ai-network-llms:Q4_K_M
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf JoeiBanana/ai-network-llms:Q4_K_M # Run inference directly in the terminal: llama cli -hf JoeiBanana/ai-network-llms:Q4_K_M
Use pre-built binary
# Download pre-built binary from: # https://github.com/ggerganov/llama.cpp/releases # Start a local OpenAI-compatible server with a web UI: ./llama-server -hf JoeiBanana/ai-network-llms:Q4_K_M # Run inference directly in the terminal: ./llama-cli -hf JoeiBanana/ai-network-llms:Q4_K_M
Build from source code
git clone https://github.com/ggerganov/llama.cpp.git cd llama.cpp cmake -B build cmake --build build -j --target llama-server llama-cli # Start a local OpenAI-compatible server with a web UI: ./build/bin/llama-server -hf JoeiBanana/ai-network-llms:Q4_K_M # Run inference directly in the terminal: ./build/bin/llama-cli -hf JoeiBanana/ai-network-llms:Q4_K_M
Use Docker
docker model run hf.co/JoeiBanana/ai-network-llms:Q4_K_M
- LM Studio
- Jan
- vLLM
How to use JoeiBanana/ai-network-llms with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "JoeiBanana/ai-network-llms" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "JoeiBanana/ai-network-llms", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker
docker model run hf.co/JoeiBanana/ai-network-llms:Q4_K_M
- Ollama
How to use JoeiBanana/ai-network-llms with Ollama:
ollama run hf.co/JoeiBanana/ai-network-llms:Q4_K_M
- Unsloth Desktop
- Pi
How to use JoeiBanana/ai-network-llms with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf JoeiBanana/ai-network-llms:Q4_K_M
Configure the model in Pi
# Install Pi: npm install -g @earendil-works/pi-coding-agent # Add to ~/.pi/agent/models.json: { "providers": { "llama-cpp": { "baseUrl": "http://localhost:8080/v1", "api": "openai-completions", "apiKey": "none", "models": [ { "id": "JoeiBanana/ai-network-llms:Q4_K_M" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Docker Model Runner
How to use JoeiBanana/ai-network-llms with Docker Model Runner:
docker model run hf.co/JoeiBanana/ai-network-llms:Q4_K_M
- Lemonade
How to use JoeiBanana/ai-network-llms with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull JoeiBanana/ai-network-llms:Q4_K_M
Run and chat with the model
lemonade run user.ai-network-llms-Q4_K_M
List all available models
lemonade list
- Hermes Agent
How to use JoeiBanana/ai-network-llms with Hermes Agent:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf JoeiBanana/ai-network-llms:Q4_K_M
Configure Hermes
# Install Hermes: curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash hermes setup # Point Hermes at the local server: hermes config set model.provider custom hermes config set model.base_url http://127.0.0.1:8080/v1 hermes config set model.default JoeiBanana/ai-network-llms:Q4_K_M
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use JoeiBanana/ai-network-llms with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf JoeiBanana/ai-network-llms:Q4_K_M
Configure OpenClaw
# Install OpenClaw: npm install -g openclaw@latest # Register the local server and set it as the default model: openclaw onboard --non-interactive --mode local \ --auth-choice custom-api-key \ --custom-base-url http://127.0.0.1:8080/v1 \ --custom-model-id "JoeiBanana/ai-network-llms:Q4_K_M" \ --custom-provider-id llama-cpp \ --custom-compatibility openai \ --custom-text-input \ --accept-risk \ --skip-health
Run OpenClaw
openclaw agent --local --agent main --message "Hello from Hugging Face"
| {"instruction": "Analyze and correlate the following Wazuh alert with the Cisco running configuration. Determine which device, interface, VLAN, or ACL is related to the given indicators, and describe the affected network components.", "context_summary": "Incident type: port_scan. Severity: high, classification: suspicious. Indicators: none. Recommended actions: Block source IP 203.0.113.45 at firewall, Notify security team.", "wazuh_alert": {"incident_type": "port_scan", "classification": "suspicious", "severity": "high", "source_ip": "203.0.113.45", "destination_ip": "10.0.20.7", "ioc": ["203.0.113.45"], "recommended_actions": ["Block source IP 203.0.113.45 at firewall", "Notify security team"], "explanation": "A port scan is an attempt to probe multiple ports on a system, which can be indicative of malicious activity"}, "config_raw": ""} | |
| {"instruction": "Analyze and correlate the following Wazuh alert with the Cisco running configuration. Determine which device, interface, VLAN, or ACL is related to the given indicators, and describe the affected network components.", "context_summary": "Incident type: data_exfiltration. Severity: high, classification: suspicious. Indicators: 10.1.1.15, 185.199.108.12. Recommended actions: Verify data transfer with network team, Review firewall rules and configurations.", "wazuh_alert": {"incident_type": "data_exfiltration", "classification": "suspicious", "severity": "high", "source_ip": "10.1.1.15", "destination_ip": "185.199.108.12", "iocs": ["10.1.1.15", "185.199.108.12"], "recommended_actions": ["Verify data transfer with network team", "Review firewall rules and configurations"], "explanation": "The event indicates a potential exfiltration of large amounts of data from the internal host to an external host over HTTPS"}, "config_raw": ""} | |
| {"instruction": "Analyze and correlate the following Wazuh alert with the Cisco running configuration. Determine which device, interface, VLAN, or ACL is related to the given indicators, and describe the affected network components.", "context_summary": "Incident type: malware. Severity: high, classification: suspicious. Indicators: d41d8cd98f00b204e9800998ecf8427e. Recommended actions: Remove the malware, Run full system scan.", "wazuh_alert": {"incident_type": "malware", "classification": "suspicious", "severity": "high", "source_ip": null, "destination_ip": null, "iocs": ["d41d8cd98f00b204e9800998ecf8427e"], "recommended_actions": ["Remove the malware", "Run full system scan"], "explanation": "The Wazuh alert indicates that a malicious binary was detected on the system, which suggests potential malware activity. The recommended actions are to remove the malware and run a full system scan to ensure no further issues."}, "config_raw": ""} | |
| {"instruction": "Analyze and correlate the following Wazuh alert with the Cisco running configuration. Determine which device, interface, VLAN, or ACL is related to the given indicators, and describe the affected network components.", "context_summary": "Incident type: bgp_route_table_anomaly. Severity: medium, classification: suspicious. Indicators: none. Recommended actions: Verify the BGP configuration on core-router-01, Check for any recent changes to the routing policy.", "wazuh_alert": {"incident_type": "bgp_route_table_anomaly", "classification": "suspicious", "severity": "medium", "source_ip": null, "destination_ip": "198.51.100.9", "ioc": ["10.0.0.0/8", "172.16.0.0/12"], "recommended_actions": ["Verify the BGP configuration on core-router-01", "Check for any recent changes to the routing policy"], "explanation": "The log indicates an unexpected prefix announcement from a peer router, which could be indicative of a potential security risk or misconfiguration."}, "config_raw": ""} | |
| {"instruction": "Analyze and correlate the following Wazuh alert with the Cisco running configuration. Determine which device, interface, VLAN, or ACL is related to the given indicators, and describe the affected network components.", "context_summary": "Incident type: brute_force. Severity: high, classification: suspicious. Indicators: none. Recommended actions: Block source IP 192.0.2.111, Investigate further.", "wazuh_alert": {"incident_type": "brute_force", "classification": "suspicious", "severity": "high", "source_ip": "192.0.2.111", "destination_ip": null, "ioc_list": ["192.0.2.111"], "recommended_actions": ["Block source IP 192.0.2.111", "Investigate further"], "explanation": "This alert indicates a high volume of RDP authentication failures, which may indicate a brute force attack"}, "config_raw": ""} | |
| {"instruction": "Analyze and correlate the following Wazuh alert with the Cisco running configuration. Determine which device, interface, VLAN, or ACL is related to the given indicators, and describe the affected network components.", "context_summary": "Incident type: suspicious. Severity: medium, classification: suspicious. Indicators: none. Recommended actions: Verify container logs for suspicious activity, Check for signs of unauthorized code execution.", "wazuh_alert": {"incident_type": "suspicious", "classification": "suspicious", "severity": "medium", "source_ip": "10.0.80.6", "destination_ip": "185.199.108.12", "ioc_list": ["185.199.108.12"], "recommended_actions": ["Verify container logs for suspicious activity", "Check for signs of unauthorized code execution"], "explanation": "This incident indicates that the container has been compromised by an external payload, which may lead to further malicious activity."}, "config_raw": ""} | |