Enigma2 with PuTTY: Complete SSH Setup & Command Guide
master G
- 📡 Part 1: Initial PuTTY Setup & Connection
- ⚙️ Part 2: Essential Enigma2 SSH Commands (Cheat Sheet)
- Logs & Troubleshooting
- 🔐 Part 3: Security & Best Practices
- 🚨 Part 4: Common Issues & Fixes
- 📂 Part 5: Useful File Paths to Know
- Pro Tip: Always run init 4 before editing critical files and init 3 after to restart the GUI cleanly.
Topic: Advanced Enigma2 Management | Difficulty: Intermediate | Tools: PuTTY (Windows)
Looking to unlock true power-user control of your Enigma2 receiver? SSH access via PuTTY gives you command-line mastery, letting you troubleshoot, automate, and configure your box in ways the GUI can't. This guide covers everything from your first connection to essential command examples.
📡 Part 1: Initial PuTTY Setup & Connection
Step 1: Enable SSH on Your Enigma2 Box
Before connecting, SSH must be active on your receiver:
- Go to MENU > Setup > System > Network
- Select Password & Security (or similar, varies by image)
- Ensure SSH or Enable SSH is set to Yes/Enabled
- Note your receiver's local IP address
Step 2: Configure PuTTY on Windows
- Download PuTTY from the official site (putty.org) - use the standalone
.exe - Launch PuTTY and enter connection details:
- Host Name: Your receiver's IP (e.g.,
192.168.1.100) - Port:
22 - Connection Type:
SSH
- Host Name: Your receiver's IP (e.g.,
- Save your session for quick future access:
- Enter a name (e.g., "My_Enigma2_Box")
- Click Save
Step 3: First Login
- Click Open to start the connection
- Accept the security alert (first time only)
- At the login prompt, enter:
login as: root
password: [password must first be setup on Enigma2 image to gain access]
- Note: Most images require a password to be setup first to gain access - Create password for FTP: OE-A images
- You should see a command prompt ending with
~#- you're in!
⚙️ Part 2: Essential Enigma2 SSH Commands (Cheat Sheet)
Save these commands for daily use. Most require root access (which you have).
System Control & Information
reboot # Restart the entire receiver
init 4 # Stop Enigma2 GUI (safe mode for edits)
init 3 # Restart Enigma2 GUI
top # Live system resource monitor (Ctrl+C to exit)
df -h # Check disk space usage
free -m # Check RAM usage
File & Configuration Management
cd /etc/enigma2 # Navigate to main config directory
ls -la # List files with details
nano bouquets.tv # Edit channel list with nano editor
cp file.conf file.conf.backup # Create backup before editing
Service Management
/etc/init.d/enigma2 restart # Restart Enigma2 service only
/etc/init.d/networking restart # Restart network services
Package & Plugin Management (opkg)
opkg update # Update available package list
opkg list-installed # Show all installed plugins/packages
opkg install plugin-name # Install a specific plugin
opkg remove plugin-name # Remove a plugin
Logs & Troubleshooting
tail -f /var/log/messages # Monitor system logs in real-time
dmesg | tail -20 # View last 20 kernel messages
ps aux | grep enigma2 # Check if Enigma2 process is running
🔐 Part 3: Security & Best Practices
⚠️ Important: With great power comes great responsibility. SSH access is essentially "root" control.
Change the Default Password (Immediately!)
Once logged in, run:
passwd
Then enter and confirm a strong new password.
Create an SSH Key Pair (Advanced/Secure)
For password-less, more secure login:
- Generate keys on your PC with PuTTYgen
- Upload the public key to
/root/.ssh/authorized_keyson the receiver - Disable password authentication in
/etc/ssh/sshd_config(advanced)
Disable SSH When Not Needed
For long periods of non-use, go back to MENU > Setup > System > Network and disable SSH.
🚨 Part 4: Common Issues & Fixes
"Connection Refused" Error
• SSH is not enabled on the receiver (go back to Part 1, Step 1)
• Wrong IP address - double-check in your receiver's network settings
• Firewall blocking port 22
"Access Denied" / Login Failures
• Incorrect username (should be root)
• Password was changed and forgotten
• Try blank password if you never set one
Session Disconnects After Inactivity
In PuTTY, before connecting:
- Go to Connection
- Set "Seconds between keepalives" to
60 - This sends a small packet every minute to keep the connection alive
📂 Part 5: Useful File Paths to Know
Pro Tip: Always run init 4 before editing critical files and init 3 after to restart the GUI cleanly.
linuxsat-support.com/thread/161760/