| Feature / Service | Azure Load Balancer | Application Gateway | Azure Front Door | Traffic Manager |
|---|---|---|---|---|
| OSI Layer | Layer 4 (Transport) | Layer 7 (Application) | Layer 7 (Application) | DNS-based (Layer 7 via DNS) |
| Scope | Regional or Global | Regional | Global | Global |
| Traffic Type | TCP/UDP (non-HTTP/S) | HTTP/HTTPS | HTTP/HTTPS | Any (via DNS redirection) |
| Protocol Awareness | No content inspection | URL path, host header, SSL termination | URL path, host header, SSL termination, caching | DNS-based routing only |
| Health Probes | TCP/HTTP/HTTPS | HTTP/HTTPS | HTTP/HTTPS | DNS endpoint monitoring |
| Session Affinity | Source IP affinity | Cookie-based | Supported | Not supported |
| Web Application Firewall | ❌ | ✅ | ✅ | ❌ |
| SSL Termination | ❌ | ✅ | ✅ | ❌ |
| Caching / CDN | ❌ | ❌ | ✅ | ❌ |
| Public/Private Support | ✅ Both | ✅ Both | ✅ Public only | ✅ Public only |
| Use Case | Internal or external TCP/UDP balancing | Secure web apps with custom routing | Global web apps with low latency | Geo-routing and DNS-based failover |
| Best For | VM-level traffic, AKS, backend services | Web apps needing WAF, SSL offload | APIs, static content, multi-region apps | Multi-region apps needing DNS balancing |
| Pricing | Basic (free), Standard (paid) | Standard_v2 / WAF_v2 | Standard / Premium | Based on DNS queries and monitoring |
Author: Manjunath
“Life is about passions. Thank you for sharing mine” -- M. Schumacher
🧩 OSI Model Layers – Complete Overview
| Layer | Function | Key Protocols & Examples |
|---|---|---|
| Application (7) | Closest to the user; provides network services and interfaces for applications | HTTP, FTP, DNS, SMTP, SNMP |
| Presentation (6) | Translates, encrypts, compresses data; ensures machine-independent data formatting | SSL/TLS, JPEG, MPEG, ASCII, EBCDIC |
| Session (5) | Manages sessions or connections between applications; handles authentication and synchronization | NetBIOS, RPC, PPTP, SAP, SDP |
| Transport (4) | Provides reliable or unreliable data transport with error recovery and flow control | TCP, UDP, SCTP, SPX |
| Network (3) | Handles logical addressing and routing between different networks | IP (IPv4/IPv6), ICMP, IGMP, IPsec |
| Data Link (2) | Ensures reliable transfer across physical link; handles MAC addressing and framing | Ethernet, PPP, ARP, MAC, HDLC, Frame Relay |
| Physical (1) | Transmits raw bitstreams over physical media; defines hardware specs and signal modulation | Coaxial cable, RJ45, Fiber optics, Wi-Fi, Bluetooth, Hubs |
☁️ Cloud Migration Strategies in a Nutshell
Thinking about moving to the cloud? There’s more than one way to get there. Each migration approach has its own pros, cons, and ideal use cases. In this post, we’ll break down six major cloud migration strategies that organizations use to transition smoothly and smartly.
🧱 1. Lift and Shift (Rehost)
Move it as-is. This strategy involves migrating your existing apps to the cloud without any code changes.
- ✅ Fastest method
- ✅ No code changes
- ❌ Doesn’t leverage cloud-native benefits
- Best for: Legacy apps or fast migrations
🛠️ 2. Replatform
Tweak a little. Make minor changes to use managed cloud services (like migrating from on-prem SQL Server to Azure SQL Database).
- ✅ Better performance
- ✅ Less maintenance
- ❌ Still not fully cloud-native
- Best for: Apps needing light optimization
🔁 3. Refactor (Re-architect)
Redesign for the cloud. This involves reworking app architecture to use microservices, containers, or serverless technologies.
- ✅ Maximum scalability and cloud benefits
- ✅ Future-proof architecture
- ❌ Higher cost and complexity
- Best for: Strategic modernization of core systems
🛍️ 4. Repurchase
Buy new (SaaS). Replace your existing app with a SaaS solution, like moving to Salesforce or Microsoft 365.
- ✅ Low maintenance
- ✅ Fastest implementation
- ❌ Limited customizability
- Best for: Standard tools like CRM, HR, or Email
🗑️ 5. Retire
Let it go. Identify and decommission apps that are no longer used or necessary.
- ✅ Saves cost
- ✅ Reduces system clutter
- ❌ Risk of dependencies
- Best for: Obsolete or duplicate applications
⏳ 6. Retain
Keep it on-prem for now. Retain certain applications that are not ready for the cloud due to business or technical constraints.
- ✅ Safe for sensitive workloads
- ❌ Misses out on cloud benefits
- Best for: Apps with regulatory or latency concerns
📊 Quick Comparison Table
| Strategy | Code Change | Speed | Cloud Benefits | Best For |
|---|---|---|---|---|
| Lift & Shift | ❌ None | 🟢 Fast | 🔴 Low | Legacy/Quick Wins |
| Replatform | ⚠️ Minor | 🟡 Medium | 🟡 Partial | Light Optimization |
| Refactor | ✅ High | 🔴 Slow | 🟢 Full | Strategic Modernization |
| Repurchase | ❌ None | 🟢 Fast | 🟢 Full (SaaS) | Commodity Tools |
| Retire | ❌ N/A | 🟢 Fast | 🔴 N/A | Unused Systems |
| Retain | ❌ N/A | N/A | 🔴 None | Critical On-Prem Apps |
Containers vs. Virtual Machines: What’s the Difference?
Understanding Containers and VMs
Containers: Lightweight & Agile
Containers provide application-level isolation, using the host operating system’s kernel. They are fast, scalable, and resource-efficient, ideal for microservices and cloud deployments.
Virtual Machines: Full OS Environments
VMs, on the other hand, provide full isolation by running a complete operating system inside a virtualized environment. They are great for strong security boundaries and running multiple OS types on the same hardware.
Comparison Table: Containers vs. Virtual Machines
| Feature | Virtual Machine (VM) | Container |
|---|---|---|
| Isolation | Provides strong isolation with its own OS kernel. | Lightweight isolation, shares host OS kernel. |
| Operating System | Runs a full OS, including the kernel. | Runs only user-mode OS components. |
| Resource Usage | Needs more CPU, memory, storage. | Uses fewer system resources. |
| Guest Compatibility | Can run any OS (Linux, Windows, etc.). | Runs same OS version as the host. |
| Deployment | Managed via Hyper-V, VMware, VirtualBox. | Uses Docker, Kubernetes for deployment. |
| Updates & Upgrades | Requires full OS upgrades & manual updates. | Easily updated via image rebuild process. |
| Storage & Networking | Uses virtual hard disks (VHDs), private networks. | Uses shared storage, network isolation. |
| Fault Tolerance | VM failover restarts the OS on a new server. | Containers are recreated instantly by an orchestrator. |
| Load Balancing | Moves VMs to balance workloads. | Orchestrators scale containers dynamically. |
Which One Should You Use?
Both containers and VMs complement each other. Containers are best for modern, cloud-native applications, while VMs provide stronger security and OS flexibility. In fact, many container deployments run on VMs for enhanced scalability!
Which solution fits your workload best? Containers, VMs, or both? Let’s discuss in the comments! 🚀
🚧 Troubleshooting Azure Storage Table Entity Insert Error: Network Rule Blocking Requests
When working with Azure Storage Accounts configured in a private network, you may occasionally face connectivity issues, especially during programmatic operations like inserting entities into a Table Storage. Recently, while inserting a new entity, we encountered the following error:
ERROR:
The request may be blocked by network rules of storage account.
Please check network rule set using
'az storage account show -n accountname --query networkRuleSet'.
If you want to change the default action to apply when no rule matches,
please use 'az storage account update'.
This error clearly indicates that the network rules on the storage account are blocking the request. Here’s how we debugged and resolved the issue.
🧪 Problem Context
Our setup involves:
- A private endpoint-enabled Azure Storage Account.
- IP whitelisting done dynamically during the pipeline using GitHub Actions.
- The following command used to allow the runner’s IP address:
az storage account network-rule add \
--resource-group ${{ vars.RESOURCEGROUP_NAME }} \
--account-name ${{ vars.STORAGEACCOUNT_NAME }} \
--action Allow \
--ip-address ${{ steps.ip.outputs.ipv4 }} \
-o none --only-show-errors
Despite successfully executing this command, any immediate operation (like inserting into Table Storage) would fail with the aforementioned error.
🔍 Root Cause
Azure’s network rule updates—such as IP whitelisting—are not instantaneous. Even though the az command returns success, the rules can take 5 to 30 seconds to fully propagate across Azure’s networking stack.
This propagation delay means that your request may still be blocked right after whitelisting, resulting in transient errors.
✅ Resolution
To work around this, we added a short delay after the IP whitelist command before initiating any storage operations. Here’s a sample shell script update:
echo "Whitelisting IP: ${{ steps.ip.outputs.ipv4 }}"
az storage account network-rule add \
--resource-group ${{ vars.RESOURCEGROUP_NAME }} \
--account-name ${{ vars.STORAGEACCOUNT_NAME }} \
--action Allow \
--ip-address ${{ steps.ip.outputs.ipv4 }} \
-o none --only-show-errors
echo "Waiting for network rule to propagate..."
sleep 30 # Adjust between 5-30 seconds based on testing
# Now perform the table insert operation
💡 Pro Tips
- Use retries: If you’re automating this via scripts or CI/CD pipelines, consider implementing a retry mechanism instead of a fixed sleep.
- Log current rules: Use the following command to verify if the IP is indeed whitelisted:
az storage account show -n <account-name> --query networkRuleSet.ipRules - Audit Logs: Check Azure Activity Logs for insights into rule application times.
🧾 Conclusion
When dealing with Azure Storage Accounts in a private network, remember that network rule changes aren’t immediate. Always plan for a short delay or retry logic to handle propagation time. This small adjustment can save hours of confusion and debugging.
5 Famous Laws That Offer Life Lessons for Better Living ✨
In a world full of chaos and decision-making, there are a few timeless laws—some humorous, some philosophical—that offer surprising clarity and guidance. These famous principles, though not necessarily written in a constitution or passed in court, have earned a respected place in both professional and personal spaces. Let’s dive into five such “laws” that continue to shape how we think, act, and succeed. 🚀
1. Murphy’s Law 😬
“Anything that can go wrong, will go wrong.”
This famously pessimistic law serves as a humble reminder that life doesn’t always go as planned. While it may sound discouraging, Murphy’s Law teaches us the importance of being prepared. 🧯
2. Kidlin’s Law ✍️
“If you write the problem down clearly, then the matter is half solved.”
Clarity is power. 💡 Often, we’re overwhelmed not by the problem itself, but by its vague nature. By defining and articulating the issue, Kidlin’s Law reminds us that solutions start to unfold naturally. 🧠
3. Gilbert’s Law 🛠️
“When you take on a task, finding the best way to achieve the desired result is always your responsibility.”
This law emphasizes ownership and mindful execution. 🎯 It’s about doing things with focus and integrity, pursuing results without burnout. 🕊️
4. Wilson’s Law 📚
“If you prioritize knowledge and intelligence, money will continue to come.”
Invest in your mind, and the rewards will follow. 💸 Wilson’s Law reminds us that wisdom and growth pave the most sustainable paths to success. 🌱
5. Falkland’s Law 🤔
“If you don’t have to make a decision about something, then don’t decide.”
This principle teaches that not every decision is necessary. 🧘♂️ Avoiding mental clutter can lead to better focus and less stress. 🧭
Final Thoughts 💭
These five laws are more than catchy quotes—they are guiding lights in uncertain times. 🌟 Whether you’re managing a business, building your career, or navigating personal challenges, remembering these principles can give you clarity, resilience, and peace of mind. 🧘♀️
Which of these laws speaks to you the most? Have one of your own? Share it in the comments! 💬👇
.NET Framework vs .NET Core: Key Differences
.NET Framework and .NET Core differ significantly in architecture, deployment, performance, and their support for modern development needs. Below is a detailed comparison covering both high-level and low-level aspects.
Key Differences
| Feature | .NET Framework | .NET Core |
|---|---|---|
| Platform Support | Windows only | Cross-platform (Windows, Linux, macOS) |
| Performance | Moderate due to legacy architecture | Optimized for high performance with Just-In-Time (JIT) and Ahead-Of-Time (AOT) compilation improvements |
| Deployment | Requires installation of .NET Framework on the system | Can be deployed as a self-contained application without requiring .NET installation |
| Microservices Support | Limited support due to monolithic architecture | Designed for microservices with built-in support for containerization (Docker, Kubernetes) |
| Future Development | No longer actively developed (last version .NET Framework 4.8) | Actively maintained, evolved into .NET 8+ |
| Runtime | CLR (Common Language Runtime) with Just-In-Time (JIT) compilation | CoreCLR with improved JIT and support for Ahead-Of-Time (AOT) compilation |
| APIs & Libraries | Includes older Windows-specific APIs (e.g., WCF, Web Forms, Windows Workflow Foundation) | Uses .NET Standard libraries and modern APIs with broader compatibility |
| Development Model | Traditional Windows development with limited DevOps support | Supports modern DevOps practices, CI/CD pipelines, and cloud-native applications |
Low-Level Differences
- Garbage Collection: .NET Core has an improved garbage collection mechanism, including low-latency GC modes suitable for high-performance applications.
- Memory Management: .NET Core optimizes memory usage with Span and ValueTask to reduce allocations and improve efficiency.
- Networking: .NET Core provides an enhanced networking stack with HTTP/2 support, asynchronous programming improvements, and lower latency.
- Security Model: .NET Core follows a more modular security model with built-in support for modern authentication protocols (OAuth, OpenID Connect).
- Threading and Concurrency: .NET Core enhances parallel processing with features like System.Threading.Channels and Task-based asynchronous patterns.
The choice between .NET Framework and .NET Core depends on your needs. If you’re maintaining legacy applications that rely on Windows-specific features, .NET Framework is suitable. However, for new, scalable, high-performance applications, .NET Core (or .NET 8+) is the best choice.
Unveiling the Secrets of Azure WAF & App Gateway Logs with KQL
When running applications on Azure, ensuring security and performance is paramount. Azure Web Application Firewall (WAF) and Application Gateway generate extensive logs that help diagnose security threats, server failures, and performance bottlenecks. But how do you extract meaningful insights from these logs? The answer lies in Kusto Query Language (KQL).
In this blog post, I’ll guide you through some powerful KQL queries to analyze WAF logs and detect failures in Azure Application Gateway. Whether you’re a security analyst or a DevOps engineer, these queries will help you troubleshoot issues like a pro!
🔥 Detecting Blocked Requests by WAF
Azure WAF is designed to protect your applications from malicious requests. But how do you check if legitimate users are getting blocked?
AzureDiagnostics
| where ResourceType == "APPLICATIONGATEWAYS"
| where Category == "ApplicationGatewayFirewallLog"
| where action_s == "Block"
| project TimeGenerated, clientIp_s, requestUri_s, ruleName_s, details_data_s
| order by TimeGenerated desc
🛠️ How This Helps:
Identifies requests that were blocked by WAF.
Helps fine-tune WAF rules to reduce false positives.
Tracks client IPs and URLs being flagged as threats.
🚨 Identifying Application Gateway Failures
Application Gateway failures can be catastrophic for your users. If your app is throwing HTTP 500 errors, you need to know why.
AzureDiagnostics
| where ResourceType == "APPLICATIONGATEWAYS"
| where Category == "ApplicationGatewayAccessLog"
| where httpStatus_d >= 500
| project TimeGenerated, requestUri_s, httpStatus_d, backendPoolName_s,backendSettingName_s, host_s
| order by TimeGenerated desc
🛠️ Why This Query is Important:
Helps identify server-side failures.
Detects backend servers that may be down.
Quickly find affected URLs and services.
⚡ Uncovering High Latency Requests
Nobody likes a slow website. If users experience delays, they might leave your site frustrated. This query helps find slow API responses.
AzureDiagnostics
| where ResourceType == "APPLICATIONGATEWAYS"
| where Category == "ApplicationGatewayPerformanceLog"
| where timeTaken_d > 3000 // Requests taking more than 3 seconds
| project TimeGenerated, requestUri_s, timeTaken_d, clientIp_s, host_s
| order by timeTaken_d desc
🛠️ What You Gain:
Detects slow requests causing performance issues.
Identifies whether the delay is from the backend or frontend.
Helps optimize server response times.
🕵️ Tracking WAF Logs for a Specific Client IP
Want to investigate if a particular user or bot is getting blocked? This query is your best friend!
AzureDiagnostics
| where ResourceType == "APPLICATIONGATEWAYS"
| where Category == "ApplicationGatewayFirewallLog"
| where clientIp_s == "X.X.X.X" // Replace with actual client IP
| order by TimeGenerated desc
🛠️ Why Use This:
Track a specific user experiencing access issues.
Identify potential attackers trying to breach security.
Debug WAF rule misconfigurations.
💀 Detecting Backend Failures in App Gateway
Application Gateway connects to backend servers. If the backend is failing, requests will not be processed correctly.
AzureDiagnostics
| where ResourceType == "APPLICATIONGATEWAYS"
| where Category == "ApplicationGatewayAccessLog"
| where httpStatus_d <> "200"
| where requestUri_s = "/status-0123456789abcdef"
| project TimeGenerated, requestUri_s, httpStatus_d, backendPoolName_s, backendSettingName_s, host_s
| order by TimeGenerated desc
🛠️ Key Insights:
Detects backend servers going offline.
Helps analyze downtime patterns.
Prevents cascading failures in multi-server deployments.
Final Thoughts
Mastering KQL can transform the way you troubleshoot and secure your Azure infrastructure. Whether you’re dealing with WAF security issues, slow applications, or backend failures, these queries will make your life easier.
So, next time your boss asks, “Why is our app slow?” or “Why did a request get blocked?”, you know exactly where to look!
🔎 Have a favorite KQL query for Azure logs? Drop it in the comments below!
Understanding Escape Characters in Excel: How to Handle Special Symbols
When working with Excel, you might encounter situations where special characters such as the asterisk (*) behave unexpectedly. This is because Excel treats certain symbols as wildcards or operators rather than plain text. In this blog, we will explore how to escape characters in Excel to ensure they are interpreted correctly.
Why Do We Need to Escape Characters in Excel?
Excel uses some characters, including *, ?, and ~, as wildcards in functions like SEARCH, MATCH, and FILTER. For example:
*(asterisk) represents any number of characters.?(question mark) represents a single character.~(tilde) is used as an escape character to treat the wildcard characters as literals.
If you need Excel to treat * as a regular character instead of a wildcard, you must escape it properly.
How to Escape * in Excel
1. Using the Tilde (~) for Escape
The tilde (~) is used to escape special characters in Excel formulas. If you need to find or compare a literal asterisk, prefix it with a tilde (~). For example:
=SEARCH("~*", A1)This formula searches for * in cell A1 as a literal character instead of a wildcard.
2. Using Quotation Marks in Formulas
When working with text functions, enclose special characters within double quotes. However, if using functions like SUBSTITUTE, you don’t need escaping:
=SUBSTITUTE(A1, "*", "#")This formula replaces all * characters in A1 with #.
3. Formatting Cells as Text
If you want Excel to treat an asterisk as text rather than a wildcard:
- Select the cells where you will enter data.
- Right-click and choose Format Cells.
- Select Text and click OK.
- Now, when you type
*, Excel will treat it as text.
4. Using Apostrophe (') Before Special Characters
If you need to input * in a cell without triggering wildcard behavior, start the entry with an apostrophe ('). For example:
'*This ensures Excel treats it as plain text.
AWS vs Azure vs GCP
AWS (Amazon Web Services) vs Azure (Microsoft) vs GCP (Google Cloud Platform) – A Quick Comparison of the main services
Storage
| Service type | Description | AWS | Azure | GCP |
| Object storage | For storing any files you regularly use | Simple Storage Service (S3) | Blob Storage | Cloud Storage Buckets |
| Archive storage | Low cost (but slower) storage for rarely used files | S3 Glacier Instant, Glacier Flexible, Glacier Deep Archive tiers | Blob Cool/Cold/Archive tiers | Cloud Storage Nearline, Coldline, Archive tiers |
| File storage | For storing files needing hierarchical organization | Elastic File System (EFS), FSx | Avers vFXT, Files | Filestore |
| Block storage | For storing groups of related files | Elastic Block Storage | Disk Storage | Persistent Disk |
| Hybrid storage | Move files between on-prem & cloud | Storage Gateway | StorSimple, Migrate | Storage Transfer Service |
| Edge/offline storage | Move offline data to the cloud | Snowball | Data Box | Transfer Appliance |
| Backup | Prevent data loss | Backup | Backup | Backup and Disaster Recovery |
Database
| Service type | Description | AWS | Azure | GCP |
| Relational DB management | Standard SQL DB (PostgreSQL, MySQL, SQL Server, etc.) | Relational Database Service (RDS), Aurora | SQL, SQL Database | Cloud SQL, Cloud Spanner |
| NoSQL: Key-value | Redis-like DBs for semi-structured data | DynamoDB | Cosmos DB, Table storage | Cloud BigTable, Firestore |
| NoSQL: Document | MongoDB/CouchDB-like DBs for hierarchical JSON data | DocumentDB | Cosmos DB | Firestore, Firebase Realtime Database |
| NoSQL: Column store | Cassandra/HBase-like DBs for structured hierarchical data | Keyspaces | Cosmos DB | Cloud BigTable |
| NoSQL: Graph | Neo4j-like DBs for connected data | Neptune | N/A | N/A |
| Caching | Redis/Memcached-like memory for calculations | ElastiCache | Cache for Redis, HPC Cache | Memorystore |
| Time Series DB | DB tuned for time series data | Timestream | Time Series Insights | Cloud BigTable |
| Blockchain | Dogecoin, etc. | Managed Blockchain | Blockchain Service, Blockchain Workbench, Confidential Ledger | N/A |
Compute
| Service type | Description | AWS | Azure | GCP |
| Virtual machines | Software-emulated computers | Elastic Compute Cloud (EC2) | Virtual Machines | Compute Engine |
| Spot virtual machines | Cost-effective VMs | EC2 Spot Instances | Spot Virtual Machines | Spot VMs |
| Autoscaling | Adjust resources to match demand | EC2 Auto Scaling | Virtual Machine Scale Sets | Instance Groups |
| Functions as a service (Serverless computing) | Execute code chunks without worrying about infrastructure | Lambda | Functions | Cloud Functions |
| Platform as a service | Manage applications without worrying about infrastructure | Elastic Beanstalk, Red Hat OpenShift on AWS | App Service, Cloud Services, Spring Cloud, Red Hat OpenShift | App Engine |
| Batch scheduling | Run code at specified times | Batch | Batch | Batch, Cloud Scheduler |
| Isolated servers | VM on your own machine, for high security | Dedicated Instances | Dedicated Host | Sole-tenant Nodes, Shielded VMs |
| On-premise/Edge devices | Cloud-services on your own hardware | Outposts, Snow Family | Modular Datacenter, Stack Hub, Stack HCI, Stack Edge | N/A |
| Quantum computing | Determine if cat is alive or dead | Braket | Quantum | N/A |
Analytics
ML & AI
Networking & Content Delivery
| Service type | Description | AWS | Azure | GCP |
| Content delivery network | Serve content to users | CloudFront | Content Delivery Network | Cloud CDN and Media CDN |
| Application Programming Interface (API) management | Build and deploy APIs | API Gateway | API Apps, API Management | Apigee API Management |
| Domain Name System (DNS) | Route end users to applications | Route 53 | DNS | Cloud DNS |
| Load balancing | Distribute work evenly across machines | Elastic Load Balancing (ELB) | Application Gateway, Load Balancer, Traffic Manager | Cloud Load Balancing |
Containers
| Service type | Description | AWS | Azure | GCP |
| Managed containers | Run and deploy containers | Elastic Kubernetes Service, Elastic Container Service | Kubernetes Service, Container Apps | Kubernetes Engine |
| Container registration | Manage container images | Elastic Container Registry | Container Registry | Artifact Registry |
Management & Security, Identity
| Service type | Description | AWS | Azure | GCP |
| Access management | User permissions and authentication | Identity and Access Management (IAM) | Entra ID | Cloud Identity |
| Activity tracking | Track user Activity | CloudTrail | Monitor Activity Log | Access Transparency and Access Approval |
| Security | Protect your data, network and applications | Security Hub | Security | Security Command Center |
| Monitoring | Monitor network traffic and detect anomalies | CloudWatch, Transit Gateway Network Manager | Monitor, Anomaly Detector | Operations, Network Intelligence Center |
| Automation | Preform processes automatically | OpsWorks | Automation | Compute Engine Management |
| Cost optimization | Reduce your cloud spend | Cost Optimization | Cost Management | Recommender |
Techy Chalkboard in bits and pieces 
You must be logged in to post a comment.